Privacy Policy

Last updated 26 October 2026

YumAURA is a cooking diary you share with people you choose. This page describes what we collect, why, who helps us run it, and how to get a copy of your data or delete it. It describes our processing. It is not itself your consent. Where we need permission, we ask for it separately: your phone asks before the camera, microphone or photo library is used and before we send you notifications, and we will ask before any recipe import is sent to an AI provider.

It covers the YumAURA app, the pages on yumaura.io, and email you send to support.yumaura@gmail.com.

Who we are

YumAURA is run by Edison Tan (“we”), who is the controller of your personal data. You can reach us at support.yumaura@gmail.com about anything on this page. We apply UK data protection law to this service.

What we collect

• Your account: an account ID, your email address and a password. You sign in with your email address and password. Our sign-in provider stores the password as a one-way hash: we cannot turn the hash back into the password. When you create an account, or tap Forgot? on the sign-in screen, we email you a one-time code. When you change the email address you sign in with, we email the new address a link to confirm it. When you create an account we also ask your date of birth; nobody else can see it. We keep when you agreed to our Terms of Use, and which version. If you stop before your account is made, or the date of birth you give is under 13, the email address and password you typed are deleted within a day, and straight away where the app can tell us.
• Your profile: your name, handle, bio and profile photo, the city you chose if you chose one, and whether your account is private. A new account starts private if you are under 18, and public if you are 18 or over.
• Your city, if you choose one: one city you pick from our list, or none. It is a name you choose: the app does not use your phone’s location for it. It is shown on your profile, wherever your bio is shown, to you and the people who follow you, and to anyone else signed in only if your account is public and the date of birth you gave says you are 18 or over. It is also on your taste card if you share that card. It is not put on a post, a post’s picture or a link. We keep the city you last chose and when you chose it, because a move to a different city is once in six months. We also keep whether you want to be ranked in your city, which is on unless you turn it off, and whether the date of birth you gave says you are 18 or over. If your city is not on our list you can send us its name, and we keep that name with your account.
• Your city’s leaderboard: anybody signed in can look at any city’s leaderboard. If you are on your city’s, they see your name, handle and photo, how many posts and recipes you shared with Everyone, and how many weeks in a row you posted. Nobody you have blocked, or who has blocked you, sees you there. You are on it only if the date of birth you gave says you are 18 or over, your account is not private, and you have not turned ranking off. Only what you shared with Everyone is counted, at most three posts and one recipe a day, and never a recipe you keep for subscribers. A leaderboard’s month and year turn at that city’s own midnight. A city may also have a challenge for a month, set by us: one more board of the same people, counting only posts of recipes with one tag, by the same rules.
• Your city’s shelf: people who chose the same city as you see a shelf on Discover named for it, such as Cooking in London, with a list behind it. If the date of birth you gave says you are 18 or over, the recipes you share with Everyone can be on it, even if you turned ranking off, but never a recipe you keep for subscribers. If your account is private, they are on it only for the people who follow you. It is ordered by how many posts of each recipe, of those you can see, people based in that city who are 18 or over logged in the last 30 days; the number is not shown. Your own recipes are not on the shelf you see, and clearing your city takes them off it at once.
• What you post: the photos and short videos you choose, and what you add to them: the dish, a caption, a recipe, how it went, who you cooked with, and a place. The place is a name: one you pick from a list or type yourself. While you are choosing a place, the app may ask to use your phone’s location to list places near you, through Apple’s maps on iPhone. That location is used only for that list: it is not stored or sent to us, and the post keeps only the place name you pick. Location data in a photo or clip is still removed when we prepare it to be shown, and the original file is not kept.
• What you do with other people: who you follow, your Yums and replies, messages, the posts and recipes you save, and anyone you block or report. When someone who follows you opens the profile of a person you follow, it can show your first name and photo among the people they follow who follow that person. It shows them nothing your Following list does not.
• Feedback you send from Settings → Send Feedback: the message, your name, handle and account ID, the app and phone system versions, the screen you were on, and a reference number for the request.
• Support email you send us, and our replies.
• Technical records: our servers log each request your phone makes: the time, the kind of request, whether it worked, how long it took, and the build number of the app that sent it. Each request’s log also carries two random reference numbers for it, one your phone makes and one our server makes, so that a fault you tell us about can be found. Those logs do not include your IP address. The companies that run our servers and sign-in keep their own connection logs, which do include your IP address (see below). To limit abuse, our server also counts requests from each address for about an hour, and keeps only a one-way hash of the address to do it.
• Your phone: a record of each phone you sign in on, with the kind of phone, the app version, whether you allowed notifications and, if you did, its notification address.
• Your time zone: your phone’s time zone, so your day, your streak, your goals and the leaderboard week turn at your own midnight. It is updated when your phone’s changes.
• Screen records: which screens you opened, and some of what you did there, such as giving a Yum, sending a reply or a message, or sharing an invite. These can include the ID of the post or recipe involved. They do not include what you wrote or searched for.
• Our server’s records of what you do: when you post, follow someone, give a Yum, reply, save a recipe and the like, our server makes a record of it with the IDs involved, such as yours and the post’s or recipe’s, and some facts about it, such as who it is shared with or whether it has a photo. They never hold what you wrote. We use them to send notifications, keep search up to date and see which parts of the app are used, and send a copy to PostHog (see below).
• Nutrition on recipes: a recipe’s calorie and nutrient figures are worked out on our own servers from its ingredient list when it is opened. They are shown only to people whose date of birth says they are 18 or over: nobody else is sent them, even for a recipe of their own. They are not stored, and no AI service is used. If you switch nutrition off on recipes in Settings → Nutrition, we keep that you did, and when. If you correct how a line of your own recipe is counted, we keep that correction with the recipe, and anyone 18 or over who can open the recipe sees figures that use it.
• Your taste profile, if you make one: the cuisines, dishes and flavours you pick, what you are working towards, your diet, how many you cook for, how much cooking suits you, and any foods you can’t eat. Described below.
• Your cooking aura, if you choose one: the one or two habits you pick for how you cook lately. Described below.
• Paid partnerships, if we have approved you as a chef and you show one: for each thing a brand pays you to show, its picture, what it is, the brand and your link. Described below.
• Chef subscriptions, if our team gives you one: which chef, when it started, and when it ends or ended. A subscription is given by our team, free; nothing is sold. It lets you open the recipes that chef keeps for subscribers. The chef is not shown who subscribes.

