Privacy Policy

What we collect

• Account details. If you sign in with email, your email address and a password (stored hashed — we never see it in plain text). If you use Sign in with Apple or Google, we receive the name and email address they choose to share (Apple may give us a private relay address). If you continue as a guest, we create an anonymous account with a random ID and no email address. You don’t have to give us an email address — you can use the app as a guest — but without a sign-in you can’t get back to your data on another device or after losing this one.
• Profile. A display name (required for accounts, not for guests), and an avatar if you add one. Your display name is shown to the other members of your household and, if you share a recipe, to everyone in the Community.
• Your household’s data. Everything you put into the app: your household’s name and members, inventory items (names, quantities, expiry dates, aisles), shopping list items (including brand, quantity and unit), prices, shopping trips, spending and budget, recipes, meal plans, and the recipes you save, hide or report and the creators you block.
• Photos. Photos you add to items, recipes or your avatar, and any screenshots you attach to a problem report.
• Notifications. A push token for your device (only if you allow notifications) and your notification settings.
• Technical data. When the app connects, our servers and service providers receive your IP address, device type, app version and request logs, as any online service does. We also use your IP address to limit abuse, for example to cap how often the AI features can be used. Our websites set only the cookies needed to keep you signed in and remember your household; we don’t use advertising or analytics cookies on them.
• Totals, not tracking. We count how many times each recipe has been opened or saved. Those totals aren’t tied to you. We don’t use a separate analytics or crash-reporting service in the app.
• What you send us. If you email us we keep what you send. If you send a problem report we keep your message, your contact email if you give one, any screenshots you attach, and a few details the app adds: app version, operating system, device model, language, time zone, the screen you were on, an error reference and whether you’re a guest or signed in. We use these only to help you and fix problems.

Camera and photos. The app asks for camera access only to scan barcodes and take photos, and for photo-library access only when you pick a photo. Barcode scanning happens on your device; we send just the barcode number to Open Food Facts to look up the product.

How we use it, and why

• To run the app — your account, syncing between your devices and household members, and the expiry, running-low and weekly meal-plan reminders. Basis: performing our contract with you.
• To send push notifications you’ve allowed. Basis: your consent — you can withdraw it any time in the app’s notification settings or your device settings.
• To suggest recipes and identify items from photos using AI. Basis: performing our contract with you.
• To show ads. Basis: your consent (see Advertising below).
• To keep OopsOut safe and working — preventing abuse, moderating community recipes, handling reports and fixing problems. Basis: our legitimate interests.
• To meet our legal obligations.

We don’t sell your personal data, and we don’t use it to make automated decisions with legal or similarly significant effects on you.

Who we share it with

We use service providers to run OopsOut. They may only use your data to provide their service to us, except where noted.

• Supabase — our database, sign-in and file storage. Our project is hosted in London.
• Hostinger — hosts our web server and the app’s API, in the UK.
• Google Firebase Cloud Messaging and Apple Push Notification service — deliver push notifications.
• Apple and Google — only if you choose Sign in with Apple or Google.
• Anthropic — powers our AI features. We send only the dish name you ask about, or the photo you ask us to identify — not your name, email or account details. Anthropic’s own privacy policy applies to what it receives.
• Open Food Facts — receives the barcode number you scan, plus the technical data any web request carries.
• Google AdMob — serves ads (see Advertising below).

We may also disclose data where the law requires it, or to protect the safety of our users.

Advertising

OopsOut shows banner ads served by Google AdMob. We don’t choose the individual ads. Every ad in OopsOut is non-personalised: we don’t ask to track you across other apps and websites, and we don’t ask for your iPhone’s advertising identifier. AdMob may still use device data such as your IP address, device type and app version to deliver ads, limit how often you see them, prevent fraud and measure performance — see how Google uses information from apps that use its services.

Where the law requires it, such as in the UK, you’ll see Google’s consent form before ads load. If you decline, you’ll still see ads.

What other people can see

• Your household. Everyone in your household sees everything in it — inventory, shopping list, recipes, meal plans and spending. Anyone who has your household’s invite code can join it, so only share the code with people you want to have that access.
• Community recipes. A recipe you choose to share is visible to every OopsOut user, with your display name and avatar. You can make it private again at any time, and change your display name in Settings.
• Photos. Photos you upload are kept in storage that can be opened by anyone who has the image’s address. Each address contains a long random identifier and isn’t listed anywhere, but we can’t stop a link you share from being opened. Please don’t photograph anything sensitive.

How long we keep your data

We keep your data while you have an account. To delete it, open Settings → Delete account in the app. That permanently deletes your profile, your sign-in, your profile photo and problem-report screenshots, and any household you solely own, including its inventory, shopping list, recipes, meal plan and their photos. If you own a household that still has other members, we’ll ask you to remove them first. Households you’re only a member of stay with their owner and you are simply removed; photos and recipes you added there stay with that household, no longer linked to you. If you had shared a recipe to the Community it stays visible there without your name unless you make it private first.

Guests can remove their data with Settings → Clear guest data. We keep problem reports for as long as we need to deal with them (they are no longer linked to your account once you delete it), and anything we are legally required to keep for as long as the law requires.

Your rights

Under UK data protection law you can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, or move it to another service, and you can withdraw consent you have given us at any time.

• Settings → Download my data prepares a copy of your data; the download link expires after 10 minutes.
• Edit profile (tap your profile at the top of Settings) lets you change your display name and avatar.
• Settings → Delete account deletes your account, as described above.

For anything else, email cs@ccdigitlab.com. We’ll reply within one month.

Complaints. If you’re unhappy with how we’ve handled your data, email cs@ccdigitlab.com and we’ll acknowledge your complaint within 30 days, look into it and tell you the outcome without undue delay. You can also complain to the Information Commissioner’s Office at ico.org.uk.

Transfers outside the UK

Some of our providers, such as Google, Apple, Anthropic and Supabase, may process data outside the UK. Where they do, we rely on the safeguards available under UK data protection law, such as approved standard contractual clauses or an adequacy arrangement. Email cs@ccdigitlab.com if you’d like details of the safeguards for a particular provider.

Security

Data is encrypted in transit, passwords are stored hashed, and our database uses row-level access rules so people can only reach their own household’s data. No system is perfectly secure, so please keep your device and your household invite code safe.

Children

OopsOut isn’t directed at children under 13 and we don’t knowingly collect their data. If you think a child has given us their data, email cs@ccdigitlab.com and we’ll delete it.

Changes to this policy

If we change this policy we’ll update this page and the date at the top, and tell you in the app if the change is significant.

Contact us

Crestline Create Digit Lab Ltd, registered in England and Wales, company number 16805497.
Registered office: Apt 903, Fifty5ive, 55 Queen Street, Salford, Manchester M3 7GX.
cs@ccdigitlab.com