FREE / LOCAL / ARTICLE 50 + C2PA 2.4

Know what your AI must disclose before 2 August.

Turn a real deployment scenario into likely transparency paths, usable disclosure copy and an evidence queue. No questionnaire upload and no invented compliance score.

Decision aid only. Not legal advice, implementation verification or compliance certification.
50(1-5)SIX DECISION PATHS
EN / ES / ZHBROWSER LANGUAGE
C2PA 2.4UNSIGNED AUTHORING VIEW
LOCALASSESSMENT AND EXPORT

SCOPE / TRIGGERS / EVIDENCE

Describe the deployment, not the marketing claim.

Unknown is a valid answer. The checker keeps uncertainty visible instead of silently treating it as compliant or exempt.

01

WHO / WHERE

Scope signals

02

WHAT PEOPLE EXPERIENCE

Article 50 triggers

SYNTHETIC CONTENT TYPES
03

WHAT EXISTS TODAY

Implementation evidence

C2PA 2.4 AUTHORING FIELDSOPTIONAL / DOES NOT SIGN A CREDENTIAL

LOCAL CONTRACT: ANSWERS, NAMES AND MODEL IDENTIFIERS STAY IN THIS TAB. LOCAL EXPORTS INCLUDE THE IDENTIFIERS YOU ENTER.

DECISION AID / NO SCORE

Implementation map

WAITING FOR SCENARIO
50(1-5)

Run the checker to see likely triggers, review points, visible labels and missing implementation evidence.

OFFICIAL SOURCES / EXPLICIT LIMITS

A map for implementation work, not a legal verdict.

The rules are derived from the Commission guidance published 20 July 2026 and Article 50. C2PA output follows the 2.4 field shape but remains unsigned and unbound.

01

Scope before score

The tool preserves unknown facts and possible exceptions as review items. It never converts them into a compliance percentage.

02

Visible is not machine-readable

A deepfake disclosure cannot rely only on embedded metadata. A visible label also does not create a robust machine mark.

03

Draft is not credential

The JSON authoring view is not CBOR, a manifest, a signature, an asset binding, crJSON or independent verification.