Privacy policy

Privacy policy

Cyber Trends Design Group · the app and thechefsamora.co.zw · updated 28 October 2026 23 sections

In short

Plain version: your taste profile, meal plan and recipes stay on your phone. Your account, your bookings and messages, and a chef's public listing are held in Google Firebase, where only the people who need them can read them. What you type into the AI kitchen, and any photograph you take of your fridge or of your plate, is sent to Google to be answered. Anything you publish to the feed is public to everyone using the app. Nothing is sold, advertised against, or used to train anything.

01

Who we are

TheChefSamora is published by Cyber Trends Design Group Limited. This policy covers the Android app and our website, thechefsamora.co.zw. The website has a section of its own near the end.

Where this policy says "we", it means Cyber Trends Design Group Limited. Where it says "the app", it means the software on your phone.

02

What stays on your phone

A good deal of what the app holds never leaves the device it is on. Stored locally, and nowhere else unless you back up:

  • Your taste profile: dietary preferences, favourite cuisines, allergies, cooking time, meal style, budget, kitchen equipment and experience level
  • Recipes, kitchen notes and notifications
  • Your meal plan and grocery list
  • Saved recipes and the chefs you follow
  • Recipes you import from other sites, including the photograph from the original page
  • Every recipe you have finished cooking and when you finished it — the list under Notes, and what decides how the home screen greets you
  • Your app settings, including the theme
  • If you are a chef, the parts of your profile that are not in your public listing, including your languages, cancellation policy and how you want to be paid

This lives in the app's private storage. Uninstalling the app deletes all of it. Signing out leaves it in place for when you sign back in; if a different account signs in on this phone, everything of yours is deleted before anything of theirs is shown. The sections below describe everything that does leave the phone.

03

Your account

Accounts are handled by Firebase Authentication, a Google service. When you register with an email address we hold that address and an authentication record; we never see or store your password. If you sign in with Google we receive your name, email address and profile picture from your Google account, and nothing else. If you sign in with Apple we receive the name you choose to share, the first time only, and an email address — your own, or a private relay address from Apple if you chose to hide yours. If you turn on two-step sign-in, Firebase holds that setting as well.

Each time you sign in, the app also keeps a short account record in our database: your name, your email address, whether you use the app as a cook or a chef, whether you have finished setting up, and when you last signed in. Only your own signed-in account can read or change it.

Firebase gives your account an identifier. That identifier, not your email address, is what everything we hold is filed under, so changing your email does not detach you from your own records.

04

Your profile photo and your handle

Both are optional.

If you add a profile photo, it is uploaded to Firebase Storage and shown to the people you talk to. Anybody holding its link can load it, which is what makes it appear on a page at all; only you can replace it. To have it removed, write to us.

If you publish a handle so other cooks can find you, the handle and the display name you chose are readable by any signed-in account. Nothing else is attached to it — not your email address, and nothing that can be worked back to one. Releasing the handle in the app removes it.

05

The feed

The feed is the one part of the app that is public. Everything else in this policy is either on your phone or shared with one other person.

A post carries your display name, your handle, your profile photo, the title and text you wrote, the photograph you attached, and a copy of the recipe you attached if you chose one. Any signed-in account can read it. Deleting a post removes it and its photograph.

A comment under a post carries your display name, your handle, your profile photo and the words you wrote. It never carries a photograph — the app does not let a comment hold one. Any signed-in account can read it. You can delete your own comment at any time, and whoever wrote the post it sits under can take it off their post.

Every post is checked automatically as it is written: its words go to Google's Gemini model and its photograph to Google's image safety check, both in Google Cloud, to see whether it breaks the kitchen rules. A comment is checked the same way, its words only. Nothing is kept by us from that check except the outcome.

When a post or a comment is removed — by that check, by three people reporting it, or by us — a copy is kept where only a reviewer can read it, for twelve months, so the decision can be looked at again or undone.

