Back to Craive

Privacy

Last updated 12 October 2026

What Craive stores

The names and colours you give family members, the meals you enter and any notes you write about them, how each member rates them, your weekly plan, what you confirm you cooked, and your grocery list. Craive stores the email address you sign in with so it can find your kitchen again, and the email addresses of anyone else you invite to plan.

Meal notes are free text. If you write something health-related there — an allergy, a diet — it is stored exactly as you typed it, with the rest of your kitchen, and shown to everyone who plans with you.

Receipts, recipes and what you bought

When you tick something off the list, Craive keeps a record of it — the item, the store and when — so it can tell you what a meal costs to shop for. A receipt you photograph is kept with that record: the photo, the store's name, the date and total printed on it, and each line as printed, cleaned up and priced. Everyone who plans in your kitchen can open any of its receipts, and each photo opens through a link that stops working within five minutes.

Before a photo is kept on our servers or read, Craive takes out what the camera wrote beside the picture — where and when it was taken, and with what — keeping only which way up it goes. A photo on this phone keeps what the camera wrote for as long as the phone keeps it; our server takes it out of the copy it receives.

A receipt's photo is removed from our servers once 90 days have passed since the receipt was settled, or since it reached our servers if it never is. Craive does this the next time your kitchen's receipts are opened after that, so a kitchen no one opens keeps its photos until someone does. The receipt's details stay until you delete them. A receipt is kept until you delete it or the kitchen: Delete this receipt, on its sheet, removes its photo and what it read for everyone who plans with you; the prices it added to what you bought, and the matches it taught (below), stay. There is no setting to keep a photo for less or longer in this version.

Recipes you save keep their title, time, ingredient lines, steps and the address you imported them from, without the tracking a newsletter adds to a link — who it was sent to, and which campaign.

To read a receipt, a photographed recipe or a recipe page Craive cannot read on its own, Craive sends it to Anthropic, whose Claude model reads it and sends the words back. Anthropic says it keeps what it reads for up to 30 days, to check for abuse, and does not use it to train its models; that is Anthropic's own policy, not something Craive controls. A photo is sent whole, so anything printed on it — a loyalty number, the last digits of a card — goes with it. Our servers keep no recipe photo, only the recipe you save; until then your phone keeps its own copy (see Where it lives). A recipe link is fetched by our server, never by your phone, and only from public web addresses.

On Android you can share a recipe page to Craive. Craive then opens at a web address with the link in it, and any words the sharing app sent along. Vercel, which hosts Craive, records that address in its request log, as it records every address Craive is opened at. Craive takes the link out of the address before error reports or analytics start, and never writes it to a log of its own. The link is then read like one you pasted, and saved without its tracking. If you'd rather the address never held it, paste the link into From a link instead.

Each receipt you settle teaches your kitchen what its lines mean: a line as printed at that store, and the item you said it was — in your own word when you tell Craive a printed line is something you ticked. Your kitchen keeps these matches, even after the receipt that taught them is deleted, until the kitchen is deleted, and they are in Download my data.

Shared matching is off unless the parent who set up the kitchen turns it on under Family. When it is on, it teaches other kitchens what a receipt line means once three kitchens agree: the printed words, the store's name and the item's name. Never your prices, your dates, your address, or which kitchen said so. Switching it off means your kitchen neither gives nor gets those matches, and deleting your kitchen takes its matches out of what others see.

What Craive does not store

No location beyond the time zone your phone reports, no photos other than the receipts you choose to keep and a recipe photo waiting on this phone for its recipe to be saved or discarded, no contacts, no calendar event locations or notes, and no event titles kept: a title is read on your phone to name a busy night and is never stored or sent. Family members other than the signed-in parents have no accounts and no email addresses in Craive; they are names you chose.

Your calendars

On the Craive iPhone app, and only if you allow it, Craive reads the start and end of each event on the calendars you choose, and whether it is an all-day event. It reads an event's title only to name a busy night on your phone. It never reads a location or a note.

The calendars you match to each person stay on your phone. Only each person's answer for a night leaves it: home, late or out. Craive keeps those answers with your kitchen, and deletes them when the kitchen is deleted. Signing out clears the matching from that phone.

The owner's download includes the names of the calendars and the person each one belongs to, made on the owner's phone. Keep that file private.

Where it lives

On this phone, so a change you make in a dead zone is kept until it can be sent and the list is there when you have no signal. IndexedDB holds the last copy of your kitchen, the outbox, a copy of the kitchen's recipes, so cook mode opens with no signal, and any receipt photo waiting for signal — it is sent once and then removed from the phone. A receipt photo Craive refused stays on this phone until you tap Remove beside it on Receipts. A recipe photo is kept there too until the recipe read from it is saved or discarded; one whose read did not get through waits on the Shelf until you read it again or remove it, and like a waiting receipt photo it outlasts a sign-out. The outbox holds changes waiting to be sent and changes Craive refused, each marked with the internal id of the kitchen it was made in. Refused changes stay on this phone until you deal with them, or until you sign out and choose to forget them.

localStorage holds anything half-typed — a meal form, the several-at-once box, a family member, a usual, a store's new name, and the planner box, which can hold the other parent's email address — a recipe Craive read that you have not saved yet, the answers you chose on a receipt you have not settled, the address you last signed in with, how many times the app has opened here, whether you dismissed the install card, the latest price paid for each ingredient, so a meal's cost shows offline, and a recipe link you shared to Craive or pasted into From a link, until Craive has read it or you remove it from the Shelf. So is a link another site opened Craive with; the Shelf offers it and never reads it unless you add it.

