Skip to content
Clause50EU AI Act evidence — starting with Article 50.EU AI Act evidence, starting with Article 50

Clause50 is an EU AI Act evidence platform. It classifies an AI system against the whole Act from one intake — prohibited practices under Article 5 are refused, high-risk systems are screened against all eight Annex III areas and documented across the nine sections of the Annex IV technical file, and the four Article 50 transparency duties are evidenced — and it answers every obligation that applies with append-only, Ed25519-signed evidence that anyone can verify without an account. It records evidence against the 2027 high-risk obligations today, so the file exists on the day they bind — or on the day a significant change brings a legacy system into scope. It pre-fills the EU declaration of conformity and refuses to sign it. The same intake also screens the system against the GDPR duties an AI system that processes personal data owes — the data protection impact assessment, Article 22 automated decisions, notices to the people whose data it processes, its Article 30 record entry and transfers — scored separately from the AI Act. It is not the quality management system, conformity assessment, EU database registration or the fundamental rights impact assessment — those stay yours, whichever tool you use.

  • 2 Aug 2026: Article 50 in force. Transparency duties apply to chatbots, synthetic content and deep fakes.
  • 2 Dec 2026: Two new bans; marking grace ends. Two new Article 5 bans apply, and older generative systems must mark their output. 34 days to go.
  • 2 Dec 2027: High-risk obligations bind. Evidence you do not have yet cannot be back-dated. 399 days to go.
EU AI Act evidence for agencies · starting with Article 50

Prove every client’s Article 50 position — one signed pack per system.

Every client’s chatbots and AI-generated content, their evidence and their gaps, in one workspace — and a signed pack anyone can verify. When a client’s system turns out to be high-risk, the same intake records its Annex IV technical file for 2 December 2027. Where it processes personal data, the same intake screens its GDPR duties too — already in force.

Classifying needs a free account — no card, ever · The Article 50 check needs none · A plan decides only whether the signed document leaves

An example client roll-up: four clients, three on Article 50 and one high-risk, each with its evidence status and its signed documents.

Every covered requirement points to evidence you can open.
5Obligations in force under Article 50, modelled
25High-risk obligations recordable now for 2 December 2027
9Annex IV sections, each bound to a cited requirement
0AI model calls when a signed document is generated — asserted by a test
The agency problem

You ship AI on dozens of client sites. Each one is a separate Article 50 question — and you are the one asked to answer it.

Every client is a separate audit

A regulator's complaint or a client's enterprise buyer can ask for proof that a chatbot says it is AI and that generated images are marked. Screenshots in a shared folder do not survive that question.

Proof goes stale every release

Redesign a site, swap a model, change a prompt — and last month's evidence no longer describes what is live. Keeping it current by hand, across a whole client book, does not scale.

The questionnaire line

The vendor questionnaire now has an "EU AI Act evidence?" line. Answering it credibly, per client, on demand, is either a billable headache or a lost deal.

How Clause50 works

Add. Prove. Watch. Export.

AI systemyou describe it
Risk classderived, you confirm
Applicable obligationsin force / from 2027
Evidenceappend-only
Signed evidence packEd25519-signed
Public verificationat /verify, no account

Add a client system

Record the system and answer the intake. The risk class is derived from your answers and confirmed by you.

Connect or upload

Upload documents, connect read-only sources, or attest against a checklist. Every item enters an append-only, hash-chained store.

Watch coverage

See what is evidenced and what is missing, per client. When evidence ages, you record a change, or the rule pack is updated, the system is re-scored and anything newly stale or missing is flagged.

Export the signed pack

The Article 50 evidence pack — or the Annex IV technical file — Ed25519-signed and verifiable without an account.

Clause50 documents; it does not sit in your live traffic. Nothing to install on client sites, and nothing of ours in the critical path.

The method in full — and the role of AI →
Does it apply to your client?

Article 50 is the front door. The same intake screens the rest.

One intake · 32 obligations per system — 6 in force today, 26 recorded now for 2 December 2026 and 2 December 2027 · rule pack 2026.35

