Privacy Policy

Last updated August 14, 2026

CookRight is made by 8x Social. This policy describes what we collect when you use the CookRight app and cookright.app, why we collect it, who else touches it, how long we keep it, and how to get rid of it. The short version: we collect what the product needs to work, some of it is health information and we treat it that way, we sell none of it, and you can erase all of it in one action.

It is written to be read rather than to be defensible, and it is specific on purpose — where a claim below is narrow (“never a name”, “no IP address”), the narrowness is the point.

What we collect

• Your email address — to sign you in with a one-time code. There are no passwords.
• Your household's eater profiles — the name or label you give each person, an age bracket (child, teen, adult, senior — never a birthdate), allergies, diets and other food rules, dislikes, goals, and a portion size (a cooking multiplier — never a body weight).
• Your dinners — recipes generated for you, the ones you save, whether you cooked them and how they went, and the lightweight preferences the app infers from your answers.
• Subscription and plan status — which plan you are on, when it changed, and how many recipes you have generated this month against your allowance.
• A two-letter country code — derived from your connection when you call our API, so we know which countries we serve. We store the country only. We do not store your IP address, city, or any precise location.
• Product and crash data — which screens are used, which actions succeed or fail, and what breaks. These events never contain profile names, allergy names, recipe content, or anything you type as free text.
• Anything you write to us — the email address and message you send through the support form. See How long we keep it for the one caveat that applies to these.

Health information, handled like it matters

Allergies and dietary restrictions are health information, and profiles in your household can describe children. We designed around that. Children never sign in and have no accounts — a child's profile is data the household admin manages, like a name on a grocery list. We deliberately collect an age bracket instead of a date of birth, and a portion multiplier instead of a body weight, because the coarser value is all the product needs.

Under GDPR terms, health data is a special category, and our basis for holding it is your explicit consent, given when you enter it — the app cannot do its job without it. You withdraw that consent by deleting the profile or your account, and nothing is retained afterwards.

What we send to our AI provider

Generating a recipe requires sending your table's requirements to OpenAI. This is the single point at which dietary data leaves our infrastructure, so here is exactly what goes:

• each eater as an anonymous label — e1, e2, e3 — with their age bracket, portion multiplier, and their dietary rules (for example “peanut allergy”, “halal”, “no mushrooms”);
• what you asked for — the craving or mood you picked, any ingredients you said you have or have run out of, and your answers to the app's questions.

Names never leave your device.Not the profile names, not your display name. Nor does your email address, your account ID, or your location. OpenAI cannot connect a request to you or to any person in your household, because we never send anything that would let it. Under OpenAI's API terms this content is not used to train their models, and they retain it for a short period for abuse monitoring only.

The safety check itself does not happen at the AI provider. The model proposes a recipe; a deterministic checker running on our servers against a versioned ingredient list decides whether it can be shown to you. A proposal that violates an allergy is discarded, not negotiated with.

Children's data

CookRight is not directed at children and children do not use it. You must be at least 13 to hold an account — 16 in countries where that is the minimum. Information about a child in your household is provided by you, the adult managing the account, and is used only to check recipes for that child. A child profile never receives a login, a notification, or an email from us, is never treated as a separate person in analytics, and is never used for marketing or for any form of advertising or profiling. If you believe a child has created an account, write to us and we will delete it.

Who processes data for us

These are all of them. There are no others, and this list changes only when the code does.

• Supabase — Database and sign-in. Every account and household record lives here, isolated by row-level security so one household can never read another.
• OpenAI — Generates recipes and recipe ideas. Receives the dietary rules for a request against anonymous labels — never a name, never your email, never your account ID. Detailed below.
• Resend — Delivers your sign-in code, as the mail sender behind Supabase authentication. Sees your email address and the code.
• RevenueCat — Manages subscription state. Sees your account ID and purchase status. Apple handles the payment itself, so neither RevenueCat nor we ever see card details.
• PostHog — Product analytics for the app, hosted in the EU. Events carry a screen name, a tier or a count — never a profile name, an allergy, or recipe content.
• Sentry — Crash reporting. Reports are stripped of profile, constraint and recipe fields before they leave your device or our servers, and carry an account ID rather than an email.
• Vercel — Hosts this website and our APIs, and supplies the two-letter country code we store. No IP address and no precise location is ever written to our database.

