Privacy policy
Last updated: 1 November 2026
Readkave is a browser extension for reading ebooks. It is designed so that your reading stays yours: Readkave does not collect, store on servers, sell or share any personal data.
What stays on your device
- The book files you open, their covers and metadata
- Your reading position in each book
- Bookmarks, highlights and notes
- Reader settings (theme, font, layout, read-aloud voice and speed)
All of this is stored in your browser's own storage (IndexedDB and extension storage) on your computer. It is never uploaded. Removing the extension deletes it; you can also delete everything from Readkave's settings (Library → Settings → Your data).
When Readkave uses the internet
Only when you ask for something that needs it:
- Opening a book from a link (right-click → "Open in Readkave", or "From URL"): Readkave downloads that file from the site you chose. It asks for permission to access that site first.
- Define: the word you selected is sent to Wiktionary (en.wiktionary.org, run by the Wikimedia Foundation) to fetch its definition. For books in some languages (Uzbek, for now) Readkave also asks for the word's likely dictionary forms, for example kelmoq for keldi.
- Translate: uses the translator built into Chrome, which runs on your device; Readkave sends nothing anywhere. The first translation into a new language makes Chrome download a language pack from Google. When Chrome can't translate a language, the card offers a link Open in Google Translate: only if you click it, the selected text opens on translate.google.com, where Google's privacy policy applies.
- Read aloud: uses the voices installed in your browser or operating system. Some "online" voices are provided by the browser vendor; Readkave itself sends no text to any server.
- Error reports: when a book can't be opened, Readkave shows a button to send an anonymous error report. Only if you press it, Readkave sends readkave.com the kind of error and its technical message (with names, paths and links removed), where in Readkave's code it happened, how the book was opened (for example dropped or from a link, never the link itself), its format, EPUB version and approximate size, whether it has an encryption file (as books with protected fonts do), the versions of Readkave, its book engine and the browser, the operating system and the interface language. Never the book, its file name, title or contents, and nothing that identifies you. We use reports only to fix Readkave.
If you remove Readkave
When the extension is removed, Chrome opens a page on readkave.com that asks one question: why you removed it. The page address carries the Readkave version, Chrome's interface language and the kinds of errors Readkave recently met when opening books, such as "EPUB, damaged" (the format and the kind of error only, never file names). From version 1.2.3 it also carries anonymous platform and version information: the operating system, the browser family (Chrome, Chromium, Edge or Brave), whether a book ever opened and roughly how long Readkave was installed (0, 1, 2–7 or 8+ days). When the page opens, we count the removal, whether or not you answer: we store the Readkave version, the interface language, those four values and the date (day only). Answering is optional; if you answer, we store your choice, that version, that language, those kinds of errors and the date (day only). Two more questions and a note are optional too: whether you managed to open a book and, if a book wouldn't open, what kind of file it was and what happened (up to 300 characters); if you fill them in, we store them as you wrote them, so please leave out personal details. We do not store your IP address, your browser's version or user agent or any identifier, and the answer cannot be linked to you or to your books.
What Readkave does not do
- No accounts, sign-in or sync (there is nothing to sign in to)
- No analytics, telemetry, automatic crash reporting or advertising identifiers (an error report is sent only when you press its button)
- No cookies of its own
- No reading of your browsing history or of web pages you visit
Permissions, in plain words
- Storage: to keep your books and notes in the browser.
- Context menus: to add "Open in Readkave" to ebook links.
- Downloads and file access (optional, off by default): when you turn on "Open ebook files in Readkave", the extension notices when the browser is about to download an ebook and opens it in the reader instead. It never touches other downloads.
- Access to a website (optional): requested only for the specific site of a link you asked Readkave to open, at that moment.
Children
Readkave is not directed at children under 13 and, as it collects no personal data, it processes none from anyone.
Changes
If this policy changes, the new version will be published here with a new date. Because the extension collects no personal data, changes would only be to clarify wording or to describe a new optional feature.
Contact
Questions: hello@readkave.com.