Privacy Policy

Last Updated: August 29, 2026

1. Introduction

This policy covers the Readable Recipes browser extension and this website. The short version: there are no accounts, we don't know who you are, and the only data the extension ever sends anywhere is anonymous recipe content — never before you've seen and accepted the first-run disclosure, and you can opt out in settings anytime.

2. What the Extension Collects

Readable Recipes is free, and we use anonymous recipe data to develop and improve it. After you accept the first-run disclosure, the extension collects anonymous recipe data when you open the reader on a recipe page:

• The recipe's functional facts: title, ingredients, steps, prep/cook/total times, yield, and nutrition
• The address (URL) of the recipe page it was found on

This is used only to develop and improve Readable Recipes. We don't sell it, and no identifier of any kind travels with it — no name, no email, no account, no user ID, no install ID, no IP-based profile. Two people contributing the same recipe are indistinguishable from one.

Issue reports

If you tap "Report a problem", the extension sends the page address (without query string or fragment), the recipe name, our quality score, and the extractor's diagnostic notes, so we can fix the site. Nothing about you travels with it.

3. What the Extension Never Collects

• Your identity. There are no accounts and no personal information of any kind.
• Your browsing history. A page URL is only ever sent when a recipe was found there, the reader was opened, and sharing is on. Nothing is recorded about any other page you visit.
• Creative content. Photos, write-ups and headnotes, author names, and ratings stay on the page — they are deliberately excluded from what's shared.
• Anything you type. The extension reads recipe markup; it never reads forms or input.

4. Your Choices

• First run: before anything is ever sent, the extension shows a disclosure explaining exactly what's shared. Nothing is collected until you've read and accepted it.
• Anytime: sharing can be turned off in the extension's settings. This withdraws your consent to collection going forward, and turning it off also discards any pending, not-yet-sent data.
• Delete my local data: a one-click factory reset in settings clears every setting and any pending data on your device, returning the extension to its first-run state.

Because contributed data is anonymous, it cannot be traced back to you — which also means we cannot identify and selectively delete "your" contributions afterward. That is a deliberate trade: we can't delete what we can't attribute, and we can't attribute anything to you.

5. Data Retention

Contributed recipe data is kept for as long as it remains useful for developing and improving Readable Recipes. Entries are stored by recipe page, not by contributor, so a newer contribution of the same page replaces the older one. Issue reports are kept while we investigate the problem they describe. Data pending on your device auto-expires after 30 days, and you can clear it at any time (see "Your Choices" above).

6. Data Stored on Your Device

The extension keeps a small amount of data locally in your browser's extension storage:

• Your settings (theme, auto-open, sharing preference)
• A queue of pending contributions awaiting send, which auto-expires after 30 days
• Short-lived per-tab state (whether the reader is open), cleared when the browser closes
• A count of reader opens, used once to ask whether you'd like to rate the extension

This data never leaves your device except as described in section 2, and "Delete my local data" removes it all.

7. This Website

This website is a static site with no accounts. It sets no cookies, loads nothing from third parties, and runs no analytics. If that ever changes, this policy and the Cookie Policy will be updated before anything new loads.

8. Service Providers

Contributed data and issue reports are stored with Cloudflare (hosting and storage). Issue reports are also copied into a private GitHub issue tracker so we can act on them. Neither receives anything that identifies you, because nothing that identifies you is collected.

9. Children's Privacy

Our service does not address anyone under the age of 13, and since we collect no personal information, we do not knowingly hold personal data about anyone, children included.

10. Changes to This Privacy Policy

We may update this policy as the product changes. Updates are posted on this page with a revised "Last Updated" date, and material changes to what the extension collects will also be reflected in the extension's own disclosure before they take effect.

11. Contact Us

If you have any questions about this Privacy Policy, please contact us.