Privacy Policy
1. Who we are
Satiate is a mobile app that estimates the calories and macronutrients in a meal from a photograph, and tracks them against daily targets.
The data fiduciary — the person who determines the purpose and means of processing your personal data under India's Digital Personal Data Protection Act, 2023 (DPDPA) — is Shubham Dubey, an individual based in NIT, Faridabad, Haryana 121005, India. You can reach us at hello@clanassist.com.
This policy covers the Satiate mobile app and these pages. It sits alongside our Terms of Service.
2. The short version
- We collect your sign-in identity, the body statistics you enter during onboarding, the meals, weigh-ins and (if you turn it on) steps you log, and the meal photographs you upload.
- Your meal photographs are sent to OpenAI so that the app can estimate their nutrition. Your daily targets are worked out on your phone.
- When the app hits an error, it sends us an error report with your email and name, so we can fix it and tell you when it is fixed. These reports go to our own server, not a third-party service, and are deleted after 30 days (section 3.4).
- There is no third-party analytics or advertising SDK, and no cross-app tracking of any kind.
- We never sell your data, and we never use it to train our own AI models.
- You can erase your account and its data yourself, from the Profile tab, at any time.
3. What we collect
3.1 Account and identity
You sign in with Google. Sign-in is handled by our own sign-in service, which we run on our hosting provider (Render) with its own database (Neon), so no outside authentication company holds your identity record. Through it we receive and store your email address, your name and a user identifier, and the address of your Google profile picture, which the app shows. We never see or store your Google password.
The sign-in service keeps a record of each sign-in and sign-out: the time, your email address, the approximate country, and your device model, Android version and app version. The IP address of a sign-in is kept for 30 days and then cleared. It is used only to keep accounts secure and to investigate sign-in problems. Versions of the app before 1.2 signed in through Clerk, an outside authentication provider. We no longer use Clerk; the records it still holds from those versions are deleted when we close our Clerk account.
3.2 Body and health-related data
The onboarding questionnaire collects nine answers: gender, date of birth, height, current weight, goal (lose, maintain or gain), target weight, activity level, desired weekly pace, and diet preference. We also store your device's timezone, so that "today" means your day and not ours.
From these we generate and store your daily calorie target, your protein, carbohydrate and fat targets, and a one-line explanation of how they were derived. You can change your answers later in Profile → Personal details.
If you log your weight, we store each weigh-in (one per day) so we can show your progress and offer you a new daily target as your weight changes.
Body statistics, diet preference and meal photographs are health-related data. Under the GDPR they are "special category" data (Article 9). India's DPDPA does not define a separate category for sensitive personal data, but we handle this data only with your explicit consent regardless, and you can withdraw that consent at any time by deleting your account.
3.3 Meal photographs and nutrition records
When you log a meal we store the photograph you took or chose, and the record produced from it: the meal name, the estimated calories, protein, carbohydrate and fat, the time you logged it, and whether the analysis succeeded or failed.
Photographs are taken from your camera or picked from your photo library. Nothing leaves your device until you tap to analyse a meal. If the model decides a photo is not food, the record is discarded — though the uploaded image file itself remains in storage until you delete your account.
You can add a short description to a photo (for example “2 rotis, made with ghee”). It is optional. It is sent to OpenAI with the photo to improve the estimate and is not saved with your meal record.
Before a photograph is stored, it is checked automatically by OpenAI's moderation service for sexual, graphically violent or self-harm content. A photo that fails this check is rejected and never stored; we keep only a log line that an upload from your account was rejected and in which category, not the image.
3.4 Diagnostic and technical data
Error reports. When something goes wrong in the app or on our server, an error report is sent to our own error-tracking server. A report holds the error message and where in the code it happened, the app version, your phone's model, its operating system version and language, the last few screens you opened and actions you took in the app, and your email address and name. We use these reports only to fix bugs and to tell the people a bug affected once it is fixed. They are never used for marketing. Each report is deleted automatically after 30 days. The list of people a bug affected (email and name) is kept until that bug has not happened for 30 days, so we can still tell them when it is fixed.
App opens. Each time you open the app, we record the time, your platform (Android or iOS) and the app version, linked to your account. We use this to see how many people use the app and which versions are still in use.
We do not use any third-party crash-reporting, analytics or session-recording tool. Our servers see the IP address of each request as a normal part of serving it, but we do not log or store it.
3.5 Feedback you send
If you use Send feedback in the Profile tab, we store your message, the type you picked (bug, idea or other), the app version and your platform (Android or iOS), linked to your account so we can reply by email. Sending feedback is optional.
3.6 Food searches
When you search the food list, we store what you typed, how many foods matched, and which food you then picked, linked to your account. We use it for one thing: finding the foods and spellings our catalogue is missing, so the next search works. It is not used for advertising or profiling, and it is never shared.
3.7 Packets you scan
When you scan a packet's barcode, our server looks the barcode number up in Open Food Facts, a public food database. Only the barcode number is sent, never anything about you. If the packet isn't found and you type in the nutrition from its label, that food is added to Satiate's shared food list so the next person who scans it finds it. Other users see the food and its nutrition, never who added it.
3.8 Steps
If you turn on step counting, Satiate reads the number of steps your phone counts each day, using Android's Physical activity permission and Google Play services on your phone. We store one total per day with your account so you can see past days and so your goal forecast can use them. We don't read your location, and we don't get steps from other apps or watches. You can turn it off any time in your phone's settings (Apps → Satiate → Permissions).
3.9 Purchases
Satiate Pro is sold through Google Play, which handles the payment. We never see your card, UPI or bank details. Google tells us which plan you bought, its order number, whether it is active, renewing, cancelled or refunded, and when it ends. We store that with your account so the app knows how many scans you have.
3.10 Emails we send you
Besides replies to your feedback, we send a few emails to the address on your account: a welcome email, a birthday greeting (from the date of birth you gave us), a note when you reach a logging streak, news about new features, and a note when a food you searched for and couldn't find has been added. They use only your email address, your name and your activity in the app. If you'd rather not get them, email hello@clanassist.com and we will stop.
3.11 Reminders
Meal, water and protein reminders are scheduled on your phone. Nothing about them is sent to us. You can turn them off in your phone's settings (Apps → Satiate → Notifications).
4. What we do not collect
This list is as much a part of the policy as the one above, and it is verifiable in our source code:
- No location data. The app never requests or accesses your location.
- No advertising identifiers and no tracking. There is no ad SDK, no IDFA or Android advertising ID, no App Tracking Transparency prompt, and no sharing of data with advertisers or data brokers. We do not track you across other apps or websites.
- No third-party analytics or diagnostics SDK of any kind.
- No contacts, calendar, other apps' health data or microphone recordings. The app never reads Health Connect, your Google Fit account or any other app's health data, and never records audio. The only activity data it reads is your phone's own step count, and only if you turn step counting on (section 3.8).
- No payment details. Google Play takes payment for Satiate Pro; we never see your card, UPI or bank details (section 3.9).
- No social features. Your data is never shown to other users. The one shared thing is the nutrition you type in for a packet, shown without your name (section 3.7).
On iOS the app declares a microphone usage string, required by the camera
library we use even though the app never records audio. On Android the
equivalent RECORD_AUDIO permission is explicitly blocked and does
not appear in the app's manifest.
5. Why we process your data, and on what legal basis
| Data | Purpose | Legal basis |
|---|---|---|
| Email address, user identifier | Create your account, sign you in, keep your data available across devices | Performance of our agreement with you (GDPR Art. 6(1)(b)); your consent, given when you agree to this Policy (DPDPA Section 6) |
| Body statistics, diet preference, timezone | Generate and store your daily calorie and macronutrient targets | Explicit consent (GDPR Art. 9(2)(a); DPDPA Section 6) |
| Meal photographs and nutrition records | Estimate what you ate and show you your day | Explicit consent (GDPR Art. 9(2)(a); DPDPA Section 6) |
| Weigh-ins and daily step totals | Show your progress, forecast your goal date and keep your targets right as your weight changes | Explicit consent (GDPR Art. 9(2)(a); DPDPA Section 6) |
| Purchase records from Google Play | Give you the scans your plan includes, and handle renewals, cancellations and refunds | Performance of our agreement with you (GDPR Art. 6(1)(b)); your consent, given when you agree to this Policy (DPDPA Section 6) |
| Error reports (including your email and name) and app opens | Find and fix bugs, tell affected people when a bug is fixed, and see which app versions are in use | Legitimate interests (GDPR Art. 6(1)(f)); your consent, given when you agree to this Policy (DPDPA Section 6) |
| Email address, name, date of birth, logging activity | Send the emails in section 3.10 | Legitimate interests (GDPR Art. 6(1)(f)); your consent, given when you agree to this Policy (DPDPA Section 6) |
| Feedback you submit | Answer you and improve the app | Legitimate interests (GDPR Art. 6(1)(f)); your consent, given when you agree to this Policy (DPDPA Section 6) |
| Food searches and the food picked | Find foods and spellings missing from the catalogue | Legitimate interests (GDPR Art. 6(1)(f)); your consent, given when you agree to this Policy (DPDPA Section 6) |
Where we rely on explicit consent, you may withdraw it at any time by deleting your account (section 12). Withdrawal does not affect processing carried out beforehand.
Before you have an account. You can complete the questionnaire and see your targets before signing in. Your targets are worked out on your phone, so in that flow nothing is sent to us or to anyone else. Your answers are saved only once you sign in and the plan is attached to an account.
6. Who else receives your data
We do not sell your data and we do not share it for anyone else's marketing. We use the following processors to run the Service. Each receives only what it needs.
| Provider | What it receives | Why |
|---|---|---|
| Clerk (no longer used) | Nothing new. It still holds the email address, sign-in identity and session records of accounts created before app version 1.2 | Our former sign-in provider; those records are deleted when we close our Clerk account |
| Sign-in request; app distribution; payment for Satiate Pro, which Google processes itself | You chose them as your sign-in provider, and Google Play sells the app's plans | |
| OpenAI | Your meal photographs (resized) and any description you add to a photo | Estimating meal nutrition and checking photos for prohibited content |
| ImageKit | Your meal photographs | Image storage and delivery |
| Neon | Your profile, targets, meals, weigh-ins, steps and purchase records | Our database |
| Trigger.dev | Meal identifiers and image links, your email address and name (for account sync and the emails in section 3.10), and account identifiers for scheduled deletion | Runs the background jobs that analyse meals, send emails and erase deleted accounts |
| Render | Every request the app makes, and the error reports in section 3.4 | Hosts our API server and our error-tracking server |
| Resend | Your email address, your name and the email's contents | Delivers the emails in section 3.10 |
| Expo | Requests for app updates, with the app version, your phone's platform and a random identifier for this install of the app | Delivers small app updates without a new Play Store download |
| Open Food Facts | A packet's barcode number only, nothing about you | Looking up a scanned packet's nutrition |
We may also disclose data where we are legally required to, or to establish or defend legal claims. If the Service is ever transferred to another operator, we will tell you before your data moves.
7. Where your data goes
Our providers operate outside India. In particular, our database is hosted in the
United States (AWS us-east-2), and OpenAI processes your
photographs in the United States.
Under India's DPDPA (Section 16), personal data may be transferred outside India except to countries the Central Government specifically restricts by notification; no such restriction currently applies to our providers.
8. How long we keep it
| Data | Retention |
|---|---|
| Profile, targets, meal records and photographs | Until you delete your account. |
| Sign-in identity | Deleted with your account |
| Feedback you sent | Until you delete your account |
| Food searches | Until you delete your account |
| Weigh-ins, daily step totals and app opens | Until you delete your account |
| Purchase records | Until you delete your account. Google Play keeps its own record of the purchase under its own policy. |
| Error reports | Each report: 30 days, then deleted automatically. Your email and name on a bug's list of affected people: until that bug has not happened for 30 days. |
| Nutrition you typed in for a packet | Stays in the shared food list after you delete your account, no longer linked to you |
| Background job history held by Trigger.dev | 1 day, on our current (free-tier) plan |
| Database backups held by Neon | Up to 6 hours of point-in-time recovery history, on our current (free-tier) plan. We do not manage or delete backups ourselves; they age out automatically under Neon's own retention window. |
9. How we protect your data
These are the measures actually implemented in the app and its API:
- All traffic between the app, our API and our providers runs over encrypted connections (HTTPS/TLS).
- Your session token is held in the device's secure storage — the iOS Keychain or the Android Keystore — not in ordinary app storage.
- Every endpoint that touches your data verifies a signed session token before doing anything, and resolves your records from that token rather than from anything the app sends.
- Our API returns an explicit allow-list of fields, so internal identifiers and columns never leave the server.
- Incoming account webhooks are rejected unless their cryptographic signature verifies, and each event is processed exactly once.
- Credentials for the database, image storage and AI providers exist only on the server; the app never holds them.
- Live progress updates for your meal analysis use a short-lived token scoped to that single job.
- Uploads are size-limited and validated before being accepted.
Encryption at rest, physical security and network isolation are provided by our infrastructure providers under their own certifications. No system is perfectly secure, and we cannot guarantee absolute security. If a breach affects your rights, we will notify you and the Data Protection Board of India as required under DPDPA Section 8(6).
10. Automated processing
Your daily targets are calculated on your phone with a standard published formula. Every photo estimate is produced automatically by an AI model, with no human review, and you can edit the numbers before you save the meal.
We do not consider this to produce legal or similarly significant effects on you: the output is a nutrition estimate, not a decision about you, and nothing follows from it automatically. We do not profile you for advertising, scoring or any other purpose. If you disagree with a result or want a human to look at it, write to us at hello@clanassist.com.
11. Your rights
Under India's DPDPA and, where it applies to you, the GDPR, you have the right to:
- obtain a summary of the personal data we process about you and the processing activities carried out (DPDPA Section 11);
- learn the purpose of processing and whether it is used accordingly;
- know the identities of other data fiduciaries and processors with whom your data has been shared, and what data was shared (DPDPA Section 11);
- have inaccurate or incomplete data corrected, updated and completed (DPDPA Section 12);
- have your data erased once it is no longer needed, and have us notify recipients of erasure or correction (DPDPA Section 12);
- nominate another individual to exercise these rights on your behalf if you die or become incapacitated (DPDPA Section 14);
- lodge a grievance with us and, if unresolved, with the Data Protection Board of India (DPDPA Section 13);
- receive your data in a portable, machine-readable format, and restrict or object to processing, including processing based on legitimate interests (where the GDPR applies to you);
- withdraw your consent at any time (DPDPA Section 6(4));
- object to a result produced solely by automated analysis that works to your detriment, and claim compensation for damage caused by unlawful processing (where the GDPR applies to you).
Erasure is self-service — from the Profile tab, no request needed (section 12). Correction of your body statistics is self-service too, in Profile → Personal details. Access and portability are handled manually: the app has no data-export screen. Email hello@clanassist.com and we will action your request. We respond within 30 days, and within one month under the GDPR where it applies to you.
12. What deletion really removes — and what it does not
You can delete your account in the app, from Profile → tap your name → Delete account. You are signed out at once and the account is kept, untouched, for a 14-day recovery period, in case the request was a mistake or was not yours: sign back in within it and you can restore the account. When the 14 days end it is erased permanently, and we cannot restore it. Erasure removes:
- every meal photograph you have uploaded, from our image storage;
- your profile record — body statistics, goal, preferences, timezone and targets;
- every meal you have logged, with all its nutrition data;
- your weigh-ins, your daily step totals and your purchase records;
- your feedback messages, your food search history and your app opens;
- your sign-in identity with our sign-in service. (An account from before app version 1.2 also has an old record at Clerk, which we no longer use; it goes when we close our Clerk account.)
Being straight with you about what it does not reach:
- Background job history held by Trigger.dev retains the inputs those jobs ran on — including your onboarding answers and meal image links — until it expires under that provider's 1-day retention window.
- Database backups held by Neon may hold a copy of your data for up to 6 hours after erasure, until that point-in-time recovery window ages out.
- The sign-in log keeps a line for each sign-in and sign-out: the time, your email address, the approximate country and your device model. Deleting your account does not remove these lines; only the IP address on them is cleared, 30 days after the sign-in.
- Error reports that include your email and name are deleted on their own schedule (section 8), not when your account is erased.
- Nutrition you typed in for a packet stays in the shared food list, no longer linked to you.
- Google Play's own purchase records are kept by Google under its own policy.
If you want these cleared sooner, email hello@clanassist.com and we will make the requests on your behalf.
13. Children
Satiate is not intended for anyone under 16, and our Terms of Service require you to be at least that age. We do not knowingly collect data from children. The app asks for your date of birth to calculate calorie needs, not to verify your age. If you believe a child has given us their data, contact us at hello@clanassist.com and we will delete it.
14. Changes to this policy
We will update this policy when what we do changes. The current version always lives at this address with its effective date at the top. Where a change materially affects how we use your data, we will make reasonable efforts to tell you in the app or by email before it takes effect, and where the law requires it we will ask for your consent again.
15. Contact and complaints
For any privacy question, or to exercise any right above, write to hello@clanassist.com.
If you are not satisfied with our response, you may complain to the Data Protection Board of India, established under the DPDPA. If you are in the EEA, you may instead complain to the supervisory authority where you live or work.