How Reglog checks what it publishes

Short version: every legal claim on Reglog is checked against the official text of the EU AI Act before it is published, and anything we cannot confirm is removed or labelled as uncertain. Research and drafting are done with the help of AI tools; an editor decides what is published. Nothing on Reglog is reviewed by a lawyer, and none of it is legal advice.

The sources we check against

A claim counts as verified only when it matches a primary source. In order of authority:

• The legal text itself. Regulation (EU) 2024/1689 as published in the Official Journal, the consolidated version that includes the Digital Omnibus (Regulation (EU) 2026/1744), and any other implementing or amending act, read from EUR-Lex and the EU Publications Office.
• Official guidance. Commission guidelines, the AI Office and the Commission’s AI Act pages. We cite guidelines by document number and paragraph, and say when they are drafts or non-binding.
• National and standards sources. National gazettes for implementation laws, and the CEN-CENELEC project record for harmonised standards.

News articles, law-firm notes and other trackers are used only to find leads. They are never the basis for a claim on their own.

How a guide is made

1. Research. Each week we look for what changed: new acts in the Official Journal, Commission guidance, standards and national laws.
2. Drafting. Guides are drafted with AI assistance from that research and from the legal text.
3. Checking. Every quotation, article, paragraph and Annex reference, date and amount is compared with the primary text in separate checking passes whose job is to disprove the draft, not to approve it. A wrong reference is corrected; a claim that cannot be confirmed is removed or marked as unverified; where the text is genuinely ambiguous, the guide says so and sets out the readings rather than picking one.
4. Publication. An editor decides whether the corrected guide is published. Drafts that fail the check stay unpublished.

How a changelog entry is made

Each changelog entry states what changed, who it affects (provider, deployer, importer, distributor), the risk tier, and when it takes effect, and it links to its official source. An entry appears on the site only after it has been checked against that source and marked verified in our editing tool, which records when; the entry shows that date.

Corrections and updates

When we find an error, or the law or its guidance changes, we correct the page and update the date it shows. Where the change matters to a reader, the text says what changed and when, rather than silently rewriting it. To report an error, write to hello@reglog.io with the page and the source that contradicts it.

What “verified” does not mean

• It is not legal advice, and it is not a lawyer’s opinion.
• It does not tell you whether your company complies. The obligation check maps the rules to the answers you give; it does not assess your systems.
• We do not rate or certify any vendor or product as compliant.
• Where an official question is still open, a verified page can only tell you that it is open.

Who runs Reglog

Reglog is a Solvion project. Contact: hello@reglog.io. See also our privacy notice.

This is an information service, not legal advice.