Privacy

• We keep what you save so the app can show it back to you. That’s it.
• Nothing you save is public, and nothing is sold, ever. People at your tables see only what you share with them.
• No ads, no tracking, and no analytics cookies. The only cookies keep you signed in.
• gingham counts how the app is used, in its own database, to make it better. Those counts are never sold or shown to anyone else.
• You can download everything or delete your account at any time from the You tab.

• Your account: your email address and a scrambled form of your password that can’t be turned back into the password.
• Your recipes: everything in them, including where each came from (the link, site, or cook, how it came in, and when), the recipe a version of yours was made from, and whether it’s private or shared at a table.
• Photos: photos you add to recipes, screenshots and pages you ask gingham to read. gingham doesn’t download or keep photos from other sites or from files you bring from other apps; a recipe site’s own photo is shown from that site.
• What you add while cooking: notes, favorites, your meal plan, your shopping list, and the dishes you name as cards to fill in.
• Your profile: your name if you give one, the diets you follow, your allergies, foods you avoid, and US or metric units. Allergies and diets are only used to warn you about ingredients and to pick swaps.
• Tables: the tables you start or join, who is at each one, the recipes shared there and who shared them, the photo you add for people at your tables to see, and invite codes. Codes are kept only in a scrambled form, so a copy of the database can’t be used to join anything.
• How often you use Claude: for each time gingham asks Claude for help, what kind of help it was, the model, how much text went in and out, and whether it worked. This keeps the monthly limit fair and the costs in check. It doesn’t keep what was sent.

Your browser also keeps a little on each device: the steps and ingredients you’ve checked off in cook mode, until you finish, a recipe you’re editing but haven’t saved yet, and the list in Add many at once until you save it. Files you choose there (bookmarks, or recipes from Paprika or Mela) are opened on the device too. All of that stays on the device and never reaches gingham until you save a recipe.

A few companies do the heavy lifting. Each one only gets what it needs to do its part.

• Supabase stores the database, handles signing in, and keeps your photos, on servers in the United States.
• Cloudflare hosts the app. Your pages and requests pass through its network. When you create an account, its Turnstile check also makes sure you’re a person and not a script, using what your browser and connection tell it, such as your IP address.
• Resend delivers the emails gingham sends about your account, such as a code to reset your password or to confirm a new email address. It gets your email address and the email itself, and nothing else. There are no newsletters, and gingham’s emails have no tracking pixels or tracked links.
• Anthropic runs Claude, the AI that reads photos, pasted text, video captions, and pages with no recipe data, and suggests swaps. It’s only used when you use one of those features, and it gets only what that feature needs: the photo, text, or caption to read, and for swaps, the ingredient, the recipe’s name, what you say you have, and your allergies, diets, and foods you avoid. Under Anthropic’s terms for apps like this one, what we send isn’t used to train its models.

When you paste a link, gingham’s server fetches that page for you, so the site sees a visit from gingham, not from your phone.

A table is a small private group you start or join with an invite code. Nobody can find a table or join one without a code from someone at it, and an owner can remove anyone.

• They see: your name and the photo you add for them, and the recipes you choose to share at that table, with their photos, the original scans they were read from, and any changes you make later.
• They never see: your email, diets, allergies, foods you avoid, notes, favorites, meal plan, shopping list, or any recipe you haven’t shared there.
• Saving a copy: anyone at the table can save a copy of a recipe you shared, photos included, which then belongs to them. Taking the recipe off the table doesn’t remove copies already saved.
• Leaving: when you leave a table, or an owner removes you, the recipes you shared there leave with you, and you stop seeing everyone else’s. A table’s owners can also take any recipe off it; it stays in its cook’s own recipes.

To see whether gingham is working for people, and what to make better, gingham counts how the app is used. The counts are kept in gingham’s own database, next to your recipes. There’s no outside analytics service, no tracking script, and no extra cookie.

• What it counts: the day you made your account, each day you opened gingham (once a day at most), each recipe you save and how it came in (a link, a photo, pasted text, typed in, a house recipe, or your own version), when an import doesn’t work and a short reason (such as “no recipe on the page”), when you start cook mode, and when you start or join a table. How often you use Claude is already kept, as described above.
• What it never keeps: your IP address, your device or browser, the pages you look at, the links you paste, or the words in any recipe, and nothing about what you do anywhere else.
• Who sees them: only the person who runs gingham, on a private page, as totals and a short list of accounts (email, when each joined and was last active, and how many recipes each has). They’re never sold, shared, or shown to anyone else, including people at your tables.
• When they go: your counts are in your download, and they’re deleted with your account.

• Sell or rent your information, or share it for advertising.
• Show ads, anywhere.
• Make anything you save public. There are no public profiles and no way for strangers to find you.
• Use tracking pixels, analytics cookies, or anything that follows you to other sites.

Nothing you save is visible to anyone else unless you share it at one of your tables. If gingham ever lets you publish a recipe you wrote yourself, it will happen only when you choose to, one recipe at a time, and this page will say so first.

One cookie keeps you signed in. While you choose a new password after a reset, a second one remembers that for up to an hour. Neither can be read by scripts on the page, and the first is gone when you sign out.

• Download: on the You tab, Download my recipes and data gives you one file with everything above, including your tables, what you shared there, and what gingham counted about your use. Photos are listed as links that open while you’re signed in.
• Delete: on the You tab, Delete my account removes your account and everything in it right away, photos included, and takes your recipes off every table. Copies other people saved stay theirs. It can’t be undone. Copies in our providers’ short-term backups and logs, if any, age out on their own.

gingham isn’t meant for children under 13, and we don’t knowingly keep their information.

If this policy changes, the date at the top changes too, and anything important will be pointed out in the app before it takes effect.

Write to hello@joingingham.com. A person reads every message.