Labelling without manual work
The required label, the JSON-LD manifest and the QR code are set on save. Whoever writes the article does not need to know anything about Article 50.
Coming soon
AI content labelling under Article 50 of the EU AI Act.
Labels, JSON-LD and QR codes that survive an audit: AI Act Content Signer detects AI-generated content on save, labels it under Article 50 of the EU AI Act and signs it with Ed25519 – for editorial teams, agencies and shops on WordPress, TYPO3, Shopware and Shopify, with no manual label workflow.
- Label, JSON-LD and QR code land in your frontend automatically
- Every label can be verified through an open endpoint
- Detection returns a risk score – the decision stays with a human
Launching on 1 December 2026
Launching on 1 December 2026.
We are live – get started.
Integrates with
- WordPress
- TYPO3
- Shopware 6
- Shopify
- REST API
- SDKs: Python · JS · Go · PHP
What changes for you
Three things that cost manual work, guesswork or billable lawyer hours today.
Evidence that stays verifiable
Signature and audit entry can be checked at any time – by third parties too, without access to your system. A screenshot is not evidence. A signature is.
Stays in your infrastructure
SaaS in the EU or your own server via Docker Compose – air-gapped if you need it. Your content stays where you want it.
Three steps from draft to proof
No new editorial process – one more checkbox and a signature that holds.
-
Detect
Content is scored on save – with a calibrated risk score (AUC ≈ 0.90 on our reference corpus) and a risk band instead of false certainty.
-
Label
Article 50 label, JSON-LD manifest and QR code go straight into the frontend – visible to readers, machine-readable for reviewers.
-
Sign
Ed25519 signature with monthly derived keys, plus a SHA-256 hash chain in the audit log. Later edits do not go unnoticed.
- Content
- #4821 · Battery cell recall
- Detection
- High risk score 0.72
- Label
- visible · JSON-LD · QR
- Signature
- Ed25519 · 12 Aug 2026 14:03
- Fingerprint
- sha256:9f2c…d41a
- Status
- verified
Durable, not just claimed
What holds is built to be verifiable – and what does not hold is not promised.
Ed25519 per RFC 8032
Signatures with monthly derived keys; the matching public key is available openly.
SHA-256 hash chain
Every audit entry chains the previous hash. A later edit breaks the chain.
Detection without exaggeration
The model returns a review signal, not a verdict. The durable layer is the signature – detection helps you prioritise.
Cookieless reach measurement
Measurement runs on Umami – self-hosted in the EU, no cookies, nothing written to your browser, no ad tracking and no profiling. Details in the privacy policy.
Frequently asked questions about Article 50 and labelling
Short answers to the questions that come up most before launch.
What does Article 50 of the EU AI Act require?
Article 50 requires AI-generated or AI-manipulated content to be identifiable as such: visible to people and, for synthetic content, additionally marked in a machine-readable format. Text, images, audio and video are typically affected. The AI Act Content Signer sets both layers automatically: a visible label in the frontend and a machine-readable mark in the source.
Which systems does the AI Act Content Signer support?
It is available for WordPress, TYPO3, Shopware 6 and Shopify, and can be connected to any custom application via a REST API and SDKs for Python, JavaScript, Go and PHP.
Where is my content processed?
Your choice: SaaS in an EU data centre or your own server via Docker Compose, air-gapped if you need it. Self-hosted, your content never leaves your network; in SaaS mode the text being checked is sent to our API. Before launch we will extend the privacy policy to cover these processing operations.
How reliable is the detection of AI-generated content?
The model returns a review signal, not a verdict: a calibrated risk score (measured: AUC ≈ 0.90 on our reference corpus; at the review threshold it flags roughly 13% of human-written text) and a risk band. The decision stays with a human – the durable layer is the signature.
How can a label be verified?
Every label can be checked through an open endpoint: the Ed25519 signature, the manifest and the matching audit entry. Third parties need no access to your system. A screenshot is not evidence. A signature is.
When does it launch and how do I get notified?
Launch is on 1 December 2026. Use the form on this page or write to contact@aiactcontentsigner.de and we will send you a single notification; the address is deleted afterwards.
This overview is not legal advice.
Launching on 1 December 2026
Get a single notification when the Signer becomes available.