Brasa — Privacy Policy

Last updated: 8 October 2026

Brasa has no accounts and collects nothing about you. What you keep — your kitchen, saved recipes, ratings, shopping list and history — stays on your phone. Photographs you take are sent to be looked at, used to write your recipe, and not kept.

What never leaves your phone

• Your kitchen and what is in it
• Saved recipes
• Your shopping list
• Ratings, notes and cooking history
• Your palate profile
• Your chosen language
• The diagnostics log

None of this is uploaded, and Android's automatic backup is switched off for Brasa, so it is not copied to your Google Drive either. Uninstalling the app deletes all of it. The diagnostics log is sent nowhere unless you tap Share this log and choose where it goes.

What is sent when you cook

Each request sends only what is needed to answer it:

• Photographs of the raw cut, the pan, or your shopping
• A description of the cut — protein, bone, thickness
• The dish you chose, when asking for a recipe
• Your ingredient list as text, so recipes can substitute
• Ratings and the notes you wrote, when working out your palate
• Your language, so the answer comes back in it

All of it travels over an encrypted connection. No name, email, phone number, account, advertising ID, or device identifier is attached, because Brasa does not have any of those.

What is stored on our side

• Usage counters. Which endpoint was called, when, and how many tokens it used. No photographs, no text you wrote, nothing that points back at a person or a phone.
• A cache of finished recipes, so the same dish is not generated twice. It is filed under a one-way hash of the cut and dish, holds only the recipe itself, and expires after six months.

Photographs are never written to storage. They are read and discarded.

Your IP address

Read at the moment of the request to apply rate limits, so one source cannot overwhelm the service. Brasa does not store it or attach it to anything. Cloudflare handles it as our hosting provider under its own policy.

Who else is involved

• Anthropic PBC reads the photographs and text to produce identifications and recipes. Under its commercial API terms this content is not used to train models. It may be retained briefly for safety monitoring. Privacy policy
• Cloudflare, Inc. hosts the service and protects it from abuse. Privacy policy

There is no advertising, no analytics, no tracking, no crash-reporting service, and no third-party SDK collecting anything in the background.

Permissions Brasa asks for

• Camera — to photograph the cut, the pan, and your shopping. Only when you tap the shutter. Brasa cannot use the camera in the background.
• Notifications — to tell you a step timer has finished. Created on your phone; nothing is registered with a push service and no push token exists.
• Alarms & reminders — so a timer fires at the moment it is due rather than whenever the phone next wakes up.

Children

Brasa is not directed at children under 13 and does not knowingly collect anything from them.

Who is responsible for this data

Brasa is made and run by Chris Edwards, in Ontario, Canada, who is the data controller for the little that is stored. Questions, requests and complaints go to BrasaWorldFood@gmail.com.

Where the law gives you the right to complain to a data protection authority — in the EU, the UK, and elsewhere — you can do so with the authority where you live, whether or not you have written here first.

Your rights

There is no account to close and no profile to request, because nothing stored on our side identifies you. Everything Brasa holds about your cooking is on your phone and under your control: clear it from Profile, or uninstall the app to remove all of it at once.

The terms

What Brasa does and does not promise — including food safety, allergies and the subscription — is on the terms page.

Changes

If this changes, the date at the top changes with it.

Contact

Questions about this policy: BrasaWorldFood@gmail.com