Privacy Policy — railreader2

Summary

railreader2 does not collect, transmit, or store any personal data. It is a fully offline desktop application. No analytics, no telemetry, no network requests, no accounts.

Data stored locally

railreader2 stores the following data on your computer only, in the platform-standard application data directory:

Configuration — your settings (zoom thresholds, colour effects, UI preferences) in a JSON file. No personal information is included.
Annotations and bookmarks — highlights, notes, and bookmarks you create on PDF documents, stored as JSON files in the application data directory.
Recent files list — paths to recently opened PDFs, stored in the configuration file for convenience. These are local file paths only.

None of this data leaves your computer. You can delete all stored data at any time via Help → Clean Up Temp Files in the application, or by removing the configuration directory manually:

Linux: ~/.config/railreader2/
Windows: %APPDATA%\railreader2\
macOS: ~/Library/Application Support/railreader2/

Network access

railreader2 makes no network requests. PDF rendering, layout analysis (via the bundled ONNX model), and all other features run entirely on your device. The application does not check for updates, send crash reports, or communicate with any server.

Third-party services

railreader2 does not integrate with any third-party services, advertising networks, or analytics platforms.

The optional AI Agent CLI (available only when building from source) can connect to an OpenAI-compatible API if you configure it with your own API key. This component is not included in the distributed application and is entirely opt-in. Your API key and any data sent to the API are governed by the respective API provider's privacy policy, not this one.

Children's privacy

railreader2 does not collect any data from any user, including children.

Changes to this policy

If this policy changes, the updated version will be posted at this URL. Since railreader2 collects no data, substantive changes are unlikely.

Contact

For questions about this privacy policy, open an issue on GitHub.