Privacy policy
Last updated November 19, 2026
Card to Table is a small app for keeping and sharing family recipes. This page explains, in plain words, what it stores about you, who helps run it, and how to get your data deleted.
What we keep
- Your account: your email address, and the name and profile picture Google shares if you sign in with Google. Your name is shown to people in your family groups and on recipes you share.
- Your recipes: everything you type, paste, scan or import, including photos (the dish photo and, if you choose to keep it, the original scanned card).
- Family groups: which groups you belong to.
- Ratings and shares: stars and reviews you leave, and counts of how often recipes are shared or opened from a public link. Opens by people who aren't signed in are counted without knowing who they are.
- Scan records: for each scan, the type (photo, text or link), whether it worked, how long it took and how much processing it used. These records never include the photo or text itself.
Who can see your recipes
- Private recipes and their photos: only you.
- Family recipes: members of the family group you chose.
- Public recipes: anyone with the link, and signed-in users in Discover. Making a recipe Private again stops its link working.
Photos are stored privately and shown through short-lived links to people allowed to see the recipe.
Who helps run Card to Table
- Supabase stores the database, sign-ins and photos (in the United States).
- Vercel hosts the website.
- Anthropic reads a photo, pasted text or web page when you ask Card to Table to scan or import a recipe, and sends back the recipe. Nothing is sent to Anthropic unless you scan, paste or import. Under Anthropic's commercial terms, what we send isn't used to train their models.
- Google handles "Continue with Google" sign-in and shares your name, email and profile picture with us.
- Sentry receives error reports when something breaks: what went wrong, which page, and your account's ID number. Not your recipes, name or email.
- PostHog counts how Card to Table is used: pages opened, and when someone scans, imports, shares, rates or exports a recipe, linked to your account's ID number. No recipe text, names, emails or IP addresses, no recordings of your screen, and no cookies.
When you import from a link, our server visits that web page to read the recipe.
What we don't do
- We don't sell your data or share it with advertisers.
- We don't show ads.
- We don't use your recipes or photos to train AI models.
- We don't track you on other websites.
Cookies and offline copies
Card to Table uses cookies to keep you signed in, and a one-day cookie so a public recipe link opened twice in a day counts once. There are no advertising or tracking cookies.
So recipes work without a connection, your browser keeps a copy of recipes you open, on your device only. Signing out deletes those copies.
Deleting your data
You can delete any recipe and its photos at any time from the recipe page. To delete your whole account and everything in it, email dashenfelder@gmail.com from the address you sign in with, and we'll delete it within 30 days. Recipes you saved a copy of from someone else are yours to keep or delete; copies others saved of your recipes belong to them.
Children
Card to Table isn't meant for children under 13, and we don't knowingly collect their information.
Changes
If this policy changes, we'll update this page and the date at the top.
Contact
Questions or requests: dashenfelder@gmail.com.