The short version
Brasa has no accounts, shows no ads, uses no third-party tracking SDKs, and does not sell your personal data. Your library syncs across your devices end-to-end encrypted, so even we can't read it. Your recipes are yours. Questions? hello@brasa.recipes
Who we are
Brasa is an independent app ("we", "us"). This policy covers the Brasa app and its extensions, including the Share extension, widgets, and Quick Look thumbnails.
What Brasa stores
Brasa stores the recipes you capture or create, including titles, ingredients, steps, notes, times, images, meal plans, and shopping lists.
That data is stored:
- On your device, in Brasa's private app storage.
- In Brasa Sync, our end-to-end encrypted sync service, so your library can sync across your devices.
Brasa Sync is end-to-end encrypted: your recipes, images, and notes are encrypted on your device before they are uploaded, using a key kept in your iCloud Keychain that is never shared with Brasa. Our servers only ever hold encrypted data we cannot read — we cannot browse your library. There is no Brasa account; your devices are linked to each other privately, never through your Apple ID or email.
Cloud processing
Most Brasa features work on your device. Some features use cloud processing when you ask Brasa to import, understand, search for, or enrich recipes.
For example, Brasa may send recipe text, OCR text from a recipe photo, a recipe URL, or a search query to cloud services so the requested feature can work. Brasa sends only what is needed for that feature.
We do not use this content for advertising or tracking, and we do not use your recipe content to train AI models. Our processing service is configured not to store what you send, such as recipe text, photos, or search queries.
Brasa does not attach your name, Apple ID, email address, or a Brasa account to these requests. Brasa has no account system to attach.
Brasa Voice
Brasa Voice — the spoken voice in hands-free Cook Mode — runs entirely on your device. Listening, speech recognition, and speech synthesis all happen locally; your voice and what Brasa says back are never uploaded. Enabling Brasa Voice downloads a one-time voice model (about 330 MB) from Hugging Face, a third-party file host. That download contains no personal data and sends none, though Hugging Face receives ordinary network metadata, such as your IP address, as with any web download.
Device permissions
Brasa asks for these permissions only when you use the related feature:
- Camera — to photograph a printed recipe.
- Photo Library — to pick a recipe photo or screenshot to import.
- Reminders — to add shopping-list items to a Reminders list, if you choose.
- Calendar — to mirror your planned meals to a calendar, if you choose.
- Microphone — to hear hands-free voice commands in Cook Mode. Audio is processed on your device and never uploaded.
- Speech Recognition — to understand those commands, and to turn the narration of saved cooking videos into recipe steps. Recognition runs on your device; your speech never leaves it.
You can change or revoke any permission in the iOS Settings app.
What Brasa does not do
- No app user accounts.
- No advertising or ad networks.
- No app analytics, telemetry, or usage tracking.
- No third-party tracking SDKs.
- No selling or sharing your data with data brokers.
Data retention and deletion
Your recipes remain until you delete them. Deleting a recipe removes it from your device and syncs that deletion to your other devices. Brasa's "Delete all recipes and images" option erases your library from this device and permanently deletes the encrypted copy held by Brasa Sync. You can also delete the app to remove its local data.
Content sent for cloud processing is used to complete the feature you requested and is not retained by Brasa.
If you join the Brasa email list on brasa.recipes, we store your email address until you unsubscribe or ask us to remove it. Every Brasa email includes an unsubscribe link, and you can also reply to any Brasa email to be removed. We may also store the signup source, campaign parameters, referrer, and browser user agent so we know which links are working. To limit signup abuse we briefly keep a one-way hash of the submitting network address — never the address itself — and discard it automatically.
The website also stores basic first-party page events, such as page views, CTA clicks, signup attempts, successful signups, and share clicks. These rows do not include your email address or IP address. They may include campaign parameters, page path, referrer, browser user agent, and Cloudflare-provided country/colo metadata so we can understand which launch channels are worth continuing.
Service providers
Brasa relies on service providers to operate Brasa Sync (encrypted storage), cloud AI processing, source search, app authentication, and abuse prevention. Data held for Brasa Sync is end-to-end encrypted, so these providers cannot read your recipes. Providers process data only to deliver the feature you chose to use or to keep the service available and secure.
Children
Brasa is not directed at children and does not knowingly collect information from children.
Changes to this policy
If we change this policy we will update the date at the top and post the new version at the same address. Significant changes will be noted in the app's release notes.
Contact
Questions about privacy or this policy: hello@brasa.recipes.
Terms for using Brasa are available in the Terms of Use.