Privacy policy

Last updated: September 20, 2026

TabTome processes pages and text you select to build an EPUB, save it on your computer, or deliver it to Kindle or PocketBook. The developer operates no processing server, receives no book content, and uses no analytics.

TabTome extension → TabTome app on your computer → your SMTP provider → Amazon or PocketBook

Data processed

When processing starts

A page is extracted only after you select a tab and start a send, or invoke the extension from the context menu. Pasted content is processed only after you paste it and issue the send command. The extension does not inspect or send tabs automatically.

Where data is sent

Prepared content moves from the extension to the installed TabTome app through a local Native Messaging channel. The browser store treats this as transmission outside the extension even though both parts run on the same computer.

When email delivery is selected, the app builds the EPUB in memory and sends an email through the SMTP account you configure. The SMTP provider receives the addresses, subject, EPUB attachment, and ordinary mail-connection metadata. The selected Amazon Send to Kindle or Send-to-PocketBook service then receives the message. Their own terms and privacy policies govern their storage and processing.

When local saving is selected, the app writes the EPUB to the configured folder on your computer and does not connect to SMTP for that book. The “email and save” mode performs both actions.

When images are included, the browser may retrieve them from the source website. That server receives ordinary network request data. Images from an open page may use the current site session; images referenced by pasted HTML are fetched without cookies or HTTP authentication.

Data the developer does not receive

The project has no developer-operated server for processing pages or EPUB files. The developer does not receive pages, books, email addresses, SMTP passwords, send history, or diagnostic logs. The extension and project website use no analytics, advertising, trackers, or telemetry.

Local storage and retention

Deleting data

Remove the Firefox or Chrome extension to delete its local settings. When uninstalling the Windows app, answer “Yes” when asked whether to remove user data. You can also delete %LOCALAPPDATA%\PageToEreaderLocal manually after closing the browser and app. Delete saved EPUB files with the normal Windows file controls from the selected folder. Use the SMTP provider, Amazon, or PocketBook controls to delete copies held by those services.

Security and limitations

Communication from the extension is restricted to the extension ID. HTML is sanitized before EPUB creation, input sizes are limited, and the SMTP password is protected with Windows DPAPI. These measures do not protect against malware already running as the same Windows user or against compromise of the email account.

Private windows

The extension does not run in private Firefox or Chromium windows. This prevents metadata from a private tab from being written to the local send ledger.

Changes to this policy

If data flows or retention periods change, this page and the date at the top will be updated. Material new types of transmission must also be reflected in the extension permissions and disclosed through the relevant browser store.

Contact

Privacy questions can be submitted through the project’s GitHub Issues. Do not post email addresses, passwords, page content, or other personal information in a public issue.