We use technical records, the record of your phone, screen records and our server’s records of what you do to keep YumAURA working and secure, to send you notifications, and to see which parts of the app are used. We do not use them to advertise to you.

YumAURA only sees the photos and videos you pick. It uses the camera and microphone only while you take a photo or record a clip, and the microphone while you record your voice over a video you are editing. That voice stays on your phone until you post the video, and then it is part of the video’s sound. We do not sell your data. A chef we have approved may show, on their own recipe, things a brand pays them to show, labelled Ad; this is described below. A brand may also pay us for one shelf on Discover, labelled Ad, which we show only to people whose date of birth says they are 18 or over; this is described below too. Both are switched off today: nobody is shown a paid partnership or a paid shelf. There is no analytics or advertising code from another company in the app. Our own servers send PostHog our records of what you do, and the app and our servers send Sentry a report when they fail; both are described below. Apple also receives the app’s crash reports if you have chosen to share them: in your iPhone’s settings, under sharing analytics with app developers, or through TestFlight if you use a test version. The pages on yumaura.io do not set cookies and do not load third-party analytics.

Why we use it

• To run YumAURA for you (our agreement with you): your account, your diary, showing your posts to the people you choose, messages, and saved recipes.
• To keep YumAURA safe and working (our legitimate interests): stopping abuse, acting on reports, fixing bugs, protecting accounts, and keeping a record that a deletion or a support action happened.
• With your permission (consent): access to your camera, microphone and photos, and notifications, which you can turn off at any time in your phone’s Settings. Recipe reading help, described below, is a separate permission. It is off, and we will ask before we turn a send to an AI provider on for your imports. So is the How you eat part of your taste profile, described below, which you give by answering and withdraw by taking an answer off or deleting your taste profile.

Who can see what you post

You choose who can see each post when you share it, and you can change it later. Other YumAURA users can see your name, handle and profile photo. Suggested for you shows your account to adults only if the date of birth you gave says you are 18 or over; people whose date of birth says they are under 18 are shown it either way. People search follows the same age rule, except that people you follow or who follow you can find your account regardless of age. Only an accepted follow counts, not a pending request. Anyone with a link to your profile can still open it. If you gave no date of birth, Suggested for you shows you only people whose date of birth says they are 18 or over; people search also includes people you follow or who follow you, once the follow is accepted. If you are under 18, your account starts private: people ask to follow you, you approve each one, and your posts reach only the people who follow you. A recipe you share with Everyone can still be found and read by anyone. If you are 18 or over, your account starts public, and anyone can follow you. An account made without a date of birth starts private. If we learn later that an account belongs to someone under 18, we make it private and tell them. You can change your account’s setting in Settings → Privacy.

