Privacy Policy

The short version

The files you process on Play PDF never leave your device. Every tool runs in your browser using JavaScript — there is no server that receives, stores, or even briefly touches the contents of your PDFs, images, or the passwords you set. We can't see them, because they're never sent to us.

What we don't collect

• File contents, filenames, or document metadata
• Passwords you set when locking or unlocking a PDF
• Any account information — there is no sign-up, so there's no account data

What does exist

Like any website, requests to load Play PDF's pages pass through our hosting provider (Firebase Hosting, operated by Google), which may log standard technical information — IP address, browser type, and request timestamps — for security and reliability purposes. This is infrastructure-level logging common to virtually all web hosting, not something Play PDF itself collects or has access to on a per-visitor basis.

Play PDF uses GoatCounter for basic, privacy-respecting usage analytics — which pages get visited, in aggregate. It doesn't use cookies, doesn't track you individually across sites, and doesn't collect any personal data. It never sees the files you process, since those never leave your device in the first place. Play PDF does not use any advertising trackers.

Local browser storage

Some tools may use your browser's local storage to remember a preference (like your last-used settings) on your own device. This data stays on your device, is never transmitted anywhere, and can be cleared at any time from your browser's settings.

If you activate a Pro license, the key and the email address it was issued to are stored the same way — in your browser's local storage, on your device only. Checking whether a key is valid happens entirely in your browser (it's a cryptographic signature check against a public key built into the site) — activating Pro never sends anything to a server, including the key itself or your email address.

Changes to this policy

If Play PDF ever adds a feature that changes how data is handled — for instance, a feature that requires sending a file to a server — this policy will be updated to describe it clearly before that feature ships, not after.

Questions

Reach out via the contact page for anything not covered here.