Privacy Policy

RUMBO TECH LABS, S.A.S. (a Mexican Sociedad por Acciones Simplificada, doing business as Rumbo Tech Labs), located at Zona Cementos Atoyac, Calle 5, No. 28, C.P. 72023, Puebla, Puebla, Mexico, is the controller of the personal data collected through the CalorIA Scan application ("the App") and the caloriascan.com website ("the Site").

Privacy contact (data subject rights under Mexican law, GDPR and U.S. requests): privacy@caloriascan.com

• Name and email address provided by Apple or Google when you sign in. If you use Apple's "Hide My Email", we receive only Apple's relay address.
• A unique user ID assigned by our authentication system (Supabase Auth) and your Apple or Google account identifier.
• Session tokens, IP address and sign-in date/time, for security and fraud prevention.

We only capture an image when you take a photo on the scan screen or choose one from your gallery. The image is compressed on your device and sent, encrypted (HTTPS), through our server to OpenAI for analysis. You can scan before creating an account. Along with the image we send your language, the tip style you chose and, if you provided it in your profile and gave the optional body-data consent, your sex (solely to word the tips with the correct grammatical form). We do not store the image in our database or file storage; we keep only the analysis result (food and nutritional values). Please do not photograph people, documents or any information other than your food.

Purchase user ID, product purchased, transaction IDs, subscription status, country and currency. Payments are processed by Apple (App Store) or Google (Google Play); we never receive or store your card details.

Through Firebase Analytics and Firebase Crashlytics (Google LLC): crash reports, device model, operating system and App version, country and language, subscription plan, and usage events (for example, scans performed, food name and calories when you save an entry, sign-in, subscription screens and purchases). They are tied to an installation identifier generated by Firebase, not to your name or email.

On Android, Firebase may read the device advertising ID (AAID) for analytics. On iOS we do not request tracking permission (ATT) and do not read the IDFA.

If you scan before signing up, we use an anonymous device identifier (IDFV on iOS / SSAID on Android) and keep the scan result for up to 30 days so it can be linked to your account if you register. We also keep a per-device trial scan counter (anonymous identifier, number of scans and dates) with no time limit, solely to stop the free trial from being reset; it contains no photos or health data. If you correct a scan result, we store that correction to improve accuracy; when you delete your account it is disassociated from you.

We do not access your location, contacts, or Apple Health / Health Connect, and we do not record audio. We do not sell your data or use it to track you across third-party apps or websites.

• Create and authenticate your account and keep your session. GDPR basis: performance of a contract (Art. 6.1.b).
• Analyze your food photos with AI to estimate calories and macronutrients. GDPR basis: performance of a contract; for health data, explicit consent (Art. 9.2.a).
• Save your meal history and sync it across devices. GDPR basis: explicit consent (Art. 9.2.a).
• Calculate your calorie goal and personalize tips with your body data, only if you choose to enter it. GDPR basis: optional explicit consent (Art. 9.2.a).
• Manage your subscription and validate purchases. GDPR basis: performance of a contract.
• Security, fraud prevention and bug fixing. GDPR basis: legitimate interest (Art. 6.1.f).
• Handle rights requests and meet legal obligations. GDPR basis: legal obligation (Art. 6.1.c).

• Send you reminders and progress notifications, only if you enable notifications.
• Usage analytics to improve the service (Firebase Analytics) and analysis-accuracy statistics. They do not include photos. GDPR basis: consent (Art. 6.1.a).

You may refuse secondary purposes from the start or at any time by turning off notifications, turning off analytics (once the App allows it), or writing to privacy@caloriascan.com with the subject "Objection". Refusing does not affect the service.

We do not sell your data, we do not use it for third-party advertising or marketing, we do not share it with data brokers, and we do not use your health data to make decisions with legal effects on you.

We share only the minimum data necessary with the following providers, who act as processors under contract and on our instructions:

Stores your account, profile and nutrition history, encrypted at rest. supabase.com/privacy

Receives the food photo, your language, the tip style and, if you provided it and gave the optional body-data consent, your sex (only for the grammatical form of the tips); it does not receive your name, email, weight, height or age. Under its API terms, OpenAI does not use data sent through the API to train its models. OpenAI may retain the data for up to 30 days solely to detect abuse (or longer if required by law or if its systems detect prohibited content), and then deletes it. openai.com/policies/privacy-policy

Receives your purchase user ID and transaction information from the App Store / Google Play. revenuecat.com/privacy

apple.com/legal/privacy · policies.google.com/privacy

Receives the data described in section 2(e). firebase.google.com/support/privacy

Only if you accept in the cookie banner. Google acts as an independent controller. Details in section 13.

We may also disclose data if a competent authority requires it by law.

Our providers process data in the U.S. Because they act as processors on our behalf, these disclosures do not require your consent under the LFPDPPP, and we contractually require them to protect your data at a level equivalent to this policy. For users in the EEA, the UK and Switzerland, these transfers rely on the European Commission's Standard Contractual Clauses and/or the EU-U.S. Data Privacy Framework, depending on the provider.

