Data and privacy
Last updated: 2026-05-25
Your recipes, pantry, shopping list, and cooking history stay inside your kitchen. This page covers the one narrow exception: an aggregate signal about ingredient names that the operator uses to grow the shared ingredient catalog.
What stays in your kitchen
The operator can’t read these through the admin console:
- Your recipes and their text, tags, or categories
- Your menu, meal plan, or scheduled cooks
- Your pantry contents and overrides
- Your shopping list, custom items, and aisles
- Your cooking history
- Who in your kitchen typed what, or when
What the operator sees
When you type an ingredient name that isn’t in the shared catalog yet, mirepoix saves it as a pending discovery in your kitchen. The operator’s admin view collects those pending names across every kitchen and shows two things per name:
- The ingredient name itself
- A count of how many kitchens have seen it
The view leaves out anything that could tie a name back to you:
- No kitchen identity, name, or slug
- No user identity
- No recipe, quick bite, or pantry entry it came from
- No name that appears in fewer than three kitchens
That last threshold is a floor, not a setting. A name has to show up in at least three separate kitchens before it’s visible to the operator at all.
Getting to that view takes a separate admin sign-in that times out every twelve hours. Every page load lands in the security log.
What it’s used for
One thing: deciding which entries to add to the shared ingredient catalog. New entries give future kitchens nutrition data and the right unit handling out of the box.
The aggregate isn’t fed into any machine-learning model or training pipeline — it’s a read-only signal a person reads and acts on. Adding entries to the shared catalog is a separate, reviewable change to the project’s source, not a click in this view. Names drop off the view once the catalog can resolve them.
What never happens
Your kitchen’s content — your recipes, tags, pantry, shopping list, cooking history, and the link between any of those and your account — never:
- Gets sold
- Gets shared with third parties
- Gets used for advertising, recommendations, or behavioral profiling
- Gets exported to third-party analytics
- Gets used to train any machine-learning model, by the operator or by any third party
- Gets mapped to your kitchen identity in the admin view, in logs, or in exports
The one exception is the k-anonymized ingredient-name aggregate described above under “What the operator sees.” That aggregate is used solely by a human operator to decide which entries to add to the shared catalog. It isn’t sold, isn’t shared with third parties, isn’t used for machine-learning training, and contains no link back to your kitchen.
Changes
- 2026-05-25 — Tightened the scope of “your data” claims to specifically name kitchen-private content, and added an explicit carve-out paragraph for the k-anonymized ingredient-name aggregate. No change to what the operator collects or sees; the prior wording was accurate but read as broader than the underlying behavior.