Privacy, in plain language.

Your files are processed on your device. Account and payment information is handled separately to provide paid access.

Files stay in your browser

The application reads files you choose into browser memory and runs local workers. It has no file-upload API or server file storage. Files, names, paths, extracted text, metadata values, hashes and reports are excluded from our application requests and analytics. Clear the workspace or close the tab to release your job. Downloads are stored wherever your browser saves them.

Connections you choose

Opening a direct file URL asks your browser to fetch that asset from its source, without credentials or a referrer. That source receives a normal network request, including your IP address. CORS restrictions may block access. Content Credentials are inspected with the official SDK and self-hosted runtime resources. Remote manifests and online certificate requests are disabled. No signer trust list is configured.

Account and payment information

Hosted Stripe Checkout processes payment details. We store a minimal purchase ledger, payment identifiers, offer, confirmation time, access grants, refund/dispute status, webhook IDs and purchase email. Entering an email at checkout does not grant access to earlier purchases. Restoration requires an ownership link sent through the configured email provider (Resend).

Cookies, local storage and events

A secure HttpOnly cookie associates your browser with purchases. Saved presets store selected field labels locally; file contents are not persisted. We count allowlisted events such as tool opening, inspection, cleanup, download and checkout. Fields are limited to known formats, offers, features, predefined campaign/source labels and a random identifier for the current page visit. The identifier is kept only in page memory and stored as a hash with events; it does not identify a person across visits. No session replay or advertising scripts are enabled.

Retention and requests

Magic-link tokens are hashed and expire after 15 minutes. Used or expired tokens are removed during subsequent link issuance. Rate-limit keys contain hashes of network addresses or emails and expire from active storage after 24 hours. Purchase records may need retention for accounting and dispute obligations; the merchant must publish its applicable legal retention schedule before accepting payments. Contact the configured operator for access or deletion requests.