Discover can show a wall of the posts people share with Everyone, newest first, to anyone signed in who does not follow them. A post you share with Everyone is on it only if you chose Everyone where the app says that anyone can find it on Discover, and only while the date of birth you gave says you are 18 or over. A post you shared with Everyone before the app said so is not on it, and choosing Followers or Only me takes a post off it at once. Your own posts and those of people you follow are not on the wall you see, and nobody you have blocked, or who has blocked you, sees yours there. This wall is switched off today.

A post you share with Everyone shows a card wherever its link is pasted, such as in a message or a chat app: the picture that leads the post, your first name, and the dish’s name when you gave one, or the title of the recipe it was cooked from when you wrote that recipe yourself and share it with Everyone. A recipe you wrote and share with Everyone shows a card too: its own photo, its title, your first name, and how many ingredients and steps it has. People who are not on YumAURA can see these cards, and so can someone you have blocked. Nothing else is on them: no caption, no names, no place, no Yums or replies. If your account is private, or the date of birth you gave says you are under 18, your links show the YumAURA card, with no picture and no name. The link of a post or recipe shared only with your followers, or only with you, shows the same YumAURA card for every link, with no picture and no name. A card a chat app has already drawn can stay in that chat after you change who can see the post or recipe, or delete it, and we cannot take it out of someone else’s chat.

If you name someone on a post, they can see that post, including one that is otherwise private to you. Taking their name off removes that access. If you have also sent them the post in a message, the message can keep their access until you unsend it.

If they add their side of the evening, YumAURA copies the photos and clips onto that side, as their own copies in their diary, with the dish’s name, the place and the recipe notes you cooked with; notes you wrote are credited to your @handle. Those copies stay if you later delete your post, take their name off, or close your account. You keep the copyright in your photos and clips. The copy lets them keep the evening in their diary inside YumAURA. It does not transfer that copyright, and it is not permission for them to republish the photos elsewhere. A side that never received a photo, and has nothing they wrote on it, is deleted with your post.

You can start a direct message with someone who follows you, even if you do not follow them back, when the dates of birth you both gave say you are 18 or over. Otherwise a direct message is only between two people who follow each other. You cannot start one with someone who does not follow you, and a conversation started this way stays open while either of you follows the other. A group is different. The person who starts a group must follow, and be followed by, everyone they add, but the others in it do not need to follow each other. So a group can put you in a conversation with someone you do not follow. You can only name people you and they already follow. In a reply you can mention someone who follows you, with @ and their handle. They are told, unless they have turned Replies off. A mention never lets anyone see a post they could not already see, and someone who cannot see it is not told. Only people who can see who you follow, or who follows you, can tell a mention from the words around it.

A block hides your posts and your messages from each other inside the app, and deletes the Yums and replies each of you left on the other’s posts, and the replies each of you wrote to the other’s replies, wherever they are. The mentions each of you made of the other go too, and the reply that held one keeps its words. The Terms of Use say what else a block does. A link you have already shared can still be opened by anyone who has it.

Your taste profile

Your taste profile is optional. You can make it as you sign up, or later in Edit Profile, under Your Taste and How You Eat, by answering up to six questions. Each answer is saved when you go on to the next question, and you can change or delete any of it there at any time.

It has two parts. Your taste is the cuisines, dishes and flavours you pick, and any you take off. It makes your taste card. Once ten of your Cooks or saves carry a cuisine, a dish or a flavour, that list is ordered by what you cook and save, your Only me Cooks included, and your picks stay on it. A Cook you said you didn’t like counts for nothing. Beside each cuisine is the number your own ranking gives it, which only you see. How you eat is what you are working towards, your diet, how many you cook for, your skill level, whether you want quick weeknight dinners, and the foods you can’t eat, such as peanuts or milk. Some of these answers say something about your health, and a diet such as halal or kosher can say something about your religion. So we keep this part only because you choose to tell us, and we never work any of it out from what you cook or save.

Nobody but you can see your taste profile in the app, including the people who follow you, and our support panel cannot show it. It is not on your profile. When you share your taste card, it carries your taste: a line about it, up to two counts and up to three cuisines. While your picks lead, the counts are how many cuisines and dishes you picked, and the cuisines are your first three picks. Once your cooking leads, the counts are how many Cooks you have and how many cuisines you have cooked, and the cuisines are the three you cook most, all counting your Only me Cooks too. A card never names a Cook and never shows your numbers. From How you eat it carries only what you choose for that card: one more line with a diet, an aim or your cooking goal. The foods you can’t eat are on a card only if you switch them on for that one share. That switch is off every time. The picture of your card is drawn on your phone. If you send it to an Instagram Story, your newest post shared with Everyone goes with it as the background. A picture goes only where you send it, and once it is sent it cannot be called back.

