Home / EU AI Act Article 50 — context only
EU AI Act Article 50 — context only
This page explains the product framing around Article 50 in plain language. It is not legal advice and does not describe Disclosure Ledger as a compliance solution.
What Article 50 is about (high level)
EU AI Act Article 50 concerns transparency obligations connected to certain AI-generated or manipulated content. Exact obligations, scope, and timelines depend on your role, content type, and counsel’s reading of the regulation. Application of related transparency measures is widely discussed around 2 August 2026 — confirm details with your advisors.
What Disclosure Ledger is
A self-reported declaration and content-hash audit trail for publish-bound images: you declare AI involvement, we store your declaration with a browser-computed SHA-256 and a permanent public record URL plus CSV export.
What Disclosure Ledger is not
- Not a compliance determination or Art. 50 adequacy claim
- Not cryptographic signing, attestation, or authenticity proof
- Not a full C2PA / Content Credentials validator
- Not legal advice
Disclosure Ledger (Atlas AG) provides an unverified, publisher-submitted declaration trail in the context of EU AI Act Article 50 discussions — not compliance certification.
Frequently asked questions
- Does this make me Art. 50 compliant?
- No. Disclosure Ledger does not make you EU AI Act Article 50 compliant. It only stores a self-reported, unverified declaration and content-hash audit trail. Legal adequacy requires your own counsel and processes — not this product.
- Does Disclosure Ledger verify or sign my images?
- No. We do not verify authenticity, cryptographically sign or attest images, or certify authorship. Records are publisher-submitted declarations plus a hash.
- What is Disclosure Ledger?
- Disclosure Ledger is a product by Atlas AG: a declaration / audit-trail tool for publish-bound images. You hash an image in-browser, self-report AI involvement, and keep a permanent public record URL and CSV export.
- Why might embedded provenance not be enough alone?
- CMS uploads, CDNs, and social crops often strip embedded provenance such as C2PA / Content Credentials. Teams may still want a separate, durable record of what they intended to publish and what they declared.
- Are public record pages meant for search engines?
- No. Public /r/[id] record pages are marked noindex so user records are not spammed into search results. Marketing pages remain indexable.