A boundary, not a promise.
ProvSeal is designed so that verification and signing happen in your environment. Hover over the plan: your files and keys stay inside the boundary.
Files · Selected or dropped, they are used only for the requested action: verify, inspect or sign. Never sent to a ProvSeal server.
Private keys · Imported or generated by you, they stay on their own medium. Never import a production key into an environment you do not control.
Verification · The manifest is read and the signature checked in your environment.
Reports · Generated locally, exportable as JSON for your tools.
Three design rules
Your files and keys stay in your environment.
- Local processingProvSeal processes supported media files directly in the local extension environment.
- No upload to a ProvSeal serverVerification and signing workflows are designed to run locally, without uploading your files to a ProvSeal backend.
- Explicit actions onlyThe extension may read selected local files, visible media on the current tab, and signing material that you explicitly import or generate.
- Zero data exfiltration by designSelected media stays in the browser context for the requested verify, inspect or sign action.
- File handlingWhen 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.
Extension permissions, one by one.
ProvSeal requests only the permissions needed to provide its core features: file verification, local signing, page media scan, context menu actions, download of signed files, and local settings.
They are never used for:
- Advertising
- Tracking
- Profiling
- Browsing history collection
Limited Use disclosure
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.
Certificates and keys
A valid signature and public trust are not the same thing.
- A test certificate equals public trust
- A production key can go anywhere
C2PA signing requires a certificate and private key. ProvSeal supports test certificates for development and demo workflows, and may support imported signing material such as .p12 or .pfx files.
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.
Private keys should always be handled carefully. Do not import production signing credentials into environments you do not control.
How trust status is displayed
Status labels explain available evidence in the extension UI. They are not truth verdicts.
- TrustedThe media contains valid Content Credentials and the certificate chain is recognized by the configured trust sources.
- Signed but untrustedThe media contains a cryptographically valid signature, but the certificate is not recognized as publicly trusted.
- InvalidThe media contains C2PA data, but integrity or signature validation failed.
- No credentialsNo C2PA evidence was detected. This does not mean the content is fake.
- ProvSeal is a member of the Content Authenticity Initiative (CAI), a community supporting digital content provenance and transparency.
Any doubt about our security?
Report it privately: we review it before any public disclosure.