huddles.ai
info@huddlesai.com
huddles.ai

Privacy Policy

Last updated: 18 September 2026 · Baca dalam Bahasa Malaysia

The short version

  • When you scan a meal, the photo is sent to Anthropic, so it can be read and turned into calories. That is the core of what the app does.
  • It travels through a relay we run, which keeps no copy of the photo, and Anthropic is not told who you are.
  • Location and camera metadata are removed from the photo before it is sent. The app never asks for your location at all.
  • The meals you log sync to your account so a new phone is not a fresh start. The photos themselves stay on your phone and are never uploaded.
  • Your height, weight, age and goal never leave your phone.
  • There is no analytics, crash-reporting, advertising or tracking software in the app of any kind, and nothing is sold or shared for advertising.

1. Who we are

Oat AI is a mobile application that estimates the nutrition of a meal from a photograph of it. It is operated by huddles.ai, based in Malaysia.

Photographs you scan travel through our own relay server, which checks that the request comes from a signed-in Oat AI account and counts how many scans that account has used, to enforce the daily allowance. The relay keeps counts, not content — your photographs are never stored on it.

huddles.ai is the data controller for the information described here. You can reach us about anything on this page at info@huddlesai.com.

2. What we collect

2.1 Account information

Oat AI is used with an account, and the only ways in are Sign in with Apple and Sign in with Google. There is no password to set. From whichever you choose we receive your name and email address — if you use Apple’s Hide My Email, what we receive is Apple’s relay address rather than your real one, and that is all we ever see. Accounts are handled by our authentication provider, Clerk.

2.2 Meal photographs

When you scan a meal, the app prepares the photograph before anything is sent:

  • it is re-encoded as a JPEG, which removes the metadata your phone attached to the original — GPS coordinates, camera and lens details, and the capture timestamp do not travel with it;
  • it is scaled down so its longest edge is no more than 1,568 pixels;
  • that copy is sent to our relay with nothing beside it but the image type and which of the three modes you chose — full plate, packet, or menu board. No name, no time, no location, no device identifier.

The relay passes it straight to the model provider and holds it only in memory for the few seconds that takes. We do not keep a copy of any photograph.

A copy does stay on your phone. Every scan saves its photograph into the app’s own storage so the meal in your log still has its picture later. Those files stay on the device, are never uploaded, and are cleared when the meal is deleted or the app is uninstalled.

The app does not request access to your photo library. Choosing an existing photo uses your phone’s own picker, which hands the app the single image you picked and nothing else — the app cannot browse, scan or read the rest of your library.

2.3 Your food log

The meals you log are stored on your phone and synced to your account so they survive a new phone. What syncs is the record, not the picture: the dish name and any note, its calories and macronutrients, fibre, sugar, sodium, the balance score, the parts the scanner broke the dish into, the date and time you logged it, which meal of the day it was, and whether it came from a scan, a barcode, a search, a saved meal or was entered by hand. This is held for us by Supabase and is readable only by your account.

2.4 Your body details and targets — on your phone only

The answers you give during setup — your country, gender, age, height, weight, goal, pace and activity level — and the daily calorie and macro targets worked out from them are stored only on your phone. They are not uploaded to us, and they are not part of the sync described above. Uninstalling the app removes them, and we cannot recover them for you.

2.5 Saved meals and recent foods

Meals you save for reuse, and the short list of foods you logged most recently, are kept on your phone only.

2.6 Barcodes and food search

Scanning a barcode or searching for a packaged food queries Open Food Facts, a public food database, directly from your phone rather than through our relay. Open Food Facts therefore receives the barcode you scanned or the words you typed, the country from your setup answers as a search filter, and, as with any request your phone makes to any website, your IP address. It is not told who you are, and we do not receive a record of what you searched for.

2.7 Scan allowance

So that the service stays fast and affordable, the relay allows 30 scans a day and at most 10 in a minute for each account. To do that it keeps a count — two numbers per account, and nothing else. Its operational logs record that an account made a scan, which model answered and how long it took; they never contain the photograph.

2.8 What we do not collect

No analytics. No crash reporting. No advertising or attribution software. No location — the app never asks for it. No contacts. No microphone. No health or fitness data from Apple Health. No device advertising identifiers. No tracking of you across other apps or websites, and no App Tracking Transparency prompt because there is nothing to track you with.

3. Why we use it

WhatWhyLegal basis (UK/EU GDPR)
Account informationTo create and secure your accountPerformance of a contract
Meal photographsTo recognise the food and estimate its nutritionPerformance of a contract, and your explicit consent (see below)
Your food logTo show your day and week, and to sync it to your other devicesPerformance of a contract, and your explicit consent (see below)
Scan countsTo enforce the allowance and prevent abuseLegitimate interests
Security and service integrityTo keep the service working and safeLegitimate interests

What you eat, what you weigh and what you are trying to change about it say something about your health. That makes parts of your food log “special category” data under Article 9 of the GDPR and sensitive personal data under Malaysia’s Personal Data Protection Act 2010. Where that is the case we rely on your explicit consent, which you give by choosing to scan a meal and to log it. You can withdraw it at any time by not logging further meals and by deleting your account.

