Privacy Policy

Who we are

Brasa.ai (“Brasa”, “the app”) is operated by Happy Tax Franchising, LLC (“we”, “us”), the publisher and seller of Brasa on the App Store. We are responsible for the personal data described in this policy. Brasa is built by Mariano Valle. This policy covers the Brasa iPhone app and this website. Questions and privacy requests go to marianovalle13@gmail.com.

What we collect

We collect what you enter, what you capture with a feature, and some data that is collected automatically while the app runs:

• Profile and goals: age, sex, height, weight, activity level, goal, target weight, weekly pace, the obstacles you pick during setup, your calorie and macro targets, and an optional profile photo.
• Meals you log: photos you take (one photo or three angles) or pick from your photo library; short video scans, of which Brasa sends only four still frames (it never uploads the video file or any sound); meals you type or say; and barcodes you scan. For each meal we keep the result: food names, portions, calories, macros and hidden calories, the AI’s notes, its health verdict, score and reasons, the capture type, the number of photos, the time you logged it, and any edits you make.
• My Kitchen: the products you save, with name, type, aliases, serving size, nutrition and barcode.
• Workouts and health data you add: workout type, intensity, minutes and estimated calories; lab reports you upload and the results read from them; and the resting heart rate you type in. Brasa does not currently connect to Apple Health.
• Recipes and progress: recipes you create or import from a cookbook, recipe bookmarks, and your streak and challenge progress.
• Account data: a random account ID created on first launch. If you link Sign in with Apple, we also keep your Apple user ID, the email Apple gives us and your name if Apple shares it (see Accounts).
• Purchases: your subscription status and App Store transaction records, through Apple and RevenueCat, and any promo code you redeem (which offer it was, and when it starts and ends). From version 1.0.7, also whether you installed Brasa from one of our App Store ads (see Service providers). We never see your payment card.
• Usage and diagnostics: app events, crash reports and a log of AI requests, all linked to your account ID, and standard request logs kept by Google Cloud (see Analytics and crash reports).
• Device and security data: device model, iOS and app version, your IP address when the app connects to our backend or the services listed below and, from version 1.0.7, Apple App Attest and Firebase App Check tokens that let our server confirm requests come from the genuine app.
• Help improve Brasa samples: only if you join that program (see below).
• Emails you send us: your email address, your message and anything you attach. They are kept in our Gmail mailbox, under Google’s terms, until we delete them.

Brasa never asks for your location and never browses your photo library: you pick each photo with the iOS photo picker.

Where it lives

Your data is stored on your device first. It is always mirrored to our backend (Google Firebase) under your account ID, whether or not you have linked an Apple ID, for backup and multi-device restore. The mirror holds your profile, your meal log (without photos), My Kitchen, workouts, the results extracted from lab reports (your latest report and up to 12 earlier ones), resting heart rate, recipes, a small copy of your profile photo, and your streak and challenge progress.

Brasa keeps a small copy of each meal photo, and the photos of recipes you create or import, on your iPhone only (they are not part of the cloud mirror). From version 1.0.7, Brasa excludes them from iPhone backups. Photos or video from a scan that hasn’t finished are kept on your iPhone, and are included in its backups, until the scan finishes or, if it never does, until Brasa clears them the first time you open the app at least 3 days after you took them. Other Brasa data on your iPhone is included in your iCloud or computer backups.

Our backend runs on Google Cloud in the United States. Data is encrypted in transit and at rest.

Reminders and notifications are created on your iPhone from your own log. From version 1.0.7, a “Meal logged” notification can show calories and protein on your lock screen. You can turn notifications off in iOS Settings → Brasa → Notifications.

This website doesn’t use cookies or analytics. Our web host, Google Firebase Hosting, sees your IP address in order to serve the pages, and so does Apple, which serves the App Store badge on our home page.

AI processing

Brasa’s AI analysis runs on xAI (Grok). The app sends each request to our server, which passes xAI only what the estimate needs:

• meal photos, or the four still frames from a video scan;
• meals you type or say, as text;
• your goal and daily calorie target;
• for scans and described meals set to At home (the default), the names, types and aliases of your active My Kitchen products;
• up to 8 food photos you choose during setup, if you try the hidden-calorie check;
• lab report photos, or the first four pages of a PDF, when you upload bloodwork;
• cookbook page text or page images, and the book name, when you import a cookbook.

