๐ท๏ธ
How we mark machine-generated content
On two levels, because the Act asks for two: one for you, one for machines.
What you see
- A permanent bar at the top of the chat: "You are chatting with an AI assistant, not a human colleague."
- The assistant introduces itself in its first reply as well.
- AI-written sections of the tools carry their own label.
What machines see
- Every AI reply carries data-ai-generated="true" in the HTML.
- API responses send an X-AI-Generated: true header and an ai_generated field.
- The very first event of the chat stream is the disclosure itself, in three languages.
For text there is no invisible watermark today that survives copying and reflowing. So we use metadata-based provenance marking โ the Act names this alongside watermarking.
๐งพ
For clients: written statement of compliance
If you order a chatbot or a phone AI from us, the Act makes you the deployer and us the provider. The provider obligations are ours, and we put that in writing.
- A written statement of compliance for your contract, citing Article 50.
- Disclosure built into the system and impossible to switch off.
- Machine-readable marking of generated output, with documented settings.
Request the statement โ