A link shared while nobody is signed in waits only in that Craive window, until someone signs in there or the window is closed.

Every window keeps, until it is closed, when Craive last reloaded itself to finish loading, and when its offline page last tried again; the window you cook in also keeps the step you were on and any timers you set — step numbers and times, under the meal's internal id.

A cookie, craive-tz, remembers your time zone for a year so tonight is tonight the moment the page first shows, not a guess it corrects a beat later. A second cookie, craive-hh, remembers for a year which of your kitchens you last opened, so returning to Craive puts you back where you left off instead of guessing. Signing in sets cookies of its own: one that keeps you signed in — your address, encrypted — until you sign out or thirty days after you signed in, and a few that carry the sign-in itself (the page to come back to, and checks that the sign-in is yours), which each last fifteen minutes or until the browser closes. When you delete everything or leave a kitchen, Craive keeps a scrambled note for 31 days that stops anyone using an old sign-in; it cannot be turned back into your address.

Beside the photos kept on this phone, localStorage holds two numbers for each kind: how many photos are kept, and how many of them the browser cleared that you have not yet read about, until you tap Got it. Numbers only, named by a code for your address, never the address and never a photo. Delete all my data takes both. Signing out, a session that ends on its own and Leave this kitchen leave them, as they leave the photos.

The outbox keeps two more numbers in localStorage, named by a code for your address as the photo numbers are: how many changes it holds, waiting or refused, and a counter that puts them in order across windows. Delete all my data and Leave this kitchen clear both. Signing in and out also leaves a short note there for Craive's other windows, written by the sign-in library, which names no one.

When your session ends, the sign-in screen clears the kitchen copy, whatever you had half-typed, the address and craive-hh, and with them the copy of the recipes and the prices; changes, receipt photos and every recipe link waiting to be read stay until that address signs in again. Signing out yourself from Family clears the links too, and says so before it does.

Delete all my data (under Family) removes the outbox, the launch count, craive-tz and craive-hh along with everything else. Leave this kitchen clears this phone as Delete all my data does, except the receipt and recipe photos still waiting and the numbers beside them, which stay as they do at a sign-out: one may be for a kitchen of your own. It leaves the recipe links waiting to be read too. Neither cookie says anything about your family — craive-tz is a time zone name and craive-hh is an internal id for a kitchen, not its contents.

And on our servers (Supabase, hosted in the United States) so everyone who plans sees one kitchen. The server keeps earlier versions of your kitchen so we can restore it if something goes wrong: every version from the last fourteen days, up to two hundred, and always at least the last thirty, however old; those go when the kitchen does. Craive limits how often a kitchen's recipes and receipts can be read, so it also keeps the time of each recent read: when it happened, never what was read. A read's time stays even after you delete its receipt, until a later read clears it or the kitchen is deleted.

Error reports go to Sentry with cookies, request bodies, email addresses and phone numbers stripped before they leave the app. A web address in a report keeps only which page it was, never a link shared to Craive, and a recipe page Craive fetched is named only by its site. For about one visit in ten, Sentry also receives how long a screen and its requests took, stripped the same way.

There is no session replay of any kind — neither the error reporter nor the analytics record your screen. Product analytics (PostHog), when enabled, record page views only: each says which screen was opened, and carries the phone's browser, system, screen size, language and time zone and the phone's IP address, as it would reach any website. There are no clicks, no time on a screen, no errors and no recordings, and never names, emails or meal names. Craive asks PostHog not to work out a place from that address; whether PostHog then keeps the address is a setting on PostHog's side, which Craive cannot see from here. Analytics keep nothing on this phone — no cookie, nothing in its storage — so every visit looks to them like a new one.

Who handles it

Who can sign in

Craive keeps a list of the email addresses allowed to sign in. Your address stays on that list until you ask us to remove it, so it is not deleted by Delete all my data.

Deleting

Before either of the below, Download my data, under Family and again on the delete sheet, saves the kitchen as you see it — members, meals, ratings, the plan and the list — with its recipes, its receipts (what they read, not the photos), what you bought and its receipt matches, as a file on this phone. Nothing is sent anywhere to make it; those last four are read from Craive when the button first comes into view, and what you bought and the matches are shown nowhere else in the app.

Delete all my data, under Family, removes the kitchen you set up immediately and completely, for everyone who plans in it — its recipes, what you bought, every receipt and every receipt photo, and its matches, shared or not, with it. If you were invited into someone else's kitchen, Leave this kitchen, under Family, removes your address from the kitchen, and from its version history once thirty newer changes have been saved and fourteen days have passed (or after two hundred newer changes, if that is sooner), and leaves their kitchen intact. Your own kitchen, the one Craive started when you first signed in, is kept through a leave if anything is in it, and deleted with the leave if it is empty. The hosting provider's own backups age out within thirty days; we keep nothing for you afterwards.

Children

Craive is used by parents. It does not knowingly collect information from children and provides no accounts for them.

Your rights

You can see your kitchen by opening it, take a copy of what it shows with Download my data (a JSON file any text editor or other software can read), correct it by editing it, and delete it with Delete all my data or Leave this kitchen. Two things Craive keeps beside the kitchen are not in that copy: the older versions of it the server keeps for restoring it, and the times of recent reads (both under Where it lives); both go when the kitchen does. The one thing those controls do not reach is your address on the sign-in list: write to the address below to have it removed, or to ask anything else about your data, and we will answer within a month.

If a parent invited you to plan and you never signed in, your address is in their kitchen with no Leave for you to tap, so write to the address below: we will take your address off that kitchen and out of its restore points, and tell you within a month when it is done.

Contact

privacy@stoudtlabs.io