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
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 — with one exception: a recipe you deliberately share by link, described on the right
Held on our server
- An account with no name and no password — just a random ID and a secret key your phone stores. There is no email attached to it unless you give us one. We ask for one when you want free credits and before you buy a credit pack, and we ask you to confirm it by tapping a link we send; it is then attached to that same account — one address, one account. You can ask us to delete the whole account at any time (see §6).
- Recipes you choose to share. When you share a recipe, a
copy is saved on our server. That is what keeps the link short and gives it
a preview in a message, and it is what lets anyone who opens the link see
the recipe. We can see it too — it is in our database, which is how we can
remove it if someone reports it. What we are allowed to do with a recipe you
shared is set out in section 5 of the terms, and it
is broader than the link you sent. Nothing from
the Health Tracker is ever part of a shared recipe.
Two details we would rather state than leave unsaid. The shared copy is recorded against your account — that is how we can find it if you ask us to delete it, and how we stop one account flooding the service. And if you share on a recipe that somebody else shared with you, we record which share it came from, so we can tell an original from a passed-along copy. Neither of those is shown to anyone. A person who opens your link sees the recipe and nothing about you. - Your Recipe Share credit balance, and how many credits each AI action used.
- If you buy a credit pack: which pack, how many credits it gave you, how much was paid, how much of that was tax, and Stripe's own reference for the payment. Not your card details, not your name, and not your billing address — those are typed on Stripe's page and stay with Stripe.
- 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
- Not your search text. When you use an AI search, the words go to Anthropic to answer the question and are not stored by us.
- Not the names of your foods, and not their categories. We record that an item was added and whether it was a food or a recipe. Not what it was.
- Not anything from the tracker. We may record that the tracker was opened. Never a single number inside it.
- No cookies, no tracking pixels, no advertising or analytics services. No Google Analytics, no Meta or TikTok pixel, nothing of that kind, anywhere in the app.
- No IP address stored with your activity or your messages. An address is used briefly to limit signup and message abuse, and those counters are deleted within about two days.
3 · We do not sell your personal data, and we do not try to un-anonymise it
Your personal information is not for sale. Not to advertisers, not to data brokers, not to researchers, not in aggregate, not ever. That covers your account, your credit balance, the email address if you gave us one, and every count we keep. There is no consent box here to opt out of, because there is nothing to opt out of.
We also do not try to work out who you are. We take reasonable steps to keep anonymous data anonymous, and we publicly commit not to attempt to re-identify it.
A recipe you choose to share is a different thing, and we would rather say so than leave it unsaid. It is something you publish through the app — not information about you — and what we may do with it is set out in section 5 of the terms. Recipes you never share are not covered by any of that; they stay on your phone.
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
| Who | What they do | What 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 |
| Stripe the payment company |
Takes the payment when you buy a credit pack, and works out any sales tax due where you live | Your card details and billing address, typed on Stripe's own page — they do not pass through this app and we never see or store them. We send Stripe only which pack you chose and the random id for your account. Nothing about your food, your weight, your pantry or anything you have logged is sent. |
| Resend the email company |
Sends the one message that confirms your email address, and any later recipe tips or app updates | Your email address, and a link with a one-time code in it — only when you ask for free credits. Nothing about your food, your weight, your pantry or anything you have logged is sent, and your address is never written into our server logs. |
| 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. |
| The recipe website you choose whichever site the recipe is on |
When you send us a recipe's web address, our server opens that page and reads the ingredients and directions out of it | The request comes from our server, not from your phone, so the site sees our address and not yours. It learns that someone asked for that page. It is not told who you are, and nothing you have typed, saved or logged is sent to it. |
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.
| Who | What 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
| What | Kept for |
|---|---|
| Your account and credit balance | As long as the account exists |
| Activity counts (a session, an item added, a search) | About 180 days, then deleted |
| Messages you send us | About 90 days, then deleted |
| Recipes you share by link | As long as people keep opening the link — a year after the last time it was opened, it is deleted |
| Codes for why an AI request failed | About 30 days, then deleted |
| Abuse-limit counters | About 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 we hold no name for the account, please send the request from the same device so it can be matched to the right account.
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, and before you buy a credit pack. When you give us one, we send a single message with a link to confirm it — that is how we know the address is real, and it is the only message you have to receive. After that we may occasionally send recipe tips and app updates, and you can unsubscribe from those at any time; unsubscribing does not affect your credits. Each email address can be used for one account.
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:
- Inside the app — the "Message us" button. Easiest, and it arrives with your account attached.
- By email — recipeshare.help@gmail.com. Use this one for privacy requests and data deletion. Copyright takedown notices have their own contact, just below.
Copyright complaints
If you believe a recipe shared through this app copies your work, write to our designated agent and we will remove it: Perry Medina, 266 Concord Lane, Middletown, New York 10940, (845) 537-0131, recipeshare.help@gmail.com.
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.