Kitchen Bot
Privacy
What Kitchen Bot keeps about you and your kitchen, where it is kept, and how to take it away.
Last updated .
What the app stores
Your email address and name are held by Clerk, the sign-in service. Kitchen Bot itself keeps only an account id for you.
Kitchen Bot stores what you enter: your items, what is at home, your essentials, recipes and tags, plans, grocery lists, purchases and prices, and the receipt photos, product photos and order recordings you upload.
Things that can be sensitive
Dietary tags and notes can say something about your health or your beliefs. Receipt photos are stored as you took them, so they can show card digits, loyalty numbers and order numbers.
Where it lives and who handles it
Clerk handles sign-in, Railway hosts the app and its database, and Cloudflare R2 holds the files you upload. Receipts are read on the computer of the person who runs Kitchen Bot (the operator), never by a cloud AI model.
The operator can reach the database and the files.
Who can see it
Only your household can see it in the app. Each household has one planner, and nothing is shared with other households.
Taking a copy, and deleting
You can do both yourself in Settings. “Take a copy” gives you everything as a JSON file, plus spreadsheets (CSV). “Delete this kitchen” removes every row and every file.
Your sign-in account is separate: ask the operator and it is deleted for you.
How long it is kept
Your data is kept while your kitchen exists, and uploaded images are kept as long as the kitchen is, unless you delete one yourself from its receipt. Nightly backups are kept for 30 days and then deleted, so a deleted kitchen is gone from the backups within 30 days.
Logs
Kitchen Bot is built not to write request bodies, images, email addresses or card-like digit strings to its logs.
Questions
Ask the person who invited you to this kitchen.