Origin
The file was captured in Lens on a specific enrolled device.
Trust and Credentials
Lens attaches verifiable capture evidence to every signed photo and video, so viewers can understand where media came from and whether it changed.
A Content Credential tells people who captured the file, when it was captured, and whether its integrity still holds. It is your evidence trail, not just metadata.
Each signed capture carries a compact evidence chain. Verification tools can inspect this chain without relying on Lens-specific infrastructure.
The file was captured in Lens on a specific enrolled device.
Edits or tampering become detectable through hash validation.
When available, a TSA timestamp anchors capture time externally.
Optional context such as location and app version supports audits.
Lens uses open standards and hardware-backed signing so credentials remain portable, inspectable, and tamper-evident.
Open provenance standard that packages capture evidence and assertions into an inspectable manifest.
Hardware-backed signing key generated on-device. The key is non-exportable and bound to your iPhone.
When online, Lens requests an external TSA timestamp to establish trusted capture time in the provenance chain.
Device time is checked against trusted network sources to prevent spoofed capture times.
Hash-based integrity checks make edits or tampering visible to verification tools.
Structured metadata container used to embed C2PA manifests directly in media files.
Core trust features are live in production workflows. Production CA certificate issuance remains in progress.
Product conformance is public and independently verifiable. Individual captures may still show as Unrecognized Signer in some viewers until our production CA certificate is issued. That affects signer display, not our conformance status.
Lens follows progressive disclosure so users can understand trust quickly and auditors can inspect full detail when required.