Last updated: May 8, 2026

This policy covers both the RSS to Kindle web application at rsstokindle.com and the RSS to Kindle Chrome extension. It describes exactly what data we collect, how we use it, where it is stored, and which third parties receive it.

Single purpose. RSS to Kindle exists to send articles you choose — either from RSS feeds you subscribe to or from the page open in your browser — to your Kindle as an EPUB email attachment, and to optionally show your own Kindle highlights. We do not use your data for advertising, we do not sell or rent your data, and we do not share your data with anyone except the service providers listed below who are required to process it solely to deliver the service.

Data the web app collects

When you create an account on rsstokindle.com we collect and store:

• Account identity — your email address, first/last name (if you provide them), and profile image (optional). Sign-in is handled by Clerk; for OAuth sign-in (Google) we also receive the OAuth identifier Clerk returns.
• Your Kindle email address — the @kindle.com address you enter so we can deliver EPUBs to your device.
• Feed subscriptions and preferences — the RSS feed URLs you add, digest schedule, and per-feed settings.
• Send history — a record of which articles we have already emailed to your Kindle so we don't send duplicates, including article titles, source URLs, and timestamps.
• Product analytics — pseudonymous events (page views, button clicks, errors) collected via PostHog and basic traffic metrics via Vercel Analytics. Not sold and not used for advertising.

Data the Chrome extension collects

The extension only collects data in response to a deliberate action you take inside it:

• Active tab URL, page title, and page HTML — read only when you click the extension's “Send to my Kindle” button. The HTML is sent over HTTPS to our backend (Convex) so the article extractor can isolate the readable content, build an EPUB, and email it to your Kindle address via Resend. The source HTML is processed transiently for that single request and is not retained after the email is sent.
• Your Kindle library and highlights from read.amazon.com/notebook — read only when you open the extension's “View Kindle highlights” page while you are signed in to Amazon. Book titles, authors, ASINs, and highlight text are scraped from the page you already have access to and displayed back to you locally inside the extension. This highlight data is not uploaded to our servers.
• Sign-in session — Clerk session cookies and a session token stored via chrome.storage so the extension stays signed in and can authenticate requests to our backend.

The extension does not read tabs in the background, does not track your browsing history, and does not collect form input, passwords, financial information, health information, personal communications, or any data unrelated to the article-sending and highlights features described above.

Why each Chrome permission is required

• activeTab — lets the extension read the URL, title, and HTML of the tab you are currently viewing, and only after you click the toolbar icon.
• scripting — runs a one-shot script in the active tab to capture the page's HTML so the article can be extracted, and to read the Kindle notebook page when you open the highlights view.
• storage — stores your Clerk sign-in session locally in the browser so you don't have to sign in every time you open the popup.
• cookies — required by Clerk to read its own session cookie from rsstokindle.com (or the Clerk sync host) so signing in on the website also signs you in inside the extension.
• Host permissions for read.amazon.com, the Convex backend, Clerk, and rsstokindle.com — needed so the extension can scrape the Kindle notebook page (when you open the highlights view), call the backend that extracts articles and sends EPUBs, complete sign-in against Clerk, and link out to your account on the web app.

Limited use of user data

Consistent with the Chrome Web Store Limited Use requirements, we use data the extension handles only for the user-facing features described above (sending the open page to your Kindle, and displaying your own Kindle highlights back to you). We do not transfer this data to third parties for advertising, we do not use it for credit or lending purposes, and humans do not read it except (a) with your explicit consent, (b) for security investigations, or (c) when required by law.

Third parties that receive your data

We use the following service providers to operate RSS to Kindle. Each receives only the data needed to perform its function and is contractually limited to processing it on our behalf.

• Clerk (clerk.com) — authentication and session management. Receives your email, name, profile image (if any), OAuth identifiers, and authentication events.
• Convex (convex.dev) — our backend database and serverless functions. Stores your account record, Kindle email, feed subscriptions, and send history, and processes article HTML transiently when you send a page from the extension.
• Resend (resend.com) — transactional email provider that delivers the EPUB attachment to your Kindle email address. Receives your Kindle email address, article title, and the EPUB file at the moment of delivery.
• Amazon (read.amazon.com / @kindle.com) — the destination of every EPUB email. Amazon receives the EPUB and your Kindle email address as the email recipient.
• PostHog (posthog.com, US region) — product analytics for the web app. Receives pseudonymous event data (page paths, button clicks, error stacks). Does not receive article contents or Kindle email addresses.
• Vercel (vercel.com) — hosts the web app and provides basic traffic analytics. Receives standard HTTP request metadata (IP, user agent, referrer, path).

We do not use any third-party advertising, retargeting, or data broker services.

Where data is stored

Account data, feed subscriptions, send history, and analytics are stored on servers operated by Convex, Clerk, PostHog, and Vercel in the United States. Kindle highlights you view in the extension stay on your device and are not uploaded.

Data retention

We keep your account data for as long as your account is active. Article HTML sent from the extension is processed only for the duration of the request and is not stored after the EPUB is emailed. Send-history records are retained so we can avoid sending you the same article twice. You may request deletion of your account and all associated data at any time by emailing the address below; we will delete the data within 30 days, except where retention is required by law.

Your choices and consent

You control whether the extension collects any page data: nothing is read until you click “Send to my Kindle” or open the highlights view. You can sign out at any time, you can uninstall the extension to revoke its permissions, and you can update your Kindle email or feed list from the dashboard. For analytics, we honor the browser's Global Privacy Control / Do Not Track signal where supported.

Children's privacy

RSS to Kindle is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us and we will delete it.

Changes to this policy

We may update this policy from time to time. Material changes will be reflected here with a new “last updated” date. Continued use of the service after an update constitutes acceptance of the revised policy.

Contact

Questions, deletion requests, or other data requests — email martyamark@gmail.com.