Oodie · Last updated 25 September 2026
Oodie saves recipes, plans the week and builds a shopping list. This page says exactly what leaves your phone to make that work, what happens to it, and how to get rid of it. It describes what the app actually does, not what a policy template says an app might do.
The short version. Your recipes are yours. We store them so they survive a lost phone and follow you to a new one. We do not sell them, we do not advertise against them, and we do not use them to train AI models. Delete your account in Settings and they are gone from our servers.
Oodie is published by Meera AI. Contact us at info@supremedigital.uk for anything on this page, including a request to see or delete your data.
| What | Why, and where it goes |
|---|---|
| Your email address | It is your account. Sign-in is handled by Amazon Cognito; if you sign in with Google or Apple, we receive your email address and nothing else from that account — no contacts, no profile, no Drive, no iCloud. |
| Your recipes, collections, meal plan and shopping list | Stored on your phone first, then synced to our database so they survive losing the handset. Only your account can read them, unless you share a recipe or a space. Sharing a recipe publishes a public page for that recipe. Anyone with the link can open it. A space (a collection or a plan) is shared with people you add by their Oodie id, or who join with an invite code. They can view or edit that space, as you set. The shopping list itself stays a message on your phone; it is not stored as a public page. Your Oodie id is a short code on your account so someone can add you. It is made from the first letters of your email address, with digits added if those are taken, and people in a space you share can see it. It is not your sign-in id. |
| What you log eating | If you use the Nutrition tab, each entry — a name, a date, a meal, a portion and its calories and macros — is stored on your phone and synced to our database with the rest of your library, so it survives losing the handset. Only your account can read it. It is never shared through a space or a public recipe page. Turning the Nutrition tab off in Preferences stops new entries; deleting your account deletes them. |
| Links you import from | When you paste or share a recipe link, our server fetches that page, reads the recipe out of it and stores the result as your recipe. We keep the link with the recipe so it can credit its source. If the site is a social app that did not give our servers the caption, the app may open that public link on your phone, copy the caption from the page, and send that caption (not the HTML) to our servers. The site may see your IP address and set cookies in that in-app browser; we do not keep a login there. |
| Photos you import from | A photo or screenshot you choose for an import is uploaded to our image storage and read once to extract the recipe. It then stays as that recipe's picture until you delete the recipe. Camera photos are not stored in the shared extract cache; they stay with your account. When we write a new recipe, we look up a public-domain food photograph using the dish name (not your account) and, if one is found, copy it into the same storage as that recipe's picture. |
| Barcodes you scan | Scanning a packet sends the barcode number — nothing else, and no picture — to our servers, which look it up in our own table and then in Open Food Facts, a public database of packaged food. We keep what a barcode means (brand, product, serving size, macros) so the next person to scan the same packet does not need a second lookup. That table is keyed by the barcode and is not tied to your account. |
| Photos of a nutrition label | If a packet is not in either database, you can photograph the nutrition table on the back. That image is uploaded to our image storage and read once by an AI model to get the numbers off it. What we keep afterwards is the product and its macros against that barcode, shared as above. The photograph is not attached to your account or shown anywhere. |
| A public extract cache | When an import comes from a public web URL, we may keep the structured recipe we read so the next person who shares the same link does not make us fetch it again. This cache is keyed by the public URL, not by you. Photos you take are not added to it. |
| A record of each import | Which kind of import it was, which website it came from, which AI model ran, how many tokens it used and whether it worked. This is how we notice an import path has broken and how we price the free tier. |
| Purchase state | If you subscribe, Google Play or the App Store gives us a purchase token (or an App Store original transaction id). We ask that store whether it is valid and store whether your subscription is active and when it expires. We never see your card. |
| A city for Discover and the planner | Optional. You type it in Preferences. We send the city name with Discover, a plan-populate request or a grocery-simplify request so we can pick the right catalog (India metro or UK/Europe), season, weather and typical shop availability. We do not read your location, and we do not store the city on the account. |
| Discover catalog | Not your data. We keep a shared index of public
schema.org/Recipe pages, with a copy of the structured recipe
and its photo, so Discover can load a dish when you tap it. The index is
not tied to your account. Saving a dish copies it into your recipes like
any other import. |
| Which Discover dishes you saved | When a dish you saved from Discover syncs, we note that your account saved that dish and when. We only ever use this as a count, to rank the dishes most people saved this fortnight. Nobody else sees who saved what, and deleting your account deletes the record. |
| Server logs | Ordinary request logs, kept 30 days, for keeping the service up. |
This one is worth its own heading, because it is the most sensitive permission Oodie asks for and the answer is the simplest.
If you turn it on, Oodie reads two numbers from Apple Health (on iPhone) or Health Connect (on Android): the energy you burned at rest and the energy you burned moving, for the last seven days. They are used on the phone to work out whether an active day should raise that day's calorie target, and for nothing else.
Companies process some of your data on our behalf, each for one job:
| Who | What they do with it |
|---|---|
| Amazon Web Services (Mumbai region) | Runs the servers, the database and the image storage. Stored recipe data is held in India (Mumbai). When a recipe import or nutrition estimate needs a model, the same account calls Amazon Bedrock; that inference request may be processed in another AWS commercial Region. |
| Anthropic | Provides the Claude model Amazon Bedrock runs for us. Recipe text or an image is sent for that request and the structured result comes back. Bedrock's commercial terms, and Anthropic's, do not permit training on that traffic. |
| Google Play | On Android, takes payment and tells us whether a subscription is live. Google's own privacy policy governs the payment itself. |
| Apple | On iPhone, the App Store takes payment and tells us whether a subscription is live. If you choose Continue with Apple, Apple confirms your email address and nothing else. Apple's own privacy policy governs those steps. |
| Google (sign-in) | Only if you choose "Continue with Google", and only to confirm your email address. |
| Open Food Facts | When you scan a packet we do not already have, we ask this public food database what that barcode is. They see the barcode number and our server's address. They do not see your account, your phone or anything else about you. |
| Openverse | When we write a new recipe, we ask Openverse for a public-domain food photograph that matches the dish name. They see that search, not your account. If a photo is found we copy it into our image storage. |
| Open-Meteo | If you typed a city, we may fetch a public forecast for it so Discover and the planner can follow the weather. They see the city, not your account. |
Nobody else receives your data. We do not sell it or share it for advertising, and there is no third party paying us for access to it.
These features send data to an AI model, and each is something you start deliberately:
Nutrition numbers are estimates from a food table (and, for missing foods, a model). They are not a measurement and not nutritional advice. Allergen flags are a keyword pass over the ingredient list. We do our best and cannot guarantee a dish is free of traces. The app says so wherever it shows them. Do not rely on either for a medical diet or a severe allergy.
Settings → Delete account, in the app. It removes your recipes, collections, meal plan, shopping list, food log, uploaded photos, the spaces you made (including any waiting in Recently deleted), your place in anyone else's spaces, and the record of which Discover dishes you saved from our servers immediately, along with your email address. If you had claimed a creator profile, it goes back to being a name under the dishes. The two exceptions are the anonymised records described in section 5.
What a barcode means is not deleted with your account, because it was never about you: the row says what is in a packet, keyed by the number printed on it, and is shared by everyone who scans it.
Deleting your account does not cancel your subscription — only the store you paid through can do that. Cancel it in the Play Store or in Settings → Apple ID → Subscriptions first, or you will keep being charged for an account that no longer exists.
If you cannot open the app, email info@supremedigital.uk from the address you signed up with and we will do it for you.
Everything travels over HTTPS. The database is encrypted at rest and is not reachable from the internet. Images are private and served only through our content delivery network. Your recipes are scoped to your account at the database level, not merely filtered in code, so there is no query that could accidentally return someone else's.
No system is perfect. If you find a security problem, please tell us at info@supremedigital.uk before telling anybody else, and we will fix it.
Oodie is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has created an account, email us and we will delete it.
Wherever you live, you can ask us for a copy of your data, ask us to correct it, or ask us to delete it. Deletion is built into the app; for the other two, email info@supremedigital.uk and we will reply within 30 days.
If you are in India, this includes your rights under the Digital Personal Data Protection Act, 2023. If you are in the EEA or UK, our legal basis is performance of a contract for the parts of the app you asked for, and legitimate interests for keeping the service running and preventing abuse.
If this policy changes in a way that affects what we collect or who we send it to, the app will tell you before the change takes effect. The date at the top always reflects the current version.