Reelry AI transparency

Protocol version: 2026-09-15.1. Operator: Health3 AG, Switzerland.

This document describes Reelry's implementation, verification methods and limits. It is not a certification of legal compliance, ownership, factual accuracy or safety. Live enablement and processing counts are published at /api/ai-transparency/status. Those counts cover enrolled exports, not every historical file.

What the labels mean

• AI-generated video: the workflow generates visual content with AI.
• AI-generated and supplied visuals: the output combines generated and supplied visual material.
• AI narration over supplied photos: Reelry adds synthetic narration to supplied pictures.
• Video assembled from supplied photos: this does not assert that the uploaded pictures are real, licensed or human-created.
• AI-assisted video: detailed component provenance is not fully classified, including some legacy workflows.

These disclosures are separate from Reelry branding, customer permission to publish, and any endorsement. Purchasing a clean export removes promotional branding; it does not purchase removal of origin information.

How a final MP4 is prepared

1. Rendering creates a stored source asset. Its workspace permissions continue to apply.
2. A durable preparation job records the exact source. A lease prevents simultaneous workers from completing the same job.
3. When enabled, Adobe TrustMark B/BCH5 embeds the same opaque 61-bit payload into every decoded video frame. This is an established image watermark applied frame by frame, not a claim of an unremovable watermark. The encoder runs the published B model with one CPU inference thread and spinning disabled; the original Content Authenticity SDK independently decodes verification samples. ONNX Runtime telemetry is disabled before initialization.
4. The encoded result is checked on three sampled frames. Encoded audio packets must be unchanged, and the picture comparison must exceed the configured PSNR threshold.
5. The final asset receives an ES256-signed C2PA manifest containing a minimal origin statement and verification instructions. No customer name, email, brief, workspace identifier or private source URL is included in that statement.
6. When timestamping is enabled, DigiCert receives only an RFC3161 cryptographic digest request. Its documented endpoint uses HTTP; the signed response is independently validated against DigiCert's timestamp root. Video, narration text, customer details and signing keys are not sent to that service.
7. Signature, content binding and configured marking checks must pass before the job is recorded as ready. Normal viewing and export then resolve to the verified copy.

Preparation is separate from generation billing. A failed attempt keeps the source render, schedules a bounded retry, and can escalate to operator review. It does not request another paid generation. If delivery enforcement is enabled for an enrolled output, the app shows preparation status instead of claiming an unverified file is ready.

Signing trust and timestamps

Public signing certificates and trust anchors are available at /.well-known/reelry-provenance.json. Signing keys are encrypted in Supabase Vault and available only to the server-owned signing path. Preparation requests require a current, expiring job lease; the service is not a general-purpose signing endpoint.

Reelry-published trust anchors establish trust in Reelry's own statement. They are not an independent identity certificate or a claim of membership in the C2PA Trust List. A DigiCert timestamp attests to time and digest binding; it does not certify Reelry's identity, business, legal compliance or the video’s claims. Signing and timestamp trust are checked separately. When policy permits a timestamp-service fallback, the origin statement remains signed but the result explicitly reports that no independent timestamp was verified. Strict timestamp enforcement can be configured separately.

Verify an export

The browser verifier hashes a selected file locally and sends only the SHA-256 digest to Reelry. An exact match means the bytes match an export that Reelry validated and registered. No match may mean an older, changed, unregistered or unrelated file; it does not mean human origin.

The optional watermark check uploads one sampled frame to Reelry for in-memory detection. The frame is not stored and is not sent to an AI-generation provider. A recognized watermark alone does not establish an unmodified file, ownership, factual accuracy or an authentic signature: watermarks can survive editing or be copied.

The public product-ad sample is available for review alongside its digest and measured results in the evidence file.

For independent inspection, use the reference verifier and public technical protocol. It uses the public Content Authenticity SDK and can inspect files locally. Technical source snapshots and checksums are listed in the source index.

