LimePDF privacy
Your documents stay local.
LimePDF processes PDFs on your device. No account is required, and the installation counter receives no documents, event names or presentation activity.
Recorded installations
LimePDF automatically sends a minimal confirmation when a supported browser reports that installation has completed. The public total counts confirmations received by the service. Opening the installation screen, pressing Install, cancelling, choosing Use in browser, reopening or updating the app does not add an installation.
What is sent and retained
The message body contains only the reporting protocol version. It contains no installation or device identifier, name, email, country or timestamp. The service adds one to an aggregate; its database retains the total and when counting started, with no individual installation records or usage history.
There is no stored reporting queue or automatic retry. If the app is offline or busy when the confirmation arrives, the report is discarded. A failed delivery also remains uncounted. Reports are not sent retrospectively when the app next opens.
What the total means
Browser support and delivery vary, so this is not a complete count of installations, unique people or active apps. Without a persistent identifier, the service cannot deduplicate every repeated confirmation, reinstall or report from another window. Earlier installations are not estimated or added retrospectively.
The total cannot identify an individual report or subtract it later. Old app versions using the previous reporting format are rejected without storing their delivery tokens.
Reading the total and network processing
The website and app request only the public aggregate, without an identifier or cookies. The app caches the latest valid result and checks at most once a day while open, online and idle. This read does not report an installation. The counter sets no tracking cookies and uses no advertising or analytics SDK.
Cloudflare hosts the service and necessarily processes connection information, including IP addresses. A temporary network-based rate limit protects the reporting endpoint; addresses are not stored in the counter database. Application request logs and traces are disabled. Counter storage is restricted to the EU; Cloudflare's network and security processing may occur elsewhere under its service terms.
The migration removes any legacy temporary token hashes from the active database and cancels their cleanup alarms. Cloudflare supports infrastructure recovery history for up to 30 days; removal from the active database is not a claim of immediate erasure from that recovery history.
Questions about this counter or privacy: [email protected].