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. For Saver accounts, this also includes the Google Gemini API key you supply: it is stored encrypted, used only to run that account’s chapter translations, never displayed back to you in full, and deleted when you remove it.
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. When your plan downloads the next chapter ahead of time, that chapter text stays in your browser’s memory only until you open the chapter.
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. Books you import on the website (ePub, txt, or md) are stored only in this browser on this device, are never uploaded, and can be deleted at any time.
Translation providers and service providers
OpenReader uses AI services from third-party providers to translate chapters and build glossaries. Currently these are OpenAI and Google (Gemini). Chapter text you submit is sent to these providers only to produce your translation, and may be processed outside Thailand. We do not allow them to use your content to train their models (per their API terms). On the Saver plan, chapter translation runs with the Google Gemini API key you saved yourself, so that chapter text is processed by Google under your own key and Google account terms, while glossary terms are still identified through OpenReader's own provider account; the keys are stored encrypted with AES-256-GCM and are never returned in full. 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. The OpenReader website loads public chapters using Scrapling on our hosted servers. Challenged pages may use an isolated temporary browser profile, deleted after the request. Chapter text is not stored by the capture service. Optional private-browser trials use Kernel to run a remote publisher browser. Kernel processes publisher sign-in and page content in that browser. The application does not request session recordings and disables Kernel telemetry collection.
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; Delete account on the website profile page removes your account and its data permanently. The privacy migration removes older server-side chapter caches. Historical backups, security, legal, billing, and provider-held records may have separate retention periods. Private-browser trial metadata and allowance reservations are kept in Redis for up to 60 days; source HTML and chapter text are not stored in this ledger. If you choose Remember sign-in, publisher cookies and browser state are saved in a private Kernel profile until you forget that sign-in or request its removal. Publisher sessions may expire earlier.
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. Use Forget saved publisher sign-in in the private-browser panel to remove an opted-in profile. If the trial is unavailable, request profile removal through OpenReader support. OpenReader logout does not remove publisher profiles.
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.
Consent records
When you accept our Terms of Service and Privacy Policy, we record which document versions you accepted, when you accepted them, and where the acceptance came from (for example this website or the iOS app). We also keep the IP address and user-agent of that request as evidence of your consent, and we record marketing choices the same way. These records are kept as proof of consent, as described under retention below.
Marketing communications
With your consent, we use the email address registered to your account (and your name) to send newsletters, product news, offers, promotions, surveys, and event invitations about OpenReader and related products we may offer in future. We may use email service providers to send these messages and to measure them, including whether a message was opened or a link was clicked. You can withdraw your consent at any time through the unsubscribe link in any marketing message or from your account settings. Withdrawing stops future marketing email; it does not affect processing carried out before you withdrew, and service messages about your account, billing, security, and policy changes are always sent while you have an account.
Legal bases for processing
Where the law requires us to name a legal basis, we rely on: performance of a contract (providing the account, translation, reader, and plan features you asked for); legitimate interests (keeping the service secure, preventing fraud, abuse, and ban evasion, enforcing our Terms of Service and Fair Play Policy, and improving the service, balanced against your rights); consent (marketing email, and anything else we ask your permission for, which you can withdraw at any time); and legal obligation (records we must keep, and answers to lawful requests). Our providers and processors may process data outside Thailand; where the law requires it, we rely on appropriate safeguards for those transfers.
Keeping consent and enforcement records
Account, reading, and preference data is deleted or de-identified when you delete your account, within the retention described above. Consent records and enforcement records — including suspensions, terminations, and Fair Play Policy decisions — may be kept after your account is closed for as long as we need them to prove consent, to prevent fraud, to stop someone from evading a ban, and to meet our legal obligations. Records kept for these purposes are used only for them.
Your privacy rights
Under your local law, you may have the right to access the personal data we hold about you, to ask us to correct it, to ask us to delete it, to object to or restrict some processing, to receive a copy in a portable format, and to withdraw consent you have given. In Thailand, the Personal Data Protection Act (PDPA) gives you these rights, including the right to complain to the Office of the Personal Data Protection Committee; readers elsewhere may have equivalent rights, for example under the GDPR. To use a right, contact OpenReader support from your account email and identify your request, and we may need to verify your account first. Withdrawing consent to marketing takes effect immediately and does not affect your access to the service.
Detecting and enforcing violations
We use account, usage, device, and request data to detect and enforce violations of our Terms of Service and Fair Play Policy — for example automated access, attempts to bypass limits, billing or referral abuse, and account sharing. Where we find a violation, we may act as the Terms of Service describes, including suspending or terminating an account. Data used for enforcement may be kept as described above.