What changed, what it touches, what you could do.
Rule changes from official sources, matched to your systems and turned into suggested engineering preparation.
How it works
What changed?
New laws, regulations, guidance, enforcement and serious proposals on AI, privacy and data, read from the official source and dated.
What does it touch?
On a paid plan, each development is matched to your own data flows by location, data type and activity, with the reason shown.
What could you do?
Suggested preparation for engineering teams: options to consider, never definitive legal advice.
One generic brief, every Monday
The free brief gathers the week’s most significant cleared developments across Canada, the US and the EU, ten at most. Verified Developments come first, then the rest by Urgency and Momentum. Same edition for every reader, in English or French. The examples on this page use made-up content.
Two scales, kept apart
Every item carries one label and two five-step scales. Momentum is how likely a development is to be adopted. Urgency is whether to prepare, and how soon. A likely rule can be low urgency, and an early proposal can be worth preparing for, so the two are never merged into one score, and there are no percentages.
Four labels
- Verified Development
- Confirmed in an official source, with the passage checked word for word.
- Interpretation
- What a development may mean. Never presented as fact.
- Sentiment Signal
- Political, industry or press reaction. Context, not fact.
- Suggested Preparation
- An option to consider. Never legal advice.
Matched to your own data flows
On a paid plan, your team maps where data goes: places, data types and activities. Each development is matched to those flows, and every match says why. A location alone never makes a match.
Preparation your team can act on
Each finding says what changed, why it matters to you and what you could consider doing. Your team turns a suggestion into an action and works on it, and an Admin marks it handled. Paid plans only.
Your support-chatbot flow sends refund decisions through an AI model.
Consider logging each automated refund decision with its inputs, and keeping the log for two years.
Checked before it reaches you
s. 12 Records. An operator that uses an automated system to make a decision about an individual shall keep a record of that decision for two years. s. 13 Notice. The operator shall tell the individual, in plain language, that an automated system was used. s. 14 Review. On request, the operator shall have a person review the decision.
Operators must keep a record of each automated decision for two years.
“shall keep a record of that decision for two years”
Operators must register each automated system with the regulator.
“shall register each automated system”
- Only official sources (legislatures, regulators, courts, gazettes) can produce a Verified Development.
- Every quote is checked word for word against the page we captured. A claim whose quote isn’t found is dropped.
- Automated checks screen every item, and a person reviews anything our checks flag. Nothing flagged is published until it is approved.
- Viminate is regulatory intelligence, not legal advice.
Where we look
Federal sources in Canada and the United States, and the institutions of the European Union, plus a few news and commentary sources for reaction. Provinces, states and member states come next.
OPC · Canada Gazette · LEGISinfo · ISED · Federal Register · FTC · NIST · White House · EDPB · EDPS · European Commission · EU Publications Office
Start with the free brief
Every plan follows the same laws and sources. Plans differ in personalization, cadence and depth.
| Feature | Free$0Get the free brief | Personalized IntelligenceUS$299 / monthopens soon | Infrastructure IntelligenceUS$999 / monthopens soon |
|---|---|---|---|
| Weekly brief | Generic, by email | Personalized: web edition and email | Personalized: web edition, email and division editions |
| Your company’s data | Not included | Data flows by country, state or province | Plus a graph of providers, services and regions |
| Regulatory scan | Weekly | Weekly | Daily, with same-day alerts |
| Matching | Not included | Location, data types, activities and flags | Plus each node and provider commitments |
| Collaboration and actions | Not included | Included | Included |
| Personalization sentences | Not included | Included | Included |
| PDF and Markdown export | Not included | Included | Included |
| Provider policy-change alerts | Not included | Not included | Included |
| Divisions and division admins | Not included | Not included | Included |
| Graph edit approvals | Not included | Not included | Included |
| SSO (SAML/OIDC) and SCIM | Not included | Not included | Included |
| API, MCP server, review skill, CLI | Not included | Not included | Included |
| Codebase crawler and PR review | Not included | Add-on, priced separately | Add-on, priced separately |
Paid plans include the creator’s seat. Extra seats are US$30 per person per month for Admin or Infrastructure, and US$20 for Reader.
Paid plans open soon.