Map Article 50 to role, evidence, and a falsifier, the condition that would disprove it.
This guided self-assessment orients you to transparency duties for a role in an AI system. It is not an applicability verdict: legal applicability stays unknown until a lawyer assesses the specific case.
◌ Static and registration-free: your answer lives only in this browser and does not leave it.
Legal applicability
unknown - a lawyer must assess the specific system and context
Choose your working role
Choose your working role
Choose the closest role for orientation. The choice is not stored or sent anywhere.
Showing orientation for role
Provider
Legal applicability: unknown - a lawyer must assess the specific system and context
Article 50(1)
Disclosure of AI interaction
People should know they are directly interacting with an AI system unless this is obvious from the circumstances.
Key dates (act and guidance addresses)
02.08.2026
02.12.2026
02.02.2027
Notice before the first bot answer
Evidence and boundary: A dated screenshot or recording shows the notice in every channel: web, mobile, and voice.
Falsifier: Open the channel as a new user without cookies: if no notice appears before the first bot answer, the item fails.
Notice survives redesign
Evidence and boundary: The release checklist and latest release record contain a separate check for this notice.
Falsifier: Find the latest deployment without that check: one record shows the process does not hold the requirement.
Article 50(2)
Machine-readable marking of synthetic content
AI-generated audio, images, video, and text need machine-readable marking within the applicable boundaries.
Key dates (act and guidance addresses)
02.08.2026
02.12.2026
02.02.2027
Signed metadata
Evidence and boundary: An independent reader such as c2patool or a C2PA Viewer provides dated output for a concrete file.
Falsifier: Re-save the file in a common editor and test again: a disappearing manifest is a named limitation, not hidden success.
Robust watermark where applicable
Evidence and boundary: A dated provider-detector output is kept for a control sample.
Falsifier: Test after a screenshot or transcode: if detection disappears, record that boundary explicitly.
Generator and role register
Evidence and boundary: A dated inventory names each system owner and its provider/deployer role.
Falsifier: An API generator call in billing or logs absent from the inventory falsifies its completeness.
Responsibility boundaries
Responsibility boundaries
This is not legal advice.
This tool does not create an attorney-client relationship.
We are not affiliated with the European Union or the European Commission.
The tool does not resolve legal interpretation for a specific case or an industry conformity assessment. That is a lawyer's work; legal applicability remains unknown.