Chef Pepper Privacy Policy

What we store, why, who can see it, and how to delete it.

Effective: 16 September 2026
Who we are: Simply In Depth Ltd
Contact: support@simplyindepth.com

Chef Pepper is a cooking app. You ask it for a recipe, it writes one, and it keeps what you cook so a new phone does not lose it. This policy explains what that means for your data.

1. The short version

You need an account, because the app cooks using a service we pay for.
Your recipes, your cooking profile and (if you turn it on) your photographs are kept with your account so they survive a reinstall.
Your conversations with Chef Pepper stay on your phone. They are not uploaded, with one narrow exception you choose: reporting an answer sends that one message so somebody can read it.
If you publish, your name goes with it. Every published recipe names the cook who wrote it, and every cook has a short code — like @A7F33T — that anyone can look up. What you write about yourself is separate, and yours to show or keep. Your allergies are never on your profile either way.
We do not use advertising identifiers, we do not track you across other apps or websites, and the app contains no advertising, analytics or crash-reporting SDK.
You can delete your account from inside the app, and it really deletes.

2. What we store, and why

What	Why	Where
Your email address and account identifier	To sign you in and attach your recipes to you	Our database (Supabase)
What you ask Chef Pepper, and the recipe it writes	To produce the recipe and to keep it in your Recipe Book	Sent to our server and to OpenAI. The recipe is stored. The question itself is not — except when you ask for a change to a saved recipe ("make it lighter"), which is stored alongside the new version so you can see what changed
Your cooking profile — allergies, dietary restrictions, instructions, dislikes, cuisines, sodium limit, servings, skill level, equipment, measurement system, budget	So a reinstall does not quietly lose your allergies	Stored only while "Remember my settings if I change phones" is on. Turning it off deletes the stored copy
Your profile — a display name you choose, a UID we mint for you, an avatar you pick from a fixed set, and whatever you write in "about" and your cooking note	So a cook who liked your recipe can see who wrote it	Our database. Your name, UID, avatar and published recipes are visible to other cooks. What you write in "about" and your cooking note is shown only while you turn that on — see section 5
Photographs you attach to a recipe	So a reinstall does not lose them	Stored only while photo backup is on. Turning it off deletes them
Ratings, personal notes, favourites, collections and Recipe Book membership	To keep your Recipe Book	Our database
Cooking progress and questions asked while cooking	To let you resume a recipe mid-cook	Our database
Recipes you choose to publish	To show them in Discover, where anyone using the app can find them	Our database, publicly readable
Recipes you choose to share by link	So the person you send it to can open it	Our database, readable by whoever holds the link until it is opened
Comments you write on a published recipe	To show them under that recipe, with the name and UID on your profile	Our database, publicly readable
Cooks you have blocked	So we can stop showing you each other	Our database. Shown only to you. The cook you blocked is never told, and nobody can ask who has blocked them
A report you send us	So somebody can look at it	Our database
A thumbs up or down on an answer	To tell whether Chef Pepper's answers are any good, in aggregate	Our database — the direction and which answer, never the text
Purchases of Chef Credits	To give you what you paid for, and to handle refunds	Our database, and Google Play

What stays on your device

Your chat history, your Cook Mode switches and your text size never leave your phone. Uninstalling the app removes them, and nobody — including us — can recover them.

The one exception, which you control: if you tap Report this answer on something Chef Pepper said, that message is sent with your report so that a person can read it and act on it. The dialog says so before you send. Nothing else from that conversation is sent, and nothing is sent unless you tap report.

3. Photographs

Photographs are resized and re-encoded before they are saved or uploaded. That process discards the metadata your camera attached, including any location recorded in the original image. We never receive it.

Photo backup is off unless you turn it on. You are asked the first time you attach a photograph.

4. Who else sees your data

We use three processors and no others:

Supabase — hosts our database, authentication and file storage.
OpenAI — receives what you ask Chef Pepper and your cooking profile, in order to write the recipe. It is sent to produce your answer, not to train a model on you.
Google Play — handles sign-in and payments. We never see your card details; we receive a purchase token which we verify with Google.

