No cloud uploads
Selected media is not sent to a ProvSeal backend for verification or signing.
ProvSeal
How ProvSeal handles files, permissions and user data — local-first by design.
ProvSeal processes supported media files directly in the local extension environment. Verification and signing workflows are designed to run locally, without uploading your files to a ProvSeal backend.
Selected media is not sent to a ProvSeal backend for verification or signing.
Parsing and validation run in the browser / extension context.
Files and page media are only read when you choose verify, inspect, sign or scan.
Selected media stays in the browser context for the requested verify, inspect or sign action.
When you select or drop a file into the extension, the file is used only for the requested action: verify, inspect, or sign.
ProvSeal does not use your files for advertising, profiling, training, or unrelated analytics.
ProvSeal requests only the permissions needed to provide its core features.
Permissions are not used for advertising, tracking, profiling, or unrelated browsing history collection.
The use of information received from extension permissions adheres to applicable store User Data Policy requirements, including Limited Use.
User data is used only to provide and improve the extension’s single purpose: local C2PA Content Credentials signing, verification and page media analysis.
Demo signing material and embedded demos have clear boundaries — they never imply public trust or outbound media transfer.
A test certificate is useful for learning, demos and internal validation. It can show how a C2PA signing workflow works, but it does not mean the signature is publicly trusted.
For production trust, organizations should use certificates issued through the C2PA trust ecosystem.
With your consent, the website uses Google Analytics and limited product analytics events to understand page usage and install interest.
Events may include a pseudonymous browser identifier, page path, language, referrer hostname, campaign parameters and coarse location supplied by the hosting platform.
Analytics consent and the pseudonymous browser identifier are stored in your browser. You can reopen Cookie settings in the footer at any time.
Our team is committed to transparency. Read more about our trust architecture or get in touch.