Privacy.
Short version: we do not keep your data on our own server, and we do not sell it. That is the whole policy. The rest is detail.
Your email
We have your email only if you handed it over yourself, either for the free pack or with a question. Letters are sent through Resend, and the address itself is stored there too. It is used to send you letters from the house. Every letter has an unsubscribe link. Use it and the letters stop. If you want the address erased completely, write to [email protected] and we delete it.
If you left an email with a question, it is optional, and it is used for one thing: answering you.
Downloads
The free pack does not ask you to register. No account, no form standing in the doorway.
Tracking
There are no advertising trackers and no cookies here. You will not see a cookie banner, because there is nothing for you to accept. If we use site analytics, it counts visits anonymously, with no personal data attached.
Contact
Questions about any of this, or a request to delete something: [email protected]. A person reads it.
Online EPUB Reader
The rest of this page is the privacy policy of Online EPUB Reader, our free reading app, written in the terms Google asks for. It covers both places the reader runs: the Chrome extension from the Chrome Web Store, and the web reader at app.readinside.com, which is the same reader opened in a browser tab without installing anything. Effective date: August 26, 2026.
Short version, same as above: your books stay in your own browser, on your own device, and we never see them.
What the reader is
Online EPUB Reader opens and reads e-books in a browser tab. Your books, reading positions, notes and settings live in your browser's own storage on your own device.
Neither form has a developer server behind it. There is no account, no sign-up, and no library of yours kept anywhere but your own browser. The extension makes no network calls of its own at all. The web reader is a set of static files, and it speaks to exactly one outside address, Google's own, and only in the one case described below.
Permissions the extension asks for
storage: keeps your library, reading positions and settings on your device.unlimitedStorage: e-books are large files, and the local library needs more than the default storage quota.
The extension requests no other permissions. It cannot read your browsing history, your other tabs, your email, or any account of yours.
Opening a book from Google Drive
The web reader can be listed in Google Drive's Open with menu, so that an EPUB sitting in your Drive opens in the reader with one click. This is the only feature that involves an account of yours, it is entirely optional, and nothing happens until you ask for it: you click Open with and then the reader on a file in your own Drive, and then press the button on the card the reader shows you. If you never do that, no Google account is ever touched.
When you do, Google asks for your permission on its own consent screen, and the reader receives a temporary access token, never your password and never a password of any kind. The token is held in the tab's memory for the length of that visit and is written to no storage. Closing the tab discards it.
Two permissions are requested, and they are the narrowest Google offers for this:
drive.file: see and download only the file you opened. This permission cannot list your Drive, cannot search it, and cannot reach any other file in it. Google grants it per file, at the moment you choose that file yourself.drive.install: the permission that puts the reader in the Open with menu in the first place. It grants no access to any file or to any content of yours, and exists only so that the menu entry can appear.
With that token the reader makes exactly two requests, both to www.googleapis.com, Google's own address: one for the file's name and size, and one for the file itself. The book travels straight from Google into your browser tab, then into your local library, exactly like a book you added from your own disk. It does not pass through any server of ours, because there is none, and no part of it, not the name, not the contents, not the fact that you opened it, is ever sent to the developer or to anyone else.
You can take the permission back at any time, without uninstalling anything, at myaccount.google.com/permissions.
What the reader collects
Information you provide directly. None, unless you choose to write to us. The reader has no accounts, sign-ups, or logins, and it never asks for your name, email address, phone number, mailing address, payment information, or any other personal detail. If you send feedback by email, we receive what you send and use it only to reply and to improve the product.
Information collected automatically. None. The reader sets no cookies and uses no tracking pixels, web beacons, or similar technologies. It does not log your IP address, device or browser details, location, or how you use it.
Information from third parties. None. The developer does not buy, receive, or combine any information about you from data brokers, advertisers, social networks, or any other outside source.
The only content the reader ever reads is the books and pages you yourself add to the library, from your disk or from your Google Drive when you choose a file there yourself, and it reads them only to display them to you.
What the reader stores
- The books and files you import into the library, with their covers and metadata, and your reading positions, kept in your browser's own storage on your device.
- Your notes, highlights, reading diary, and the pages you save to read later, kept the same way.
- The settings you choose (theme, font, layout), kept the same way.
- Nothing else. Nothing is stored on any developer server, because there is no developer server. A Google Drive access token, if you ever ask for one, is held in the tab's memory for that visit only and is written to no storage at all.
The preferences you set are used only to remember your own choices between sessions. Nothing is used for advertising, profiling, credit or lending decisions, or any purpose other than providing the feature you requested.
Sharing
The reader does not share, sell, rent, transfer, or disclose your data, including your books, notes and the preferences you save, to anyone. There are no business partners, affiliated companies, advertisers, or data brokers involved, and your data would not change hands in any sale or merger, because the developer never receives or holds it in the first place. The web reader contacts two outside addresses, and neither one is given anything of yours: Google's, when you yourself choose to open a file from your own Google Drive, which is your browser asking your own account for your own file; and the developer's own visit counter, described under Analytics below, which is told which page you opened and nothing at all about the book on it. The only conceivable exception is a valid legal order, and as the developer keeps no copy of your data, there is nothing to produce.
Google's Limited Use requirements
Online EPUB Reader's use of information will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Online EPUB Reader's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Concretely: the file you open from Google Drive is used for the one purpose you asked for, displaying it and placing it in your own local library. It is transferred to no one, it is never sold, and it is never used for advertising or for any purpose you did not request.
In particular, Online EPUB Reader does not use any artificial-intelligence or machine-learning model or service, whether the developer's own or a third party's, and it does not transfer, sell, or use user data, whether raw, aggregated, or derived, to create, train, or improve any artificial-intelligence or machine-learning model. The reader only does what you ask of it, opening and displaying the books and pages you add, and no content of yours ever leaves your device.
Keeping and deleting your data
The reader keeps your data for as long as you keep it: books, positions, notes and settings stay in your browser's own storage until you delete them. You can remove any book from the library at any time. Uninstalling the extension from chrome://extensions erases its library, positions, notes and settings along with it, and on the web reader, clearing the site data for app.readinside.com in your browser does the same. Because the developer keeps no copy of your data, there is nothing on the developer's side to request deletion of.
Your books and notes always stay under your control on your own device: export your notes at any time from the notebook, remove books from the library, clear the storage to erase everything, and withdraw the Google Drive permission whenever you like. If you live in the European Economic Area, the United Kingdom, or another region with data-protection rights, those rights apply to any personal data a company holds about you. Since the developer holds none, please still feel free to write with any question.
Legal basis, borders, children
To the limited extent any data is processed at all, namely the library you build and the preferences you choose, the legal basis is your consent, given when you install or open the reader and use it, and the performance of the feature you requested. Your library crosses no border, because it is not collected or stored outside your own device. The anonymous visit count described under Analytics is handled on the developer's own server, which may stand in another country, and it carries nothing that identifies you or names anything you read. The reader is a reading tool intended for general use. It is not directed at children under the age of 13 (or under 16 in the European Economic Area), and it does not knowingly collect personal information from children.
Analytics and third-party code
The extension contains no analytics of any kind. The web reader at app.readinside.com counts visits, with Umami running on the developer's own server. It records which page was opened, without the query string that address may carry, the page that sent you there, and the coarse facts every web request carries anyway: browser, operating system, screen size, and country. It sets no cookie, keeps no IP address, builds no profile, and follows you to no other site. Nothing from your library reaches it: not a book, not a title, not a file name, not a Google Drive file identifier, and not the page you are on inside a book. You will not see a cookie banner, because there is nothing for you to accept.
Neither the extension nor the web reader uses Google Analytics or any other third-party analytics service to observe how you use it. The reader contains no third-party plug-ins, social-media widgets, or advertisements. The one third-party code it ever loads is Google's own sign-in library, and only on the web reader, only to show you Google's consent window when you have asked to open a file from your Drive. What Google does with your account is governed by Google's privacy policy, not this one.
How your data is protected
Your books, notes and settings are stored by your own browser, on your own device, under your operating-system account, and are never sent to the developer or to any external server. No method of electronic storage can be guaranteed to be perfectly secure, but the reader stores and transmits nothing outside your browser, apart from the anonymous visit count described above.
Changes, and where to write
If this policy changes, the update will be posted on this page with a new date. The terms of service are at readinside.com/terms. Questions about the reader: [email protected].
Last updated: August 27, 2026