To build the request, our server also receives your age, sex, height, weight and activity level and, for scans and described meals set to At home, your full My Kitchen list. It does not pass those details to xAI, and it does not store the photos, video frames or documents you send for analysis.

xAI uses this data only to return the analysis to us and does not use it to train its models.

Since October 12, 2026, Brasa’s xAI account uses Zero Data Retention: xAI processes each request and does not store it or its response. Requests sent before that date may be kept by xAI for up to 30 days to check for abuse or misuse, and are then deleted.

Lab reports often show your name, date of birth or patient ID. If you prefer, crop or cover those before uploading; Brasa only needs the results.

If we add or change an AI provider, we will update this policy before it receives your data.

Voice

When you say a meal, Apple’s speech recognition turns your voice into text. Apple may process the audio on its servers under Apple’s privacy policy. Brasa does not save or upload the audio; the text is handled like a typed description.

Barcode lookups and My Kitchen

When you scan a barcode, in the camera’s Barcode mode or in My Kitchen, your phone looks the number up directly in Open Food Facts (openfoodfacts.org), a public food database. Only the barcode number is sent, never your account ID. Like any website, Open Food Facts also sees your IP address and basic technical details such as the app version, and its own privacy policy applies to that lookup.

My Kitchen products sync to your account like the rest of your log. When a scan or described meal is set to At home, which is the default, the app sends your product list to our server, and the names, types and aliases of your active products are included in the request to xAI so it can recognize them. To stop this, switch the camera to Eating out; the choice also applies to meals you type or say. If you have turned off Auto-log scans in Settings, photos and videos you pick from your library are still analyzed as At home.

Optional “Help improve Brasa” program

If you join this optional program in Settings (turn on Help improve Brasa, then tap Join improvement program), Brasa uploads copies of the images from the photo and video meal scans you log (for video, still frames) together with the AI’s estimate, the nutrition result you accepted or corrected, any later edit to that meal’s nutrition, the capture mode and the app version. We use these samples only to evaluate and improve Brasa’s food recognition and calorie estimation. Joining is not required to use any app feature.

Before upload, Brasa re-encodes contributed images to remove embedded metadata such as GPS location, capture date and device details. Samples don’t include your name, email, account ID, body measurements or device identifiers. Visible pixels can still show surroundings or people, so avoid contributing images that contain private information.

Samples are not anonymous, though. Each one carries the ID and the exact time of the meal’s AI estimate, its calories, confidence and verdict, and an ID for each food in it (and, for a food matched to a My Kitchen product, that product’s ID and name). The same IDs are stored with that meal in your meal log and with your My Kitchen products, and our AI request log keeps the same time, calories, confidence and verdict with your account ID. So we can match a sample to your account while any of those records exists. The AI request log is kept even after you delete the meal or your account (see How long we keep data). If you want your samples deleted, email us, ideally before you delete your account (see Finding your account).

We delete contributed samples in batches, at least once a year, so that none is kept longer than 24 months. They are not sold, used for advertising or provided to third-party model-training programs. You can turn the program off at any time in Settings to stop future contributions; turning it off does not delete samples already uploaded.

Analytics and crash reports

We use Google Firebase Analytics and Firebase Crashlytics to understand how Brasa is used and to fix bugs. Both are linked to your random account ID, so this data is not anonymous.

• Analytics events record the screens and features you use and details such as each logged meal’s calories, confidence and health verdict; the kind of photo when a scan is rejected (for example, a person); workout type, minutes and calories; your goal and calorie target; for each lab report you save, how many markers were read and how many were out of range (not the values); the results of the setup photo check (photos, meals found and hidden calories); when you see a subscription screen and whether a free trial is available to you, the plan you buy, and whether a restore found a subscription; promo code redemptions (the type of offer, not the code); and notifications opened. Firebase also collects your device model, iOS version, app version, language, approximate location derived from your IP address, and identifiers for this app on your device.
• Our AI request log records, with your account ID, the outcome of each AI request: scan mode, calories, confidence and verdict; for a rejected photo, a short description of what it showed; how many lab markers were read, or why a report was rejected; cookbook import counts; and, for the setup photo check, how many photos and meals were found and their hidden calories.
• Standard request logs: Google Cloud logs each request the app makes to our server, with your IP address, the app build and iOS version your iPhone reports, and the time.
• Crash reports include the error and its message, the stack trace, device model, iOS version, a Crashlytics installation ID, your account ID, the screen where the error happened and your most recent app events.

