Privacy policy
Doomreader, on the web at doomreaderapp.com and as the Android app com.doomreaderapp. Last changed 7 November 2026.
The short version
Your books and your reading stay on your device. To improve the app, Doomreader records how it is used (which screens are opened, what is tapped, the title and author of books you add, and recordings of the screen) through PostHog, an analytics service; you can turn this off in Settings. If you have Pro, the books you add yourself and your reading data are also kept in your own cloud space, which only you can reach. If you have Pro and a username, you have a public reading profile unless you make it private: it shows what you read, including the title, author and cover of books you add yourself (unless you turn that off) and short quotes from passages you highlight, and it is listed in the app and can appear in search engines (below). If you save a web article, its link goes to our server so it can fetch the article for you; neither is kept there. If you share an article from Doomreader, our server keeps its link, title, site name and picture address under a short link, so whoever you send it to can open it. If you follow a blog or newsletter (signed in), our server keeps its feed address, which accounts follow it, and 90 days of its posts. If you ask a question about a book, an article or your library (with AI credits), the question and a few short passages go through our server to Google's Gemini to answer it; we keep none of them. If you listen with a natural voice (with AI credits), each paragraph's text goes to our server, which has Gemini read it aloud and keeps the audio, shared by everyone and not linked to you. If you have AI credits (they come with Pro and Max), we keep the credits each month gave you and what they were used on. If you keep a friend streak with someone, you and they see which days each of you reached your daily goal.
Without signing in
The books you add are saved in your browser's storage on your device, together with your reading progress in each book, your notes, the passages you highlight (including posts you mark with the heart) and the words you save (each with the sentence it was saved in), the Kindle highlights you import, what daily review has shown you, and your settings. The files themselves are never sent anywhere. Apart from the link of a web article you choose to save, the questions you choose to ask, usage analytics (which since 19 October 2026 include the title and author of a book you add), and what a public reading profile shows (each below), your library is not sent anywhere either. Clearing the app's data or uninstalling the app removes it.
Usage analytics
We use PostHog (PostHog Inc., United States) to see how Doomreader is used, so we can find what works, what confuses people and what breaks, and improve it. It runs in the app and on this website, and it collects:
- usage events: the screens and pages opened, the buttons tapped, and actions such as adding a book, reading cards (counted in batches), highlighting a post, asking a question, starting a subscription or changing a setting. For a free book from our library the event names that book; for a book you added yourself it says that it is your own book, its format (EPUB or PDF), a rough size, for a PDF roughly how many pictures it has (since 21 October 2026) and, since 19 October 2026, the title and author the book itself gives (never the file's name, and nothing when the book gives no usable title), so we can see what kinds of books people bring. When a book's Hindi is set in an old, pre-Unicode font (since 25 October 2026), the event names that font (such as Chanakya or Kruti Dev) and whether the app could read it, never any of its text. On the website's book, quote, list and guide pages, an event says which page was opened and whether a search engine sent you there (only the search engine's name, never what you searched for). On the website's free tools, an event says that a file was opened (its format and a rough size), how many books a Kindle file held and which format was downloaded, and a reading speed test's result rounded to the nearest ten words a minute; the files themselves and your highlights are read in your browser and never sent, and the converter's results are hidden in session recordings. Events never contain the text of your books, your notes, your highlights, the words you save, your questions or the answers, or the link of an article you saved (only its website's name);
- session recordings: a replay of what was on the screen and how you moved through the app, which can include the text of the book or article on screen. What you type into a field is hidden in the recording, as are your notes, your questions, your email address and the books listed from a Goodreads file you import;
- errors the app runs into, and how fast pages load;
- device and browser details (type of device, operating system, browser, screen size, language), the page that sent you to us, and your IP address, from which PostHog works out an approximate location (country and city);
- a random identifier kept in your browser's storage, so a visit can be connected with the next one. No cookie is set for this.
Once a week we add up how many cards each reader read in the week before, from these events, and publish only the totals at every fifth percentile and the number of readers, as a small public file. The app downloads it and compares your own count with it on your device, to say, for example, that you read more than 70% of readers last week (only when that is half or more, and only in a week with at least 100 readers). Your count is not sent for this.
If you sign in, these events are connected with your account (your user id, email address, name and plan), so we can see how the app is used across your devices. When you sign out, the app starts again with a new random identifier. Our server also sends PostHog a few events of its own, under your user id: when a subscription starts, renews, is cancelled or stops, with its plan, length, currency, amount and country, and when a question about a book is answered or refused, with the reason. These never contain your questions or the passages.
To stop it, open Settings in the app and turn off "Allow usage analytics". Nothing is then loaded or sent from that browser, on the app or on this website. It is also off when your browser sends Do Not Track or Global Privacy Control. PostHog keeps the data for us under its data processing agreement, and describes its handling at posthog.com/privacy.
Sharing an article
When you share a saved article from Doomreader (since 30 October 2026), the app sends our server the article's link, its title, its website's name and the address of its first picture, and our server keeps them in Google Firebase in the United States under a short link (doomreaderapp.com/app/r/ and a short code), with your user id if you are signed in. Anyone with the short link can see the title, the website's name and the picture, and open the article in Doomreader, which fetches it from its site as a saved article is fetched; the text of the article is never kept. Sharing the same article with the same title again gives the same short link. Your user id is never shown to anyone, and deleting your account removes it from the links you shared, which keep working. To stop the service being misused, the server counts how many links are shared per hour, as it does for saving articles (below), and its logs keep the site's name and a scrambled form of the link, never the link itself. Opening a shared article does not save it; tapping Save does, as any saved article.
Saving web articles
When you paste or share a link to a web article, the link is sent to our server, which fetches that one page from its site, picks out the article and sends it back to your device, where it is saved like a book. Neither the link nor the article is stored on our server. To stop the service being misused, the server counts how many articles are saved per hour, keyed by a scrambled form of your IP address (or of your user id when you are signed in), and deletes the counts after a few hours; its logs keep the site's name and a scrambled form of the link, never the link itself. The site you save from sees a request from our server, not from you. A link saved from the browser extension is the one exception to "nothing stored": see below. Since 21 October 2026 the pictures in saved articles, newsletters and followed posts are shown, fetched through our server when they come on screen, so a picture's site sees a request from our server, never your address; our hosting provider's network keeps a copy of each picture for up to a week, to serve it again, not linked to anyone, and our logs keep only counts. If you have Pro, the articles you save are kept in your own cloud space like your books (see below).
The browser extension
The Doomreader extension for Chrome and Edge saves the page you choose, or a link you right-click, to your account. To connect it you sign in to Doomreader and tap Connect; our server then gives the extension a key that can only save links (we keep only a scrambled form of the key, with your user id, the browser's name and when it was made and last used). The extension never gets your password or your sign-in, has no analytics, and reads nothing on the pages you visit. When you save, it sends that one page's address to our server, which fetches the page once to check it holds an article and keeps the address and the article's title in your account until your app takes them in and saves the article on your device, at most 30 days; it also counts how many links you saved from the extension this month, for the free allowance. The extension keeps the key, your account's email (shown in its window) and the last save's result in your browser. You can disconnect it on your account page, under Browser extension, which deletes the key at once; deleting your account deletes the keys and anything waiting.
Following blogs and newsletters
Following needs an account: since 7 November 2026 any signed-in account can follow up to 10 blogs, and up to 500 with Pro (it was part of Pro before), and what is described here is kept the same way with or without Pro. Newsletters by email (your personal newsletter address) are part of Pro. When you follow a blog or newsletter, the link you paste goes to our server, which looks for the site's feed (fetching that page and, if needed, a few usual feed addresses on the same site). Unlike a single saved article, following is kept on our server, in Google Firebase in the United States: the feed's address and name, which accounts follow it (under your user id), and when you followed it. Once a day our server reads each followed feed for everyone who follows it, and keeps the text of its new posts (public web text, one copy shared by all its followers) for 90 days after each was published, then deletes it. Your devices download the posts of the feeds you follow, and keep which posts you have read (the posts' ids and when, for 90 days) in your own cloud space so all your devices agree. A post you save, highlight or write a note on becomes one of your saved articles. Our logs keep counts, never the addresses you follow. Unfollowing stops it at once; deleting your account deletes your follows and read posts.
If you use your personal newsletter address (when it is offered), mail sent to it passes through a small mail server we run in Google Cloud, which keeps nothing and hands it to our server; the text of each email is then kept in your own cloud space for 90 days and deleted. Attachments are not kept; a picture's address is kept with the email's text, and the picture is fetched through our server when it is shown (as above). Mail to your address while you do not have Pro is not kept. If an email you send there is just a link (you forwarded a link to save it), our server fetches that one page as it does for a pasted link and keeps the article's text in place of the email, for the same 90 days; your devices then save it among your saved articles. Our logs keep a scrambled form of the link, never the link itself.
With each email we keep its way to unsubscribe (since 22 October 2026): the unsubscribe address the sender gives in the email's headers, or else the link of its own "Unsubscribe" line, and a scrambled key for that kind of email (its mailing list, or else the sender's address), kept with the email for the same 90 days. When you tap "Unsubscribe from these emails", our server sends the unsubscribe request to the sender for you, where the sender takes one that way (that request carries no information about you beyond the sender's own link); otherwise your device opens the sender's unsubscribe page or an email to the sender's unsubscribe address. We then keep that you unsubscribed from that kind of email, under your user id, so your other emails of it say so; it is deleted with your account. Our logs never keep the address, the link or the sender.
Your reading profile, following, comments and reviews
To comment you need to sign in and pick a username, which is public: it shows on your comments, and with Pro it is your page's address, doomreaderapp.com/u/your-username. We keep it, the name you choose to show, when your account was made and when you accepted the community rules, in Google Firebase in the United States, under your user id. A username needs no plan.
A public reading profile, following other readers and the Following view are part of Doomreader Pro (since 12 October 2026; they were free before). Since 20 October 2026 your profile is public from the moment you choose your username (you can tick "Make my profile private" there instead), and it is shown only while you have Pro. While it is public, anyone, signed in or not, can see the parts you chose: the books you finished and are reading, the passages you highlighted, the saved articles you read to the end, your streak and best streak, the cards you have read, and when you joined. It is listed under Readers in the app's Discover tab, where anyone can find it, and it can be shown to readers of the same free book, in that book's details in the app, when it shows you reading or having finished that book; search engines can list it. The people who follow you see the same in their Following view. Our server makes your profile from the reading you sync with Pro (your books and your progress in them, the books you finished, your highlights, your saved articles and your streak), shortly after each sync, so it is the same on all your devices; your app no longer sends a copy of it. For an article you read to the end, the server reads the start of its saved text in your cloud space to find the link you saved it from. Nothing is shown that is not already in your synced reading.
If your Pro ends, your profile goes offline within a minute and its parts are deleted from our servers; your username, your followers and the people you follow are kept, and if you renew, your profile is made again from your synced reading. Your comments stay, under your username.
This includes books you add yourself (since 12 October 2026), unless you turn off "Books I added" on the Profile and privacy page (since 20 October 2026), which leaves every book you added yourself, its passages and its cover off your profile: their title and author, and a small picture of the cover. Your app makes that picture from the cover it already keeps for your shelf, at most 200 pixels wide, and sends it to our server only while the book is on your public profile (our server cannot make it, since a PDF's cover is drawn on your device); we keep it in Google Firebase in the United States, serve it only while your profile is public and you have Pro, and delete it when the book leaves your profile or with your account. The book itself, its file and its file name are never sent. A passage you highlighted in a book you added, or in an article, shows only as a short quote of about 300 characters; the notes you add to highlights are never shown. A saved article you read to the end shows its title, its website and a link to the address you saved it from, never its text. If your profile was public before that date, it began showing them with that update.
Your notes and your Kindle highlights are never shown, nor are articles you saved but did not finish. When you make your profile private, the page goes offline within a minute, and nobody else can see these parts, which we keep only to show you your own profile while you have Pro; copies that search engines or other people already made are outside our control. You can make your profile private, turn any section off, turn off "Books I added" to hide every book you added yourself, and remove any single book, article or passage from your profile: on your profile, tap the three dots beside it and choose "Remove from profile". It stays off until you show it again from "Hidden from profile" on the Profile and privacy page. We keep which ones you removed, with your account, so all your devices agree.
If you follow someone, we keep who you follow and when, under your user id, and count your followers and the people you follow. The people you follow, and your followers, are not shown to anyone else; the two counts are, unless you hide them. Your app keeps a copy of the public profiles of the people you follow, for your Following view. Following is one way: no one is asked, and the person you follow is not told, though a dot in their app shows they have a new follower unless they turned that off. Unfollowing, or removing a follower, deletes the record at once.
Comments you post on a passage of a free book are public: anyone can read them, with your username. We keep each comment, the book and the place it is on (with short fingerprints of the passage's text, never the text itself), when it was posted and edited, the language of your app, who liked it, and any reports about it. We count how many comments each account posts per minute, hour and day, to stop spam. When you delete a comment, its text is deleted; if it has replies, a marker that it was deleted stays so the replies keep their place. If you report a comment, it is hidden from you at once, and we keep the report and the reason; the person you reported is not told who reported them. We review reported comments by hand and may hide or delete comments, or stop an account commenting, under the community rules in our terms; a comment reported by three people is hidden until we review it, and its author sees why. We may in future use an automated check to help find comments that break those rules; this page will say so before we do.
Book reviews (since 21 October 2026) are public too: anyone can read them, with your username, in the book's details in the app, on your public profile while it is public and you have Pro, and, for our free books, on the book's page on our website, where search engines can list them. We keep each review's stars, its words if you write any, whether you marked it as having spoilers, the book it is about, the language of your app, when it was posted and edited, and any reports about it, in Google Firebase in the United States, under your user id. For a free book, the book is its catalogue entry. For a book you added yourself, it is the free book its text matched, or, if you turned comments on for it, its fingerprint's match (below), or else its title and author, which you send with the review and which are shown with it: the review sheet says so before you post. The book itself and its file are never sent. We count how many reviews each account posts per minute, hour and day, to stop spam. Deleting a review deletes it at once, and deleting your account deletes all your reviews. If you import your Goodreads library, your ratings and reviews stay on your device unless you choose to post your ratings of free books as reviews after the import; only then are they sent, with the words of your Goodreads reviews. Reports, blocks, the review of reports and a review being hidden after three reports work as for comments, under the same community rules.
If you open a book you added yourself and it is the same text as one of our free books, the app can tell this on your device, by comparing short fingerprints of its sentences with the free book's, which it downloads like a cover. If you choose to see that book's comments, you see and post in the free book's comments; nothing about your own file is sent to us.
For other books you added, you can turn on comments per book. Your device then sends us a fingerprint of the book: 64 numbers made from the first words of its sentences, from which the text cannot be rebuilt, and the book's language. We use it to connect you with readers of the same book and keep it with your account while comments are on for that book. For these comments we do not receive the book, its text, its file name or, unless you add it, its title (your public profile, above, is separate: it shows the title of books you add while it is on). Turning comments off for the book, or deleting your account, removes you from it.
Friend streaks (since 26 October 2026) need a username but no plan. A friend streak is seen only by the two people in it, never by anyone else and never on a public page. While you have one (or have sent an invite or made an invite link), your app sends our server, on opening and when you reach your daily goal, which of your last three days reached your goal (the dates only, never how many cards you read) and your time zone; we keep the dates of the last 14 days you reached your goal, with each friend streak you have, so the server can count the days you both reached and both of you see the same number. Your friend sees which days this week you reached your goal, whether you have reached it today, your username and the name you show; you see the same of theirs. We also keep who invited whom and when, when it started, its current and best count, a nudge (when it was sent and on which of your days, shown once in their app; no email or notification is sent), and who ended it. An invite link works for 14 days, and anyone you give it to can see your username and name and accept it; we count how many invites you send each day, to stop spam. Ending a friend streak deletes it after the other person has been told once (or after 30 days); deleting your account deletes all of yours and your days.
If you block someone, we keep that, so they can no longer see your profile in the app, follow you or reply to your comments, you no longer see their comments, and any following or friend streak between you ends (a friend streak ends without them being told), and neither of you can invite the other. They are not told, but your public page stays readable by anyone who is signed out. If you report a profile, we keep the report and the reason; the person you reported is not told who reported them. A profile reported by several people may be made private until we review it, under the community rules in our terms.
Asking about a book, an article or your library
Signed in, you can ask a question about the book or article you are reading, or about your whole library, using AI credits. The app picks a few short passages that may hold the answer on your device (never a whole book or article; for your library, from the search index each book has on your device and from your saved articles) and sends them, with your question and, for one book or article, its title and author, to our server, signed in as you. Our server sends them to Google's Gemini API, which writes the answer, and the answer comes back to your device. We use Gemini's paid service, not its free one, whose terms let Google use what is sent to improve its products. Our server does not store your question, the passages or the answer. It keeps, under your user id, the credits each question used, and how many questions you asked today and this minute (to stop a runaway button spending your credits); its logs keep the number of words used (in tokens), never what was asked, with a scrambled form of your user id.
If you speak a question instead of typing it, the app uses your browser's own speech recognition. Some browsers, such as Chrome, send the sound to their maker's servers (Google, for Chrome) to turn it into text; that is the browser's service, not ours, and we never receive the sound. If the answer is read aloud, your device's voices read it, as for listening (below).
Podcasts
Since 21 November 2026 you can follow podcasts and play their episodes in Doomreader. Following one needs an account, with or without Pro. When you follow a show, the link you paste goes to our server: a show's feed is fetched from its address, and an Apple Podcasts link is first looked up with Apple's public podcast directory (our server asks Apple for the show's feed; nothing about you is sent). Our server keeps, in Google Firebase in the United States, the show's name, host, picture and list of episodes (their titles, dates, lengths and audio addresses; one copy shared by everyone who follows it), which accounts follow it (under your user id) and when you followed it, and reads the feed again every few hours while anyone follows it. When you play an episode, your device fetches its audio directly from the address the show's feed gives, as any podcast app does: that is the show's own host, and sometimes a measurement service the show uses (named in that address), and they see your device's IP address and that this episode was played, under their own privacy policies. The audio never passes through our server, and we never keep it. Show pictures are fetched through our server, as articles' pictures are. Where you are in each episode is kept on your device; with Pro it is also kept in your own cloud space so you can go on on another device. Unfollowing stops it at once; deleting your account deletes your follows.
Transcripts (since 22 November 2026, with Pro): when you open an episode's transcript, the app asks our server for it, signed in as you. If the show publishes a transcript in its feed, our server fetches it from the address the feed gives. Otherwise, if you agree to the price in AI credits, our server downloads the episode's audio from the show's address and has Google's Gemini API (its paid service) turn it into text with the time of each word; only the audio is sent, nothing about you. Either way the transcript is kept on our server, in Google Firebase in the United States, once for each episode, not under your account; it is never published and is shown only to readers with Pro (an AI one only to readers who paid for it). Under your user id our server keeps the credits it cost and, while one is being made, that you are waiting for it. Your highlights and notes on a transcript's lines are kept on your device; with Pro they are also kept in your own cloud space, like your other notes. Sharing a line shares only that line, with the episode and show named.
Natural voices
Listening with your device's voices happens on your device, except for voices your browser marks as online: Chrome's Google voices, which the app picks first where Chrome offers them, are Chrome's service, and Chrome sends the text being read to Google to speak it (that is the browser's service, not ours, and we never receive it). Pick another voice under Aa to keep listening on the device. If you choose a natural voice instead, the app sends the text of each paragraph as it comes up (and the next few, about a minute ahead), with the voice's name and the book's language, to our server, signed in as you, using AI credits. Our server has Google's Gemini API (its paid service) read the paragraph aloud and keeps the audio, in a private Google Cloud Storage bucket in the United States, under a code made from the voice and the text, not under your account. The same paragraph in the same voice is the same audio for everyone, so it is made once and kept; we do not delete it automatically. The text of books you added yourself can therefore be kept on our server as audio, without any link to you. Your device downloads the audio through a link that works for a few minutes and keeps it, so hearing it again sends nothing. Our server keeps, under your user id, the credits used and the words read aloud not yet charged; its logs keep the number of words and the voice, never the text.
Free books and the discover feed
The free books (public-domain classics from Standard Ebooks, Project Gutenberg and Wikisource) are fetched from our own storage on Google Cloud Storage: the list of books in the languages you chose (in every language if you sync, so the app can tell a free book from your own), short excerpts, covers and, when you choose to read or add one, the book itself. These are plain downloads of public files, the same for everyone, with no account, cookie or identifier attached. As with any download, Google's servers see your IP address and browser details.
To keep the discover feed fresh and a little closer to your taste, the app remembers on your device which excerpts you have seen (the most recent few thousand) and a small score for the authors and genres you read on or add. This is worked out on your device and is not sent anywhere, unless you have Pro, which syncs it.
If you have Pro
Sync is optional. You sign in with your Google account, in which case Google tells us your name, email address and a user id, or with an email address and a password, which Firebase keeps only as a secure hash that we cannot read. To confirm an email address, we send it one link; we send nothing else unless you ask for a password reset. From then on these are stored in Google Firebase, in the United States, under your user id:
- the book files you add (EPUB and PDF), with their title, author and size; for a free book, only its title, author and size, since its file is the public copy in our own storage and your other devices download it from there;
- the web articles you save: their text, title, site, author, date and link (and their pictures' addresses and the links in their text, not the pictures; an emailed newsletter you save may have no link of its own);
- your reading progress in each book and article (where you are, and the furthest point you have read), and when you last read it;
- the posts you highlight with the heart, including the passage (up to 1,000 characters);
- your discover history and preferences: which free book excerpts you have seen, the scores for the authors and genres you read on or add, and the genres you chose for discover, so the discover feed is the same on all your devices;
- the blogs and newsletters you follow, which of their posts you have read, how far you are in the posts you read without saving them (since 24 October 2026, each kept at most 90 days), and the emails sent to your newsletter address (see "Following blogs and newsletters" above; since 7 November 2026 the blogs you follow and what you read of them are kept for any signed-in account, with or without Pro, and the emails with Pro);
- your notes, with the passage each one is on (a note you delete is wiped, leaving only a marker that it was deleted, so your other devices delete it too);
- the passages you highlight in a book (the text, your note on it, where it is in the book, and short codes made from the paragraph's words so it can be found again; a highlight you remove is wiped, leaving only a marker), and the words you save (the word, the sentence it was in, and where; never a definition);
- the Kindle highlights you import: each passage, your Kindle note on it, the book's title and author as Kindle names them, and its page and location (a highlight you delete is wiped, leaving only a marker that it was deleted, so importing the same file again does not bring it back);
- daily review's record of each note and highlight it has shown you: how often you kept it, when it comes back, and whether you archived it (no text);
- your reading habit: the cards read on each day, your daily goal and the days it changed, any day you mended a streak, the badges you earned and your records, the quests you finished, the books you finished (their titles), cards read and time spent reading by month, and the cards read in each book by month with its title, author, language and genre (no book text);
- your preferences, each with when you chose it, so they are the same on all your devices: listening speed, the app's language, the languages of the free books, how often discover cards show, progress moments, whether words you look up are saved, how many items daily review brings and which kinds, and the order of an author's books. Settings about your screen (card size, text size, font, colours, theme), your listening voice and whether usage analytics is allowed stay on each device and are never sent;
- where you are in each podcast episode you played, and whether you finished it (since 21 November 2026; the shows you follow are kept for any signed-in account, with or without Pro, see "Podcasts" above);
- your highlights and notes on the lines of podcast transcripts (since 22 November 2026, see "Podcasts" above);
- whether your account has sync switched on.
They are used only to keep your library the same on all your devices. They are not shared, sold or used for advertising. Security rules let only your signed-in account read or change them. Everything travels encrypted.
Firebase, which runs sign-in and storage for us, also receives your IP address and browser details when you sign in or sync, as any web service does. Google acts on our behalf here and describes its handling at firebase.google.com/support/privacy.
Deleting your data
Removing a book or an article removes it from the cloud as well as from your device. Your notes on it are kept, since they are your own writing, until you delete them, which removes them from the cloud too. To delete your whole account and everything stored with it, open the account button in the app and tap "Delete my account"; it is deleted at once. That also deletes your browser extension's keys and any links it saved that were waiting, your reading profile (with the cover pictures of books you added and the list of items you removed from it), your username (which someone else may then take), your blocks, who you follow and who follows you, your friend streaks, invite links and the days kept for them, and your comments (a comment that has replies is replaced by "Comment deleted").
Payments
Doomreader Pro and Max are bought on our website's pricing page. The payment is handled by Razorpay (Razorpay Software Private Limited, India), our payment processor: you enter your card or other payment details in Razorpay's own payment window, and we never see them. Razorpay tells us about each payment: the plan, the amount, when it renews or ends, whether the card was issued outside India, and the country of the card when it says so. Before you pay we ask where you live, the country and, in India, the State, because tax law requires it on the invoice we issue; it also decides whether you pay in rupees or US dollars. We keep these payment records, and the invoices (with your account id), for as long as tax law requires, even after an account is deleted. AI credits come with the plan each month: we keep the credits each month gave you and when they expire (two months after), and what you used them on (asking, natural voices) without any of the text, under your user id. Deleting your account deletes your credits; the payment records and invoices stay, as above. Razorpay's own handling is described at razorpay.com/privacy.
When you open the pricing page, where Pro and Max are bought (from the website and from the Android app alike, which opens it in Chrome), it asks our server which prices to show. The server works out your country from the request itself, to choose rupees or US dollars, and writes only that country in its log; nothing else is kept. Your account page shows no prices and asks for none.
Feedback and sharing
If you send feedback from the app, we store what you send so we can read it and answer it: your message, the email address you give for a reply (if any), and, if you leave "Include device details" ticked, the app's version, your browser's user agent, your screen size, whether you use the Android app or a browser, and your theme and feed look. You do not need to be signed in, and nothing else about you or your books is attached. It is kept in Google Firebase in the United States, where only we can read it, and deleted when you ask at privacy@doomreaderapp.com. Emailing us instead works just as well.
When you import Kindle highlights, the file you choose is read on your device; it is not sent anywhere (with sync on, the highlights are stored as described above).
When you import your library from Goodreads, the file you choose is read on your device and never uploaded. Only the free books it matches, which books you finished and on what day (and which of them came from the import, so badges count only reading done in the app), and a "Want to read" shelf are kept, like any other books in your library (and, with sync on, stored as described above); your ratings, reviews and notes from the file are not kept.
When you export your notes (as Markdown, text, or a zip for Obsidian or Notion), the file or text is made on your device and goes only where you send it through your phone's own share sheet, or into your downloads; we are not told.
When you share a passage as an image or share the app, the image is made on your device and goes only where you send it through your phone's own share sheet; we are not told.
When you share an EPUB or a PDF to Doomreader from another app (since 26 October 2026), it goes from that app to Doomreader on your device and is added like a book you choose yourself; it is not uploaded. We are told that a share arrived, how many files it held and how many were books, and that a book you add came this way, never the files' names.
Your rights, wherever you live
These apply to everyone, and include your rights under the EU and UK GDPR, India's Digital Personal Data Protection Act and similar laws. You can ask to see the data we hold about you, have it corrected, get a copy to take elsewhere, have it deleted, or object to how it is used. Deleting your account in the app does most of this at once; for anything else, email privacy@doomreaderapp.com and we answer within 30 days. If you think we have got something wrong, you can also complain to your local data protection authority.
Why we may use your data: to provide the sync you signed up for and the subscription you bought (performing our contract with you); to keep invoices and order records, which tax law requires (legal obligation); to fetch an article you ask us to save and to answer a question you ask about what you are reading (your request); to read and answer feedback you choose to send (your consent, which you can withdraw by asking us to delete it); to keep the service secure and stop abuse, such as the hourly count of saved articles (legitimate interest); and to understand how the app is used and improve it, through usage analytics, which you can turn off in Settings (legitimate interest). Nothing is used for advertising, and we do not sell data.
Where it is kept: Google Firebase stores synced data in the United States. Google processes it for us under its data processing terms, which include the EU Standard Contractual Clauses for transfers out of Europe. PostHog stores usage analytics in the United States and processes it for us under its data processing agreement.
Children
Doomreader is not made for children under 13.
Changes and contact
If this policy changes, the date at the top changes too. Questions go to privacy@doomreaderapp.com.