Code-measure mapping
Every claim is itemized, so no claim can exceed its row. This table maps Section 1 of the EU Transparency Code (Art. 50(2)) to what the platform implements and what remains the customer's responsibility.
| Code Section 1 measure (Art. 50(2)) | Oprindo | Customer |
|---|---|---|
| Machine-readable marking — signed metadata | Implemented by platform (C2PA manifest + trusted timestamp; trust state disclosed) — sample asset + c2patool report | Integrate at generation time |
| Machine-readable marking — imperceptible watermark | Adapter interface implemented; robustness benchmarks are internal testing, published report pending. Or customer's own provider. | Select + configure adapter |
| Detection availability | Hosted verify endpoint — live (try it); per-tenant detection in private beta | Link/expose to their users |
| Detection interoperability (Feb 2027 signatory commitment) | Planned — registry-compatible design | Applies if they sign the Code |
| Marking robustness / state of the art | Internal testing — published survivability + robustness report pending; matrix status will change when it ships | Assess adequacy for their system |
| Implementation records | Implemented by platform (evidence log + export) — CSV/PDF samples | Retain; present to authorities |
| Policies, ToS anti-removal clauses, testing, legal assessment | — | Customer responsibility |
What this platform is, in one breath:
Technical controls and implementation evidence mapped to Section 1 of the EU Transparency Code.
Designed to help providers implement and evidence Article 50 marking measures. Compliance depends on the customer's complete implementation and circumstances.
On the Feb 2027 row: detection interoperability is a Code signatory
commitment — a common API method, embedded signpost, or consortium solution — that applies to
signatories, not automatically to all providers. The platform is designed to join that common
solution when it emerges, not to be it.