Privacy Policy
Last updated: 2026-10-10. This policy explains how PDFLocal, operated by Revolt Bots LLC, processes personal data — in line with the EU General Data Protection Regulation (GDPR, in particular Articles 13 and 14) and applicable US state privacy laws such as the California Consumer Privacy Act (CCPA).
The short version
Your files never leave your device. Every PDF operation runs entirely in your browser using WebAssembly. No file data is ever uploaded. We use a minimal server only for license validation, abuse prevention, and anonymous daily totals of which pages and tools are used. None of it requires cookies.
1. Identity of the Controller
The controller responsible for the processing of your personal data within the meaning of Art. 4 (7) GDPR is:
Revolt Bots LLC
Florida, United States
Contact: contact form
2. Contact Details
For all questions regarding data protection and the exercise of your rights as a data subject, please write to us through our contact form and choose “Privacy request”. We reply by email.
We have not appointed a data protection officer because we are not required to under Art. 37 GDPR.
No file uploads
When you use any tool on PDFLocal, the PDF processing happens locally in your browser using a WebAssembly-powered engine. Your files are never sent to a server. They stay on your machine from start to finish.
3. Purposes and Legal Bases of Processing
We process personal data only where we have a lawful basis to do so. The processing activities, their purposes, and the corresponding legal bases under Art. 6 (1) GDPR are:
- Delivery of the website — IP address and standard HTTP request data are processed by our hosting/CDN provider (Cloudflare) for the technical operation of the site, abuse prevention, and DDoS protection. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in providing a secure service).
- License validation, device binding & daily limit enforcement — For Pro users, we validate the license key you enter against Lemon Squeezy and cache only a salted one-way hash of that key together with a validity flag — never the raw key, your email, or any order details. So that a single license can be used on only a limited number of devices, we also store a salted one-way hash of your key combined with a random per-device identifier (and, as a fallback, your device signature), each mapped to the opaque activation identifier Lemon Squeezy returns; this is what lets you remove Pro from a device to free a slot, and it contains no name, email, location, or file data. So you can regain access without contacting us when your other devices are lost or unreachable, a self-service reset frees every device slot for a license at once; to make this possible without ever storing your devices, we keep a salted one-way hash of your key mapped to the list of opaque Lemon Squeezy activation identifiers, and — to rate-limit resets to once every 30 days — a self-expiring cooldown marker plus an anonymous reset count (a number only, never the key). None of these contain a name, email, location, or file data. For free users, we count daily tool usages per salted, IP-derived bucket; the raw IP address is never stored. Legal basis: Art. 6 (1) (b) GDPR (performance of the Pro contract) and Art. 6 (1) (f) GDPR (legitimate interest in abuse prevention and preventing license-sharing).
- Pro device-slot recovery (device signature) — Only when a Pro license is checked or removed, your browser sends a coarse device signature computed from your user-agent, language, screen dimensions, colour depth, time-zone offset, and processor-core count, hashed (SHA-256) before it leaves your device. Its single use: if you clear your browser data (which also clears the random device identifier), it lets this device get its own Pro slot back instead of using up another. It is stored only as a salted hash beside that slot (see Retention), is not linked to your identity, and the underlying attributes are never stored. It is not sent for free-tier use: daily limits and one-time Pro trials are counted by a salted hash of your IP address. Legal basis: Art. 6 (1) (b) GDPR (performance of the Pro contract) and Art. 6 (1) (f) GDPR (legitimate interest in preventing license-sharing).
- Pro purchases — When you buy a Pro license, our Merchant of Record, Lemon Squeezy, processes your billing data. PDFLocal receives no purchase webhook and keeps no purchase record: no order ID, email, name, billing address, or payment detail is stored on our side. Your license key is checked only when you enter it into the app. Legal basis: Art. 6 (1) (b) GDPR.
- Anonymous usage counts — When a tool finishes, your browser sends the tool's name and the interface language, and our server adds one to a daily total for that tool and language. When you load a page, your browser sends the page's address (in its English form), the interface language, whether the screen is a phone, tablet, or desktop, and the name of the website that linked you to us (only its hostname, never a path or search terms); the server adds the country code Cloudflare reports for the connection. Pressing the Buy button, or following a link from a Pro paywall to the Pro page, is counted the same way. Every one of these goes into a daily total. Most totals hold a single kind of fact (all countries together, all referrers, all screen sizes); the exception is that page views and tool runs are also split by country, so that we can see what is popular where, and neither is ever stored together with a referrer or a screen size. No IP address, device identifier, device signature, cookie, local-storage entry, or time of day is stored with any of it, so the totals are not personal data once written; we use them to learn which pages and tools people use and where visitors come from. Our own counters count nothing for a browser that sends Do Not Track or Global Privacy Control, or for automated browsers and search-engine crawlers. Tool-run counts are rate-limited like every request to our server by a short-lived salted IP hash (see Retention); page-view counts do not read your IP address at all. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in improving the Service).
- Page-speed and visit statistics (Cloudflare Web Analytics) — Cloudflare, which hosts this site, adds a small script to our pages that reports how quickly the page loaded, which page it was, and your browser and operating-system version, together with a random identifier that exists only for that one page load. It sets no cookie and stores nothing in your browser, and Cloudflare states that it does not track individual visitors across its customers' sites. Cloudflare sees your IP address, as it does for every request to the site. We use it to see how fast the site is and how many people visit. Unlike our own counters above, this script is run by Cloudflare, and we do not control whether it honours Do Not Track or Global Privacy Control. Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in running a fast, working service).
- Contact form and email correspondence — If you write to us through the contact form, your browser sends what you typed (topic, email address, optional name, and message) to our server, which emails it to our support inbox with your address as the reply address. The server does not store the message; like every request, it is rate-limited by a short-lived salted IP hash, and your IP address is not included in the email. We then process your email address and the conversation to respond. Legal basis: Art. 6 (1) (b) GDPR where your request concerns a purchase, otherwise Art. 6 (1) (f) GDPR (legitimate interest in answering inquiries).
No cross-site tracking
PDFLocal has no ads, no tracking pixels, and no cross-site tracking, and nothing follows you from one site or visit to the next. The usage data we collect is limited to anonymous daily totals: which pages are viewed, which tools are used, where visits come from, which countries and screen sizes they come from, and how often the Buy button is pressed, plus the cookie-free page-speed statistics from Cloudflare's Web Analytics. We store no IP address, device identifier, or browser signature with any of it, and no total can be traced back to a person. We do not sell or share any data with third parties.
No cookies
PDFLocal does not set any cookies: no authentication, preference, or third-party cookies of any kind. Your browser's local storage, which only your browser can read, holds your Pro license key if you have one, a random device identifier used to count Pro device slots, and your free-tier usage count for the day.
4. Recipients of Personal Data
We use the following processors and recipients to operate the Service:
- Cloudflare, Inc. — CDN, edge hosting, our license/usage server, the database holding the anonymous daily counts, and Cloudflare Web Analytics (page-speed and visit statistics). Cloudflare processes IP addresses and HTTP-request metadata as our processor under a Data Processing Agreement. International transfers are covered by the EU Standard Contractual Clauses.
- Google LLC — hosts our support mailbox (Google Workspace), where contact-form messages and email correspondence are received and kept. Acts as our processor; international transfers are covered by the EU Standard Contractual Clauses.
- Amazon Web Services, Inc. — sends our email replies (Amazon SES). Processes the recipient address and message as our processor; international transfers are covered by the EU Standard Contractual Clauses.
- Lemon Squeezy (Lemon Squeezy LLC) — Merchant of Record for Pro license purchases. Acts as an independent controller for billing data; their privacy policy applies to the payment transaction. We do not receive your email, order ID, or any billing data from Lemon Squeezy — Pro entitlement is checked by validating the key you enter against their keyless License API.
We do not sell, rent, or otherwise transfer personal data to third parties for marketing purposes.
License validation
A lightweight server is used for license-key validation, Pro entitlement checks, daily usage-limit enforcement for free-tier users, and the anonymous tool-run counts described below. These requests contain no file data. To check your Pro license, the server validates the key you enter against LemonSqueezy and caches only a salted one-way hash of the key plus a validity flag, never your email, the raw key, or any order details. Only when a Pro license is checked or removed does your browser also send a coarse device signature, derived from your browser, language, screen size, time zone, and processor-core count and hashed before it leaves your device. It has one use: if you clear your browser data, it lets this device get its own Pro slot back instead of using up another. Free-tier limits and trials are counted by a salted hash of your IP address, never by this signature.
Analytics
When you load a page or finish a task, your browser sends a few anonymous facts, and our server adds each one to a running total for the day: which page was viewed and in which interface language; which tool was used, when a tool finishes; roughly where the visit came from (the website that linked to us, or "direct"); the visitor's country, which Cloudflare works out from the connection and which we keep only as a two-letter country code; whether the screen is a phone, a tablet, or a desktop; and whether someone pressed the Buy button or followed a link to the Pro page. Page and tool totals are also kept per country, so we can see what is popular where and do not mistake one country's habits for another's; a referrer or a screen size is never stored next to a country or a page. Nothing else is stored: no IP address, no device identifier, no browser signature, and no time of day, and no total describes any one person. No cookies or local storage are used for any of it. If your browser sends Do Not Track or Global Privacy Control, our own counters count nothing for you at all. Separately, Cloudflare, which hosts this site, measures page-load speed and visits with its own Web Analytics; it sets no cookie and stores nothing in your browser.
5. Retention Periods
- License validation cache (salted hash of the key → validity flag): cached for at most 24 hours and then re-validated; no email or order record is kept. Tax and accounting records for your purchase are held by Lemon Squeezy as Merchant of Record, not by us.
- Device-binding seat mappings (salted hash of the key plus a per-device identifier → opaque Lemon Squeezy activation id): kept up to 12 months and refreshed on each successful validation; removed when you remove Pro from a device. Contains no identity, location, or file data.
- Device-slot index (salted hash of the key → list of opaque Lemon Squeezy activation ids): kept up to 12 months so a self-service reset can free every slot at once; cleared when the reset runs. Contains no identity, location, or file data.
- Device-reset cooldown & counter (salted, key-derived): a self-expiring marker that limits resets to once every 30 days, plus an anonymous count of how many resets have occurred. Neither stores your key, identity, or file data.
- Device-signature seat entry (salted hash of the key plus the device signature → opaque Lemon Squeezy activation id): kept up to 12 months beside the device-binding mapping above and removed with it. Contains no identity, location, or file data.
- Daily-usage counters (salted, IP-derived): reset every 24 hours; no historic record is retained.
- Rate-limit counters (salted, IP-derived): per-minute counters expire after 90 seconds and per-day counters after 24 hours.
- Per-tool free-trial markers (salted, IP-derived): a single timestamp kept up to 12 months so each Pro tool's one-time free trial cannot be reused; it contains no file data and no identity.
- Server access logs: retained for a maximum of 30 days, then deleted or anonymized.
- Contact-form messages and email correspondence: not stored on our server; kept in our support mailbox for as long as needed to handle your request and any follow-up.
- Anonymous daily counts (tool runs by day, tool and interface language, and by day, tool and country; page views by day, page and language, and by day, page and country; and separate totals by day for countries, referring websites, screen sizes, and Buy / Pro-page clicks): kept indefinitely as aggregate statistics. They contain no IP address, identifier, or other personal data.
- Cloudflare Web Analytics data: held by Cloudflare under its own schedule. At the time of writing it keeps unsampled data for 7 days, then reduces it to about a tenth of its volume, and shows us the previous six months.
6. Your Rights as a Data Subject
Under the GDPR you have the following rights with regard to the personal data we process about you:
- Right of access (Art. 15 GDPR)
- Right to rectification (Art. 16 GDPR)
- Right to erasure / “right to be forgotten” (Art. 17 GDPR)
- Right to restriction of processing (Art. 18 GDPR)
- Right to data portability (Art. 20 GDPR)
- Right to object (Art. 21 GDPR)
- Right to withdraw consent at any time, where processing is based on consent (Art. 7 (3) GDPR), without affecting the lawfulness of prior processing.
To exercise any of these rights, write to us through our contact form.
7. Right to Lodge a Complaint with a Supervisory Authority
If you are located in the European Union, the European Economic Area, or the United Kingdom, you have the right to lodge a complaint with your local data-protection supervisory authority (Art. 77 GDPR / UK GDPR) if you believe our processing of your personal data infringes data-protection law. You may contact the authority in your country of residence, your place of work, or the place of the alleged infringement.
8. Automated Decision-Making
We do not use automated decision-making, including profiling, within the meaning of Art. 22 (1) and (4) GDPR.
9. California Privacy Rights (CCPA/CPRA)
If you are a California resident, the California Consumer Privacy Act (as amended by the CPRA) gives you the right to know what personal information we collect, to access or delete it, and to opt out of its sale or sharing. We do not sell or share your personal information, and the files you process never leave your browser. To exercise your California privacy rights, write to us through our contact form. We will not discriminate against you for exercising these rights.
Verifiable privacy
Because all processing happens client-side, you can verify this by inspecting your browser's network tab while using any tool. You will see zero file data leaving your device.