Skip to content

Accountability record

How Trusq publishes, checks and corrects

Automated systems do most of the work behind Trusq: monitoring the primary EU sources, drafting, publishing and re-checking. This page records how that work is checked and corrected, with live figures, including what has not been verified yet.

23 815automated source checks
100changes detected
53published
16not yet editorially verified

Live counts from the same database that serves the updates feed. Publishing since 26 Jun 2026. Most recent entry 6 Nov 2026. Of everything detected, 92 arrived through automated monitoring rather than a person adding it, and 37 published entries have since been editorially verified against their primary source.

Publish first, verify in the open

A change detected in an official EU source is published immediately, labelled not yet editorially verified, with a link to its primary source. Trusq editorial then checks it against the official text and corrects or withdraws it where needed. The number of entries not yet verified is shown above. The method is described on how Trusq stays current.

Hourly actuality control

Every hour, Trusq re-checks its published claims against the official sources and raises an operational alarm when a claim no longer matches. See the latest source-check timestamp and route-level evidence on What Trusq monitors, and the current service state on the status page.

What we got wrong, and fixed in public

Because changes are published before the editorial check, an error can be public until that check corrects it. Every correction is listed here, and the original URL stays the same. 4 published entries have been corrected after publication.

EntryWhat was wrong
Commission fines AliExpress €550 million for breaching the Digital Services ActFiled under the wrong framework and described as enforcement against a member state. AliExpress is a platform, and the action falls under the DSA, not the AI Act.
Commission publishes Code of Practice on marking and labelling AI-generated…Mapped to the GPAI articles (53/55). It actually supports the Article 50(2)/(4) transparency duties.
Digital Omnibus — high-risk deferralStatus was stale: still recorded as pending after the act had been published in the Official Journal on 24 July 2026 and entered into force.
Judgment of the Court (Third Chamber) of 5 November 2026. — Joachim Lindenberg…The automatic action pointed to AI systems. The ruling interprets the GDPR right of access (Articles 4(7), 15 and 23) in a supervisory authority's complaint file; it is not about AI.

Rule releases and customer data

The rules that customer workspaces are checked against change only through an explicit release step, and every release is recorded in an audit trail with the time and the actor. Customer content is processed only by an EU AI provider; no customer data reaches a US model. The boundaries are on our trust & data page.
← Back to Trusq