Privacy, plainly

Converting a recipe. Your recipe is sent to an AI service (Anthropic) to build the table, and comes straight back. What happens next depends on where it came from:

• A public link — the table gets a public page in the library, credited and linked to its source, and the conversion is cached so the next person doesn't pay for it twice. This is disclosed next to the input box.
• Pasted text or a photo — private. Nothing is stored unless you explicitly share, save, or report it. Photos are processed for the conversion and not kept.
• A bulk import — private, like pasted text. The links you import are converted into your own recipe box and are not added to the library, even though they are public links. If a recipe already has a library page because someone converted it the ordinary way, that page stays as it is — importing it neither publishes nor removes anything.
• The browser extension — sends the source page URL to RecipeTables. Public-link conversions work as described above. If our reader cannot read a page, the extension can send its rendered HTML, or recipe text you paste as a fallback. You can also explicitly choose to convert selected text. For image clipping, the screenshot is cropped in your browser: only the crop you preview and choose to convert is sent to our backend and Anthropic, never the full screenshot. Captured-page, pasted, selected-text and image conversions produce an unlistedtable: anyone with its link can read it, but it is excluded from the library, sitemap and search indexing. The source credit omits URL query strings and fragments. We keep the resulting table, not the captured HTML, text or image. Extension results are also saved to your recipe box when you are signed in; signed-out visitors can choose Save themselves.

Extension history. The extension can keep up to 50 recent result links and their source details locally for up to 30 days. You can clear or disable this history. It belongs to the browser profile, so other people using that profile can see it; it is not synced to your RecipeTables account and signing out does not clear it. History is neither read nor saved in private windows. Conversion and rating counters stay in the browser and are not transmitted.

Sharing."Copy link" and "Share" create a public page anyone with the URL can see. That's the point of them.

Accounts.Sign-in is handled by Clerk. We keep your list of saved tables and your unit preference. While you're signed in, tables you convert are added to that list automatically, so a refresh never costs you a conversion — they're yours and private, not published anywhere. Delete your account and the list goes with it.

Reports and feedback. Reporting a table sends me that table, your note, your email if you leave one, and — as the dialog says — the original text or photos, so the bug can actually be reproduced. Used for fixing the product, nothing else.

Newsletter. Opt-in only — an unticked box at signup, or a question you can answer no to, and no is remembered. Delivered by MailerLite, unsubscribe from any email, and your address is never used for anything else.

Analytics. Vercel Web Analytics — aggregate page counts, no advertising trackers, no selling anything to anyone.

On your device.Your theme and unit choices live in your browser's local storage. Clerk sets a session cookie when you sign in. A preference cookie remembers that you have seen the homepage introduction for one year, so it does not replay on each visit. Another preference cookie remembers recently shown public library recipes for 30 days, to keep homepage suggestions varied.

Questions about any of this: the Feedback button on the homepage reaches me directly. This page changes only when the product does.