Privacy policy
Last updated 14 November 2026.
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.
Squeezy is run by Olivier McNicoll, the person the terms are with. Wherever this policy says "we", that is him.
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 we store is in the United States, in the US East region. The exception is the visit counts, which Umami holds, in the United States or the European Union.
- We do not sell your data, we run no ad trackers, and no card details ever reach us. We count visits and a few actions through Umami. It sets no cookies. When you are signed in, a count carries an anonymous number made from your account, and never your name, email address or a recipe.
- Recipe text and your questions to the assistant are sent to Anthropic, which is the company whose model reads them.
- 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, or you are a kitchen's admin and switch on its public book, which lists only recipes the kitchen wrote itself and lets anyone with its address open and cook them. A share of a recipe you imported carries the recipe and its credit, runs out after a few opens, and records nothing about who opened it; a share of a recipe your kitchen wrote does not run out. If an opener signs up and keeps the recipe, their new account notes who it came from.
- Deleting your account, in Settings, deletes your data. What it cannot reach, and what it leaves on purpose, is 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. The language you pick on Settings, if you pick one, so every device you sign in on reads in it. 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. 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 Squeezy holds about them; they are never shown anyone's email address, only the names people in your kitchen gave.
Asking to join a kitchen. If you ask to join a kitchen from an expired invite, the person who made the kitchen sees your name for up to a week. The request goes when it is answered, when the week ends, or when you delete your account.
A public book, if you switch one on. A kitchen's admin can publish the recipes the kitchen wrote itself (never one imported or sent) at an address made from the kitchen's name. The page shows the kitchen's name, the recipes' titles and the day each was added, and a link to the admin's channel if they typed one. Anyone who has the address can open each listed recipe and cook it in full, with no limit on opens: pressing Cook makes a share of the recipe's current version with no sender, and that one share is reused for every later visitor. It is off until an admin turns it on, it carries no member, address or count of cooks, and search engines are asked to leave it alone. It is the one place a stranger can see a list of recipes without being sent a link.
The closed beta's list. While Squeezy is open to invited people only, your email address is kept on the list of people let in, with the day you were added, until an admin removes you.
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.
Translations. When we translate a recipe, we keep each translated sentence, with nothing about you or the recipe attached, so the same sentence in another recipe is never translated twice.
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 Squeezy breaks, it sends the error's type, which script line it came from, which screen you were on, which build you were running and, if you are signed in, the random identifier of your kitchen, so we can find your crash when you tell us about it. It never sends the error message, your email address, or anything about your device, because an error message can contain the name of a recipe or an email address. While we have error alerts switched on, that report, and a short note when an import fails or our server errors (a kind of failure and a count, never a recipe, an address or an identifier of yours), also go to Sentry, a company that emails us when something breaks.
Visit and usage counts. When a screen opens, Squeezy tells Umami, an analytics service, that a screen opened. It also tells it, by name, when somebody signs up, starts an import or finishes or fails one (link, paste or photo, and for a failure the kind of failure), answers one of the import's questions (which question, never your answer), starts, finishes or abandons a cook, sets a timer, adds to or clears a shopping list, makes or opens a share link, signs up from one, plans a recipe, opens a recipe's Details, or starts reading your recipes again. What goes with a count is the shape of the screen, such as "a recipe" and never which one, the site you came from if you followed a link, and the language, screen size and browser your browser reports. Umami also sees your IP address, as any server does when it answers a request, and works out a country from it. By its own description it keeps page views, the site you came from, the browser, the operating system, the kind of device and the country, anonymised, and no personally identifiable information; it does not say what becomes of the address itself, so take it that Umami sees it. Never a recipe, a title, a link, an email address or anything you typed. Umami sets no cookie. Squeezy keeps the anonymous number on your device, and a note that a share link brought you here until you sign up. A browser that asks not to be tracked is not counted at all.
When you are signed in, a count also carries an anonymous number for your account. It is a one-way scramble of your account's identifier, so it is the same on every device you sign in on, and we can count your visits from all of them as one person's. It is never your email address or your account's identifier, and it cannot be turned back into either. Someone who is not signed in has none, and signing out takes it away. Once each time the app opens, it also tells Umami four plain facts beside that number: how many people are in your kitchen, which language the app is set to, whether it was opened from your home screen, and which version of the app is running. They are sent on their own, with no screen, address, title or site you came from, and never a name, an email address or anything you typed.
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, except for a request
that failed, below. The path can itself be a link: a guest link (/g/…) holds the id of the account that
invited the guest and works for twelve hours, and a share link (/s/…) opens its recipe to whoever holds
it. Whoever can read our host's request log can therefore read those links, and tie a guest link to the
account that sent it.
How syncing went. After your phone syncs, it sends us a few counts: how many times it synced and how each ended, how many changes went each way, how often a change met one made on another phone, and roughly how long a change took to reach us, as one of five ranges. We add them to everyone else's for that hour and keep only the totals, for 90 days, with no account, device, kitchen or anything you wrote in them.
What the app writes down when something goes wrong. When a request fails, the app writes one line to the same log: which part of the app, what kind of failure, a short code for that request, our host's own code for it, and the random identifiers of the account and the kitchen it was for. The host's code is the one way a failed request can be found in the host's record of it, address and browser included. Never a recipe, an ingredient, a note or an email address. Every import that finishes, whether it worked or not, also leaves one line with the identifiers of the account and the kitchen, how long each step took and how much of the model it used; one that failed adds what kind of failure it was, and nothing from the recipe. We read these lines to find out what broke when somebody tells us it did. Our host keeps them for its own retention period.
The full register, table by table, is the data inventory the engineering team keeps. Anything that appears there appears here.
Why we hold it
Account, recipes, cooking history, plans, lists, imports, shares
- Why
- Running the service you signed up for
- Legal basis where the GDPR applies
- Performance of a contract
Sign-in tokens, server logs, rate limits
- Why
- Signing you in, keeping accounts secure, stopping abuse
- Legal basis where the GDPR applies
- Legitimate interests
Crash reports
- Why
- Fixing what breaks
- Legal basis where the GDPR applies
- Legitimate interests
Visit and usage counts
- Why
- Knowing which screens are used and which are not
- Legal basis where the GDPR applies
- Legitimate interests
Model call costs
- Why
- Enforcing quotas and knowing what the service costs
- Legal basis where the GDPR applies
- Performance of a contract, and our own legitimate interest in staying solvent
Billing records held by our payment provider
- Why
- Tax and accounting
- Legal basis where the GDPR applies
- Legal obligation
De-identified facts folded across kitchens
- Why
- Making the knowledge base better for everyone
- Legal basis where the GDPR applies
- Legitimate interests, with an opt-out
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. The visit counts are the one exception: Umami holds them, on servers in the United States or the European Union, and what it holds names nobody, only an anonymous number, as described under "Visit and usage counts" above.
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 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.
Supabase
- What reaches them
- Everything stored: recipes, cooking history, plans, uploaded photos, and the backups
- What they do
- Database, file storage and backups
Render
- What reaches them
- The running app, and its server logs
- What they do
- Hosting
Umami
- What reaches them
- Which screen opened, a few named actions, an anonymous account number and four facts about the app, with your IP address and browser details
- What they do
- Counting visits, with no cookies
Anthropic
- What reaches them
- Recipe text you import, and questions you ask the assistant
- What they do
- Reading recipes, answering questions
Resend
- What reaches them
- Your email address and the sign-in mail we send you
- What they do
- Sending sign-in mail
Sentry
- What reaches them
- Crash reports and short notes of what failed, only while alerts are switched on
- What they do
- Telling us when something breaks
- What reaches them
- Nothing from us. They give us an email address and an account identifier if you use them
- What they do
- Sign-in
Paddle
- What reaches them
- Your name, billing address, tax status and card details
- What they do
- Selling and invoicing paid plans
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.
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.
The knowledge base, and how to opt out
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 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 and no advertising cookies, and nothing follows you from one site to another. The visit counting above sets no cookie at all, 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: Squeezy exports every kitchen cached on your phone (its recipes and every version of them, your cooks, your plan and lists, and your saved feasts), and the other kitchens' recipes you have cooked or typed into, 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
You can delete your account from Settings. In every kitchen where you are the only member, it removes the kitchen, 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 every share link you made there. It also removes your billing records here, and the account itself. A kitchen you share with someone else stays with them: you leave it, and what it holds stays, as the paragraph below says.
Five things it does not reach, and we would rather say so than let you find out:
- Backups. Our database is backed up automatically. Your data disappears from those backups as they age out, within 30 days.
- The shared knowledge base. Facts already folded from your cooking stay, de-identified and unattributable to you.
- Your own devices. 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.
- Anything you exported. A file you downloaded is yours, and we cannot delete it.
- 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. Links you made in a kitchen that carries on keep working there, as the rest of that kitchen does.
A kitchen you shared that carries on. The evenings you cooked in it, the recipes you sent from it and the recipes you deleted from it still name you, by your account and email, so the people still cooking there can see who did what. Removing your name from them is not something Squeezy does yet, so your name stays on them.
Three records we keep on purpose.
- The record of what your model calls cost, with your account detached from it, because money that has been spent is an accounting fact.
- Abuse-limit counts. Each is kept against a scrambled form of an IP address, an email address or an account number, never the thing itself, and the scrambled form cannot be read back without our server's key. Most belong to an address rather than an account, they run out by themselves within a day, and an account that could erase its own count could reset a limit it had just hit.
- The closed beta's list. An address on it may belong to no account, so it stays until an admin removes it. Write to support@easysqueezy.app to have yours removed.
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. When you delete a recipe, we keep a short record that it was deleted, with the identifier of the account that deleted it, for ninety days, so your other devices learn it is gone and so we can tell who removed it in a shared kitchen. 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. Pastes, photographs and files you import from, and the working copy of any import, are deleted thirty days after the import ended or when you delete the recipe, whichever is sooner. When you import from a public web page, we keep the recipe's ingredient lines and steps from that page in our library, with nothing that ties them to you or your kitchen, so the next person who imports it does not pay for it again. The recipe keeps its own copy for as long as you keep the recipe. Sign-in links and codes expire in minutes. Server logs and crash reports keep our hosts' own retention, and carry random identifiers rather than your address; Sentry keeps its copy thirty days, while it is switched on. Visit and usage counts are held by Umami for six months, which is what its free plan keeps, and then go. They carry an anonymous number made from your account, and no name or address. Deleting your account does not remove them from Umami; they go when the six months are up. Our own abuse limits keep a count against a scrambled form of your IP address, the email address you sign in with, or your account number, never the thing itself, for one window of at most a day; the next request after the window ends clears it. Deleting your account does not remove these counts, because most belong to an address rather than an account, and the scrambled form cannot be read back without our server's key; they go when their window ends. Everything else goes when the account does, subject to the exceptions above.
Children
You need to be at least 13 to use 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 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 you imported or were sent in front of another person, and it never happens on its own: Squeezy never makes a share of an imported recipe you did not ask for. The one other door is a kitchen's public book, which an admin switches on and which lists only recipes the kitchen wrote itself, described under "What we hold": there, a visitor's Cook makes a share of that recipe, with no sender. There is no profile, and no listing of anyone's imported recipes. 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 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 seven things: the link itself, which recipe it points at, which version, how many times it has been opened, when you made it, which cook in your kitchen made it (so the person opening it is told who sent it; a share made from a public book has no sender), and the translations of its words that someone opening it asked for, kept so the same sentence is never translated twice.
We store nothing about the person who opened it, while they are only reading. No identifier, no address, no time of opening, no location, no read receipt. The share keeps a count of opens and the languages it was translated into, never who asked. 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. The page carries a short-lived signed token that proves it was really opened on a screen; it is worked out on the spot and stored nowhere.
If they sign up and keep the recipe, their new account says where it came from. It records the kitchen the recipe was copied from, the account that sent it, and the day, once, so we can credit the author. Nothing is recorded for someone who only reads, or who keeps it into an account they already had. Nothing reads these records yet. If the sender deletes their account, the sender's account number is cleared from them.
A link to a recipe you imported runs out after a small number of opens; a link to a recipe your kitchen wrote does not, and its count of opens is never touched. 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 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.
Squeezy