When you report a post or a comment, we store which one it was, which account you are and the reason you gave. The person who wrote it is not told who reported it.

When you block an account, the list of who you have blocked is stored against your account and can be read by nobody but you.

When you like a post, that is stored against your account and counted on the post. Nobody is shown who liked what, and taking the like back removes it.

A kitchen note stays on your phone unless you choose to publish it, which is a separate action on the note itself.

06

Whether you are in the app

Off until you turn it on. With it on, the people you are in a conversation with can see whether you are in the app and roughly when you last were; with it off they see neither, and nor do you. The switch is in Settings, under "Who can see you".

What is stored is one record against your account: whether you are here, and the time you last were. Any signed-in account can read it, which is what makes it useful to somebody waiting on your reply.

The time is rounded before anybody is shown it — "a few minutes ago", "yesterday", and nothing at all once it is more than a week. Nobody is ever shown a clock time: what hour somebody was on their phone is not something a conversation needs to know.

Turning it off deletes the record rather than hiding it, so there is no last-seen time left behind saying exactly when you turned it off. Deleting your account deletes it as well.

07

Reporting a conversation

If somebody writes to you in a way they should not, the menu on that conversation blocks them and reports them.

Blocking is kept against your account, readable by nobody but you, and it stops their messages at the database rather than hiding them on your phone. Reporting stores which conversation it was, which account you are, which account it is about and the reason you gave — never the messages themselves. A reviewer can open the conversation if they have to. The person you reported is not told who reported them, and the report is kept for twelve months and then deleted.

08

The AI kitchen, and what it sends to Google

This is the part of the app that shares the most, so it is worth reading.

The AI kitchen, the nutrition estimate, the calorie scan, ingredient substitutions, recipe writing, AI search and reading recipes from a link all work by sending a request to Google's Gemini models through Firebase AI Logic. Depending on which you use, that request contains:

  • The message you typed, and up to the last ten messages in the conversation
  • The ingredients found by your most recent pantry scan, when they are relevant
  • The title, ingredients and method of the recipe you are looking at
  • Your search terms
  • The photograph you took of a plate, when you ask what is on it
  • The text of a recipe page you asked the app to import, when the page does not describe its recipe in a form the app can read by itself

It does not contain your name, your email address, your account identifier, your allergies, your location or your saved recipes.

Google processes these requests under its own terms as our service provider. We do not control how long Google holds a request. If that is not acceptable to you, the AI features are the only part of the app that use it, and the rest works without them.

We do not keep a copy of your conversations with the AI kitchen on any server of ours. They exist in the app's memory for the session and are gone when you close it.

09

Photographs of your fridge

The pantry scan takes a photograph and sends it to Google's Gemini models to be turned into a list of ingredients. The photograph is held in memory only for as long as that request takes. We never write it to disk, never upload it to our own servers, and it is not attached to your account.

We cannot make the same promise on Google's behalf: once the image is sent, its handling is governed by Google's terms as our processor.

The app asks for camera access at the moment you open the scan, not at launch, and no other screen uses the camera. Declining it stops the scan and nothing else.

10

Cloud backup

Your kitchen is kept against your account so that losing your phone does not lose it. This happens on its own, shortly after something changes, and "Back up to the cloud" in Settings is a way to say now rather than the only way it ever happens.

What is kept: the recipes you have written, imported or asked the AI kitchen for; your kitchen notes; which recipes you saved; the chefs you follow; your meal plan; and your taste profile, which includes the foods you said you avoid.

What is not: your photographs, which stay on your phone — a recipe or a note kept here carries its words and not its picture — and your conversations, which are covered further down and are not part of this.

Security rules on our database allow only your own signed-in account to read or write any of it. Nothing here is published: sharing a recipe or a note is the feed, which is a separate and deliberate act described above.

"Restore from the cloud" replaces what is on your phone with that backup. It does not merge, and the row says so before you press it.

