Privacy policy

Last updated 30 September 2026.

Lemon Squeezy is a recipe app. This policy says what it holds about you, why, who else sees it, and how to get rid of it. It is written to be specific enough to act on, so it names the things a shorter policy would leave out.

Questions, requests and complaints: support@easysqueezy.app. Abuse and takedown requests: abuse@easysqueezy.app. Both are read by a person.

The short version

• We hold your recipes, your cooking history, your meal plans and shopping lists, and the email address you sign in with. That is close to all of it.
• Everything is stored in the United States, in the US East region.
• We do not sell your data, we run no third-party analytics or ad trackers, and no card details ever reach us.
• Recipe text and your questions to the assistant are sent to Anthropic, which is the company whose model reads them.
• Lemon Squeezy folds de-identified facts from what people cook into a shared knowledge base. You can turn that off in Settings, and turning it off stops your evidence being used from that point on.
• Nothing you save is visible to another person unless you send them a share link. A share carries the recipe and its credit, runs out after a few opens, and records nothing about who opened it.
• Deleting your account deletes your data. Five things it cannot reach are listed below, plainly.

What we hold

Your account. The email address you sign in with, or the account identifier Google gives us if you sign in that way, and which tier you are on. A name, if you choose to give one on Settings: it is shown to the people in your kitchen — over your steps when several of you cook one pot — and to nobody else, and blanking it takes it back. We do not ask for your address, your phone number or your date of birth.

Your recipes. Titles, tags, ingredients, steps, the notes you write, where a recipe came from, and every version you have saved. Lemon Squeezy keeps old versions on purpose, so a recipe you have edited is still the recipe you cooked last month.

A guest at your stove. If you invite somebody to help cook one evening, the link you send opens that evening and nothing else, for twelve hours, and makes them no account. The name they type is written into that evening's log in your kitchen, and it is the only thing Lemon Squeezy holds about them; they are never shown anyone's email address, only the names people in your kitchen gave.

Your cooking. Every tap during a cook, with its time, so the app can tell you what is ready and what is blocked. Notes you write during a cook or at the end of the evening are stored as you typed them.

Your plans and lists. What you have decided to cook on which day, your shopping lists including anything you typed yourself, and the aisle corrections you have made.

Your imports. The link you pasted, the photograph you took, or the text you pasted, plus what our parser proposed from it and what you accepted.

What things cost. One record per call to a model, with how many tokens it used and what it cost. This is how quotas work and how we know what the service costs to run.

Crash reports. When Lemon Squeezy breaks, it sends the error's type, which script line it came from, which screen you were on, and which build you were running. It never sends the error message, any identifier, or anything about your device, because an error message can contain the name of a recipe or an email address.

Ordinary server logs. Our host records the usual things every web server records: an IP address, a browser user agent, a path and a timestamp. We do not join these to accounts.

The full register, table by table, is the data inventory the engineering team keeps. Anything that appears there appears here.

Why we hold it

Where your data lives

In the United States, in the US East region. Our database, our object storage, our backups and the app itself all run there.

If you are in Canada, that means your data is stored outside Canada and can be reached by United States law enforcement and courts under United States law. If you are in the United Kingdom or the European Economic Area, it means your data is transferred outside your country. We rely on Standard Contractual Clauses with the companies listed below to make those transfers lawful. Using Lemon Squeezy means your data will be handled in the United States.

Who else touches it

Every company below is working on our behalf, under contract, and none of them may use your data for their own purposes.

Anthropic deserves saying plainly. When you import a recipe, the page, photo or text you gave us is sent to Anthropic's model so it can be turned into a recipe. When you ask the assistant a question it cannot answer for free, the question and the relevant part of the recipe go the same way. What does not go: your dietary filter. Filtering by what you do not eat happens on your own device, and those choices never leave it.

Paddle is the seller of paid plans, which is why card details never reach us at all. They handle the payment, the invoice and the tax. Their own record of your purchase is theirs, kept for as long as tax law requires.

Dietary preferences are not health data, and not allergy safety

Lemon Squeezy has a fixed list of dietary flags: vegan, vegetarian, dairy, gluten, nuts, shellfish, pork and alcohol. Two things follow.

They describe recipes, not you. When you filter by them, the filtering happens on your device and your choices are never sent to us. We hold no information about your health, and we do not want any.

They are preferences, not allergy safety. A flag reflects what somebody typed into a recipe. It is not an audit of what is in a packet of stock cubes, and a missing flag is not a guarantee. If you have an allergy, read the labels.

The knowledge base, and how to opt out

Lemon Squeezy learns from what people cook. Facts drawn from many kitchens, such as how long a step actually takes or what people substitute for an ingredient, are folded into a shared knowledge base that makes the app better for everyone.

What crosses between accounts is facts, never text, and never anyone's recipe. Nothing is ever served until enough separate kitchens support it. Nobody sees your recipes, your notes or your cooking history but you.

You can turn this off in Settings. Doing so stops your cooking being used from that point on. It cannot pull back what has already been folded in, because a fact supported by dozens of kitchens cannot be unpicked to remove one of them. That is why this is written here from Lemon Squeezy's first day rather than added later.

Cookies

