Privacy Policy

Who Runs SueChef

SueChef is operated by Andrew Henkel in the United States. It is a personal project, not a company. There is no sales team and no marketing list.

Questions about anything on this page go to suechef@klawiter.app.

Invitation Only

Self-service account signup is not available at this time. An account exists only because someone already in a household invited your email address, and households are created by hand. If you received an invitation you did not expect, you can ignore it — an unaccepted invitation creates no account.

Data Collected

• Your account. Email address, an optional display name, and a hashed password. Passwords are stored as ASP.NET Core Identity hashes and are not recoverable in readable form — not by you, and not by us.
• Your recipes. Titles, ingredients, directions, notes, timings, nutrition figures, and any personal story you choose to attach to a recipe, along with the folders you file them in. If you added a recipe by pasting a link, the link itself is kept too, so the recipe can say where it came from. That is the web address only, not a copy of the page or the video behind it.
• Your household. Its name, and who belongs to it. Recipes belong to a household, so everyone in yours can read and edit them.
• Your displays. A name and a random key per kitchen display, plus which recipe each one is currently showing, and — once a display has registered itself — a public key identifying that screen's own program.
• What you say to a kitchen display. When you speak to a display, the recording is sent away to be turned into text and understood (see Service Providers below). SueChef does not keep the recording. It keeps the words only for a command it had to think about rather than recognise outright, so that the phrasings people actually use can be added to the ones a display knows instantly. Those are visible to your household alone, and any of them can be deleted.
• Photos of recipe cards you add. When you add a recipe from a photo, the photo is kept alongside the text read out of it, so the original card stays readable next to the typed version. It is kept for as long as that recipe is, and deleting the recipe deletes it. Photos are stored privately and are never reachable from the login-free kitchen display page.
• Ordinary web server logs, which include IP addresses and requested pages, kept for troubleshooting and to spot abuse.

What We Don't Do

• No advertising, and no advertising networks.
• No analytics, tracking pixels, or third-party scripts. The site loads no code from anywhere but itself.
• No selling, renting, or sharing of personal information with anyone, for any purpose.
• No marketing email — see Email below.
• No profiling, and no automated decisions that have a legal or similar effect on you.

Cookies

SueChef itself sets three cookies, all strictly necessary and none used for tracking: a sign-in cookie that keeps you logged in on a device, an anti-forgery cookie that stops forms being submitted from other sites, and a display cookie.

The display cookie is set only on a kitchen display, and only once that display's own small program has proved it is that display. It says which screen the page is, so the screen can be tapped to browse the recipe library. It lasts until the browser closes, is never written to the display's storage, and identifies a screen rather than a person.

One exception, and it is not ours. A recipe saved from a TikTok link shows that video in TikTok's own embedded player. While that player is on the page, your browser is talking to TikTok directly, and TikTok can see your IP address and set its own cookies under its own privacy policy. This happens only on recipes imported from TikTok, and only while you are looking at one. Every other page, including the kitchen display showing any other recipe, sets no third-party cookies at all.

Service Providers

SueChef is a small app standing on a few larger services. Each receives only what it needs to do its job:

• Amazon Web Services — hosting, storage, and outbound email. Your data lives here.
• Anthropic — recipe text and recipe photos are sent to the Claude API to be turned into structured recipes, to estimate nutrition, and to write recipe suggestions. What you say to a kitchen display is sent there too, as text, to work out which command you meant.
• Microsoft Azure AI Speech — if you use read-aloud, the text of that recipe is sent to Azure to be turned into audio. If you speak to a kitchen display, the recording is sent to Azure to be turned back into text, along with a list of your folder names and recipe titles so that Azure can recognise them when you say one. That list is sent every time the display listens, whether or not you name a recipe. The recipes themselves — ingredients, instructions and any story you have written — are never sent for speech recognition.
• TikTok — when you paste a TikTok link, SueChef reads that post's public caption, and its subtitles if the caption has no recipe in it, to fill in the recipe for you to check. Nothing about you is sent to TikTok in the process. Separately, if you then view that recipe, the video plays in TikTok's own embedded player, and your browser contacts TikTok directly as described under Cookies above.

Your password is never sent to any of them.

Email

SueChef sends transactional email only: household invitations and password resets. It sends nothing on a schedule, nothing promotional, and nothing you did not trigger, so there is no mailing list to unsubscribe from. Replies to suechef@klawiter.app reach a real person.

If you would rather receive no email from SueChef at all, submit a request to suechef@klawiter.app and your account will be removed.

Data Retention

Recipes and account data are kept until they are deleted. You can delete individual recipes and folders yourself at any time. To delete your account and everything in it, email suechef@klawiter.app.

One caveat worth being clear about: recipes belong to a household, not to an individual. Deleting your account removes you and your personal details, but recipes you added stay with your household, the same way a recipe card left in a shared box would.

Your Choices

Whatever rights your jurisdiction gives you over your data — to see it, correct it, export it, or have it erased — you can exercise here simply by asking. Email suechef@klawiter.app and it will be handled by hand, without argument.

Children

SueChef is not directed at children, and accounts are created only by invitation, so it does not knowingly collect information from children under 13.

Security

Traffic is served over HTTPS, passwords are hashed, and each household's recipes are kept separate from every other household's at the database level. That said, this is a personal project rather than an audited service — please do not keep anything in it that would be harmful to lose.

Changes

If this policy changes, the date at the top changes with it, and anyone with an account will be emailed about anything significant.