Privacy Policy

Supperpot is a recipe app for one-pot meals. Signing in is optional: you can use the whole app without an account. This page explains, in plain words, what the app does with data.

Who is responsible for your data

Supperpot is made and run by Mário Otruba, a sole trader based in Slovakia. That means I am the data controller: I decide what the app collects and why, and I am the person answerable for it.

You can reach me at hello@supperpot.com. There is no support team — your email comes to me.

Because I am based in the European Union, European data protection law (the GDPR) applies to everything Supperpot does, for every user, wherever you live. If you are in the United States or Canada that works in your favour: you get the same protections European users do.

Signing in is optional

Supperpot asks you to sign in before you subscribe, so your subscription, your answers and your first recipe can follow you to a new phone. You can sign in with Apple, with Google, or with an email address and a code we send to it.

When you sign in with Apple or Google, we receive from them two things: an account identifier and your email address. We do not receive your password, your contacts, your photos, your Google or Apple account contents, or anything else. With Sign in with Apple you may choose "Hide My Email", in which case we only ever see Apple's forwarding address and never your real one.

We use that email address for exactly one purpose: to recognise you when you open Supperpot on another phone, so your subscription, your daily recipe count, your onboarding answers and your first recipe follow you instead of starting over. We do not send marketing email. We do not sell, rent or share the address.

When you sign in, the app also stores on your account the answers you gave when you set it up (your cookware, what matters to you, household size, anything you avoid, how long you like to cook) and the first recipe it wrote for you, so they are there on a new phone. They are kept until you delete the account.

Subscriptions are processed by Apple and recorded for us by RevenueCat (RevenueCat, Inc., USA), which receives your purchase and subscription record from Apple, a random app-user identifier, your account identifier once you sign in, and the dates on which you reached each step of the sign-up flow (for example "saw the paywall"). RevenueCat never receives your email address, your photos, your answers or your recipes. We use it only to know whether a subscription is active and to see how many people subscribe.

Signing out on the phone removes the account from it immediately. To delete the account and its email address from the server entirely, open Settings and tap "Delete my account". It asks twice, then erases your account, your email address and your usage record from the server for good. Your recipes, plan and notes stay on the phone, because they were never on the server; "Clear all my data" is the separate button for those.

What stays on your phone

Your kitchen setup (cookware, household size, diet, priorities), saved recipes, weekly plan, grocery list, notes, ratings, cooking history and the basics you tick are stored only on your device. We do not upload them and cannot see them, whether or not you are signed in. Deleting the app deletes them. You can also clear them any time in Settings, "Clear all my data".

Writing a new recipe