In force now

Chatbots and assistants

Art. 50(1) — people must be told they are talking to AI.

In force now

AI-generated content

Art. 50(2)/(4) — synthetic content marked and disclosed. Systems on the market before 2 Aug 2026 have until 2 Dec 2026 to mark.

In force now

Emotion and biometric systems

Art. 50(3) — the people exposed must be informed.

Refused, not upsold

Prohibited practices

screened · refused

Art. 5 — no evidence pack at any plan level; the classification memo is still yours.

See the refusal boundary →
From 2 December 2027

When a client’s system is high-risk

25 recorded now

Annex III — screened from the same answers. Nine Annex IV sections, recordable now.

See what high-risk requires →

Also from the same record, scored separately: 17 GDPR duties for AI systems that process personal data, all in force today, with 5 documents built from them. GDPR for AI systems →

Why the evidence holds

Everyone can sign an event. Clause50 signs a case.

How the evidence was made — and who accepted it
  1. Structured factsThe system, recorded as answers to a fixed intake. Every change is a new version.
  2. Regulatory assessmentA versioned rule pack, cited to the article, decides what applies — from those answers.
  3. Supporting evidenceEach requirement bound to the documents, records and events it rests on, by content hash.
  4. Human attestationYou confirm the risk class and attest what the evidence shows. The record names who, and when.
That nothing was edited since
  1. Signed recordAn Ed25519-signed manifest that names the rule pack version it was assessed against.
  2. Versioned historyAppend-only and hash-chained. A correction is a new entry; the original stays.

A signature proves a file was not edited afterwards. It does not show how the file was made, or who accepted it. Clause50 keeps the whole chain, and the signed record names its links: the rule pack version, the evidence by hash, and who confirmed and attested.

Append-only, by constructionNo update, no delete — enforced in CI, migrations included. Every item is hash-chained to the one before it.
Signed and independently verifiableEvery finalised artifact carries an Ed25519-signed manifest. Anyone you send it to can verify it at /verify against our published key — without an account.
Per-requirement traceabilityEvery requirement in the document names the evidence its status rested on, by content hash — not a summary written after the fact.
EU-region hostingApplication, database, object store and email run in EU regions; the residual is stated on our subprocessor list.

Clause50 assembles evidence toward your obligations. It is not the compliance programme, and no software is.

Product claims on this page are asserted by tests in our codebase; the legal content of the rule pack is not yet reviewed by counsel.

Pricing

Breadth by subscription. Depth per system.

Free to classify and read your coverage. Every plan generates the same signed, verifiable documents. Monthly prices, excl. VAT — 14-day free trial.

Solo

One system, signed and verifiable.

€25/mo
1AI systems—Client organisations1Team members
Start free trial

Starter

Build your evidence record — every system in one organisation.

€49/mo
15AI systems—Client organisations5Team members
Start free trial
For agencies

Boutique

Run evidence for your clients — each a separate, sealed organisation.

€149/mo
30AI systems15Client organisations15Team members
Start free trial

Growth

Run a multi-client evidence operation, under your own branding.

€349/mo
100AI systems30Client organisations30Team members
Start free trial

Included on every plan, including Free and one-time packs: Evidence volume is never metered · Ingestion is never gated by plan · Cryptographically signed, independently verifiable · Per-requirement evidence traceability · Machine-readable marking evidence · Signed audit-log export What each means →

Single-system evidence pack
€149 one-time
One system, 6 months, no subscription.
High-risk technical-file pack
€299 one-time
One high-risk system's Annex IV technical file, for 6 months.
Enterprise
from €799/mo
Evidence at scale, on negotiated terms.
Compare every plan — what each includes, yearly prices, the packs →

Classify a system for free. Take the signed document when you need it.

Anyone may record a system, answer every screening question and read their full coverage. A plan decides one thing: whether the signed document leaves.

Four free ways to see where a client stands.

Article 50 free tools, no sign-in. They show where a site stands; none of them records evidence.