Trust
How we keep the registry true
We sell records about the law. The obvious question is who checks the law, how, and how you would know if we got it wrong. This is the written answer, with the dates.
- jurisdictions in the registry
- 169jurisdictions in the registry
- entries carrying a verification date
- 168entries carrying a verification date
- most recent verification
- 2026-08-27most recent verification
- oldest verification on file
- 2026-08-22oldest verification on file
What an entry is written from
- The instrument itself
- The published text of the regulation, directive, statute or rule — the Official Journal of the European Union for EU instruments, the state legislature or Secretary of State for US state law, the relevant national gazette elsewhere. An entry is written from the instrument, not from an article about it.
- The regulator’s own guidance
- Where a supervisory authority has published guidance, an FAQ or an enforcement priority — a Data Protection Authority, the FTC, a state Attorney General — that guidance is recorded next to the obligation it interprets, and named as guidance rather than as law.
- Enforcement record
- Decisions, fines and consent orders that show how an obligation is actually enforced, so the penalty figures on an entry are what has been imposed, not only what the statute permits.
- Commencement and transition dates
- In-force dates, phased application dates and transition periods taken from the instrument’s own commencement provisions — the part most secondary sources get wrong.
How it is built and kept
- 1
Scope before text
Each entry starts with who the instrument applies to — the thresholds, the territorial reach, the sector carve-outs — because an obligation that does not apply to you is noise. The applicability engine works off this, which is why the registry can answer "which of these are mine" rather than handing over all 169.
- 2
Obligation by obligation
Requirements are recorded as separate obligations with their own citations, not as a paragraph of summary. That is what lets a report point at the specific article behind a control.
- 3
Dated verification
Every entry carries the date it was last checked against its sources. The date is on the entry itself, on this page, and in the reports generated from it. An undated claim about a law is worth nothing a year later.
- 4
Change, then re-verify
When an instrument is amended, or a date moves, or an authority publishes guidance that changes an obligation, the affected entry is re-verified against its sources and its date advances. Entries are not silently edited without the date moving with them.
When entries were last verified
Read straight from the registry: every date on which entries were verified, and how many were verified on that date. Nothing in this table is typed by hand — it comes from the registry itself, so it cannot say one thing while the entries say another.
| Verified on | Entries | Share of the registry |
|---|---|---|
| 2026-08-27 | 3 | 2% |
| 2026-08-26 | 14 | 8% |
| 2026-08-25 | 24 | 14% |
| 2026-08-23 | 6 | 4% |
| 2026-08-22 | 121 | 72% |
What this is not
A registry entry records what we verified and the date we verified it. It is not a legal opinion that an instrument applies to your business, and we are not a law firm. Law changes between verification dates — that is why the dates are on the entries and on this page rather than buried. If an obligation drives a decision that matters to you, take the citation on the entry to your counsel and have them read the instrument.
Found something wrong? Tell us and we will fix it and move the date. Send us the entry and the source. We reply within 4 working days.