When you open a recipe, the app compares it on your phone with the foods you can’t eat. It reads what the recipe says it contains and its ingredient list, and shows a line if one matches. This is not a promise that a recipe is safe: we can only read what the recipe says, not packaged ingredients or cross-contact.

On Discover, a shelf called Your taste shows recipes that carry the cuisines, dishes, flavours and diet you picked, or what an aim you chose stands for, such as high protein. Our server chooses them from your taste profile when you open Discover, and only you see the shelf. It leaves out any recipe that would show you a warning for something you can’t eat. It changes when your answers do, and stops when you delete your taste profile. Our screen records can note that the shelf was shown and that a recipe on it was opened or saved, never what is in your taste profile.

We do not use your taste profile for ads. Screen records never hold what is in it. We do not put it in push notifications or messages. Your inbox can tell you, at most once in 30 days, when your card’s line changes, and only you see that. We do not send it to any AI service. It is included in Export Your Data. Delete Taste Profile, at the foot of Edit Profile, deletes it at once, and closing your account deletes it too.

Your cooking aura

Your cooking aura is optional. It is one question about how you cook lately: you pick one or two of seven habits, such as “I plan or prep meals ahead.”, and the app shows them as your aura, a name such as Keeper × Creator, a colour and a line. We keep the habits you picked, in the order you picked them, and when you kept them. Nothing is worked out from what you cook or save, and nothing is scored.

Your cooking aura is not part of your taste profile. It is shown on your profile, to whoever can see your profile: anyone on YumAURA if your account is public, and only the people who follow you if it is private. Nobody you have blocked, or who has blocked you, can see it. Other people see its names, its line and what each name means. Each name stands for one of the habits you picked. Nothing from your taste profile goes with it.

You can share a picture of your aura from its page. It shows its names, its line, the YumAURA wordmark and “What’s your cooking aura?”, and it is drawn on your phone; nothing leaves until you choose where it goes. The food you love, the first few of your cuisines, dishes and flavours, is on it only if you switch that on for that one share. That switch is off every time. Nothing else from your account goes on it.

You can change your picks or remove your aura at any time, from your profile or in Edit Profile, under How You Eat. Removing it does not touch your taste profile, and deleting your taste profile does not remove your aura. We do not use it for ads, and we do not send it to any AI service. It is included in Export Your Data, and closing your account deletes it.

Challenges with people you invite

Challenges are switched off today. You can start a challenge, such as cooking one dish in a week, cooking every day for seven days, or cooking the most over a few weeks, and invite people who follow you. Each person invited gets one invitation, in their inbox and, if they allow it, as a notification on their phone, and chooses whether to join. We keep each challenge’s kind, its dish and the other names you gave it, its dates, your time zone, who was invited and what each of them answered, and when.

A challenge is seen only by the people on it and the people invited to it. Once you join, the posts you log from then until it ends count towards it, including the ones only you can see. The people on it see your name, handle and photo and how far you have got: whether you cooked the dish and on which day, which of your days are done, or how many posts you logged. They never see the post itself, its photos, its words, or what you thought of it. Somebody you have blocked, or who has blocked you, does not see you on it, and you do not see them. You can leave whenever you like, which takes your name and your days off it; the person who started it can end it early.

We do not use your challenges for ads, and we do not send them to any AI service. They are included in Export Your Data. Closing your account deletes your place on every challenge and takes your name off the ones you started, which the others on them keep.

Paid partnerships on a recipe

A chef is somebody our team has approved, and wears a chef’s hat after their name. A chef may show, on a recipe they wrote, up to three things a brand pays them to show: a picture, what it is, the brand and a link. They are labelled Ad, and the link is the chef’s own. Paid partnerships are switched off today.

Our team checks each thing before anyone but the chef can see it, and can see all of a chef’s things. We accept kitchen tools, appliances and store-cupboard food. We do not accept alcohol, sweets or snacks. After the check, a thing is shown to everyone who can open the recipe.

What you are shown is decided by the recipe alone. We do not choose it by what you have cooked, saved or put on your grocery list, or by your taste profile, and we do not tell the chef or the brand who you are. Opening a link leaves YumAURA for a page that is not ours, with its own privacy policy. Our screen records can note that a recipe’s partnerships were opened: they record the recipe and a thing’s place on it, never its name, its brand or its link.

