Privacy Policy
This policy describes this release of C2PA Studio. Its central privacy choice is simple: your selected media is processed on your device. It is not sent to our server for inspection or signing.
Media and signing material
The browser receives access only to the files you select or drop. The official C2PA engine runs locally in a Web Worker using WebAssembly. Remote manifest fetching and online revocation requests are disabled. A local preview uses a temporary object URL. Reader resources and preview URLs are released when no longer needed.
If you use local signing, your certificate and private key are used in browser memory. We do not store the private key in browser storage or transmit it. The key input is cleared after an attempt. Your signed output and downloaded reports are files you control. Inspect reports before sharing them: they may contain filenames, issuer information or other details from the manifest.
Requests to the site host
Your browser requests application HTML, scripts, styles, the WASM engine and any bundled example you choose. The hosting provider can process ordinary request information, such as IP address, user agent and request time, under its own practices. There is no media-upload endpoint. Visiting an external resource follows that provider’s privacy policy.
Local storage and Cookie use
C2PA Studio does not set advertising cookies. Optional Google Analytics is described below. It uses local storage for your analytics choice, a Batch license reference and optional launch-checklist entries. IndexedDB stores a non-extractable browser activation key. The submitted activation code is not retained. These local records belong to the current browser and origin. Clear them through the relevant page action or your browser’s site-data controls. Storage may be unavailable in restricted browsing modes.
Third-party services reached through outbound links can use cookies under their own policies. If Cookie-based advertising is enabled in a future release, this policy and the applicable consent controls must be updated before those scripts are loaded. Essential local preferences and advertising consent are different purposes.
Optional Google Analytics
Google Analytics 4 is configured for this site. It loads only after you allow analytics. When enabled with your permission, Google receives page visit information and ordinary network information such as your IP address and browser details, and uses analytics cookies to distinguish visits. Advertising personalization and Google Signals are disabled by this integration. Our pageview events exclude URL query strings and fragments, selected media, filenames, manifests, certificates, private keys and activation codes. Activation, payment-return, operator and unknown pages are excluded from pageview tracking.
You can allow or decline analytics using the controls on this page when configured. Declining keeps it off; withdrawing permission reloads the page to stop the running Google tag. Existing cookies can be removed through your browser’s site-data controls. Your choice is saved in this browser when local storage is available. Review Google’s privacy policy for its processing practices.
Google AdSense and the DART cookie
Google AdSense is not loaded or configured in this release. If the operator enables it later, Google and its partners may use advertising cookies, including the DoubleClick DART cookie, to serve ads based on visits to this and other websites. Google’s advertising-cookie use allows it and its partners to personalize ads where permitted. Users can manage personalized advertising through Google My Ad Center and review Google’s advertising policies. Other participating vendors may provide choices through YourAdChoices.
Before enabling ads, the operator must assess regional consent requirements, provide the required disclosures and deploy an appropriate consent platform where necessary. A future ad integration must not receive your selected media or private signing keys. A reserved sponsor area is not evidence that Google advertising is already active.
Payments and affiliates
Purchasing is currently unavailable. When configured, a Payment Link sends you to Stripe’s hosted checkout, where Stripe handles payment details. Do not send card details through a contact message. If you activate Batch, the licensing service stores an opaque order reference, code digest, browser public key, binding revision, status and timestamps. Licensing requests contain no selected media, filenames, manifests or C2PA signing keys. The service also keeps minimal operator audit events and short-lived rate counters; counters use hashed identifiers and expired challenges are cleaned periodically. Order-support records are retained for support, and the operator must publish its retention/deletion policy before sales. Contact the operator for verified recovery or data requests. Affiliate links, when present, are identified as such; their destination services may record referral visits.
Your controls and questions
The sandbox payment extension verifies Stripe orders and prepares a transactional email containing the checkout address, order details and activation code. Pending email payloads are encrypted on the server and cleared after provider acceptance or cancellation. Local tests capture those emails privately; Resend sending is not configured. A future Resend integration would process the recipient and message under its own privacy practices. Media is never included.
Do not select a sensitive file on a device or browser you do not trust. You can close the page, clear site data and delete downloaded reports. For privacy questions, use the contact page. The operator must publish a valid contact address before a public commercial launch.