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, and the meal photographs you upload.
- Your meal photographs and your body statistics are sent to OpenAI so that the app can estimate nutrition and build your targets.
- There is no diagnostics SDK, no analytics SDK, no 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 Apple or with Google. Authentication is handled by Clerk, which creates and holds your identity record. Through it we receive and store your email address and a user identifier. Your name and profile picture are shown in the app from your Clerk profile. We never see or store your Apple or Google password.
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.
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.
3.4 Diagnostic and technical data
We do not currently use any crash-reporting, analytics or session-recording tool. The app does not collect your IP address, device information or usage events beyond what is strictly needed to run your requests (for example, our servers see the IP address of any request as a normal part of serving it, but we do not log or store it).
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, health-app data or microphone recordings. The app never reads your device's Health/Google Fit data, and never records audio.
- No payment data. The app is free and has no billing of any kind.
- No social features. Your data is never shown to other users.
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) |
| 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) |
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. In that flow your answers are sent to our servers and on to OpenAI to generate the plan, but nothing is written to our database and no account exists. 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 | Email address, sign-in identity, session and device metadata | Account creation and authentication |
| Apple, Google | Sign-in request; app distribution | You chose them as your sign-in provider |
| OpenAI | Your meal photographs (resized) and your onboarding answers, including age derived from your date of birth | Estimating meal nutrition and generating your targets |
| ImageKit | Your meal photographs | Image storage and delivery |
| Neon | Your profile, targets and meal records | Our database |
| Trigger.dev | Onboarding answers, meal identifiers and image links, email address for account-sync events | Runs the background jobs that generate plans and analyse meals |
| Expo | App framework and API hosting | Runs the app and its server endpoints |
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 and answers 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. If you do not sign in for 24 months, we delete it. |
| Sign-in identity | Deleted with your account |
| 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 and every meal estimate are produced automatically by AI models, with no human review. If the model fails or returns an implausible target, the app falls back to a standard published formula and shows you that result instead, without indicating which method was used.
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 — Profile tab, immediate, no request needed. Access, portability and correction are handled manually: the app has no data-export screen, and there is currently no screen for editing your body statistics after onboarding. 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
Deleting your account from the Profile tab is immediate and permanent. There is no recovery period and we cannot restore it. It 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 sign-in identity with our authentication provider.
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 deletion, until that point-in-time recovery window ages out.
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.