🔒

Privacy Policy

Recipe Share

Back to the app

Last updated: July 30, 2026

This is the short, plain version, because a policy nobody reads protects nobody. Recipe Share is a free app for keeping a food library, tracking what you eat, and sharing recipes. This page explains exactly what we hold, what we never hold, and who else touches it.

1 · The one-sentence version

Your food library stays on your phone. Your health log stays on this phone, on purpose. We never see it.

Everything below is the detail behind that sentence.

2 · What stays on your phone, and what reaches us

The split below is not a setting or a preference — it is how the app is built. The health side of it is never transmitted anywhere.

On your device only — never sent to us

  • Your food journal — what you ate and when
  • Body weight and any measurements
  • Your activity log
  • Calorie and macro goals
  • Any dietary notes or restrictions you enter
  • Your food library and recipes themselves

This lives in your browser's local storage. We have no copy of it, and no way to read it. That is also why backups matter — see §6.

Held on our server

  • An anonymous account — a random ID and a secret key your phone stores. No name and no password. There is no email attached to it unless you give us one, which we ask for only if you want free credits. If you do give us one, it is attached to that same account. You can ask us to delete the whole account at any time (see §6).
  • Your Recipe Share credit balance, and how many credits each AI action used.
  • Counts of what kind of thing happened — a session began, an item was added, a search ran, a recipe was shared. Counts only, never contents.
  • If an AI request failed, a short code for why we couldn't answer — never what you asked.
  • Anything you type into the in-app message box, because you sent it to us on purpose.

Things we specifically do not record

3 · We do not sell your data, and we do not try to un-anonymise it

Not to advertisers, not to data brokers, not to researchers, not in aggregate, not ever. There is no consent box here to opt out of, because there is nothing to opt out of.

We also commit publicly, here, not to re-identify anonymous data. Some of what we keep is a plain daily tally with no account attached — for example, how many recipes of each kind were shared on a given day. We do not attempt to work out which person any of those counts came from, we do not combine them with anything else in order to do so, and we do not permit anyone else to. Those tallies are only started once enough people are using the app that a count describes a pattern rather than a person.

4 · Outside services the app uses

These are all of them. We have grouped them by what they actually receive, because the two groups are not the same thing.

4a · Services that receive something you give the app

WhoWhat they doWhat reaches them
Anthropic The AI that estimates nutrition and reads label and recipe photos The text or photo you submit for that one request
Supabase The database holding accounts, credits and counts Everything in the right-hand column of §2
Netlify Hosts the app and runs the server code Ordinary web request information, kept in their logs briefly
Cloudflare The "are you a human" check when an account is first created Only what that check needs; it does not use tracking cookies
USDA FoodData Central
a U.S. government food database
Looks up nutrition facts when you search for a food in the Pantry The food name you typed, sent from your phone at the moment you search. Not sent with your name, your account, or anything else about you.
Open Food Facts
a non-profit product database
Looks up a packaged product when you scan a barcode The barcode number, sent from your phone at the moment you scan. Nothing else.

4b · Services that only send files to your device

These do not receive anything you type, save, or log. Your device asks them for a file — a typeface, a small piece of program code — and they send it. Being asked, they can see your device's internet address and which file was requested, the same as any website you visit. We want to name them rather than leave them unsaid.

WhoWhat they send
Google Fonts The two typefaces the app is set in

This group used to have two more entries. The code that draws the charts and the code that draws the QR square are now served from this app's own site, so no outside company is asked for them (changed 31 July 2026).

Neither group receives anything from the left-hand column of §2 — your food journal, weights, activity and goals never leave your device, so there is nothing of theirs to send. And none of the services above is an advertising or tracking company; we do not use any.

5 · How long we keep things

WhatKept for
Your account and credit balanceAs long as the account exists
Activity counts (a session, an item added, a search)About 180 days, then deleted
Messages you send usAbout 90 days, then deleted
Codes for why an AI request failedAbout 30 days, then deleted
Abuse-limit countersAbout 2 days

Long-run totals with no connection to any account — for example "how many searches ran in July", or "how many dessert recipes were shared today" — are kept indefinitely, because they describe the app rather than a person. They carry no account, no device and no identifier of any kind, they are never started until enough people are using the app for a count to describe a pattern instead of a person, and we commit in §3 above not to try to reverse them.

6 · Your choices

Deleting the data on your phone

Clearing this site's data in your browser settings erases your food library, your journal and everything else local — permanently, with no copy anywhere. Back up first if you want to keep it.

Deleting what we hold

Message us and ask, and we will delete your account row and the records tied to it. Because the account is anonymous, please send the request from the same device so it can be matched to the right account.

Email

The app works fully without an email address. You can keep a food library and track what you eat without ever giving us one. We ask for an email when you want free credits, after you have used up the ones you started with. If you give us one, we may occasionally send recipe tips and app updates, and you can unsubscribe at any time.

Children

Recipe Share is not directed at children under 13, and we do not knowingly collect anything from them.

7 · Who runs this, and how to reach us

Recipe Share is an independent app built and run by one person in Orange County, New York. It is not a company product and has no investors.

Two ways to get in touch, and both reach the same place:

Please don't include medical or health details in a message. We don't need them to fix a bug, and a message box is the one place where something you type does reach our server.

8 · Changes to this policy

If what we collect ever changes, this page changes with it and the date at the top moves. There is no version of this app that quietly starts collecting more than what §2 lists.