Privacy
Plain English, no legalese. Here is exactly what happens to your data.
Your statement stays on your device
Parsing happens entirely in your browser, using a local copy of the pdf.js library. The file's bytes are never transmitted, uploaded, or stored by us — you can verify this yourself in your browser's DevTools Network tab while converting.
What our server sees
Page requests, Stripe checkout session identifiers, and license keys during validation. Never your file, its contents, its name, or anything derived from it.
What Stripe sees
Payment goes through Stripe Checkout on stripe.com; Stripe processes your payment details under its own privacy policy. We never see your card number.
Analytics
We use Vercel Analytics with anonymous event names only (for example "export_csv"). No file-derived data is ever attached — this is enforced by an automated test in our codebase that fails the build if any network call site could carry such data.
What's stored on your device
Your license key (if you subscribe) and local fingerprints (SHA-256 hashes) of files you've unlocked, kept in your browser's localStorage so your unlocks persist — and, in rare cases, a small flag marking an unclaimed one-time purchase so it isn't lost. During checkout, your parsed preview is held in sessionStorage so it survives the trip to Stripe. All of it stays in your browser; clear your browser storage to remove it.
What we keep server-side
For subscribers only: your license key and its Stripe references (customer and subscription IDs), so key validation works. Nothing else. To have it deleted, email the support address on your Stripe receipt.
No accounts, no email lists
We don't collect email addresses or set tracking cookies.
Last updated: August 17, 2026