There are no ads in Brasa. Our analytics are not linked to Google Ads. Google signals, data sharing with other Google products and ad personalization are turned off in our Google Analytics settings, and from version 1.0.7 the app also tells Google Analytics not to use your data for advertising. We don’t track you across other companies’ apps or websites.

The app has no switch to turn analytics or crash reporting off, and we can’t turn them off for one person, so they stop only when you stop using Brasa. You can object, or ask us to delete the Google Analytics data and AI request log entries linked to your account, by email (see Finding your account). Crash reports expire after about 90 days.

Service providers

We share personal data only with these providers, and only so they can run part of Brasa for us or provide the feature you are using:

• Google Firebase and Google Cloud (Authentication, Firestore, Storage, Cloud Functions, Hosting, Analytics, Crashlytics, Cloud Messaging and, from version 1.0.7, App Check): hosting, sync, our backend, analytics and crash reports.
• xAI: AI analysis, as described under AI processing.
• RevenueCat: manages subscriptions. It receives your account ID, your App Store purchase records and basic device and app information. From version 1.0.7, when you open the app, RevenueCat also receives an attribution token from Apple and uses it to ask Apple whether you installed Brasa from one of our App Store ads (Apple Ads) and, if so, which campaign, ad group and keyword. RevenueCat keeps this with your account ID. Apple provides it without tracking you across other companies’ apps or websites.
• Apple: Sign in with Apple, App Store payments, speech recognition and, from version 1.0.7, App Store ad attribution and App Attest, under Apple’s privacy policy. On our website, Apple serves the App Store badge.
• Open Food Facts: barcode lookups, sent directly from your phone (the barcode number, your IP address and basic technical details, never your account ID).
• Unsplash: some recipe photos load from images.unsplash.com, which sees your IP address and which photo was requested.
• Gmail (Google): our mailbox, which holds the emails you send us.

Google (for Firebase and Google Cloud), xAI and RevenueCat process data on our behalf under terms that require them to protect it at least as well as this policy does and to use it only to provide their service to us. Apple, Open Food Facts and Unsplash receive only the limited data above, directly from your device, under their own privacy policies. Emails you send us are held in our Gmail mailbox under Google’s terms. We may also disclose data when the law requires it.

What we never do

Sell your personal data. Share health data with advertisers. Let anyone train AI models on your meal photos, except the samples you choose to contribute through Help improve Brasa.

Accounts

Brasa works without a name or email: on first launch we create a random account ID, and your data syncs under it. If you link Sign in with Apple, we store the Apple user ID, the email Apple gives us (your own address, or a private relay address if you choose Hide My Email) and the name you allow Apple to share, so you can restore your data on any device. When you delete your account, Brasa asks Apple to revoke its access to your Apple ID.

If you log out of an account that isn’t linked to Apple, you can’t sign back into it. Its cloud copy is not deleted: like the copy of any account you stop using without deleting it, it stays until you ask us to delete it (see Finding your account). To remove your data, use Delete Account instead of logging out.

Your rights

Export. Settings → Export PDF Summary Report creates a one-page summary of the current week (meals, calories and protein per day). For a full copy of your data, email us.

Delete. In Settings, tap Delete Account, then Delete everything. If your account is linked to Apple, you confirm with Apple first. Brasa then deletes from our cloud your profile, workouts, health records, recipes, profile photo, progress, 500 most recent meals and up to 100 My Kitchen products; erases what it keeps on this iPhone, such as your meals, meal photos and recipes; asks Apple to revoke Brasa’s access, if you linked Apple; deletes your account; and starts you on a new, empty one.

Deletion runs from the app. If you have logged more than 500 meals, or something fails while it runs (for example, the connection drops), some cloud records stay. If that could apply to you, email us before you delete your account so we can find and remove the rest; afterwards we may not be able to tell which records were yours. Photos or video from a scan that hadn’t finished, and the app’s offline copy of synced records, can also stay on the phone; deleting the Brasa app removes them.

Account deletion does not remove Google Analytics and crash data, purchase records at Apple and RevenueCat, our AI request log, Google Cloud’s standard request logs, or promo-code and abuse-prevention records (see How long we keep data), and it does not delete Help improve Brasa samples (see Help improve Brasa). It also does not cancel your subscription: cancel it in your Apple ID’s subscription settings.