• Account, profile and nutrition history: while your account is active, or until you delete them.
• Food photos: we do not store them. OpenAI may retain them up to 30 days solely to prevent abuse.
• Technical platform logs (Supabase): up to 7 days.
• Per-device trial scan counter: no time limit (see section 2f).
• Scans made before creating an account: 30 days if not linked to an account.
• Analytics (Firebase): events up to 14 months at most (per the retention set in Firebase); crash reports up to 90 days.
• Backups: deleted data disappears from automatic backups within 7 days.
• Transaction records: as long as applicable tax laws require.

When you delete a meal in the App, it is removed from your device and from our servers. If you are offline at that moment, the deletion completes automatically the next time you connect. Meals you deleted in versions before 2.0.5 may have remained on our servers; you can request their permanent deletion by emailing privacy@caloriascan.com with the subject "ARCO rights", or by deleting your account.

Go to Profile → Delete my account and confirm. This permanently deletes your account, profile, nutrition history. Starting with version 2.0.5 it also deletes your RevenueCat record and revokes Sign in with Apple access. Deletion from our active systems is immediate and from backups within 7 days.

Write from the email associated with your account to privacy@caloriascan.com with the subject "Delete account" or use the form at caloriascan.com/en/delete-account.html. We usually handle it in 3 to 5 business days and, in any case, within 20 business days.

Deleting your account does not cancel your subscription, because Apple or Google bills you. Cancel it in Settings → [your name] → Subscriptions (iPhone) or in Google Play → Payments & subscriptions (Android).

You have the right to Access, Rectification, Cancellation and Objection (ARCO), to withdraw your consent, and to limit the use or disclosure of your data. You can correct your data directly in Profile → My profile and cancel it by deleting your account.

From version 2.0.5, in the App: Profile → More → Withdraw consent. If you withdraw the optional body-data consent, we delete your weight, height, age, sex and activity level from your phone and our servers and the App keeps working with a general calorie target; your account stays active. The nutrition-data consent is required for the App to work: withdrawing it means deleting your account and all your data (section 7). You can also write to privacy@caloriascan.com.

Write to privacy@caloriascan.com with the subject "ARCO rights" and include: (i) your name and your account email; (ii) the right you wish to exercise and the data it relates to; and (iii) for rectification, the correct data. We will reply within 20 business days and, if applicable, carry it out within the following 15 business days. If you are not satisfied with our response, you may go to the competent data protection authority (the Secretaría Anticorrupción y Buen Gobierno).

In addition to the above, you have the right to data portability, to restriction of processing, to withdraw your consent without affecting the lawfulness of prior processing, and to lodge a complaint with the supervisory authority in your country of residence.

Depending on your state of residence (including California, Washington and Nevada), you may have the right to know what data we hold, obtain a copy, correct it, delete it, and withdraw your consent to the processing of consumer health data. We do not sell or "share" (for cross-context behavioral advertising) personal data from the App, and we will not discriminate against you for exercising your rights. You can submit your request to the same email; if we deny it, you can appeal by replying with the subject "Appeal".

Required to scan food. It is only active while the scan screen is open; we do not record video or audio.

Optional. We only access the image you choose; we do not read the rest of your gallery.

Optional. Requested only if you enable reminders.

iPhone/iPad: Settings → CalorIA Scan → turn Camera, Photos or Notifications on or off.
Android: Settings → Apps → CalorIA Scan → Permissions.

• Encryption in transit (HTTPS with TLS 1.2 or higher).
• Encryption at rest (AES-256) in our database.
• Row-level security policies: each user can only access their own data.

No system is 100% secure. If a breach significantly affects your rights, we will notify you without delay so you can take action.

CalorIA Scan is intended for people over 18 years of age. We do not knowingly collect data from minors. If you know a minor has created an account, write to privacy@caloriascan.com and we will delete it.

Calorie and macronutrient values are approximate estimates generated by artificial intelligence and may contain errors. They are not medical, nutritional or dietary advice. If you are pregnant, have a medical condition, or have a history of eating disorders, consult a healthcare professional before using the App to manage your diet.

This section applies only to the Site (caloriascan.com), not to the App. The App does not use cookies; the App's analytics are described in section 2(e).

Only Google Ads cookies (gtag.js, ID AW-18120210375), to measure campaign conversions and, if you accept, show you personalized ads on Google platforms.

By default, no advertising cookie is activated until you accept in the banner shown on your first visit.

• Accept all: Google Ads cookies are activated.
• Necessary only / Reject all: no tracking cookie is activated (this Site does not require technical cookies).

At any time via Change cookie preferences, or by clearing the site data in your browser.

If you accept, Google may receive your IP address, cookie identifiers and browsing data on the Site, and processes them as an independent controller: policies.google.com/privacy · policies.google.com/technologies/ads. For residents of U.S. states with a right to opt out of targeted advertising, "Reject all" is equivalent to exercising that right.

Consent: LFPDPPP (Mexico) and GDPR Art. 6.1.a (EU/EEA).

We will post any change on this page with its new update date. If the change is significant, we will notify you in the App and/or by email before it takes effect. If a change involves new purposes for your health data, we will ask for your express consent again.