When you ask for a new recipe, the app sends your chosen filters (cookware, time, protein, diet tags, servings, priorities) and, if you typed one, the list of what you have, to our server, which asks an AI model (Anthropic's Claude) to write the recipe. No name, email, phone number, location or advertising identifier is sent.

The server stores a random identifier created by the app on first launch, the date, and how many recipes you have made that day, so it can apply the daily allowance. If you are not signed in, that identifier is not linked to you, your Apple ID or your device's own identifiers, and we cannot use it to find out who you are. If you are signed in, the count is held against your account instead, so it is the same on every phone you use.

Recipes and illustrations the app makes for you are written by a machine and are labelled in the app as such. No person reads them before you do.

Snap my groceries

If you take a photo or choose one, the picture is sent to the same server and passed to the AI model, which lists the food it can see. The photo is processed and then discarded. It is not stored on our server, not shown to anyone, and not used to train any model. Camera and photo access are only used when you tap the button.

Recipe illustrations

New recipes get an illustration generated from the recipe text by an image model (OpenAI's GPT Image, reached through fal.ai). Only the recipe's title and its ingredient names are sent.

The subscription

Subscriptions are sold and billed by Apple through the App Store. We receive only whether a subscription is active and when it expires, passed to us by RevenueCat (see above). We never see your name, your payment details or your Apple ID. Manage or cancel a subscription in your iPhone settings.

Notifications

The daily pick reminder and the cooking timers are local notifications scheduled on your device. Nothing is sent to a server and no push service is used.

Analytics and advertising

Supperpot contains no advertising SDK and no tracking of any kind. It keeps simple anonymous counts of feature use on your device, and records in RevenueCat the date you reached each step of the sign-up flow (nothing about what you cooked or typed). Our server keeps ordinary request logs containing the random identifier, the caller's address and a timestamp, for reliability and to stop abuse.

Why we are allowed to hold what we hold

European law asks for a reason for each piece of data, not just a description. Here they are.

• Random device identifier, daily recipe count, subscription status — to give you what the app promises, including the daily allowance. Legal basis: performance of a contract with you.
• Email address and account identifier — so your subscription, allowance, answers and first recipe follow you to a new phone. Legal basis: performance of a contract with you.
• Your set-up answers and your first recipe, stored on your account — so a new phone starts where this one left off. Legal basis: performance of a contract with you.
• Sign-up step dates in RevenueCat — to see where people give up and improve the app. Legal basis: our legitimate interest in understanding how the app is used; nothing personal is included.
• Your photo and your "what I have" text — to write the recipe you asked for. Legal basis: performance of a contract, and for the camera and photo library themselves, your consent, which you give through iOS and can take back in iOS Settings at any time.
• The caller's network address and request logs — to keep the service up and stop one person running up the AI bill for everyone. Legal basis: our legitimate interest in running a service that does not fall over or go bankrupt.

Who else sees it, and where it goes

Only the companies that have to, to make the app work. Each one handles data on our instructions and may not use it for their own purposes.

• Supabase — runs our database, sign-in and server code. Holds the device identifier, the daily counts and, if you signed in, your email address. Servers in the United States.
• Anthropic — writes the recipes and reads the grocery photos. Receives the recipe request and the photo, never your email, name or location. United States.
• fal.ai, which passes the request to OpenAI's image model — draws the dish. Receives only a recipe title and ingredient names. United States.
• Apple and, if you choose it, Google — handle sign-in and, for Apple, the payment. They act on their own account, under their own privacy policies.

That list is everyone. There is no advertising network, no data broker, no analytics company, and nobody who has paid for access.

Leaving Europe. Our providers run in the United States, so data about you is processed there. We rely on the data protection terms in each provider's own agreement with us to protect it when it travels. If you want to know the current arrangement for a particular provider, email and ask.

How long we keep it

• Your photo — not kept. It is read and discarded within the same request.
• Recipe requests — not kept. We store the count, not what you asked for.
• Device identifier and daily counts — while you use the app. Counts are kept per day and are not needed once the trial and the day have passed.
• Email address and account — until you delete your account, which you can do yourself at any time in Settings.
• Server logs — deleted within 30 days.
• Everything on your phone — until you clear it or delete the app. We cannot reach it.

Your rights

Wherever you live, you can ask me to:

• tell you what data I hold about you, and give you a copy;
• correct it if it is wrong;
• delete it — though for your account you do not have to ask, the button is in Settings;
• give it to you in a portable form, which the app already does through Settings, "Export my data";
• stop using it, or object to a use you disagree with;
• restrict what I do with it while a disagreement is sorted out.

Email hello@supperpot.com and say what you want. I will answer within 30 days. I will not charge you and I will not treat you differently for asking. I may need to check you are who you say you are before handing over data, which for a signed-in account normally means replying from the email address on it.

If you think I have handled your data badly, please tell me first — it is one person and it is probably a mistake I can fix. You also have the right to complain to a regulator. In Slovakia that is the Úrad na ochranu osobných údajov Slovenskej republiky. In Canada it is the Office of the Privacy Commissioner. In the United States it is your state's Attorney General.

If you live in California

In the twelve months before the date at the top of this page, Supperpot collected the categories described above: an email address and an account identifier if you signed in, a random device identifier, and internet activity in the form of server logs.

We have not sold your personal information, and we have not shared it for cross-context behavioural advertising. There is nothing to opt out of, because it does not happen. We do not knowingly collect personal information from anyone under 16. You have the right to know, delete, correct, and not be discriminated against for exercising any of them — use the same address above.

Children

Supperpot is for cooks aged 13 and over. The app asks what year you were born before you can sign in, and turns you away if you are under 13. It keeps only the answer, never the year itself. If you believe a child under 13 has an account, email me and I will delete it.

Security, honestly

Everything travels over HTTPS. The database is locked so that the app's public key cannot read any user's record — only our server code can, using a key that never leaves the server. The AI keys are not in the app and cannot be extracted from it. There are daily limits on what the service can spend.

What I will not tell you is that this is unbreakable, because nobody can honestly say that. If something goes wrong and your data is affected, I will tell you and the Slovak regulator, and I will say what happened rather than hide it.

Your choices

• You can look at the app, answer the questions and get your first recipe written before you sign in or pay anything.
• The 100-recipe library, cook mode, the planner and the grocery list work with no network at all.
• Turning off camera or photo access in iOS Settings disables Snap my groceries and nothing else.
• "Export my data" in Settings gives you a copy of everything the app holds on your phone.
• "Clear all my data" in Settings erases everything the app has stored on your phone.
• Signing out in Settings removes your account from that phone straight away.
• "Delete my account" in Settings erases your account and email address from the server for good.

Contact

Mário Otruba, Slovakia — hello@supperpot.com

Changes

If this policy changes, the new version appears at this address with a new version number and date. If a change matters to you — a new recipient of your data, a new purpose — I will tell you in the app before it takes effect, not quietly.