11

Chef bookings and messages

A booking is stored in our database so that you and the chef see the same thing. It holds both of your account identifiers, the chef's name, your name, the chef's specialty and price, the date and time, any note you added, and whether it is waiting, confirmed, declined or cancelled. Our database rules let only the two people in a booking read it, and only the two of them can write messages under it.

So that two cooks cannot book the same evening, the app also records that the hour is taken. That record holds the date, the time and the booking's reference — not your name or anything else about you — and any signed-in account can see that the hour is gone.

Direct messages between two people work the same way: only the two participants can read the conversation. It stores each person's handle and a short preview of the latest message, so your message list can show it.

Messages cannot be edited or deleted once they are sent, by either side, because both people rely on the same record of what was agreed.

12

Notifications

If you allow notifications, your phone's notification token is stored against your account, so we know where to send them. Only your own account can read it, and signing out removes this phone from the list.

When somebody asks for a booking, answers one, or messages you, our server sends a notification through Firebase Cloud Messaging, a Google service. The notification carries the sender's name and a short preview of what they wrote, so that part of the message passes through Google on its way to your phone.

13

If you register as a chef

Your public listing is what cooks browse. It holds your name, specialty, price, how you work, your bio, your service area, your portrait, the photographs of your dishes and the hours you have opened. Any signed-in account can read it, and only chefs whose identity has been checked appear in the list cooks browse. Only you can change it. To take it down, write to us.

To be bookable you send a photograph of an identity document and of your food hygiene certificate. They are uploaded to Firebase Storage, where nothing in the app can open them — not cooks, and not you. They are looked at by a person on our team, who records whether each one checked out. We never create a shareable link to them.

We also keep a note that you have sent a document for review: your account identifier, your name, and when you sent it. Only you can read that note in the app.

14

Recipes you import from other sites

When you paste a link, the app fetches that one page from your device and reads the recipe data the site publishes for search engines. If the page does not publish it, the page's text is sent to Google's Gemini models to find the recipe, as described above. The recipe text and its photograph are saved on your phone.

The site you are importing from will see the request, as it would for any visitor. We are not told which recipes you import, and imported recipes are never shared with other users of the app.

15

Checking the app is genuine

Firebase App Check confirms that requests really come from an unmodified copy of this app rather than something pretending to be it. On released versions this uses Google Play Integrity, which reports on the app and the device — not on you, and not on anything you have done in the app.

16

Our website

Most of thechefsamora.co.zw is a set of plain pages: what the app does, and this policy. There is no advertising, no analytics and no tracking anywhere on it.

One part is different. At thechefsamora.co.zw/kitchen you can sign in with the account you already have and use two things on a bigger screen: your messages, and the AI kitchen. You cannot create an account there — that happens in the app.

  • Signing in uses the same account as the app: your email address and password, or Continue with Google. We never see your Google password
  • While you are signed in, Firebase Authentication keeps the session in your own browser's storage so you are not asked again on every page. Signing out clears it
  • Your messages on the website are the same ones the app shows, read from and written to the same place. The website keeps no separate copy
  • What you type into the AI kitchen on the website goes to Google's Gemini models through our own server, as described above for the app. The conversation is kept in your browser rather than on our servers, and clearing your browser data clears it
  • We count how many AI kitchen requests your account makes each day, so the service cannot be run up without limit. That is a number and a date against your account, and nothing about what you asked
  • If you choose light or dark in the site's theme switch, that choice is saved in your own browser so the next page opens the same way. It is never sent to us
  • The site's typeface is loaded from Google Fonts, so your browser asks Google for it and Google receives your IP address and browser details when it does
  • Like any website, each visit reaches the server that hosts the site, which sees your IP address and the page you asked for
  • Email addresses on the site open your own email app; nothing is sent until you send it