A chef can take a thing away, which takes it off every recipe and deletes its picture. We keep what it was, the brand, its link and how our check of it stood until the account is closed: it is our record of what was shown as an ad. That our team checked or refused it, and why, is also in the audit log of support actions, which is kept after an account closes (see “Deleting your account”). A chef’s paid partnerships, those taken away among them, are included in Export Your Data, and closing the account deletes them.

A shelf a brand pays for

A brand may pay us to show one shelf on Discover, on days our team sets, named Ad and Cook with the brand’s name. It holds recipes shared with Everyone whose chef shows a paid partnership with that brand, each checked by our team as described above. The line under its name says who paid for it, what chose its recipes and who is shown it. This shelf is switched off today.

We show it only to people whose date of birth says they are 18 or over. Anyone else, and anyone who gave none, is shown no shelf. What is on it is decided by the brand and the recipes alone. We do not choose it by what you have cooked, saved or put on your grocery list, or by your taste profile, and we tell the brand nothing about who saw it. Our screen records can note that the shelf was shown and which recipe on it was opened, as they do for every shelf on Discover.

Who helps us run YumAURA

These companies process data for us, to provide their service:

• Supabase: our database, sign-in and photo storage, on servers in Frankfurt, Germany. This includes the email address you sign in with, and the password hash. Supabase keeps its own logs of sign-in and storage requests, which include your IP address.
• Resend: sends the emails with your one-time sign-in codes, and the link that confirms a new email address, for our sign-in provider. It receives your email address and the code or the link.
• Render: runs our servers, in Frankfurt, Germany, including the request logs described above. Requests to our servers pass through Cloudflare, which Render uses at the edge of its network. Render and Cloudflare keep their own connection logs, which include your IP address.
• Expo: handles notifications. If you allow notifications, the app gets a notification address for your phone from Expo’s servers, and we store it with your account. When we send you a notification, its text goes through Expo’s service on its way to Apple, or to Google for an Android phone, which delivers it to your phone. That text names who it was from and the dish or recipe it is about, such as “Maya replied to your Laksa.” or “Maya mentioned you in a reply on Laksa.” It never quotes what they wrote. You can turn the names off in Settings → Notifications, and the text is then a general line, such as “New reply on your Cook.” On a new account made by someone under 18, or with no date of birth, the names start off, and you can turn them on there.
• Vercel: hosts this website. Hosting can include a connection log of a visit. Our pages do not set cookies or load anyone else’s scripts.
• Google: holds the support mailbox at support.yumaura@gmail.com. Messages you email us, and our replies, sit in that mailbox. On an Android phone, Google’s Firebase Cloud Messaging delivers notifications to your phone.
• Slack: receives the feedback you send from the app, with the details listed above: the message, your name, handle and account ID, the app and system versions, the screen and the request’s reference number. A report also sends Slack a short alert: the kind of thing reported, the reason, when, and the report’s reference number. That alert does not include who reported it or the content itself. Blocking someone sends the same short alert, saying that a person was blocked, so that our team can look at that account as it would after a report. It does not say who blocked them. If you reported something of theirs a few minutes before, or blocked them in the last 30 days, no second alert is sent: the first already told us. When you say yes to We read it wrong?, Slack receives the link of the recipe you brought in and what we read from it, and not your name, your account or anything you changed. Closing your account does not remove a copy already in Slack, but if you ask, we delete it there.
• PostHog: receives a copy of our server’s records of what you do, described above, keyed by your account ID, so that we can see which parts of the app are used. They never hold what you wrote. When you close your account we delete your record there, with those copies.
• Sentry: receives a report when the app or one of our servers fails. A report can carry your account ID, the IDs of the post, recipe or job involved, the kind of request, the app screen it happened on, and your phone’s model and system version, never what you wrote. Sentry keeps a report for no more than 90 days.
• Anthropic: only if recipe reading help is switched on, which it is not. See below.

These companies decide their own processing. They are not acting only on our instructions:

• Apple: on an iPhone, you install YumAURA from the App Store, or through TestFlight if you use a test version. Apple handles the install, and any crash reports or feedback you choose to share, under Apple’s privacy policy. Apple also delivers notifications to your iPhone. When you add a place to a post, Apple’s maps answer the search: what you type there, and your location if you allowed it, go to Apple and not to us.
• Google Play: on an Android phone, you install YumAURA from Google Play. Google handles the install, and any crash reports you choose to share, under Google’s privacy policy.

