YOUR FILES & YOUR PURCHASE
A clear view of
what stays where.
Your documents
The storefront does not upload or store your document files. Purchased web editions process documents in your browser, with local drafts separated by customer account. Core PDF, writer and OCR processing in the Windows, Android, Linux and native iOS apps happens on the device. Compatible network scanners communicate over the local network.
Optional AI
Local AI models run on your device and are off by default. The native apps include their models. The web app downloads public model files when needed; those downloads contain no documents. A user-selected remote AI service receives only the text the user explicitly approves. Connection credentials are kept for the session. Image generation in every edition sends the reviewed image prompt and options to the selected provider only after Generate is pressed: AI Horde, your chosen ComfyUI server, or OpenAI. Anonymous Horde requests enable sharing, with a disclosure before submission. ComfyUI receives the selected workflow and requires your own reachable model server; its models are not bundled. Provider keys, server addresses and workflow connections stay in session memory. Added images and their prompts are saved locally inside the project. OpenAI uses your own API billing; Horde depends on community queue availability.
Your purchase
PayPal and configured card providers process payment details on their own services. This site keeps purchase IDs, purchased edition, price and currency, payment references, permanent edition license keys, a hash of the recovery email, license channel, confirmation status, timestamps and platform download IDs for fulfillment. It does not store card numbers or PayPal passwords.
Your offline key & recovery
Your 16-character license is permanently associated with the verified payment transaction and purchased edition. The apps validate keys locally, with no server checks, device tracking, expiry or online activation. The lookup tool checks your transaction ID and normalized email hash and issues another private receipt access key; existing saved receipts remain valid. License and purchase records are kept for ongoing customer retrieval.
Your receipt access
The receipt's private access key is stored as a hash on the server. Your browser can keep your current purchase in session storage; a saved receipt file lets you re-open it on another device. Download links expire, while an authorized receipt can request a fresh link.
Website use
No advertising or analytics tools are added by this site's code. PayPal's checkout script loads when integrated checkout is available. Payment requests and downloads use essential security checks, including short-lived rate limits. The hosting service may apply its own access and operational controls.
Google Play
The direct-download license covers the Windows EXE, directly installed Android APK and Linux portable app. Purchases made through Google Play are separate and are managed by the Play Store.
Customer accounts and order history
Optional free accounts store a username, email address, salted password hash, email verification status, secure session records and purchase links. Plaintext passwords are never stored. Verification and password reset emails are delivered through the configured transactional email provider. Single-use verification links expire after 24 hours; reset links expire after one hour.
Profiles retain every linked order, including pending and refunded orders, purchase IDs, transaction references, registration keys and download IDs, without an automatic retention expiry. Purchases made while signed in link automatically. Email verification is required to open paid web editions and recover receipt access from a profile. Older purchases require the receipt access key. Signing out or refunding an order does not delete order history. Contact the seller for account or privacy requests; legally required transaction retention can still apply.
Card details are entered on Stripe’s hosted checkout. This website never stores card numbers or security codes. Paid web access requires a valid login session; purchased entitlements have no subscription expiry. Refunds, reversals and disputes may revoke access while preserving order records.