Privacy
Last updated
The short version
- We keep what you put in Romesko so we can run it for your household, and nothing for advertising. No ads, no third-party analytics or tracking, and we never sell or share your data for marketing. We look at simple counts, such as how many recipes a household has saved, to keep Romesko working and decide what to build.
- Your household’s allergies and diets are health information. They’re used only to check recipes and plan meals for you.
- An AI assistant you connect, such as ChatGPT, Claude or Muse, sees what it asks for on your behalf, and you can disconnect it any time.
- You can export your recipes and delete your account whenever you like.
Who we are
Romesko is run by Austin Zentz, an individual in Washington, DC, in the United States, who is responsible for your personal data (the “controller”). For anything about privacy, email support@romesko.com, or write to Austin Zentz at 1345 Tuckerman St NW, Washington, DC 20011-1138, United States.
What we collect, and why
Your account
Your email address and name, and how you sign in: a code we email you, Sign in with Apple (then Apple’s ID for you, the email Apple shares, which may be a private relay address, and a token we use to disconnect Romesko from your Apple Account when you delete your account or disconnect Apple), or Sign in with Google (then Google’s ID for you and the email, name and profile picture Google shares). Every way you connect signs in to the same account. We need these to give you an account and keep it yours.
Security and sign-in
Each time you sign in, we record the session with your IP address and the browser or device it came from, and keep it until the session ends (30 days at most). Counters of requests per IP address, which stop people guessing codes or overloading Romesko, are deleted within a day. We do this to keep accounts and the service safe.
Your household
Who’s in your household and their roles, and the email addresses of people you invite: we email them the invitation, which shows your household display name. Everyone in a household sees its shared data and each other’s names; a member who hasn’t given a name is shown by their email address instead.
Your household profile (health information)
The people you cook for (who can include children without an account), their allergies, dietary needs and dislikes, and the household’s preferences: cuisines, weeknight time, equipment, budget, stores and notes. You choose to enter these; we use them only to check recipes, suggest swaps and plan meals. Remove an entry and we stop using it.
Recipes, photos, plans and lists
Your recipes and their notes, ratings, tags and source links; photos (we strip location and camera details from them); your meal plan, shopping list and staples; what you cook (cook mode progress, meals marked as made, with any note, rating or photo); and what you check off at the store, which lets Romesko suggest you probably already have something. This is the service itself.
Imports
When you import a file from another app, we keep the file only until the import finishes, and a report of the import for 30 days. When you save a recipe from a link, our server fetches that page and its picture: the website sees our server, not you.
Connected assistants
When you connect ChatGPT, Claude, Muse or another assistant, we keep a record of the connection, and a log of what it did for 90 days: which tool it used, recipe IDs, dates and counts, and short search words or the title of a recipe it saved. The log never holds your profile’s contents or your notes. It lets us show you what’s connected and find problems.
Subscriptions
If you subscribe to Plus, Apple (in the App Store) or Paddle (on the web) handles the payment, and RevenueCat tells us whether your household has Plus, until when, whether it renews, and who in the household subscribed in the app (so the others see “Plus, through” your name). We never see your card details.
How we see Romesko being used
From what Romesko already keeps to run your household, we count a few things for each household: how many recipes it has and how many it added in the last 30 days, when it last added to or checked off the shopping list, when it last planned a meal, how many times a connected assistant was used, and whether it’s on a trial, Free or Plus. Only Austin Zentz and someone who helps run Romesko see these, on a private page that needs their own sign-in; no analytics company gets them, and we don’t record anything extra for them. They tell us whether Romesko is working for people and what to improve. They’re counts for the whole household, shown next to its name and its members’ names and email addresses, never what your recipes, notes or list items say, and never your household profile.
Error reports and support
When something breaks, the app and server send an error report to Sentry. We strip it down before it’s sent to the kind of error and where in our code it happened: no recipes, profile, email address or account details. If you email us, we keep the conversation so we can help you, and we may look at your account to do it: who’s in your household, how each of you signs in, your plan and its history, and what a connected assistant did (never your household profile).
Our legal reasons
Where the law asks for one (in the EU and UK, for example), our reasons are:
- Providing the service you asked for (our contract with you): your account, household, recipes, photos, plans, lists, imports, connected assistants and subscriptions.
- Your explicit consent for the allergies, diets and other health information you choose to enter. Withdraw it by removing those entries.
- Our legitimate interests in keeping Romesko secure and working: session and IP records, rate limits, the assistant log, error reports and backups; and in understanding how Romesko is used, through the household counts above, so we can improve it.
- Legal obligations, such as tax records for purchases (kept by Apple and Paddle).
Where it's kept
Romesko’s data is stored in the United States. If you use it from elsewhere, your data is transferred there.
How long we keep it
- Your account, household, profile, recipes, photos, plans, staples and cooking history: until you delete them or your account. When Plus ends, photos past Free’s 100 are kept for 60 days, then removed (see the terms).
- Cook mode progress: 180 days. What you checked off at the store: 2 years.
- Items cleared from the shopping list: 30 days after you clear them.
- Subscription records (whether your household has Plus, from where, until when, and who subscribed): until you delete your account. We also keep a receipt of each notice RevenueCat sends us (its ID and kind); once your household is deleted, nothing links those to you.
- Sessions: 30 days at most. Sign-in codes: 5 minutes. Unused invitations: 7 days.
- Request counters by IP address: about a day. The assistant log: 90 days. Import files: until the import finishes; import reports: 30 days.
- Encrypted backups: 30 days, then they’re deleted. Server logs, which record page addresses and timings but not IP addresses, are kept by our host for a short period.
Deleting your account
Delete your account in the app (Settings, then Account) or on the web (Account). Your sign-in, sessions, connected assistants and the assistant log are deleted at once.
- If you’re the only person in your household, the household goes with you: its recipes, photos, plans, lists, staples, profile and history.
- If others share the household, it stays theirs. What you added (recipes, photos, list items, cooking history) stays with the household without your name on it. Your entry under People, with any allergies, stays too, because the household plans meals around it: remove it from People first if you’d like it gone.
Copies in our encrypted backups are deleted within 30 days. Deleting your account cancels a web subscription you bought, so it won’t renew (anyone else in the household keeps Plus until the end of the period already paid for). It doesn’t cancel an App Store subscription: cancel that in your Apple Account first.
Your rights
Depending on where you live, you can ask to see the data we hold about you, get a copy of it, correct it, delete it, limit or object to how we use it, or withdraw your consent. Much of this you can do yourself: edit anything in the app, export your recipes from Import and export on the web, and delete your account. For the rest, email support@romesko.com, and we reply within one month. In the EU or UK you can also complain to your data protection authority. We don’t sell or share personal information as California law defines it, and we’ll never treat you differently for using these rights.
Keeping it safe
Everything travels encrypted (HTTPS). Sign-in codes and connection tokens are stored only in scrambled (hashed) form, backups are encrypted, and every request is checked so one household can never reach another’s data. Only Austin Zentz has access to the systems that run Romesko. Someone who helps run Romesko can also sign in to a private page that shows households, their plan and the counts described above, to help with support and with improving Romesko; they’re held to this policy. No system is perfectly secure; if a breach affects you, we’ll tell you as the law requires.
Children
Romesko isn’t meant for children under 13 to use themselves, and we don’t knowingly let them create accounts. Parents can describe children in the household profile, such as a child’s allergies; that information is the parent’s to add and remove. If you think a child has an account, email support@romesko.com and we’ll delete it.
Changes to this policy
If we change this policy in a way that matters, we’ll tell you by email or in the app before it takes effect, and update the date at the top.