RecipeTables.

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:

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 via Buttondown, unsubscribe anytime, and your address is never attached to anything else unless you tick the box that says so.

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. That's the whole cookie story.

Recipe sites. Library tables credit and link their sources. If you run a recipe site and want an entry removed: — it comes down promptly, no questions.

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