Privacy

The extension keeps four things in your browser’s local extension storage: the address of the server you paired with and the device token you pasted in; a cached copy of the site configuration that server sent back; your own settings, such as which sites are paused; and a queue of reading events that have been recorded but not yet sent.

The queue exists so that what you read is written down before any network call. Closing a tab, losing your connection, or a server that is down cannot lose it.

The extension sends your reading progress to one address: the server you entered when you paired it. Each event says which site you were on, which series and chapter it detected, and when. It sends nothing to any other host, and there is no analytics, telemetry, crash reporting, or advertising of any kind in it.

Because that server is yours, where the data lives and how long it is kept is your decision, not ours.

The extension holds no site access when you install it. When you add a reading site, Chrome asks you to grant access to that one site, and it reads pages only there. On a page it does have access to, it reads the address, the link back to the series, and the title and chapter label shown on the page. That is what it needs to work out which chapter you opened.

There is one optional setting, off unless you turn it on, that lets the extension’s button appear on every site so you can add a new reading site from the page you found it on. On a site that is not one of yours, it draws that button and does nothing else: no reading, no tracking, no requests.

It does not collect your name, email address, location, contacts, health or financial information, keystrokes, mouse movement, form contents, or your general browsing history. It has no interest in pages on sites you have not added, and no access to them.

Your account password is never stored in the browser. Pairing uses a device token you create in the app and can revoke at any time, which is the only credential the extension holds.

Nothing is sold, and nothing is shared. There is no third party in the path between the extension and your server.

Disconnecting the extension from its popup erases everything it holds locally, including the token and the unsent queue. Removing the extension does the same. Data already sent to your own server is removed by you, on that server.

Questions about this policy can go to the repository this software is published from.