Privacy

The short version: your recipes live on your phone, not with us.

What stays on your phone

Your cookbook — recipes, photos, pantry, food diary, tags — is plain files in a folder you choose on your device. We have no server that stores them, no account that holds them. Delete the app and the files are still yours.

What leaves your phone, and why

• AI rescues. When you import a screenshot, link or photo, its content is sent to our extraction service, which passes it to Google's Gemini model to be structured into a recipe, and hands the result back. It is used to answer that one request. We do not keep it.
• The rescue counter. To count AI rescues against your included 1,200 we key the tally to a one-way hash of your Play purchase token. We cannot read your identity out of it.
• Barcodes. Scanning a package queries the Open Food Facts database for that barcode.
• Crash reports. On by default so we can fix what breaks. Before anything is sent we strip out API keys, tokens, file names and folder paths — an error message can still carry a fragment of the text that broke, which is what makes it fixable. You can turn it off in Settings.
• Your own cloud, if you connect it. Backup and export to Google Drive or Dropbox go to your account, under your control. We never see those files.

What we never do

• No accounts, no sign-up, no email collection.
• No ads, no selling or sharing data with data brokers.
• No storing your recipes on our servers.

This website

This website is separate from the app. It counts nothing unless you say yes. If you do, Google Analytics sets a cookie and reports which pages you opened, roughly which country you are in, and what device you used. Nothing else. It never sees your name or email, and it never touches your recipes.

Payment

Purchases run through Google Play. We receive the purchase token to unlock the app and meter the AI cap — Google handles the payment details, we never see them.

Questions

Write us — see the contact card.