At most two, and both are doing a job you asked for. One keeps you signed in. The second is set only if you open a recipe somebody shared with you: it names that one share, so reloading the page mid-cook does not spend another open, and it lasts as long as the browser session. It carries no account, no recipe and nothing about your library. If you have never opened a share, you have the first and nothing else.

There are no analytics cookies, no advertising cookies and no third-party trackers of any kind, so there is no consent banner to click through.

Your rights

Wherever you live, you can ask us to:

• See what we hold about you.
• Export it. This one does not need us: Lemon Squeezy exports everything on your device to a file you can keep or move.
• Correct anything wrong.
• Delete your account and everything in it.
• Opt out of the knowledge base, in Settings.
• Object to anything we do on the basis of legitimate interests.

Write to support@easysqueezy.app. We will answer within 30 days. If you are in the European Economic Area or the United Kingdom you also have the right to complain to your data protection authority. If you are in California, we do not sell or share personal information as those terms are defined there, and we will not treat you differently for exercising any right.

Deleting your account

Deleting your account removes your recipes and every saved version of them, your cooking history and every note in it, your meal plans and shopping lists, your imports and any photographs you uploaded with them, and the account itself.

Five things it does not reach, and we would rather say so than let you find out:

1. Backups. Our database is backed up automatically. Your data disappears from those backups as they age out, within 30 days.
2. The shared knowledge base. Facts already folded from your cooking stay, de-identified and unattributable to you.
3. Your own devices. Lemon Squeezy stores your data on each device you use so it works without a signal. A phone that is offline or signed out keeps its copy until you clear the app's data.
4. Anything you exported. A file you downloaded is yours, and we cannot delete it.
5. A recipe somebody kept from a share you sent. It is their copy in their account now, the way a recipe you texted a friend is written down in their kitchen. Your share links stop working; what somebody already kept stays theirs.

We also keep the record of what your model calls cost, with your account detached from it, because money that has been spent is an accounting fact.

One more thing worth knowing. Notes you write during a cook are kept in a log that only ever gets appended to. Clearing a note stops it being shown and keeps the record that you wrote it and then changed your mind. Deleting the cook, or the account, is what removes the text.

How long we keep things

While your account exists, we keep it. Recipes and their versions stay until you delete them, and saved versions are deliberately never pruned. A photograph you imported a recipe from is kept as long as that recipe is, and goes with the kitchen if you delete the kitchen. One from an import that failed is deleted after seven days. If our server is interrupted in the middle of taking an upload, a photograph can be left in storage with no import to delete it by; we find those by checking storage against the import records by hand, and delete them. Sign-in links and codes expire in minutes. Server logs and crash reports keep our hosts' own retention. Everything else goes when the account does, subject to the five exceptions above.

Children

You need to be at least 13 to use Lemon Squeezy, and at least 16 in the European Economic Area. We do not ask your age and we cannot verify it, so this is a condition of use rather than a check. If you believe a child has an account, write to support@easysqueezy.app and we will delete it.

Security

Sign-in is by a sign-in mail that carries a code and a link, or by Google, so there is no Lemon Squeezy password to leak. Card details never reach us. The database is not exposed to the internet. No service is perfectly secure, and we would rather say that than imply otherwise.

Sharing a recipe

You can send someone a recipe by making a share link, including one you imported. It is the only thing that puts a recipe of yours in front of another person, and it never happens on its own: there is no public page, no profile, no listing of anyone's recipes, and Lemon Squeezy never makes a share you did not ask for. What you are allowed to share, and what we do when an author objects, is in the terms; this section is what a share is made of and what we keep about it.

What the person opening it gets is the recipe, credited, with a link to where it came from: the ingredient lines, the steps in Lemon Squeezy's own words, and anything you wrote or photographed yourself. Your own notes on that recipe travel with it, so treat them as part of what you are sending. What does not travel is anything else about you. Not your email address, not your other recipes, not your cooking history, not a note you wrote on anything else. The original author's prose and photographs do not travel either, which is a rule in the terms' import policy rather than a privacy one.

A share is pinned to the version you sent. It hands over the recipe as it was when you shared it, so editing it afterwards does not rewrite what somebody was already given.

What we store about a share is five things: the link itself, which recipe it points at, which version, how many times it has been opened, and when you made it. That is the entire record.

We store nothing whatever about the person who opened it. No identifier, no address, no time of opening, no location, no read receipt. A share knows how many times it was taken and nothing at all about who took it, which is why Lemon Squeezy cannot tell you whether your friend has looked at it yet — there is nothing to show, so no screen shows it. That is a deliberate limit rather than a feature we have not built.

A link runs out after a small number of opens. A chat app's link preview, a mail scanner reading the link or a browser fetching the page ahead of time spends nothing: an open is counted only once the page is actually open on a screen. Reading your own share costs nothing either.

Somebody who opened it can keep reading it without spending another open, for as long as that browser session lasts. That is the second of Lemon Squeezy's two cookies, described under Cookies below: it names the one share and nothing else.

Deleting the recipe, or your account, takes its share links with it.

What sharing cannot do is come back. Someone who opened your link and kept the recipe has their own copy in their own account, the same way a friend you texted a recipe to has it written down. Deleting yours does not reach theirs, and neither does a takedown.

Changes

We will update this policy when what we do changes, and the date at the top will change with it. If a change matters to you, such as a new company handling your data or a new purpose for it, we will tell you before it takes effect rather than quietly reposting the page.