We do not sell your data. We do not share it with advertisers or data brokers. We do not use it to build a profile of you for any purpose other than cooking for you.

If you supply your own OpenAI key in Settings, your requests go from your device to OpenAI directly, under your own agreement with them, and our server does not see them.

5. Things other people can see

Discover. A recipe you publish is public, and it names you — your display name and your UID. Only the recipe is published: never your notes, ratings, cooking profile, or what you asked for. You can take a recipe down at any time.
Your profile. Every cook has one: your display name, your UID, the avatar you picked, how many recipes you have published and the month you joined. Another cook reaches it by tapping your name on a recipe or a comment, or by typing your UID into the search box.
We used to let a profile be hidden entirely, and stopped, because it could not be made true. A published recipe now names the cook who wrote it — so the name is public whether or not the page is, and a switch promising otherwise would have been promising something the rest of the app contradicts.
What you write about yourself is still yours to withhold. The "about" and cooking-note fields are shown only while you turn that on, and they are off until you do.
Your allergies and dietary restrictions are never shown, on or off. You gave us those so that Chef Pepper would not make you ill, not so that they could be published. A recipe can be taken down; a medical fact cannot be un-told.
If you would rather not be seen at all, do not publish. Nothing about a cook who has published nothing is shown to anybody who has not been given their UID, and a UID is six characters out of more than two billion, so it is not something anybody finds by guessing.
Comments. A comment you write under a published recipe is public and carries the name and UID on your profile. You can delete your own comments. Nobody else can — not even the cook who published the recipe, who has to report a comment like anyone else if they want it gone.
Blocking somebody. If another cook is someone you would rather not hear from, you can block them from their comment or their profile. You stop seeing their recipes, comments and page, and they stop seeing yours.
They are not told, and there is no way for anyone to ask who has blocked them.
Blocking is not the same as reporting, and it does not remove anything. What they wrote stays where it is for every other cook. If something should not be there at all, report it — that reaches a person who can take it down for everybody. You can undo a block in Settings.
Shared links. A link you create can be opened by whoever holds it, until the first signed-in person opens it, after which it belongs to them. A link you were already sent keeps working even if one of you later blocks the other — it was handed to you deliberately.
Reports. Someone can report a recipe you published or a comment you wrote. We may remove it.

6. Deleting your account

Profile → Delete account. It is immediate and it cannot be undone.

Deleted: your recipes and their revisions, photographs, Recipe Book and collections, your cooking profile, ratings, notes, cooking progress, thumbs, your profile and everything written on it, every comment you have written, every block you made and every block made against you, your Chef Credit balance and usage records, anything you published, and everything the app kept on your device.

Kept, with you no longer attached to it:

A report you sent us about somebody else's content — a recipe, a comment, a share or something Chef Pepper said — with your identity removed. The report concerns content that may still be in front of other people, and deleting it would drop a case we may still need to act on. It can no longer be traced back to you.
The record that a purchase happened, with your identity removed. Refunds and chargebacks outlive an account, and Google may ask us about a transaction after you have gone.

Neither can identify you afterwards.

If you have uninstalled the app and cannot reach that screen, email support@simplyindepth.com from the address you signed up with and we will delete the account for you. There is also a page explaining all of this that you can reach without the app: account deletion page.

7. Keeping things

We keep what is listed in section 2 for as long as you have an account. When you delete your account it goes, except for the two severed records in section 6, which we keep for as long as we are required to — and which no longer name you.

8. Children

Chef Pepper is not directed to children and we do not knowingly collect data from anyone under

If you believe a child has given us data,

9. Your rights

Depending on where you live you may have the right to see a copy of your data, correct it, delete it, object to how we use it, or take it elsewhere. Deletion is built into the app. For anything else, email support@simplyindepth.com and we will answer within 30 days.

You can also complain to your local data protection authority. In the UK that is the ICO.

10. Security

Traffic is encrypted in transit. Your data is separated from other cooks' by database rules enforced on the server rather than by the app, so a fault in the app cannot expose somebody else's recipes. No system is perfect, and we do not claim otherwise.

11. Changes

If we change this policy we will update the date at the top, and tell you in the app if the change matters.