Privacy Policy

Ranobe Gemini does not collect, transmit, or sell your personal data. There are no ads or third-party trackers. Anonymous usage metrics are opt-in only and are limited to event counts.

• Enabled only after explicit consent on first Library open.
• Records anonymous counts for startup, install, and feature usage events.
• Does not collect chapter text, reading history payloads, API keys, OAuth tokens, or account identifiers.

To enhance or summarize a chapter, that chapter's text is sent to the AI provider you configured. There is no way around that — the model has to read the text to rewrite it. What we can tell you is exactly where it goes and what it does not touch:

• It goes to your provider, not to us. We operate no inference server and never see your chapters. The request goes from your browser straight to Google Gemini, the OpenAI-compatible endpoint you configured, or your own machine.
• Choose Ollama and nothing leaves your device. A local Ollama model means the chapter text never crosses the network at all.
• Your API key stays in your browser. Keys live in extension storage and are sent only to the provider they belong to, as that provider's API requires.
• Your provider's policy applies to what you send it. Once text reaches Google, OpenAI, or another hosted provider, that company's terms and retention policy govern it — not ours. Read theirs before sending anything you would not want retained.

Everything else — your library, reading history, settings, prompts, and cached chapters — is processed and stored locally and is never sent anywhere unless you turn on sync.

• Sync is optional and off until you choose a destination. Supported destinations are native browser sync (your existing Firefox or Chrome account), Google Drive, OneDrive, Dropbox, and WebDAV — including a NAS you run yourself.
• Every one of those is your account or your server. We have no storage backend, so there is nowhere for your backup to land that is ours.
• OAuth is performed directly with the provider; tokens are stored in your extension storage and never transmitted elsewhere. For Google Drive the extension requests only the drive.file scope, which limits it to the backup files it created.
• Backups are plain JSON unless you encrypt them. By default the backup is unencrypted and sent over HTTPS, so whoever can open the destination account can read it, as can that provider. Library → Settings → Local Backups → Encrypt backup files turns on AES-GCM-256 for exported files and for cloud backups. The key is generated on your machine, stored in extension storage, and never sent to us or to anyone else — which also means that if you lose the recovery code, nobody can recover the backup for you. Native browser sync is deliberately left unencrypted, because it stores data in the browser's own sync store, where the key already lives.
• You can back up to more than one destination at once. Note that when you do, a failure at a secondary destination is not reported — only the first destination in your list determines whether a backup is reported as successful.

• tabs: to find the reading tab a background job belongs to, and to open the library and settings pages.
• storage: to keep your settings, prompts, and library.
• identity: to complete the OAuth handshake when you opt into a cloud sync destination.
• downloads: to export local backups when you trigger them.
• alarms: to schedule periodic backups and to expire Incognito Mode at the time you set.
• notifications: to tell you when a long background job — a queued chapter, a backup — finishes or fails.
• contextMenus: to add the right-click actions on supported pages.

Host permissions are limited to three Google origins: generativelanguage.googleapis.com for the Gemini request itself, and oauth2.googleapis.com plus www.googleapis.com for Drive. Access to the supported novel sites is optional and requested per site, when you enable it. Everything else the extension can reach — an OpenAI-compatible endpoint, a local Ollama server, a WebDAV server, OneDrive, Dropbox — is opt-in and deliberately not declared here, because several of those are URLs you type yourself and no manifest can list them in advance.

The authoritative list is the permissions block in the manifest inside the package you installed — it cannot say one thing there and another here, because the browser enforces that file.

All extension data lives in your browser profile until you clear it. Backups stay in whichever account or server you sent them to until you delete them there. Enhanced chapters are cached locally for 7 days and then expire on their own. Text you sent to a hosted AI provider is retained according to that provider's policy, which we do not control.

• Clear tokens: disconnect a sync provider from Library Settings, or use "Reset Drive Auth" in the popup, to remove its stored OAuth tokens.
• Turn metrics off: the consent choice you made on first Library open is reversible at any time in Library Settings.
• Stop sending text anywhere: switch your provider to a local Ollama model, and no chapter text leaves your machine.
• Remove data: clear extension storage via your browser or uninstall the extension.

For privacy questions, open an issue on the GitHub repository.