Your data is yours. Here's the proof.
We built feed.works on a simple idea: your reading habits are nobody's business but yours. This policy explains exactly what we collect, why, and what we'll never do.
Last updated: April 2026
- We don't sell your data. Not to advertisers. Not to data brokers. Not ever.
- We don't track you across the web. No tracking pixels. No third-party analytics that phone home to Google or Facebook.
- We don't read your feeds. Workers process content you explicitly opt into, and most run privately in your browser — your content never leaves your device unless you choose to share the result. We don't scan your library for ad targeting.
- You can export everything. OPML export, anytime, no questions asked.
- You can delete everything. Account deletion removes your data. We don't keep shadow copies.
The rest of this page has the details. The lawyers can just keep scrolling.
1. What we collect
Account information. When you create an account, we collect your email address, display name, and authentication credentials. If you use passkeys (WebAuthn), we store the public key credential — never a password.
Feed data. Your subscriptions, lists, read/unread state, saved items, and any organizational structure you create. This is the core of the service.
Worker outputs. When you run a Worker (transcription, ad removal, etc.), the results are stored in your account. We don't use Worker outputs for any purpose other than showing them to you.
Usage data. We collect aggregate feature usage to improve the product — things like "how many people use search" not "what did this person search for." We don't build individual behavioral profiles.
Payment information. Handled entirely by Stripe. We never see, transmit, or store your credit card number. We receive a Stripe customer ID and subscription status. That's it.
2. What we don't collect
- Browsing history outside feed.works
- Device fingerprints
- Precise location data
- Your contacts or address book
- Content of messages outside feed.works
3. How we use your data
- To run the service. Fetching feeds, building search indexes, running Workers, storing your library. This is why the data exists.
- To improve the product. Aggregate usage patterns help us decide what to build next. We don't analyze individual reading behavior.
- To communicate with you. Account-related emails (password resets, billing receipts, security alerts). We don't send marketing emails unless you explicitly opt in. In-app messages about feed.works features (like upgrade prompts when you hit a limit) are part of the product experience, not email marketing.
4. Third parties
We use a small number of infrastructure providers to run the service:
| Provider | Purpose | What they can access |
|---|---|---|
| Stripe | Payment processing | Billing data (email, payment method, subscription) |
| AWS | Data storage and compute | Encrypted data at rest (DynamoDB, S3, Lambda) |
| Deno Deploy | Application hosting | Application code and request handling |
We do not use:
- Analytics providers that track individual users
- Ad platforms or ad networks of any kind
- Data brokers or data enrichment services
- Social login providers that report back to their platforms
A note on product messaging. You may see upgrade prompts or feature suggestions within the app — for example, when you hit a free-tier limit. These come from us, about our own product, based on your plan tier — not your reading behavior. We don't run ad platforms, and we don't scan your feeds to decide what to show you.
5. Data retention
- Active accounts: Your data is retained for as long as your account is active.
- Deleted accounts: All data is purged within 30 days of account deletion.
- Worker outputs: Retained until you delete them or close your account.
- Backups: Automated backups are encrypted and follow the same retention policy. When your data is deleted, it's deleted from backups too.
6. Your rights
- Access. Export your data anytime — OPML for feeds, plus account data on request.
- Deletion. Request full account deletion from your account settings. We process deletions within 30 days.
- Portability. OPML export is always available, free, and unlimited. Your feeds are yours to take anywhere.
- Correction. Update your account information anytime from your settings.
If you're in the EU, you have additional rights under GDPR including the right to object to processing and the right to lodge a complaint with a supervisory authority. If you're in California, you have rights under CCPA including the right to know what data we collect and the right to opt out of sale (which is easy — we don't sell your data).
7. Cookies
We use session cookies for authentication. These are functional cookies required to keep you logged in. We do not use:
- Third-party tracking cookies
- Advertising cookies
- Analytics cookies that identify individual users
8. Children
feed.works is not directed at children under 13. We do not knowingly collect data from children. If you believe a child has created an account, please contact us and we will delete it.
9. Changes to this policy
If we make material changes to this policy, we'll notify you via email at least 30 days before the changes take effect. We'll also post the updated policy here with a revised "last updated" date.
10. Contact
Questions about privacy? Email privacy@feed.works.
This policy was written to be read by humans. If something is unclear, that's our fault — email us and we'll clarify.