Privacy

Last updated 13 October 2026

What Kouzina stores

Everything Kouzina keeps, it keeps because you put it there:

• Your account — email address and a password (stored hashed; we can’t read it), plus a display name — it starts as the part of your email before the @, and you can change it in Settings — and the language you read Kouzina in, so your phones agree.
• Your family — the name of the cookbook and who belongs to it. Invitations are codes you hand to a relative; accepting one adds them to the family. An invitation addressed to an email address keeps that address — including after it is accepted or has expired — until the person who sent it leaves the cookbook or deletes their account, until someone with that address deletes their Kouzina account, or until the cookbook is deleted.
• Recipes — titles, ingredients, method, notes, who added them and where they came from.
• Photos — the recipe photo, and the photograph of the original card if you kept it (“in her hand”).
• Voice notes — recordings you attach to a recipe (“in her voice”).
• Favourites — which recipes you’ve hearted. These are personal to you, not shared with the family.
• Your plan — which plan your cookbook is on, a count of the AI imports and translations it has used (and that you have used, on the free plan), and, if you redeemed a lifetime key, which key and when. Each AI call, and any wrong key you type, is logged against your account for 48 hours.
• Share links — if you share the cookbook by link, we store the link’s token and the note you wrote for it, so the link can be shown and switched off.
• Reports — if you report a share link, a recipe or a member, we store the reason, anything you wrote, your account (if you have one), what or who you reported, and a copy of the family name, recipe title or display name as it was at that moment, so we can act on it even if it has changed since. Reports are kept so we can deal with repeat problems.
• Waiting list — if you join it on this site, your email address and the date. We send you one confirmation, then write again when Kouzina is ready, and use it for nothing else. Your browser also remembers the address so the form can show you’ve already joined.

Settings such as your chosen look and light or dark mode are kept on your own device, not on our servers.

Where it lives

Kouzina runs on Supabase: a Postgres database for the text and a storage service for photos and recordings, both hosted in Supabase’s US East region. Access is controlled row by row in the database, so a request can only ever return recipes belonging to a family you are a member of. The web app itself is served by Vercel. When you sign in or create an account, a Cloudflare Turnstile check runs on the form to keep automated sign-ups out; Cloudflare sees that one request — your IP address and browser details — in order to tell a person from a bot. It runs on the sign-in form only, nowhere else in the app, and is not used to track you. Emails Kouzina sends — the waiting-list confirmation, and account emails such as sign-up confirmation and password reset, and report notifications sent to us with a report’s details — are delivered by Resend or by Supabase’s own mailer, which see your address and the message in order to deliver it. When the iPhone or Android app opens, it asks Expo’s update service (EAS Update) for newer versions of its own code; that request carries the platform, the app version and a random per-installation identifier — Expo sees your IP address and nothing about you or your cookbook. Fonts for the printed cookbook and for this website are fetched from Google Fonts, which sees that request (your IP address and browser) and nothing else.

Who can see it

The members of your family cookbook, and anyone you choose to send a share link to. Kouzina has no discovery, no feed and no search across families: nobody can find your cookbook unless you invite them or send them its link.

The one exception is deliberate: if you share the cookbook by link, anyone with that link can read the recipes without signing in. The link shows the recipe text only — no photos, no recordings, no members’ names or email addresses — and you can switch it off at any time from the Family screen, which kills every copy of it.

Reading and translating with AI

Kouzina asks before it sends anything to an AI service, and you can change your answer at any time on the Family screen. The answer is saved on each device you use, so a new phone asks again. With it turned off, nothing is sent: recipes show as they were written, and imports are read on your phone where that is possible.

Importing. In the iPhone and Android apps, a photographed card on its own is first read on your phone, and if that works the photo is not sent to any AI service. When it can’t be — handwriting, mostly — or when you paste text, or send a photo together with typed notes, what you submitted is sent to Anthropic’s API, which reads it into a draft of ingredients and steps for you to check. When you save the recipe, the card photo is kept with it as the original (“in her hand”); nothing is kept for a draft you don’t save.

The card reader on your phone. Reading a card on the phone uses Google’s ML Kit. The photo and its text stay on the phone, but ML Kit sends Google anonymous diagnostics — the device model and system version, the app’s version, a per-installation identifier, timings and error codes — which Google uses to keep ML Kit working. It isn’t tied to your account.

Translating. When a recipe in your family’s cookbook is written in a language other than the one you use Kouzina in, its text — title, category, notes, ingredients and steps — is sent to Anthropic’s API to be translated into yours. This includes recipes other members typed in themselves. The translation is stored with the recipe so relatives who read the same language see the same one, and the recipe as written is never changed. Photos and voice notes are never sent for translation.

Those are the only things your data is sent to Anthropic for. (A once-a-day check that the service is up sends it one word, and nothing of yours.) Anthropic does not train its models on data sent through its API.

Links. Pasting a link makes our server fetch that page; the site sees an ordinary request from our server, not from you. If the page carries a structured recipe, it is read without any AI. Only if it doesn’t is the page’s text sent to Anthropic. If the site blocks us, the link is looked up on the Internet Archive and an archived copy is read instead. The recipe’s photo, if the page has one, is shown in the draft straight from that site (or the Archive), so it sees that one request from your phone. If you keep the photo, our server fetches it once more to store it with the recipe.

What we don’t do

• No advertising, and no advertising networks.
• Inside the app: no analytics, no tracking pixels, no fingerprinting and no third-party cookies. The one thing we count is visits to this website (kouzina.app). Vercel Web Analytics records which page was opened, the country, the site that sent you, and your browser, operating system and device type. It sets no cookies and stores nothing on your device, and it cannot tell one visitor from another across days: its daily visitor tag is built from the request and discarded after 24 hours. The app itself never loads it. Today Kouzina sets only what it needs to keep you signed in, plus the waiting-list reminder described above. (Two third parties see something: ML Kit’s anonymous diagnostics and Cloudflare’s bot check on the sign-in form, both described above.)
• No selling, renting or sharing of your data with anyone.
• No training of any model on your recipes, photos or recordings — by us or by anyone on our behalf.
• No reading your cookbook. We look at a family’s data only if you ask us to help with a problem, or if someone in your family or with a share link reports something, and only as far as that takes.

Deleting things

You can delete a recipe, a photo or a voice note yourself, inside the app, and it’s gone from the cookbook straight away. Leaving a family takes your access with it. An owner can also remove a member, who then needs a new invite to come back.

To delete your whole account, open Settings in the app and tap Delete account. After you confirm, your account and your personal data — your profile, family memberships, favourites and invites — are removed straight away. Reports you made, or that were about you, are kept but no longer linked to your account. If you can’t sign in, email support@kouzina.app from the address you signed up with and we’ll do it for you within 30 days.

Recipes you added to a family cookbook stay with the family (they’re the family’s recipes), no longer marked as added by you, unless you delete them first. If you were a family’s only member, that cookbook is deleted with your account, recipes, photos and voice notes included. The account deletion page walks through it.

To come off the waiting list, reply to any email we send or write to the same address.

Keeping it safe

Traffic is encrypted in transit. Passwords are hashed. Database access is enforced by row-level policies rather than by application code alone, and those policies are tested. No system is perfect; if we ever learn of a breach affecting your data we will tell you promptly.

Children

Kouzina is a family product, but accounts are for adults. Children can be shown the cookbook on a parent’s phone; they shouldn’t hold an account of their own.

Changes

If this policy changes in any way that matters, we’ll say so in the app and update the date at the top. We won’t quietly widen what we do with your data.

Contact

Kouzina is made by Jeff, in his own kitchen. Questions about privacy go to support@kouzina.app.