Terms of service
Last updated 14 November 2026.
These are the terms you agree to by using Squeezy. They are written to be read, so they are short and say what they mean. How we handle your data is a separate document: the privacy policy.
Contact: support@easysqueezy.app. Reports of abuse, and requests from anyone whose recipe has ended up somewhere it should not be: abuse@easysqueezy.app.
Who can use Squeezy
You need to be at least 13, and at least 16 in the European Economic Area. If you are using Squeezy on behalf of an organisation, you are confirming you can agree to these terms for it.
Your account
You sign in with a sign-in mail that carries a code and a link, or with Google. There is no password, which means the email account you sign in from is the key to your recipes. Keep it secure, and tell us at support@easysqueezy.app if you think someone else has reached your account.
If you can only sign in with a magic-link mail and you lose access to that inbox, we cannot get you back in. There is no password to reset and nothing else to prove who you are. You can change the email your account uses, and doing that before you switch providers or lose an old address is the only way to avoid being locked out; adding Google as a second way in avoids the risk entirely.
One account is for one person. You are responsible for what happens under yours.
What you put in Squeezy stays yours
Your recipes, your notes, your cooking history and your times belong to you. We do not claim ownership of any of it and we do not sell it.
We need your permission to do the obvious things a service has to do: store your content, back it up, process it so the app works, and show it back to you on your devices. That permission covers exactly that and ends when you delete the content or your account. It also covers showing what you chose to share to the people you shared it with, and nothing wider.
We do not use your recipes to train models. Recipe text is sent to Anthropic so a model can read it for you, under terms that say the same thing. The privacy policy has the detail.
You can export everything Squeezy holds on a device to a file, at any time, without asking us.
Recipes you import from somewhere else
Squeezy can turn a link, a photograph or pasted text into a recipe you can cook. What Squeezy will and will not do with someone else's recipe is a policy in its own right, and it binds us and not only you. It is written out here, in full, because a rule you are bound by is one you should be able to read.
What travels is Squeezy's version of the recipe, not the author's page. An import keeps the ingredient lines, the method rewritten as Squeezy's own instructions, the times, and anything you add yourself. The headnote, the story, the method as the author wrote it and every photograph stay where they were published. We do not copy them, and we do not reword them until they count as ours — the structure is extracted and the writing is discarded. Where our parser supplies a time the source never gave, the app marks it as assumed rather than putting a number in the author's mouth.
Credit travels with the recipe, and it is not optional. Every import records where it came from, and an import from a link cannot become a recipe without it. Where there is no URL to record, such as a photograph or a paste, the credit is whatever can honestly be said, and where nothing is known nothing is claimed. Credit survives editing, new versions, export and sharing: you can change a recipe until it is yours, but the app will not forget where it started. Anywhere the recipe is read in full — including a page you shared with somebody — the credit is on screen with a working link.
An import reaches nobody else unless you send it. There is no public page for it, no profile, no feed and no search index, and Squeezy never creates a share of an import you did not ask for. A kitchen's public book, which an admin must switch on, lists only recipes the kitchen wrote itself, never one imported or sent. The only door for an import is a link you make and send, and it runs out — see the sharing section below.
We fetch the one page you ask for, and nothing else. When you give Squeezy a link, it fetches that
page because you asked it to. That is a request made on your behalf and not a crawl, so it does not
read the site's robots.txt, a file meant for crawlers. Our fetcher says who it is and gives a URL a
site owner can look up; it never pretends to be a browser, and there is no second identity to retry
as. It fetches that one page — no crawling, no following links, no prefetching. If the site itself
refuses the request, that is the final answer: we do not route around it through a proxy, a headless
browser or somebody's mirror. Squeezy tells you the site would not let it read the page, and offers
to read the recipe if you paste it. Pasting is a first-class way in rather than a consolation prize,
and everything below applies to it identically.
We never sell Squeezy as a way around a creator's site. Not in the product, not on a help page, not in marketing. Their page keeps its visit, its advertising and its story, and we do not call any of it noise, filler or an obstacle. Sharing is a way to hand a friend a recipe you cooked; it is not a way for either of you to stop visiting the site it came from.
Two things this policy asks of you rather than of us. Import recipes for your own cooking, not to build a collection of somebody else's work. And if you paste text from a page, that is your act rather than ours: the rules above still govern everything Squeezy does with it afterwards, but whether you were allowed to copy it is between you and whoever wrote it.
If you wrote a recipe and object to it being here
Write to abuse@easysqueezy.app, naming a recipe, a URL or a domain, from an address that holds the rights in it. There is no form, no account, no legal notice and no lawyer.
We disable first and discuss afterwards. Every share link for recipes imported from that source stops working, no later import from it can be shared either, and you get a reply naming what was switched off. You do not have to win an argument with us about copyright first.
We acknowledge within 2 business days and the links are dead within 5. They are small numbers because Squeezy is small, and they are the ones we can keep.
What this does not do, said plainly rather than left to be discovered. It does not stop people importing from your site for their own cooking: the objection is to Squeezy handing your recipes to strangers, and answering it by refusing every cook their own copy would punish the wrong person for a different act. And it does not reach into anybody's kitchen to delete a recipe they already have — not the cook who imported it and not a friend who kept it. What we withdraw is Squeezy passing it on, which is the part Squeezy performs. We cannot un-give what was already given, any more than we could un-tell a friend; what we stop is the giving.
Sharing
You can share a recipe by making a link and sending it to someone, and that includes a recipe you imported from somebody else's site. It is the only way a recipe you imported or were sent reaches another person. A kitchen's admin can also switch on a public book of the recipes the kitchen wrote itself; it is off until they do, and anyone with its address can open and cook those recipes, with a share that Squeezy makes when a visitor presses Cook. There is no profile, no listing of imported recipes, and Squeezy never makes a share of an imported recipe you did not ask for. Nothing you save is visible to anybody until you send it or publish it.
What travels is Squeezy's version of the recipe, not the author's page. The ingredient lines, the steps in Squeezy's own words, anything you added yourself, the credit, and a link back to where it came from. The writing and the photographs stay where they were published. If you want the story and the pictures, go to the source, and the link is right there on the page for you and for whoever you sent it to. That is the import policy above, and it binds us, not just you.
A share link to a recipe you imported runs out. It opens a small number of times and then it stops, so a recipe you send to four friends cannot quietly turn into a page on the internet. A link to a recipe your kitchen wrote does not run out: that recipe is yours to publish, and it is the one a public book offers. Only opening the page spends one of those opens; something that merely fetches the link, like the preview a chat app makes, spends nothing. There is nothing for you to expire, revoke or tidy up afterwards, and no list of live links to stay on top of, because a link that runs out does not need managing. What we keep about a share, and what we deliberately do not, is in the privacy policy's section on sharing a recipe.
You are the one sharing, and that is yours to do. When you send a recipe you are handing it to people you picked, the way you would text it to them. You are saying "have this", not "publish this", and whether it is yours to hand over is your call. That is as true when the recipe is your own as when you imported it.
And we answer for what we do once somebody tells us. We are not going to hand you the sending and then treat the rest as nothing to do with us. If the person who wrote a recipe objects to Squeezy passing it on, they write to abuse@easysqueezy.app and we act, to the deadline set out in what happens when an author objects above. They do not have to win an argument with us first. What we will not do is reach into anybody's kitchen and delete the copy they cook from, yours or your friend's. What we stop is us passing it on.
Those two sit together rather than against each other. Choosing to send it is your part; doing something about it when we are asked is ours, and neither of us can hand our part to the other.
What you may not do
- Use someone else's account, or try to reach data that is not yours.
- Script or automate imports, or work around a quota.
- Import from a site in a way that dodges our own rules, including through a proxy or a mirror.
- Upload anything unlawful, or anything you do not have the right to upload.
- Attack the service, its hosts or the sites it fetches from, including by pointing an import at an address that is not a public web page.
- Resell Squeezy or pass it off as your own.
We can suspend or close an account that does any of this. Where it is reasonable to, we will say why first.
Paid plans
Squeezy is free to use. Cooking, planning, notes and shopping lists have no limits and never will: the paid tier exists only for the parts that cost money every time they run.
Free gives you 10 recipe imports a month and 5 model-backed assistant questions a day. Plus is $5 a month and lifts both: imports, subject to a ceiling that exists to stop scripts rather than to meter anybody, and the assistant's daily cap, with no ceiling at all.
Cancelling never removes data. An import is expensive once and nearly free to keep, so a lapsed subscription keeps every recipe you have ever imported. You drop back to the free tier's limits on new work, and nothing you already have goes away.
Payments are handled by Paddle, which is the seller of record. Your contract for the payment itself is with them, they issue the invoice, and their terms and refund policy apply to it. We never see your card.
Prices can change. If they do, we will tell you before your next renewal, and you can cancel.
Cooking is yours
Squeezy helps you cook. It does not cook, and it does not know what is in your kitchen.
Squeezy does not check recipes for allergens. Ingredients are what the recipe's author wrote, not an audit of what is in a packet, and a missing ingredient is not a promise that something is absent. If you have an allergy or an intolerance, read the labels on what you buy.
Food safety is yours. Cooking temperatures, raw ingredients, storage and reheating are your responsibility and your judgement. Squeezy will show you a step and time it; it cannot tell you the chicken is done.
Times are estimates and Squeezy says whose they are. A duration is either the recipe's, one our parser assumed, or one measured from your own cooking, and the app labels which. None of them is a guarantee about your kitchen.
The assistant can be wrong. It declines rather than guesses where it can, but it is a model and it makes mistakes. Do not use it for allergy, medical or food-safety decisions.
Availability, changes and endings
Squeezy is a small service. We may change it, and features may come and go. If we are going to remove something you depend on, we will give you notice and time to export.
You can delete your account at any time, from within the app. We can close an account that breaks these terms, and if we ever shut Squeezy down we will give you at least 30 days to export your data first.
What we promise, and what we do not
Squeezy is provided as it is. To the extent the law allows, we make no warranty that it will be uninterrupted, error-free, or fit for a particular purpose, and we are not liable for indirect or consequential loss, for lost profits, or for lost data beyond what you can export yourself.
Where we are liable, our total liability is limited to whatever you paid us in the 12 months before the claim, or $50 if you paid us nothing.
Consumer law in your country may give you rights that cannot be signed away. Where it does, it wins, and nothing above limits it.
Which law applies
These terms are an agreement between you and Olivier McNicoll, the person who runs Squeezy. Wherever they say "we", that is him.
They are governed by the law of the State of New Hampshire, USA. That sits under the consumer-law paragraph above and not over it: a right your own country gives you that cannot be signed away stays yours, wherever you bring it.
Changes to these terms
We will update these terms when the service changes, and the date at the top will change with them. For a change that affects what you pay or what you may do, we will tell you before it takes effect.
Squeezy