Privacy Policy
About this policy
OpenReader is a browser extension for reading webnovels in your preferred language. This policy covers the extension, its account and translation services, and the OpenReader website. It explains data handling for chapter or selected-passage translation, the focused reader, glossary features, reading preferences, and next-chapter preparation.
Information we handle
Account data includes account identifiers, account details such as email when supplied by the account service, extension connection records, and access tokens. Subscription data includes plan, entitlement, usage, and billing-related status; the extension does not collect payment-card numbers. Reading data includes chapter text or selected passages, translations, story and chapter titles, source-site domains, chapter URLs and next-chapter links, languages, glossary terms, and translation-job status. Your device stores settings, theme, text size, line spacing, reading position, recent chapter URLs, titles and timestamps, and preparation state. Services may also receive IP addresses, browser or user-agent details, request times, and operational or security logs. IP addresses may indicate an approximate location; OpenReader does not request GPS location.
How we use information
We use this information to connect your account, extract and translate the content you request, display the reader, apply glossary terms, restore reading progress, show recent chapters, prepare the next chapter on supported sites, enforce plan limits, and operate and secure the service. Preparing the next chapter can retrieve its content while you read the current one. OpenReader does not collect a general history of unrelated browsing or access your email, messages, or health records as a feature.
Local storage and browser permissions
activeTab provides temporary access to the current page after you invoke the extension. scripting runs code bundled with the extension for chapter extraction, the reader, supported next-chapter capture, and account connection. storage saves the device data described above, including authentication credentials. Required host access connects to the configured translation API and account service. If you configure a custom API or account website, optional HTTPS or localhost access is requested for the specific configured origins. Data sent to a custom service is also subject to that service’s practices. All executable extension scripts are packaged locally; remote responses are processed as data, not executed as JavaScript or WebAssembly.
Translation providers and service providers
Chapter text and relevant glossary mappings are sent to our backend and the AI provider needed to generate a translation or identify terms. The current reader pipeline uses Google Gemini. Hosting, database, authentication, and, when enabled, payment providers process the data necessary to deliver their services. Payment-card information is handled by the payment provider rather than collected by the extension. Providers may process data in countries other than yours and apply their own retention and security terms. Account credentials are used for account access, not included in translation prompts. When a source blocks our direct server fetch, the OpenReader website may load that chapter once through a residential proxy provider (Decodo) to serve your request; the page transits the provider's network under its terms, and the chapter text is not stored.
Transient chapter text, private translations, shared glossary
OpenReader processes chapter text and selected passages in memory to translate them and prepare supported next chapters. We do not save original chapter text in our database, file caches, or durable job queues. Translations are cached only within the account that requested them and are not reused across users. Titles, URLs, navigation links, and content hashes may be kept as account-specific reading metadata. Automatically generated glossary terms and their translated mappings are shared between readers of the same novel to improve consistency. Your manual glossary edits and mappings from a linked story remain private unless you choose to suggest a shared glossary entry. AI and infrastructure providers still process information as described above.
Retention
Settings, account credentials, and recent-reading metadata remain in extension storage until cleared or uninstalled. Prepared chapter text is held in browser session memory and discarded when the session ends; runtimes without session storage use memory rather than disk. The server holds source text only during current processing and releases it afterwards. Interrupted jobs require a fresh chapter capture. The cleanup job removes private translation caches and reading metadata after 30 days without access; deletion depends on the cleanup schedule and access restarts the period. Generated shared glossary mappings and account information are retained as necessary to provide the service. Disconnecting removes local connection credentials and requests token revocation, but does not delete other account data. The privacy migration removes older server-side chapter caches. Historical backups, security, legal, billing, and provider-held records may have separate retention periods.
Your choices and deletion requests
You can change reading and language preferences, edit your glossary, disconnect your account, revoke optional site permissions in browser settings, and remove extension storage or uninstall the extension. To request access to, correction of, or deletion of server-side account and reading data, contact OpenReader support from your account email and identify your request. We may need to verify account ownership. We will explain any records that must be retained for legal or security reasons and any limits concerning backups or third-party services. Removing the extension alone does not delete server-side data.
Security
The default account and API services use HTTPS. Access tokens authorize account-specific operations, and the service applies account access controls. Tokens stored on your device are protected by your browser and device security; no transmission or storage system can be guaranteed completely secure. The optional HTTP localhost connection is intended for a service on your own device.
Chrome Web Store Limited Use
OpenReader’s use of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. We use extension data only for the disclosed reading and translation purpose and related operation, security, and reliability. We do not sell user data, use it for personalized advertising, transfer it to data brokers, or use it to determine creditworthiness. Transfers are limited to providing these features, legal requirements, security and abuse prevention, or a developer business transfer with explicit prior user consent. Human access to user data is limited to your explicit consent for specific data, necessary security or legal purposes, or aggregated and anonymized internal operations.
Website and policy updates
The website offers English and Thai pages and uses a language-preference cookie when you switch languages. The root homepage opens in English. Website hosting may process request metadata, including IP addresses, to serve and secure the site. We will publish policy changes here with an updated date and provide additional notice or consent when required for a material change in data use. Website login is provided by Clerk. The website stores its reader access token and account display details in local storage. If you start translation before login, the chapter input is temporarily kept in session storage to restore it after login, then removed. Language detection runs locally in your browser without sending text to a detection service.
Contact
For privacy questions or data requests, contact OpenReader support. Support contact details will be published on this website.