4. Who we share it with

We share personal data only with the providers that make the app work. Each is required to protect it to a standard consistent with this policy, and none of them may use it for their own purposes.

ProviderWhat they receivePurpose
AnthropicThe meal photograph and a fixed instruction. Nothing that identifies youReading the photograph and estimating its nutrition
ClerkName, email address, and the Apple or Google account you signed in withAccounts and sign-in
SupabaseYour food log, attached to your account identifierStoring your log and syncing it between your devices
CloudflareHosts our relay; receives your requests in transit (including your IP address and the photograph, held in memory only) and keeps scan counts and short-lived request logs — never the photographRunning the relay that checks your account and counts scans
Open Food FactsA barcode or search term, a country filter, and your IP address, queried directly by your phoneLooking up packaged foods
AppleSign-in, and app distributionSigning you in and delivering the app

Anthropic does not receive your name, your email address, your account identifier or any other part of your log — only the image and the same fixed instruction every scan sends. What it does with a request it has answered, including how long it holds it and whether it is reviewed for abuse, is governed by its own API terms. We do not sell your personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under California law.

5. What else is in the photograph

A picture of a plate often catches more than the plate: the people at the table, the room you are in, a receipt, a screen, a document.

  • The photograph is used only to answer the scan you asked for. We do not store it, build a profile from it, or use it for anything else.
  • Location and camera metadata are removed before it is sent, so where and when it was taken does not travel with it.

Point the camera at the food. Anything else in the frame is sent with it, so it is worth keeping other people, their faces, and anything private out of the picture.

If you believe a photograph containing your personal information was submitted to Oat AI by someone else and you want it addressed, contact us at info@huddlesai.com.

6. Where your information goes

We are based in Malaysia and our providers are based in the United States, so your information is transferred outside your country and outside Malaysia. These transfers are covered by Standard Contractual Clauses (with the UK Addendum where applicable). You can request a copy of the relevant safeguards from info@huddlesai.com.

7. How long we keep it

DataRetention
Account informationUntil you delete your account
Meal photographs sent for scanningNot retained by us; held in memory by the relay for the seconds a scan takes
Meal photographs on your phoneUntil you delete the meal or uninstall the app
Your food logUntil you delete your account. A meal you delete is marked deleted and disappears from your devices; the record is cleared when the account goes
Body details, targets, saved meals, recent foodsOn your phone until you uninstall the app or delete your account
Scan countsTwo numbers per account, kept for the current day and minute
Relay request logs (that an account scanned, which model answered)A few days, on our hosting provider’s schedule

8. Your rights

Depending on where you live, you may have the right to access, correct, delete, restrict or object to our use of your personal data, to portability, to withdraw consent, and not to be discriminated against for exercising these rights.

  • Delete your account in the app: Profile → Delete account. This deletes your food log from our servers, your account with our authentication provider, and everything the app holds on that phone — your body details, targets, saved meals and meal photographs.
  • Delete individual meals: delete them in the app, or uninstall the app to remove everything it holds on that device.
  • If you signed in with Apple, deleting your account here ends our side of it. Apple keeps its own list of the apps you have used Sign in with Apple for, which you can manage in Settings → your Apple Account → Sign in with Apple.
  • Anything else: email info@huddlesai.com. We will respond within the period required by law — one month under UK/EU GDPR, 45 days under California law, and 21 days for a data access request under the Malaysian PDPA.

Malaysia. Under the Personal Data Protection Act 2010 you may request access to and correction of your personal data, limit its processing, and withdraw consent. You may also lodge a complaint with the Personal Data Protection Commissioner.

UK and EU. You have the right to complain to your supervisory authority — in the UK, the Information Commissioner’s Office at ico.org.uk.

California. The categories of personal information we collect are identifiers, internet activity, and user content. They are collected from you directly and used for the purposes set out in section 3. Your food log and meal photographs may be “sensitive personal information”; we use them only to provide the service you requested, which does not require a “Limit the Use of My Sensitive Personal Information” option.

9. Security

Account credentials are handled by Clerk, and your session is held in your device’s secure keychain rather than ordinary app storage. Data in transit is encrypted. Every request to the relay is checked against your signed-in account before a photograph is forwarded, and your food log on our servers is readable only by your own account, enforced by the database itself. Data the app keeps on your phone sits in its private storage area, protected by your device’s own encryption, and may be included in your phone’s encrypted backup (iCloud or a computer), which we have no access to. No system is perfectly secure, and we cannot guarantee absolute security.

10. Children

Oat AI is not intended for children. You must be at least 18 years old to use it, and the setup questionnaire will not accept an age below that. We do not knowingly collect data from children. If you believe a child has given us personal data, contact us and we will delete it.

11. Changes

We update this policy when the app changes. If a change is significant we will tell you in the app before it takes effect. The “last updated” date at the top always reflects the current version. Our Terms of Use sit alongside this policy.

12. Contact

huddles.ai
info@huddlesai.com
© copyright huddles.ai 2026