Download and inspect the verifier before running it. In a local directory with Node.js 22 or later, install @contentauth/c2pa-node@0.9.5, save the verifier there, and run: node verify-reelry.mjs /path/to/video.mp4. To avoid even the public-key request, first save the key-discovery JSON and pass --keys=/path/to/keys.json. The reference verifier does not upload media or its digest. It distinguishes validating a signed watermark declaration from actually running a watermark detector.

Structured text results

AI-generated hook and caption tool responses carry a SHA-256 digest and, when signing is enabled, a detached JWS ES256 proof over the exact returned results array. The proof does not contain the actual text. Template fallbacks remain identified as templates. Save the complete JSON response and run the reference verifier on that JSON file to check the signature locally. Copying plain text without its proof does not retain this marking. These proofs have no independent timestamp and are not represented as invisible text watermarks.

AI-assisted editorial articles identify that assistance and Reelry's publication responsibility. Neither that disclosure nor an automated review is a claim of substantive human editorial review.

Coverage and lifecycle

The finished-video queue covers initial renders and subsequent source-video changes, including scene regeneration, audio/text repairs, clean rerenders and edited demos. The same authorized media-delivery boundary is used for public viewing, downloads, bulk exports and platform file sharing. A changed source invalidates an older preparation result. A new asset version receives new provenance.

The source render and marked export remain private unless the customer explicitly shares the reel. Making a reel private removes anonymous access through the media gateway. Existing short-lived viewing capabilities expire independently. Account erasure removes workspace files and related processing records. Downloaded key-discovery files can become stale after a revocation; refresh them before relying on an offline result. Public signing certificates do not contain customer information and remain available for verification of previously distributed files.

Historical media is handled separately. Processing counters are not a representation that all legacy assets are marked. The deployed status endpoint states whether new preparation and delivery enforcement are enabled.

Limits and outstanding scope

• Marking is not content moderation, a fact check, a copyright licence or an endorsement. Creative quality review remains a separate advisory process.
• PSNR is a technical comparison, not a guarantee of perceptual perfection. Published test results describe the tested files and transformations only.
• Three sampled frames do not establish resistance to every edit or attack. Cropping, recompression, replacement of content and other transformations may reduce detection or invalidate a signature.
• Provider watermarks, including Google SynthID and ElevenLabs markings, are not described as independently verified by Reelry unless specific verification evidence is recorded. Missing metadata or a negative detector result is not proof that a watermark is absent.
• A final MP4 credential does not establish complete marking coverage for standalone images, raw audio or free-form text. These output categories must be assessed independently. The protocol and live status do not assert full Article 50 compliance.
• Public-interest text needs appropriate disclosure or substantive human editorial review and responsibility where the rules apply. Automated checks alone do not establish that review.

Publishing responsibilities

Reelry identifies AI involvement on the surfaces it controls and provides disclosure text for publishing. Professional publishers remain responsible for the disclosures required in their context. Use the destination platform’s applicable AI-content controls. The app cannot guarantee that another platform preserves file metadata or that later editors retain an invisible mark.

Legal framework and review

Article 50 distinguishes provider marking/detection obligations from deployer disclosure obligations. The Commission-recognised Code of Practice is voluntary; other adequate approaches can be assessed. Its usual approach for media distributed online combines signed metadata, imperceptible marking and detection. This implementation should be evaluated against the actual scope, evidence and applicable dates before any compliance declaration is made.

No independent legal sign-off or Code signature is asserted here. The targeted transition for qualifying systems marketed before August 2, 2026 is not a blanket exemption from all disclosure duties or all later workflow changes.

Primary references:

• European Commission: Article 50 guidance
• EU transparency Code of Practice
• C2PA technical specifications
• Content Authenticity Node SDK
• Adobe TrustMark
• DigiCert RFC3161 service

Questions about a result or a technical limitation can be sent through /contact. Do not send sensitive media unless it is necessary and you are authorized to share it.