Privacy Policy

Last updated: 9 October 2026

This Privacy Policy explains how YesChef Kitchen Services LTD ("YesChef", "we", "us") collects, uses and protects the information you provide when using the YesChef app and this website. By using YesChef you agree to the practices described below. If you have any questions, contact us at enquiries@YesChefKitchenServices.com.

Information we collect

• Your account: first and last name, username, email address, a phone number if you give one, and your role in the kitchen. If you choose to sign in with Google we store the account identifier Google gives us — never your Google password.
• Your kitchen: its name, and the country and region you pick from a list so that the app applies the right food-safety rules. We do not ask for your address.
• Operational data: everything you enter to run the kitchen — recipes, ingredients, suppliers, equipment, stock, invoices, temperature logs, opening and closing checks, cooking and cooling records, cleaning records and delivery sign-offs.
• Training dates: if you record when a food-handler or manager certificate expires, we hold those dates so the app can warn you before they lapse.
• Sign-in security: a one-way hash of your password, never the password itself, and — if you turn on two-step sign-in — its secret and your recovery codes.
• Support basics: which version of the app you are on and when you were last seen, so we can help you and tell which release a problem belongs to.
• Your subscription: which plan you are on, whether it is active, and whether it was bought through Google Play or by card. Not your card details.

We do not collect payment card details through the app or this website, we do not buy or import personal data about you from third parties, and there is no advertising identifier in the app.

How your data is stored

Your data is held in an encrypted cloud database and is transmitted over secure, encrypted connections (HTTPS) at all times. The app is offline-first: your data is also held locally on your device so you can keep working without an internet connection, and it syncs securely to the cloud when you reconnect.

How we use your data

We use your information solely to provide and operate the YesChef service — to store your records, sync them across your devices, and support your account. We do not use your operational data for advertising.

What stays on your device

• Barcode scanning and reading printed text from a photograph both run on the handset itself, using a model shipped inside the app. Those images are not uploaded anywhere.
• Your records are written to the device first and sync to the cloud when there is a connection, so the app keeps working with no signal.
• There is no analytics, advertising or crash-reporting service in the app. We do not measure how you use it. The only usage information we hold is the app version and last-seen date listed above, and a count of how many scans a kitchen has made so its allowance can be measured.

Google Play services is part of Android rather than something we add, and it handles the barcode scanner and in-app purchases; what Google collects through it is governed by Google’s own privacy policy.

Who else sees your data

We do not sell or rent your personal or operational data, and we never share it for advertising. Your kitchen’s data belongs to you. A small number of named providers receive part of it, and only to make a particular feature work:

• OpenRouter — photographs you scan, and recipe-page text. Described in full below.
• Open Food Facts — a barcode, or a product name you typed, when you look up allergens. Described below.
• The recipe website you paste a link to — your device fetches that page itself. Described below.
• Brevo — your email address and the message, when we send you a verification email, a password reset, or a copy of your food-safety record.
• Stripe — card payments made on this website. Your card details go to Stripe and never reach us.
• Google Play — subscriptions bought inside the app are billed by Google. We receive the purchase record, not your payment details.
• Google — only if you choose to sign in with your Google account.
• Vercel — hosts this website and our server.

OpenRouter, Brevo, Stripe and Vercel act as our processors, under contracts that require them to protect your data and use it only to provide that service. Open Food Facts, and any recipe site you link to, do not — they are public services your own device contacts directly, and neither is sent your account details.

Cloud scanning of photographs

The app can create a recipe from a photograph of a page, and read a supplier invoice or delivery note the same way. That reading happens in the cloud, not on your device. When you scan, the photograph is sent over an encrypted connection to our server, and on to OpenRouter, which passes it to a vision model that returns the text. The current app has no on-device alternative: if you scan a page, the image leaves your device.

• Only when you scan: a photograph is sent only when you take or choose one for a scan. Nothing on your device is uploaded in the background, and your recipes, logs and records are never sent for this purpose.
• We do not keep the photograph: our server passes it straight on and retains only a count of how many scans have been made, so your plan’s allowance can be measured.
• Recipes, invoices and delivery notes alike: all three are read this way.
• And recipe-page text: when you import a recipe from a link and the site carries no structured recipe data, your device strips that page to plain text and it is sent by the same route, in place of a photograph.

For this feature OpenRouter acts as our processor and routes the request to a model host on our behalf, under the OpenRouter privacy policy. Two things follow from that: the request may be handled outside the United Kingdom and the European Economic Area, and some model hosts may use what they receive to train their own models.

If that is not acceptable for a particular document, do not scan it — recipes and deliveries can both be entered by hand instead.

Looking up allergens

When you ask the app for a product’s allergens, your device sends the barcode — or, when there is no barcode, the product name you typed — directly to Open Food Facts, a public food database. No account details go with it and the request is not signed in, but because it leaves your handset rather than our server, Open Food Facts can see your device’s internet address. Only the matched allergen names come back into the app; the rest of the reply is discarded. If you would rather not use it, allergens can be entered by hand.

Importing a recipe from a link

When you paste a recipe link, your device fetches that page directly, so the site sees the request and your device’s internet address, exactly as if you had opened it in a browser. Most recipe sites carry structured recipe data, which the app reads on the device with no cloud call at all. Only when a site carries none does the page text go for reading, by the route described above.

Your rights

You have the right to:

• Access the personal data we hold about you.
• Correct any data that is inaccurate or incomplete.
• Export your records, which the app can do for you at any time.
• Delete your data and close your account.

To access or correct your data, email us at enquiries@YesChefKitchenServices.com and we will action verified requests promptly.

Deleting your account

You can delete your account and your kitchen from inside the app, or by emailing us. We email you a copy of your food-safety record before anything is deleted. Signing in within 30 days brings the kitchen back as it was; at 30 days the kitchen and your personal details are deleted for good; your food-safety records are kept for 12 months so you can still obtain a copy, and are then deleted too. The full detail is on our account deletion page.

Cookies and tracking

The YesChef app does not use cookies. This website uses no tracking cookies and does not profile visitors.

YesChef office (desktop and the Microsoft Store app)

YesChef office is the desktop version of YesChef, at desk.yeschefkitchenservices.com and in the Microsoft Store. It signs in to the same YesChef account and talks to the same YesChef service as the Android app, so everything described above about your kitchen’s data applies to it too. It sets no cookies and contains no analytics or advertising trackers. It keeps a small amount in your browser (or in the installed app’s window, which is the same thing):

• Your sign-in, kept only for as long as the window is open. Closing the window or signing out removes it, so the next person at a shared computer is not signed in as you. While you sign in with Google, the office also keeps, for the same short time, the details it needs to finish that sign-in.
• An invoice scan you have not put on record yet: what was read from the invoice and the supplier, invoice number, account number and date as you left them, so a scan is not lost if the page reloads. It never keeps the invoice images. It is kept on that computer for up to seven days, offered back only to the same person in the same kitchen, and removed when you put the invoice on record, press "Start again", or when it is older than seven days.
• A copy of the office’s own pages, styles and icons, so that if the connection drops it can still open a page you have seen and show a "could not reach YesChef" page instead of a browser error. Your kitchen’s figures and your sign-in are never kept in this copy.

The office’s pages load their typefaces from Google Fonts, so Google receives your device’s IP address when a page opens. If you choose "Continue with Google", you sign in on Google’s own page, as you would in the app.

Changes to this policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with a revised "Last updated" date.

Contact us

For any privacy questions or requests, email enquiries@YesChefKitchenServices.com.