Privacy Policy
Last updated: November 10, 2026
1. Summary
Most FluoPDF tools process your files in your browser, so the file is never sent to us. Two features work differently, and we label them on every tool page: FluoShareuploads your file only after encrypting it in your browser (we can't read it), and the AI Assistant and Translation send text from your document to an AI provider. See How privacy works for a plain-language walkthrough.
2. How your documents are handled
Local tools
Merge, Split, Compress, PDF→Word, Rotate, Watermark, Page Numbers, Extract Pages, PDF→Image, Batch, Redact and OCR run in your browser. Your file is not uploaded. OCR downloads the open-source Tesseract engine and language data from a public CDN (jsDelivr) the first time you use it; your document is not sent.
FluoLock™ (password encryption)
Encryption and decryption happen in your browser (AES-256-GCM, key derived from your password with PBKDF2). Your password and your file are never sent to us; the encrypted .fluopdf file stays with you. If you turn on server sync, we store a lock record: your account ID, the original file name, creation date, optional expiry and open limit, open count and whether you revoked it. When anyone opens a synced file in FluoPDF, the lock ID is sent to us to check that record. The file name and these settings are also written, unencrypted, into the .fluopdf file itself.
FluoShare (zero-knowledge sharing)
Your PDF is encrypted in your browser with a password you choose; only the encrypted file is uploaded and stored, in a private storage bucket on our server. We never receive the password, so we can't read the document. To run the link we store, unencrypted: your account ID and email, the file name, expiry, download limit, download count, view-only setting and whether you revoked it.
AI Assistant and Translation (cloud processing)
Text is extracted from your PDF in your browser and sent through our server to OpenRouter, which routes it to an AI model provider to produce the answer or translation. We don't store that text or the response. OpenRouter and the model provider process it under their own terms and retention policies. Don't use these features for highly sensitive documents.
3. Other data we collect
- Account: email, optional name, password hash and two-factor settings (Appwrite Auth).
- Subscription: provider (Stripe or Creem), customer and subscription IDs, price ID, status, trial end, renewal date and whether it is set to cancel. Card details go straight to the payment provider and never reach us.
- Billing event log: the ID, type and time of each payment-provider notification we processed, so none is applied twice. No amounts or personal details.
- Legacy payment records: for subscriptions billed through Creem — event type, status, email, Creem customer and subscription IDs, amount, currency and country.
- Usage: daily counters per account (tool runs, AI requests, new secure links) for plan limits, stored under a one-way key and reset each UTC day.
- Trial record: a keyed one-way hash of your email address, so each person gets one free trial. We can't turn it back into your email.
- Trial-abuse signal: when you start a checkout we store your account ID, email and a keyed one-way hash of your IP address (never the IP itself).
- Error reports: if the site crashes in your browser, the error message, page address and stack trace are written to our server logs.
- Recent activity: the "recent files" list in the app is stored only in your browser.
4. Analytics and advertising measurement
Analytics (page views, which tools are used) and the Meta Pixel (whether our ads lead to sign-ups) load only after you accept cookies. Neither receives document contents or file names. Separately, when a subscription or trial starts, our server reports that conversion to Meta with a one-way hashed account ID — but only if you accepted marketing cookies while signed in. If you decline, never choose, or later withdraw consent on the Cookie Policy page, no such report is sent. See the Cookie Policy.
5. Retention and deletion
- Delete your account (Settings) and we cancel any active subscription, then delete your account, your subscription record, your usage counters, your FluoLock records, and every FluoShare link including its encrypted file.
- FluoShare files stop working immediately when a link is revoked, expires or reaches its open limit. An automatic cleanup then deletes the encrypted file and its record — revoked and used-up links at the next hourly run, expired links about an hour after expiry.
- Billing event log, trial record, legacy payment records and trial-abuse signals are kept after account deletion for accounting and fraud prevention. We haven't set a fixed retention period yet; ask us and we'll delete what we aren't required to keep. Stripe and Creem keep their own records under their own policies.
- Export: Settings lets you download the data we hold about your account as JSON.
6. Service providers
- Appwrite — authentication, database and file storage, self-hosted on our own server
- Cloudflare — content delivery and security
- Stripe — payment processing and billing portal; new subscriptions are sold through Link (Stripe's merchant-of-record service), which processes your payment details, billing address and location to charge you, calculate and remit tax, and send receipts
- Creem — billing for subscriptions started before we moved to Stripe (Merchant of Record for those)
- OpenRouter and the AI model providers it routes to — AI Assistant and Translation only
- jsDelivr — serves the OCR engine files to your browser
- Google Analytics or a privacy-focused analytics service, and Meta — only as described in section 4
7. Your rights
Depending on where you live (for example under the GDPR in the EU/UK or the CCPA in California), you may have the right to access, correct, export or delete your data and to object to some processing. You can export or delete your account yourself in Settings, or write to support@fluopdf.com.
8. Contact
FluoPDF is operated by Larkmond LLC, 12436 FM 1960 Rd W, Unit #1510, Houston, TX 77065, USA, which is responsible for the personal data described in this policy. Questions about this policy: support@fluopdf.com.