Effective date: June 18, 2026
Application: OpenReader — a local-first desktop PDF utility for Windows.
OpenReader does not collect, transmit, or store any personal data.
The application is designed to be entirely local-first. All PDF processing — including reading, searching, copying, annotating, merging, splitting, extracting, and compressing — occurs on your local machine. No document content is ever uploaded, transmitted, or shared with any remote service.
OpenReader makes a single optional network request:
https://api.github.com/repos/sparshsam/openreader/releases/latest
to compare the installed version against the latest published release. This request includes no
identifiers, no document data, no telemetry, and no usage statistics.The update check can be performed manually at any time via Help → Check for Updates.
No other network requests are made by the application. No analytics, crash reporting, or usage tracking is included.
OpenReader stores the following data locally on your device:
All local storage is confined to your user profile and can be cleared via the application's settings or your operating system's application data management tools.
OpenReader does not embed any third-party analytics, advertising, tracking, or telemetry SDKs.
The only external service referenced is GitHub (for the optional update check described above) and the Microsoft Store (for distribution — the Store itself may collect standard installation metrics as described in Microsoft's privacy policy).
OpenReader does not share any user data with any third party. There are no accounts, no user profiles, and no cloud sync features.
Because all processing is local, your documents remain on your device. OpenReader includes basic safety checks before rendering PDFs (file type validation, size limits, render caps) to reduce risk from malformed documents, but PDF parsing depends on underlying libraries. As with any software that opens files from untrusted sources, we recommend using OS-level sandboxing or a VM when working with sensitive or unknown documents.
If this policy changes, the updated version will be published at this same URL. Material changes will be noted in the application's changelog.
For questions about this privacy policy: open an issue on the GitHub repository.