What we never do

• We never sell your data, or share it for anyone else's advertising. Not in the sense the law means, and not in the sense you mean.
• We show no ads. We have no advertising or data-broker relationships at all.
• We never use your household's dietary or health data for marketing, and never send it to an analytics or crash-reporting service.
• We do not track you across other companies' apps or websites, and the app asks for no tracking permission because it does no tracking.
• We do not build advertising profiles, sell insights about your family, or let any third party read your household's data.

Why we are allowed to hold it

For readers in the UK, EU and similar regimes, our lawful bases are: performance of our contract with you for your account, household and subscription; explicit consent for health-related dietary data; and legitimate interests for keeping the service secure, preventing abuse of the recipe generator, and understanding in aggregate which features work. You can object to that last one at any time by writing to us.

How long we keep it

• Your account and everything in it — for as long as your account exists, so your household never has to be rebuilt. Deleting your account deletes it all, at once.
• Crash and product-analytics events— held on our providers' retention schedules, which expire them automatically; crash reports are kept for 90 days by default.
• Support messages (and signups from our pre-launch waitlist) — kept until the question is resolved and then cleared periodically. Be aware of one honest caveat: these records are filed against the email address you wrote from, not against your account, so deleting your account does not automatically remove them. Ask us at the address below and we will delete them too.
• Purchase records — Apple and RevenueCat keep their own transaction history for tax and accounting reasons, which we cannot delete on your behalf.

Deleting your data

In the app: Settings → Delete account. On the web: the deletion page. Lost access to both? Email us from the address on the account and we will do it within 30 days.

The purge runs on our servers, immediately, and is not reversible. It removes:

• · your login, account record and subscription link
• · your household and every eater profile in it
• · every allergy, diet, goal and dislike attached to those profiles
• · every saved recipe and every learned preference
• · your usage counters, analytics rows and any internal notes about your account
• · your RevenueCat subscriber record

There is no soft delete and no recovery window — when it is gone it is gone. If you share a household with a second cook, only the household admin can delete it, because it holds their data too. Deleting your account does not cancel your subscription: Apple bills that, so cancel it in your device's subscription settings.

Where your data is processed

Our providers process data in the United States and the European Union — our product analytics are on EU infrastructure specifically. Where data leaves your country, the transfer relies on the standard contractual clauses and data-processing terms we hold with each provider.

How we protect it

• Everything travels over TLS and is encrypted at rest by our database provider.
• Row-level security is on for every table, so a household's data is unreadable by any other account even if application code has a bug.
• Your sign-in token is stored in your device's secure keychain, never in ordinary app storage.
• Profile names, dietary rules and recipe content are stripped from crash reports and analytics before they are sent — enforced in code at the point of sending, not by policy.
• The recipe endpoints are rate-limited, and every request is authenticated on the server; the app is never trusted about who you are or what you have paid for.

No system is perfect. If data of yours is ever exposed, we will tell you and the relevant regulator, promptly and specifically, rather than quietly.

Cookies and this website

This marketing site sets no cookies and runs no third-party analytics or advertising scripts. The only cookies we set anywhere are the sign-in cookies on our own internal admin pages, which you will never visit. The app itself uses no advertising identifier and no cross-app tracking. If we ever add website analytics, we will update this page first and ask for consent where the law requires it.

Your rights

Wherever you live, we honour the strong version of these: ask what we hold about you, get a copy in a portable form, correct it, restrict or object to a use, withdraw consent, or delete everything yourself at any time. We will never charge you for asking, and never give you a worse product for exercising a right.

We do not sell or share personal information as California law defines those terms, so there is nothing for you to opt out of — but you have the same access and deletion rights, and you may name an authorised agent to use them. If you are in the UK or EU and we have not resolved something to your satisfaction, you may complain to your national data protection authority.

Write to privacy@cookright.app and a person will answer, normally within a few days and always within 30.

Changes

If this policy changes in a way that matters, we will say so in the app before the change applies — never silently, and never by backdating this page.

Contact

privacy@cookright.app · 8x Social, operator of CookRight