Finding your account. Brasa doesn’t need your name or email, and the app doesn’t show your account ID, so for any request by email we need your help to find your data. These help: the email address your Apple ID shares with Brasa, if you linked Sign in with Apple; the order ID on an App Store receipt for Brasa, if you subscribed; or the date, time and name of a few meals in your log, while they are still there. Once you delete your account, Brasa deletes its profile and Apple sign-in too, so your Apple email usually can’t lead us to what’s left; an App Store order ID may still work. If your account isn’t linked to Apple and you logged out of it or deleted the app, we may not be able to find its data either. We may also ask you to confirm that the request comes from you.

Withdraw consent. Turn off Help improve Brasa in Settings at any time to stop new contributions. Voice logging, bloodwork upload, heart rate, cookbook import and the setup photo check are optional, and you can turn off camera, microphone, speech recognition and notification access in iOS Settings → Brasa. The app has no way to delete a single lab report or your saved heart rate; deleting your account removes them. Withdrawing consent doesn’t affect processing done before.

Other requests. For any privacy request (access, correction, deletion, objection, restriction or a copy of your data), email marianovalle13@gmail.com with what helps us find your account. We answer within 30 days. If you are in the EU/EEA, UK, Brazil, California or another place with privacy laws, you may have additional statutory rights, including the right to complain to your local data-protection authority; the same email handles them. We won’t treat you differently for using your rights.

California and other US states. We don’t sell your personal information or share it for cross-context behavioral advertising. Because neither Brasa nor this website tracks you across other companies’ apps or websites, nothing changes when your browser or device sends a Do Not Track or Global Privacy Control signal. We use sensitive information, such as health data, to provide the features you use and, in the limited form described under Analytics and crash reports (for example, how many lab markers were out of range), to understand how Brasa is used and to fix problems.

How long we keep data

• On your iPhone: until you delete it in the app, delete your account (see Delete for what can stay) or delete the app.
• Cloud mirror (profile, meals, My Kitchen, workouts, health records, recipes, progress): until you delete the item, where the app offers that, or delete your account (see Delete for the limits). If you log out of an account that isn’t linked to Apple, or stop using Brasa without deleting your account, its cloud copy is kept until you ask us to delete it.
• Photos, video frames, documents and text sent for AI analysis: not stored by Brasa’s server, nor by xAI since October 12, 2026; requests sent earlier may be kept by xAI for up to 30 days (see AI processing).
• Help improve Brasa samples: up to 24 months (see Help improve Brasa).
• Google Analytics: event-level data for 2 months, and user-level data for up to 14 months after your last use of the app.
• Crashlytics: about 90 days.
• Google Cloud’s standard request logs: about 30 days.
• Our AI request log, promo-code redemptions and abuse-prevention counters: no fixed period yet. Nothing deletes them automatically, including when you delete your account, so they are kept until we delete them or you ask us to. Email us to have the entries linked to your account removed (see Finding your account).
• Purchase records: Apple keeps its own records under its policies. RevenueCat keeps your subscription record and, from version 1.0.7, the App Store ad attribution until we delete it; deleting your account doesn’t remove it. Email us to have it deleted (see Finding your account); we may keep what billing, tax and legal obligations require.
• Emails you send us: in our Gmail mailbox until we delete them.
• Apple speech recognition, Open Food Facts and Unsplash: under their own policies.

Legal bases and international transfers

If you are in the EU/EEA or UK, we rely on: our contract with you, to provide logging, AI estimates, sync, restore, subscriptions and the optional features you choose to use, such as reading your lab reports, saving your heart rate, voice logging, cookbook import and the setup photo check; your consent, for Help improve Brasa, which you give on its own screen in Settings; our legitimate interests, for analytics, crash reporting, request logs, measuring our App Store ads, security and abuse prevention; and our legal obligations, for purchase and tax records and for disclosures the law requires. You can withdraw consent at any time as described under Your rights.

Our backend and our providers are in the United States, so your data is transferred there. Where the law requires it, we rely on the providers’ Standard Contractual Clauses or their EU-U.S. Data Privacy Framework certification.

Children

Brasa is not directed at children under 13 (or the minimum age required in your country) and we do not knowingly collect their data. Setup does not continue for anyone who enters an age under 13. If you believe a child has given us data, email us with what you know about the account (see Finding your account) and we will delete the data we can find.

Changes

Material changes to this policy will be shown in the app or on this page. The date at the top shows when it last changed.