PageRelay Privacy Policy
Last updated: July 13, 2026
PageRelay prepares user-selected web pages and files for Kindle and e-reader delivery. The Chrome extension processes a page only after you click an explicit send action.
Data we collect
- Account email and authentication identifiers.
- Kindle delivery email, delivery preferences, and Boox Push connection status.
- For pages you explicitly send: source URL, title, detected source type, selected text, readable text, cleaned HTML, author if available on the page, and generated EPUB files.
- For files you explicitly send: filename, file type, file size, uploaded file data, public file URL when provided, and delivery target.
- For OPDS discovery: catalog URLs you connect and book or edition metadata returned by those catalogs.
- For public book discovery: topical search terms and public book metadata, publication dates, community ratings, and reading-interest signals returned by Open Library.
- Reading preferences you explicitly save and up to five recent recommendation requests. This memory can be viewed, edited, or cleared from the dashboard.
- Usage events, delivery status, billing status, and operational error messages needed to run the service.
Data we do not collect
- We do not read or store browsing history.
- We do not process pages automatically in the background.
- We do not send cookies from the browser extension.
- We do not bypass login walls or paywalls.
- We do not sell personal data.
How we use data
We use submitted page content and files to generate EPUB documents, send requested Kindle emails or Boox Push deliveries, enforce usage limits, provide billing, find books in catalogs you connect, personalize requested book recommendations, and diagnose service errors.
AI processing
For book recommendations, PageRelay sends your current request, selected filters, reading preference context, relevant OPDS catalog metadata, and normalized public book signals to Amazon Nova through Amazon Bedrock. The agent uses that data only to rank grounded catalog results; it cannot import or send a book without a separate explicit action. PageRelay does not use user content to train PageRelay-owned models.
To search catalogs you connect, PageRelay sends either your current recommendation request or up to four public candidate book titles to the search endpoint of each selected catalog. The catalog operator may process that search under its own privacy terms. PageRelay does not append saved preference notes, recent-request history, account profile data, or book contents to catalog searches.
When the agent looks for new or well-received books, it may send up to 200 characters of your current recommendation request to Open Library after removing obvious email addresses, web URLs, and UUID-shaped identifiers. PageRelay does not append saved preference notes, account profile data, catalog credentials or URLs, or book contents to that request. Avoid placing other private information in a book-search request because text not recognized by those redaction rules may be sent. Open Library returns public publication, rating, and reading-interest metadata. These signals help discovery, but a recommendation is shown as available only after a matching edition is found in a catalog you connected.
Service providers
PageRelay uses infrastructure and service providers for hosting, authentication, email delivery, Boox Push delivery, billing, storage, document preparation, and public book discovery through Open Library. These providers process data only as needed to operate the service.
Retention and deletion
Generated documents, uploaded files, and account data are retained so requested deliveries can be retried and audited. You can delete files from the dashboard and clear saved reading preferences and recent recommendation requests independently. You can also delete account data from the dashboard settings; this removes the profile, generated documents, uploaded files, delivery records, reader connections, reading memory, and usage events associated with the account.
Chrome extension permissions
The extension uses activeTab and scripting to extract the active page only after you click a PageRelay action. It uses storage to keep the explicit dashboard connection token locally. It uses tabs to read the current tab title and URL for the popup. Host access is limited to the PageRelay app and API domains for authentication and API requests. When the optional macOS native host is installed, the extension uses native messaging only to open Amazon Kindle's official Send to Kindle dialog for a file or URL you explicitly choose.
Contact
Privacy requests can be sent to privacy@cede.one.