Privacy, data flow, and account controls.
This policy explains what data OpenReader processes, how it is used, and the controls available to you. It applies to the instance currently running at https://reader.craig-online.net. Effective date: February 17, 2026.
1. Information we collect
OpenReader collects data needed to operate the service and maintain your reading state. Categories include account identifiers, uploaded content, and product usage telemetry.
- Identifiers: Email, session-related identifiers, account name, and IP metadata for authentication and security.
- Reader content: Uploaded documents, reading progress, bookmarks, and playback settings required for core functionality.
- Usage events: Feature interactions and performance analytics used to debug and improve product reliability.
2. How we use your data
- Deliver and personalize document reading and text-to-speech playback.
- Process uploaded files for parsing, synchronization, and optional audiobook export.
- Keep the platform secure and prevent abuse.
- Diagnose issues and improve performance of existing functionality.
4. Your privacy rights
Depending on your jurisdiction, rights may include access, correction, deletion, and opt-out controls. OpenReader includes in-product controls for exporting and deleting account data.
- Right to know: request details about data categories and usage.
- Right to delete: delete your account and associated records in Settings.
- Right to correct: update account data where applicable.
- Right to opt out: disable non-essential analytics through consent controls.
- Right to non-discrimination: exercising privacy rights does not reduce service access.
5. Retention and security
Account data and uploaded files are retained while your account remains active. Data is encrypted at rest in storage. OpenReader does not currently provide end-to-end encryption.
The owner of this instance may be able to access stored metadata and uploaded files needed to operate the service.
Passwords are not stored as readable plaintext; the authentication system stores credential values as non-plaintext verification data.
Account deletion triggers removal of active account records and associated storage artifacts as part of the deletion flow.
6. Processing location
Data processing location depends on the deployment environment and provider configuration selected by the instance operator.
7. Contact and open source
Questions or concerns can be raised through the project repository. Self-hosting is available if you want full infrastructure control.