Overview
ReadBack is built by an independent developer and designed around one principle: the extension should know exactly as much as it needs to help you resume reading — and nothing more. It does not require an account, does not run a backend server, and does not phone home. Every saved page, note, and statistic lives inside your own browser's local storage.
Saving a page is always something you choose to do — either from the popup or the right-click menu. ReadBack does not automatically track or save pages you haven't explicitly saved, so your library only ever contains what you put there.
Data ReadBack stores
When you save a page, ReadBack records the following, so it can rebuild your reading position later:
| Item | Purpose |
|---|---|
| Page URL & title | To identify and relist the saved page |
| Website favicon | Displayed in your Reading Library for quick recognition |
| Scroll position & saved paragraph | To scroll you back and highlight where you left off |
| Reading progress | Powers progress bars and completion status |
| Reading time & session info | Used for Statistics, Streaks, and Timeline features |
| Notes, folders, favorites | Organizational data you create yourself |
All of the above is stored using Chrome's built-in storage API, scoped to your browser profile. None of it is transmitted anywhere.
Permissions, explained
Chrome requires extensions to declare permissions up front. Here's what ReadBack asks for and why — nothing is used beyond this stated purpose.
Stores saved pages, reading progress, notes, folders, favorites, streaks, and settings locally in your browser.
Lets ReadBack read the current tab's content only at the moment you explicitly click Save Page — never in the background.
Schedules routine statistic updates and light maintenance tasks (e.g. recalculating streaks) — no network activity involved.
Adds a "Save Page" option to Chrome's right-click menu as a shortcut to the same save action available in the popup.
Used solely to locate and restore your saved paragraph on pages you've chosen to save — not to monitor browsing on other sites.
What ReadBack doesn't collect
Everything stays local
ReadBack has no backend server. There is nowhere for your data to be uploaded to, because no such destination exists in the extension. Uninstalling ReadBack, or clearing your browser's extension storage, permanently removes all saved data — there is no copy retained anywhere else.
We never sell or share your data
ReadBack does not sell, rent, trade, or share your reading data with any third party, advertiser, analytics provider, or data broker — under any circumstance. There is no monetization model built around your data; ReadBack does not display advertisements.
Your rights and control
Because everything lives in your own browser, you're always in full control:
Future features
Some planned features — such as cloud sync, optional Google authentication, or a premium subscription — are not part of this version. If any feature that involves transmitting data off your device is introduced, this policy will be updated first, and the feature will require your explicit opt-in.
Children's privacy
ReadBack is not directed at children and does not knowingly collect information from anyone. Since the extension collects no personal identifiers and requires no account, there is no mechanism by which a child's identity could be determined or stored.
Changes to this policy
If this policy changes — for example, when a future version introduces optional cloud features — the "Last updated" date at the top of this page will change, and material changes will be clearly noted here before they take effect.
Contact
Questions about this policy or how ReadBack handles data are welcome any time.