Stovebird

Privacy Policy

Last updated November 16, 2026

The short version.

This policy explains what Stovebird (“we”, “us”), operated by its owner, an individual sole proprietor based in Tennessee, USA, collects, why, who helps us process it, and your choices. Allergy, diet and similar details are covered in more depth in the Health Data Notice.

What we collect

What Examples Why
Account A random account ID; the name you give (optional); your email address if you sign in with Google or give it to us; when you joined and agreed to our terms; which invite you used. To run your account and keep invites working once.
Sign-in Your passkeys’ public keys (never your fingerprint, face or screen lock: those stay on your device); a Google account identifier if you use Google; sign-in sessions. To sign you in securely.
Your kitchen Pantry items and rough amounts; staples; household settings (whether kids eat too, foods to never use, foods you’d rather not, equipment, usual servings); recipes; your feedback; cooking timers; photos you add. To make, save and sync your recipes and run cooking timers.
Weekly plans The plan you make: its nights, dinner ideas, servings, shopping and your choices for it, including a goal (such as losing weight) and a calorie number for its dinners if you give one. Age, height, weight and sex, if you use “Not sure? Estimate it”, are worked out on your device and never saved or sent. To plan your dinners and make their recipes. Ending a plan deletes its goal, dinner size and note; its dinners stay with your past plans, to plan again, until you delete it (its recipes stay either way). A goal is kept for your next plan only if you turn on “Remember for future meals”.
Recipe requests What you asked for (meal, effort, servings, notes) and a snapshot of the kitchen details the recipe needs. To write that recipe. The snapshot is deleted when the recipe is done; the request’s record goes after 30 days.
Plan and billing Your plan; how many recipes you’ve used; what each request cost us; Stripe’s customer and subscription IDs and payment status; if you subscribe in the Android app, Google Play’s purchase token, the subscription’s plan, status and renewal date, and its order numbers. Never your card number. To give you your plan’s allowance, bill Pro, and keep costs in check.
Messages and the waitlist What you write to us, and your email if you give it; your email if you join the waitlist. To answer you and fix what you report; to tell you when there’s room for you. Waitlist emails are used for nothing else.
How the app is working Which steps you’ve reached (your pantry set up, a recipe made, rated or cooked); the ratings you give, with that recipe’s title; the days you open Stovebird; how each request went (how long it took, and whether it worked or why not); which photos were made; the kind of browser you use (such as “Safari on an iPhone” or “Instagram’s built-in browser”), or that it’s Stovebird’s Android or iPhone app, when you open an invite, sign up or run into a problem; the screens opened before signing in (just which one, whether sign-up was open and the kind of browser, and, when the link you followed carries one, its campaign code, such as “tt-nocook-1106”, and the kind of site you came from, such as “a search engine” or “TikTok”, never the page’s address); for an account made after such a visit, that same code and kind of site, kept with the account and deleted with it, so we can tell which posts bring people who cook; and error reports from the app: the screen, and what went wrong, with anything that looks like an address, link or number removed. Never your pantry, your household or the recipes themselves. To find and fix problems, and to learn whether Stovebird is useful to people, so we know what to improve.
Technical Your IP address, briefly, to limit repeated sign-in, sign-up and contact attempts (for new accounts, a one-way code made from it, kept for a week, never the address itself); our host’s short-lived request logs. Security and abuse prevention. Kept a day or two in our own records.
On your device A copy of your kitchen in your browser’s storage (in the apps, the app’s own storage), so it works offline; one sign-in cookie (in the apps, a sign-in token kept in the app’s private storage instead). Offline use and staying signed in. Signing out clears this copy.

The Android and iPhone apps

The apps show the same Stovebird as the website and use the same account, server and providers. In addition:

Sharing a recipe

When you share a recipe, anyone with its link sees the dish’s photo (the one Stovebird made, never one you took), its title, how long it takes and your first name, as does the preview a chat app shows for the link. They see the recipe itself once they sign up, and it’s saved in their account as a copy. A copy has the recipe only: never your pantry, notes, ratings, cooking history, food preferences or your own photos. You can stop sharing at any time; deleting the recipe or your account does the same. Copies people already saved stay with them. A recipe shared with you is checked against your own foods to avoid when you open it.

What the AI sees

Recipes are written by Claude, Anthropic’s AI, through Anthropic’s commercial API. For each request Stovebird sends only what that recipe needs: the request, the relevant pantry items and amounts, your staples, your household settings (including foods to avoid), a short summary of what you’ve liked, and the titles of recent recipes so it doesn’t repeat itself. To rework a recipe, it also sends that recipe and your changes. To plan a week, it sends the plan’s choices (including its goal and dinner size) and the titles of recipes you’ve loved or saved, so one can come back. It never sends your name, email address, account ID or IP address. After a recipe photo is made, Claude may check the photo against the recipe and your foods to avoid. Anthropic processes this under its commercial terms, which don’t allow it to train its models on it, and keeps it only for a limited time.

Recipe photos are made by the image model Stovebird chooses: Google’s (Gemini, the usual one), or Cloudflare’s (Workers AI) when Google’s can’t make one; Stovebird may choose OpenAI’s or BytePlus’s (Seedream) instead of Google’s. For each photo it gets only a description of the dish, its ingredients and the foods the photo mustn’t show (which can include foods you avoid), never your name, email address, account ID or IP address. Step pictures (a few of a recipe’s steps in one picture, shown while you cook) are made the same way, from what those steps say: a free account’s only on Cloudflare’s, when you start cooking.

Who helps us run Stovebird

They process data for us under their terms, only to provide their service. We don’t sell your personal information, share it for targeted advertising, or use it for advertising at all. We may disclose information if the law requires it, to protect people’s safety, or as part of a transfer of Stovebird to a new owner, who would be bound by this policy.

Cookies

The website uses one cookie, to keep you signed in. It’s required for the app to work. There are no analytics, advertising or tracking cookies. The phone apps use no cookies; they keep a sign-in token instead.

How long we keep it

Your choices and rights

These rights are for everyone, wherever you live in the US. We won’t treat you differently for using them.

Security

Sign-in uses passkeys or Google, so there’s no password to steal. On the website your session is a secure cookie that page scripts can’t read; in the apps it’s a token in the app’s private storage. Each account’s kitchen lives in its own database, and every request is checked against your account. Data travels encrypted. No system is perfectly secure; if a breach affects your data, we’ll tell you as the law requires.

Children

Stovebird is for adults 18 and over. We don’t knowingly collect data from children. If you think a child has an account, tell us and we’ll delete it.

Where it’s stored

Stovebird is offered in the United States, and to testers in the closed test of its Android app on Google Play, who may live in another country; their data is handled as this policy describes. Your data is stored by Cloudflare and processed by the providers above, which may process it in the United States and other countries.

Changes

We’ll update the date above when this policy changes, and tell you in the app before a material change takes effect.

Contact

Use the contact form; choose Privacy for privacy requests.