Supabase and Render process our database, sign-in, photos and servers in Frankfurt. That is where your account and posts are stored. It does not decide where every other provider processes data. Resend, Cloudflare, Expo, Vercel, Slack, Google, PostHog, Sentry, Apple and, if it is ever switched on, Anthropic may process data outside the UK, including in the United States. Where UK law requires a safeguard for a transfer, we use the safeguard in that provider’s contract, such as the UK International Data Transfer Addendum where the contract includes it. A Frankfurt address on its own is not that safeguard for the other providers.

Bringing a recipe in

When you import a recipe, YumAURA fetches the page you named, or uses text you paste, and tries to read it on our own servers. Fetching a page is a request to that website. Our hosting providers process the import as part of running YumAURA. Neither of those is a send to an AI company.

For a video post whose caption lists the ingredients but not the method, YumAURA can also listen to the post: it fetches the post’s sound on its own, not the video, and turns what is said into text on our own servers. That is switched off today. Once it is on, the sound is deleted as soon as it has been read and is never kept, and the words are kept with your import, as passages quoted from a page are, so that you can check the recipe against them. What is heard in a public post’s video can also be kept on its own for 30 days, linked to nobody who imported it, so that the next person to import that post, while its caption is unchanged, gets the recipe without the post being listened to again; keeping it is switched off today. Listening is not a send to an AI company.

For a post on Instagram or TikTok, YumAURA can also keep a small copy of the post’s cover picture, at most 640 pixels on its longest side, fetched from that platform’s own servers. That is switched off today. Once it is on, the copy is stored privately and shown only to you, beside the recipe you brought in and on its row in your Kitchen: never on Discover, in a share or a message, on a link’s card or on a picture you share. It is deleted when you delete the recipe or close your account.

If a recipe was read wrong, We read it wrong?, under Save, asks before it sends us anything. Say yes, and the link and what we read from it go to our team’s Slack, so we can fix our reader. Your name, your account and anything you changed are not sent. The post may join the set we test our reader on, linked to nobody.

So that sharing a post into YumAURA can bring its recipe in without opening the app, the app keeps a key on your iPhone, in the same protected storage as your sign-in, that can do nothing but bring a new recipe in from a link and, when you ask it to, send us a report that we read it wrong. A recipe kept that way is kept as the app keeps one: its ingredients go on your grocery list where the app would put them, and its words are the ones sent from your iPhone. The key lasts 90 days at most, and a new one replaces it while you use the app. Signing out deletes it from your iPhone and withdraws it when we can be reached. If you sign out with no connection, it keeps working, on no phone, until it runs out, 90 days at most. Changing your password, or signing out on another phone, does not withdraw it. Closing your account withdraws every key you have. That is switched off today.

If our own reading cannot finish a draft, recipe reading help can send the source text of that import to Anthropic, which proposes a draft for you to check. For a video, that text can include the words heard said in it. We do not attach your name, your handle, your account ID or your cooking notes to that request. The text itself can still contain those things, or someone else’s, because it is the page, caption or words you imported. We do not send a photo or a screenshot to Anthropic.

Nothing from a draft is saved as a recipe until you accept it. Rejecting the draft, or later deleting the recipe, does not undo a send that has already happened. Anthropic’s standard API terms keep requests for a limited time and allow exceptions, including for safety reviews. We have not yet confirmed retention, training use and processing region on the account we would use, so recipe reading help stays off. While it is off, nothing you import is sent to Anthropic. Switching it off does not stop the page fetch, and does not stop our hosts from processing the import.

Before we switch it on, we will say so here, confirm those provider terms, and ask you before an import of yours is sent.

How long we keep it

We keep your account, posts and messages while your account is open.

