Upload an asset, declare how AI was used, select destinations and get a dated operational route. The raw file stays in this browser. No upload occurs in this beta.
1. Asset & fingerprint
The file is read locally only to calculate SHA-256 and, for safe JPEG cases, to create Amazon XMP metadata.
No file selected.
2. Declare how it was made
3. Destinations
4. Operational route
Amazon file action
For a clean JPEG without an existing XMP packet, this beta can create a copy containing dc:subject = contains-synthetic-performer and verify that the keyword exists in the output bytes. Existing XMP is not overwritten in order to avoid damaging metadata.
Waiting for a qualifying Amazon route.
The active rule set is versioned and each route item links to its source. This is operational guidance, not legal advice. Rules can change and unresolved edge cases require additional input or review.
Rule sources in this beta
Cloud evidence history
What is stored?
Saved evidence includes the asset metadata, SHA-256 fingerprint, your declaration, route, ruleset and timestamps. The current route flow does not store the raw media file. No automatic evidence-deletion period is implemented yet.