Back to home

StripSynthID Privacy Policy

How StripSynthID handles image processing, local checks, accounts and billing information.

Scope

This policy applies to StripSynthID. The service offers image metadata cleaning, local video/audio metadata cleaning, and independent image provenance checks.

Images and processing

For image metadata cleaning, you sign in and expressly agree to send the selected image to our server. The server cleans supported metadata in memory and returns a downloadable copy. The application does not save an image library or the original/cleaned image bytes in database task records. Keep your original and download results you want to retain. Ordinary hosting and security infrastructure may process network request information.

The independent inspection page reads embedded C2PA credentials and optionally runs TrustMark Q in your browser. Those checks do not upload the image. To authorize a report and prevent duplicate charges, the site receives a SHA-256 image fingerprint, request identifier, account identity and action. It stores task/accounting records containing that fingerprint and action. A fingerprint is not an image copy, but may identify a file already known to someone who has matching bytes.

The built-in demonstration can be used without an account and without consuming uses. Closing or refreshing the page clears temporary browser file state.

Metadata removal can delete camera details, location, editing history or Content Credentials from the downloaded copy. It does not delete the original, shared copies or records held by another service. Local C2PA checks do not fetch remote manifests, certificate revocation endpoints or issuer trust lists.

Local video and audio cleaning

Video and audio files are parsed in a browser Worker and are not uploaded for processing. After successful local parsing, authorizing a paid download sends a SHA-256 file fingerprint, request identifier and account/action information to the site for usage accounting. The server does not receive media bytes or the filename. These accounting records use the same retention and replay rules described above. Keep the original; supported tags, covers, chapters or provenance records may be removed from the downloaded copy. Processing does not re-encode the audio/video streams. Browser preview depends on the file codec.

Optional online checks

Each online provider requires separate consent. An OpenAI provenance check sends the original through our server to OpenAI; an independent classifier request sends it to the configured classification service. Images are not saved in application storage or task records. Provider handling follows its applicable terms and policies. Provider result summaries may be saved for request replay and billing reconciliation; no original filename is required in provider requests. Admin events record the action/provider and outcome without image bytes. Downloaded reports are saved by you locally.

Accounts, support and billing

An account is required for your own image processing and reports. Authentication providers may supply an identifier, name, email and profile image. Passwords and sessions are handled by the site's authentication system. Social sign-in does not give us your third-party password.

The site keeps orders, subscriptions, use balances, task statuses and consumption/refund records to deliver paid service and resolve billing requests. Payment providers handle payment details; the application does not store full card numbers. See Pricing and Terms for the current plans and use rules.

Support tickets contain information you choose to submit. Do not include passwords, payment credentials or unnecessary sensitive images. Account details and support are available under Settings.

Cookies, retention and choices

Session cookies support sign-in. Language and appearance preferences may use cookies or browser storage. Optional analytics and support integrations process usage information when enabled; use any displayed consent controls to manage those choices.

Account, security, support and billing records may be retained to operate the service, resolve requests and meet applicable obligations. Hosting, authentication, email and payment providers receive information needed for their roles. We do not promise permanent result storage or absolute security.

Choose which files to process and where to save results. Submit access, correction or deletion requests through authenticated support. Some records may need to be retained for security or accounting. We update this policy when data handling changes.