Skip to content

Privacy

What Home Chef keeps about you, why, who else sees it, and how to have it deleted. No advertising, no trackers, nothing sold.

Last updated October 3, 2026.

Who is responsible

Home Chef is run by Thomas di Luccio, a private individual, who is the data controller for everything described here.

For anything about your data, write to privacy@home-chef.eu.

What is kept

Your account: your name, your email address, the language you read the app in, your password if you set one (stored only as a hash), the Google account you linked if you did, your two-step verification secret if you turned it on, and your answers about being contacted.

Your kitchen: the links, text, photos and videos you add as sources, what is read out of them, your recipes, versions, notes and cooking log, and the pictures made for them.

Your conversations with Home Chef AI and your messages to us, with the files attached to them.

A record of what your account used — a recipe read, a picture made — so the allowance can be counted.

The technical minimum: the address your requests come from and your browser’s name, stored with your session, and error reports when something breaks.

Why

Most of it is the service itself: an account, the recipes in it and the answers to your questions cannot exist without it.

The technical record, the usage record and the error reports serve a legitimate interest: keeping the app working, secure and within its limits.

Being contacted for user research or the newsletter is your consent, given and taken back in settings at any time.

Who else sees it

Only the services the app cannot work without, each processing data on our behalf and for nothing else:

  • Upsun, which hosts the app and its database, in Sweden.
  • Mistral AI, in France, which reads the sources you add, the photos of recipes you take, your conversations with Home Chef AI, and draws pictures for recipes.
  • Google, only if you choose to sign in with it.
  • SendGrid, which delivers the emails the app sends you.

Where one of them handles data outside the European Union, the transfer relies on the EU–US Data Privacy Framework or the European Commission’s standard contractual clauses.

Error reports go to an error tracker run privately by the operator, not to a third party.

When you add a link, the app fetches that page or video from its own servers: the site sees Home Chef, not you.

A recipe you share is readable by anybody with its link. Nothing else in your kitchen is.

Cookies

One session cookie, and the security token that goes with it. They keep you signed in and remember your language and theme. There are no analytics, advertising or third-party cookies, which is why there is no banner.

What the operator can see

Whoever runs the app can see the accounts and what is in them, to answer a support message or to deal with abuse. They can also open the app as you to look into a problem; each time is written down in a log that cannot be edited.

How long

Everything stays as long as your account does. A recipe you delete sits in the bin for 30 days, then is gone.

Closing your account deletes it and everything in it, files included, at once. Two records outlive it, no longer linked to you: the record of what was used, and the moderation log.

Your rights

You can ask to see what is kept about you, to have it corrected, to receive it in a portable form, to object to how it is used, or to have it deleted. Write to privacy@home-chef.eu and you will have an answer within a month.

You can close your account yourself, from the sign-in and security page.

If you think your data is mishandled, you can complain to the data protection authority where you live.

Changes

When this page changes, the date at the top changes with it.