A second part is different. At thechefsamora.co.zw/beta you can ask to test the app before it opens to everybody. That page collects two things and no more: your email address, and whether you use Android or an iPhone.

  • We send one note to that address with a link in it, so we know the address is really yours. Until you follow that link nothing else happens
  • Following it sends your address and the phone you chose to our own inbox at support@thechefsamora.co.zw, where a person reads it and decides. It goes nowhere else
  • No account is created by any of this. Accounts are made in the app, by people who have been invited — there is still no way to create one on the website
  • An address that is never confirmed is deleted after seven days. A confirmed one is kept until the testing is over, or until you ask us to remove it
  • Ask at any time, at support@thechefsamora.co.zw, and the address goes

17

What we do not do

To be explicit, because policies adapted from websites often imply otherwise:

  • There is no advertising in the app or on the website, and no advertising identifier is collected
  • There are no analytics or crash-reporting services
  • Neither the app nor the website sets advertising or tracking cookies; signing in on the website keeps a session in your browser's own storage, and nothing else
  • There is no newsletter and no marketing email. If you ask for a beta invitation we write to you twice at most — once to confirm the address, once with the invitation — and not again
  • We do not sell, rent or trade your information to anyone
  • We do not track you across other apps or websites
  • We do not collect your location
  • Your content is not used to train AI models by us

"Help improve the AI" in Settings is off unless you turn it on, and turning it on shares nothing until we build the feature it describes.

18

How long we keep things

On-device data lasts until you delete it or uninstall the app. Everything else we hold about you — your authentication and account records, your backup, your bookings and messages, and a chef's listing and verification documents — lasts until your account is deleted, or until you ask us to remove it sooner.

A post you delete goes at once. A post that was removed for breaking the rules, and any report filed about one, are kept for twelve months so the decision can be looked at again, and then deleted.

A booking the other person was part of stays with them after you delete your account, so they can still see what happened to it, but with your name and your messages removed.

19

Deleting your data

"Reset all app data" in Settings clears your taste profile — dietary preferences, cuisines, allergies and cooking preferences — and keeps your account.

"Delete my account" in Settings removes your account and everything filed under it:

  • Your sign-in, your account record and your cloud backup
  • Your profile photo and your handle
  • Your posts and the photographs on them, and the comments you have left under anybody's post
  • The reports you have filed and your block list
  • If you are a chef, your listing, its photographs and your verification documents
  • Your messages, in bookings and in direct conversations
  • Everything the app holds on your phone

If you signed in with Apple, the app also asks Apple to end its access to your Apple ID.

Bookings that are still waiting or confirmed are cancelled, and the other person is told. On bookings they keep, your name is replaced with "Deleted account". If you have not signed in during the last few minutes, the app asks you to sign in again first, so that a phone left unlocked is not enough to erase an account. Deleting your account cannot take back what the other person has already read.

In Settings you can also release your handle on its own. Uninstalling the app removes everything held on the phone, but not your account.

If you cannot use the app, write to privacy@thechefsamora.co.zw from the address on the account and we will delete it for you and confirm when it is done, within thirty days.

20

Your rights

You can ask for a copy of the information we hold about you, ask us to correct it, ask us to delete it, and object to how we use it. Zimbabwe's Data Protection Act applies, and if you are in the UK or the European Economic Area, the GDPR applies too.

If you are not satisfied with our answer you may complain to your national data protection authority. In Zimbabwe that is the Postal and Telecommunications Regulatory Authority of Zimbabwe.

21

Children

This app is not intended for children under thirteen and we do not knowingly collect information from them. If you believe a child has created an account, write to us and we will remove it.

22

Changes to this policy

If we change what the app collects or who it is shared with, we will say so in the app before the change takes effect. Small corrections are made without notice. The date at the top says when this policy last changed.

23

Contact

Cyber Trends Design Group Limited
Privacy questions: privacy@thechefsamora.co.zw
Anything else: support@thechefsamora.co.zw