• Screen records are deleted after 90 days, or sooner if you close your account.
• Our server’s records of what you do are deleted 90 days after they are made, once they have been passed on. Closing your account does not delete them sooner: they hold IDs, not what you wrote.
• A download of your data is kept for 7 days after it is ready, then deleted.
• Finished background jobs are deleted 30 days after they finish. A job can hold your words, such as feedback you sent. Text you pasted to import a recipe is removed from its job when the job finishes.
• Recipe imports: each import also keeps its own record, with the link you gave and the draft read from it, while your account is open. Short passages quoted from the page to back up the draft, and words heard said in a video post, are deleted after 90 days. The copy of a post’s cover is kept while its recipe is, or for a day when we found no recipe in the post and you added nothing to it.
• The key for bringing a recipe in: our record of each key is deleted 30 days after the key stops working, and when you close your account.
• Saved answers to your requests are deleted after 90 days. When you do some things, such as post or edit a post, reply, send a message, start a recipe or a new version of one, set a goal or make a share link, our server keeps its answer for 90 days, so that a request your phone sends twice is only done once. That answer can include what you wrote. Deleting the post, or closing your account, does not delete it sooner.
• Request logs are kept so we can fix faults and investigate abuse. We do not keep a separate long-term archive of them. Render keeps its own copy for as long as the plan we use retains logs.
• Reports are kept so we can show what was reported and what we did. They are not deleted on a fixed date.
• The log of support actions, with each look in our support panel, is kept so we can show what our team did. Each entry is deleted two years after it was written.
• A record of each phone you signed in on is deleted 90 days after that phone stops being signed in to your account, such as when you sign out on it or close your account.
• Evidence: if a report of child abuse, or a request from the police or a court, requires it, we keep an account’s posts and files, unpublished, until that is settled, even if the posts or the account are deleted.
• Feedback already in Slack, and support email already in the mailbox, stay there. Closing your account does not remove them. If you ask, we delete your feedback from Slack.

Deleting your account

You can close your account at any time in Settings → Manage Account → Delete My Account. You need to have signed in recently. You lose access straight away. There is no undo.

Normally within minutes, we then delete your posts and the photos and videos on them, including the smaller copies we made; your notes, goals, grocery list, meal plan and saves; your nutrition setting and the corrections you made to how your recipes are counted; your taste profile; your cooking aura; your city and any city you asked us to add; your messages, and your replies, with the replies other people wrote under them, and your Yums; your follows and blocks; your paid partnerships; your chef subscriptions, and if you are a chef, everyone’s subscriptions to you; your record in PostHog; the date of birth you gave; your recipe imports, with their drafts, the text you pasted and the copies of their posts’ covers; and the email address and password you sign in with. Every recipe of yours is emptied and its title becomes “Deleted recipe”. It keeps its place in the recipe history so that other people’s versions of it keep working. Each of its versions also keeps its short name and its note on what changed, if you wrote them. Someone else’s version of your recipe stays theirs, and its credit reads “Based on another cook’s recipe”. Every link you shared stops working. Messages the other person sent stay, without your words. Your place on every challenge goes, and the challenges you started stop naming you; the others on them keep them.

Copies of your photos that someone has already accepted onto their side of an evening stay in their diary, as explained above. Your copyright does not transfer with them. A side that never received a photo, and has nothing they wrote, is deleted with your account.

A few records stay after that, for a stated reason:

• A closed-account marker. Your name becomes “Deleted account”. We keep the marker so a saved copy of the app cannot recreate the account. We do not delete it on a schedule.
• The status of the deletion, for 90 days, so you can check that it finished. The receipt cannot recover anything.
• Our record that the deletion was requested and completed. It does not contain your posts or your email address. It is deleted two years after you asked, once the deletion has finished.
• Saved answers to your requests, described above, until their 90 days end. They can include what you wrote in a post, a reply or a message.
• A record of each phone you signed in on, without its notification address: the kind of phone, the app version, whether notifications were allowed, and when it was last used. It is deleted 90 days after your account is closed, or sooner if you signed out on that phone earlier.
• Places you added as where a dish came from, such as a restaurant’s name, area and link. Other people’s posts can point at them. Each still records that your account added it.
• Reports you filed or that were filed about you, and the audit log of support actions, so we can show what was reported and what we did. Each entry in that log is deleted two years after it was written.
• Feedback and support email already sent to Slack or to our mailbox.
• Database backups, until those backups are replaced. Supabase takes daily database backups. They do not include the photo files. We do not promise a fixed number of backup days. A backup taken before you closed your account still holds the account as it was then. We would only restore a backup to recover from a serious failure. If we did, an account or post deleted after that backup was taken could come back without its photos, and we do not yet have a step that deletes it again automatically. We would tell the people affected.
• A photo cached on someone else’s phone, until that cache expires. A photo they saved outside YumAURA is outside our deletion.

If recipe reading help has been used, text already sent to Anthropic stays for as long as Anthropic keeps it. Closing your account does not recall it. That help is off today, so this does not apply to current accounts.

Getting a copy of your data

