Privacy

Last updated 2 October 2026

Waft is a cooking companion. It needs very little about you, and most of what it does happens on your phone.

The short version

• Your voice is recognised on your phone. Recordings never leave it.
• We don't sell your data, and there are no ads.
• Health details are optional, kept apart from everything else, and never used for analytics.
• You can export everything, and delete everything, from inside the app.

What stays on your phone

• Your voice. Speech is turned into text on the device. No audio is recorded or sent.
• Browsing and filtering. Recipes, dietary modes and allergen filters work without a network.
• Recent searches. Kept on this phone only, and never synced.
• Planning ranges. If you use goals, the range is worked out on the phone.

What your account holds

Waft keeps your cooking on your phone and backs it up to a private account, so it is still there on your next phone. You can link Apple, Google or an email address to that account. The account holds:

• Your email address or sign-in identity, if you link one.
• Favourites, notes, ratings, cooking history, plan entries and your grocery list.
• Recipes you save from a link. They stay private to you.
• Food preferences, including allergens and dietary mode.
• People you cook for, if you add them: a name and their allergens.
• A cook's card, if you submit a community recipe. Its name and line become public once a recipe is accepted.

Health details, if you choose to add them

Goals and the meal journal are optional. If you use them, Waft holds your height, weight, birth date, activity level, any conditions you choose, the ranges you accept and the meals you log.

• They leave your phone only if you agree to keep them on your account. That agreement is recorded, and you can turn it off under Your data.
• They are stored apart from your cooking records, and they never appear in analytics, crash reports or notifications.
• They have their own export and their own delete, under Your data in the app.
• A meal you cooked is not counted as eaten until you confirm it.

Waft gives planning ranges, not medical advice.

Services that process data for us

Each one receives only what it needs for the job described.

Supabase

Stores your account and runs the server functions below.

Anthropic

Answers a question you ask mid-cook, understands a spoken command the phone couldn't, and reads a recipe you save from a link. It receives the text of that request and the recipe step it's about.

Google Cloud

Turns recipe steps into speech, and reads the text in an image you save a recipe from.

Cloudflare

Serves recipe photographs and this website.

RevenueCat

Keeps track of your subscription. Payment itself is handled by Apple or Google; we never see your card.

PostHog

Counts how the app is used, in the EU. Events carry ids, counts and durations — never your notes, your searches or any health detail.

Sentry

Receives crash reports, without personal information attached.

Apple and Google

Sign-in, if you link either, and payments through their stores.

Taking it with you, or removing it

• Export. Settings exports your recipes, notes and cooking history. Your data exports your health details separately.
• Delete your account. Settings deletes the whole account and everything in it.
• Delete health details only. Your data removes your body details or your journal, and leaves your cooking history.

When health details are removed, a line saying a removal happened, and on what day, stays — with nothing identifying you. The record of what you agreed to also stays, because it shows your details were held with permission.

This website

This site sets no cookies and collects no personal information.

Changes

The date at the top shows the latest version. If a change affects what happens to your data, the app will tell you.

Questions

Write to [email protected].