You can ask for a copy at any time from Settings → Export Your Data. You get two files, which you can download on that screen for 7 days. Then they are deleted. Each download link works for 5 minutes. One is a JSON file with your profile, your city and any city you asked us to add, posts, recipes and their versions, notes, saves, grocery list, meal plan, goals, Yums and replies, follows, followers, blocks, invites, your nutrition setting and corrections, your taste profile, your cooking aura, the date of birth you gave, when you agreed to our Terms of Use and which version, your chef subscriptions, the email address or phone number you sign in with, and your messages. If we have approved you as a chef, it also has the things you were paid to show and which of your recipes they are on. It also has the caption you wrote on each photo or video, your notification settings, and your recipe imports, each with the link it came from, if it had one, and the draft read from it. It also has each report you made: what you reported, the reason you chose, the words you wrote and when. It also has the challenges you started and your place on each you were asked to. The other is a CSV file with one row for each of your posts, to open in a spreadsheet. Your messages are every message you sent, including any you unsent, and the messages other people sent you that you can still read in the app, as the app shows them. Messages from someone you have blocked, or who has blocked you, are not included, and neither are messages you reported. The export lists your photos and videos by their storage names, not the files themselves. It does not include another person’s private material. Email us if you want a copy of something it leaves out.

Your rights, and complaints

Under UK data protection law you can ask to see, correct or delete your data, to limit or object to how we use it, to take it with you, and to withdraw any permission you gave. Email support.yumaura@gmail.com. We will answer that request within one month. That deadline is for the request itself.

A complaint about how we handle your personal data is separate. Email the same address with “privacy complaint” in the subject. We will acknowledge it within 30 days, look into what happened, and write to you with the outcome and what we will do about it. You can also complain to the Information Commissioner’s Office at ico.org.uk.

Children

YumAURA is for people aged 13 and over. When you create an account we ask your date of birth, and we do not create an account for anyone under 13. The email address and password typed before that question are deleted too. We keep only that date, nobody else can see it, and it is deleted with your account. An account created before we asked has none unless you add it, which you can do once, when your profile asks for it or where you choose your city. An account created while we asked only the month and year keeps those. If you tell us, or we otherwise learn, that an account belongs to someone under 13, we will delete it. An account that tells us it is under 13 is hidden from everyone and signed out at once, and deleted after 7 days. If the date was a mistake, it can be put right by emailing us within those 7 days.

People aged 13 to 17 may use YumAURA. Their accounts start private, and they approve each follower; an adult’s account starts public. Adults are not shown their accounts in Suggested for you. In people search, an adult can find an account under 18 only when either person follows the other and the follow is accepted; a pending request does not count. Other people under 18 can find them as before. A new account of theirs starts with notifications that do not name who acted, until they turn names on. If we learn later that an account belongs to someone under 18, we make it private and tell them. If the date of birth you gave says you are under 18, your city is shown only to you and the people who follow you, and a taste card you share does not carry it. You choose who sees each post. A direct message with someone under 18, or with someone who gave no date of birth, is only between two people who follow each other. A group can include people you do not follow, as long as whoever started it follows, and is followed by, each person in it. You can only name people you and they follow, not strangers. Like everyone, someone under 18 can be mentioned in a reply only by people they follow. Where a dish was cooked is a place name you pick or type. While you choose one, the app may ask to use your phone’s location to list places nearby; that location is not stored, and the post keeps only the name. You can report a post, recipe, profile, reply or message, and you can block someone. A recipe’s estimated calorie and nutrient figures are not shown to anyone whose date of birth says they are under 18, or who gave none. A shelf a brand pays for on Discover is not shown to anyone whose date of birth says they are under 18, or who gave none. A recipe’s paid partnerships are shown to everyone who can open the recipe, 13-to-17-year-olds included.

Allowing 13-to-17-year-olds means UK rules on children’s data can apply. These pages are not a completed children’s-data assessment. If you are under 18, or you are a parent, and something in the app worries you, email us and we will look at that account.

Keeping it secure

Traffic between the app and our servers is encrypted in transit. Access to the systems that hold your data is limited to the people who operate YumAURA and to the providers named on this page, within their service. In our support panel, a change such as hiding a post or suspending an account needs a written reason, and is logged. Looking something up in the panel, such as an account, a post’s dish name or a report, is logged too: who looked, whose data it was, and on which page. The people who operate YumAURA can also read the database directly, to run and repair it. A password hash means we cannot read your password. It is not a promise that the account cannot be attacked. No setup can promise that a breach is impossible.

Changes to this policy

If we change this policy, we will update this page and its date. If the change is significant, we will tell you in the app before it applies. While your account is open you can export your data from Settings. Switching on recipe reading help, adding analytics or advertising code from another company to the app, or sending PostHog more than the records described above, would be a significant change.