C1 Privacy Policy
Last updated: 2026-10-13
This Privacy Policy describes how the C1 mobile application
(“C1”, “we”, “us”, “our”) — operated by the C1 app operator — collects,
uses, and shares information when you use the C1 app on iOS and Android.
It reflects the data flows that are actually implemented in the C1 app as
of the date above; we do not claim to collect or use data that we do not.
1. Who we are
C1 is an AI-powered nutrition, calorie-tracking, and weight-management app.
The app publisher is the C1 app operator. For any privacy question or request
described in this policy, contact us at
support@c1-app.com.
2. Data we collect and why
2.1 Account & authentication data
- Email address, name, and password — required to create
and sign in to your C1 account. Passwords are stored only as a salted
hash and are never accessible in plaintext, even to us.
- Password reset tokens — a short-lived token is stored
when you request a password reset; it is invalidated on use or expiry.
2.2 Profile & nutrition data you provide
- Age, gender, height, weight, target weight, activity level, and goal
— used to compute your personalized daily calorie and macro targets.
- Language and theme preference.
- Meal entries you save (name, portion, calories, macros, meal type,
and — optionally — a meal photo you choose to attach).
- Water and weight log entries you record.
- Streak counters.
2.3 Meal photos (AI scan)
When you use the AI meal-scan feature, the photo you capture is sent
directly to our backend and forwarded to Google’s Gemini vision model
(via the Emergent LLM proxy) solely to identify foods and estimate
portions and nutrition. We do not keep a copy of the raw
scan photo on our servers; only the resulting nutrition items and a
scan-count record (timestamp + item count + whether the scan used your
daily allowance or a rewarded credit) are stored to enforce fair-use
limits. If you additionally attach a photo to a saved meal entry, that
photo is stored with the meal entry.
2.4 AI Coach chat
Messages you send to the C1 Coach are stored so you can revisit the
conversation, and they are forwarded to Google’s Gemini model (via the
Emergent LLM proxy) to generate the reply. Your profile fields (age,
gender, activity, goal, daily targets, and language) may be attached as
context so the assistant can personalize responses. We do not use your
chats to train third-party models.
2.5 Subscription & in-app purchase data
- When you purchase or restore a subscription, we receive a purchase
identifier from Apple (StoreKit 2 transaction JWS) or Google Play
(purchase token). We store the identifier, product ID, tier, period,
expiry date, auto-renew state, and status transitions (renewed, canceled,
refunded, expired, in grace, on hold) so we can grant the correct plan
entitlement.
- We do not receive or store your credit-card number,
bank details, or full billing address — those stay with Apple or Google.
- Real-time subscription state changes are delivered to our server by
Apple’s App Store Server Notifications V2 and Google Play’s Real-time
Developer Notifications so entitlements stay accurate without further
action from you.
2.6 Advertising (AdMob rewarded ads)
C1 shows optional Google AdMob rewarded ads that let free and Premium
users earn extra daily meal scans. When you choose to watch an ad:
- The Google Mobile Ads SDK is loaded on your device and may access
your device’s advertising identifier (Android Advertising ID / iOS IDFA
where you have granted App Tracking Transparency permission).
- Google delivers a signed Server-Side Verification callback to our
backend so we can grant one rewarded scan credit. We store the SSV
transaction id, key id, and grant timestamp for anti-abuse
(deduplication and per-plan caps).
- You can opt out of personalized ads at the OS level: on iOS via
Settings → Privacy & Security → Tracking or, when prompted,
by declining the App Tracking Transparency dialog; on Android via
Settings → Google → Ads. Denying tracking does not stop rewards
from being granted; it only removes personalization.
- Google is the data controller for ad-serving data. See Google’s
policy at
policies.google.com/technologies/ads.
2.7 Device permissions we request
| Permission | Why we ask |
| Camera | Take a photo of your meal so C1 can estimate calories and macros. |
| Photo library | Pick an existing photo from your gallery for the same purpose. |
| iOS App Tracking Transparency | Required only if you choose to see personalized rewarded ads (see 2.6). |
| Android Advertising ID | Required by Google Mobile Ads SDK; see 2.6. |
2.8 Data we do NOT collect
C1 does not currently use third-party product analytics, crash reporters,
attribution SDKs, session-recorders, marketing pixels, or any social
login / social sharing SDK. We do not collect your precise location,
contacts, microphone audio, health-app data, or on-device usage
statistics.
3. How we share data
We share the minimum data needed to run C1, with the following processors:
- Google (Gemini via Emergent LLM proxy) — receives
meal photos and coach chat messages solely to generate responses. Prompt
and image data are transmitted over HTTPS.
- Apple App Store & Google Play Billing — handle
payment processing and notify us of your subscription status.
- Google AdMob — serves rewarded ads and issues signed
SSV callbacks (see 2.6).
- Resend (email delivery, via Emergent proxy) — sends
transactional emails such as password-reset links. Only your email
address and the message body are shared with the delivery provider.
- MongoDB Atlas — hosts our operational database on
our behalf as a data processor.
We do not sell your personal information, and we do not share it with
advertisers or brokers for their own marketing purposes.
4. Data retention
- Your account, profile, meals, water logs, weight logs, and chat
history are retained for as long as your account exists.
- Scan-count records (used to enforce daily meal-scan limits) are
retained indefinitely so we can prevent quota abuse. They do not contain
the meal photo.
- Password-reset tokens expire automatically (typically within an
hour) and become unusable after they are consumed.
- Subscription and IAP event records are retained for as long as they
are needed to reconcile your entitlement and to comply with Apple and
Google’s billing dispute windows.
- When you delete your account (see Section 6), we delete your user
record, meals, water logs, weight logs, and chat history.
5. Where we store data
C1 stores operational data in MongoDB Atlas. Our backend is hosted on
the Emergent platform. Depending on your region, data may be transferred
to and stored on servers located outside your country. We rely on
standard contractual clauses or equivalent safeguards where required by
applicable law.
6. Your rights and choices
- Access & update — you can view and edit your
profile, meals, water, weight, and chats directly in the app.
- Delete your account — you can delete your account
from the Profile screen in the app; alternatively, email
support@c1-app.com. On deletion we
remove your user record and all meals, water logs, weight logs, and
chat history associated with your account. Aggregate, non-identifying
scan-count records may be retained for anti-abuse purposes.
- Manage subscriptions — subscriptions can be
reviewed and canceled at any time via Apple’s
Settings → Apple ID → Subscriptions or Google Play’s
Payments & subscriptions. Cancellation stops future
renewals; refunds are handled by Apple or Google under their policies.
- Ad personalization — see Section 2.6.
- GDPR / UK GDPR / CCPA rights — where applicable,
you have the right to access, correct, port, restrict, or object to our
processing of your personal data, and to lodge a complaint with your
supervisory authority. You have the right not to be discriminated
against for exercising a privacy right. To exercise these rights,
contact support@c1-app.com.
7. Children
C1 is not directed to children under 13, and we do not knowingly collect
personal data from children under 13. If you believe a child has
provided us data, please contact
support@c1-app.com and we will delete
it.
8. Security
We use HTTPS in transit, salted password hashing at rest, JWT-based
session tokens, and Server-Side Verification signatures for reward and
IAP callbacks. No system is 100% secure; if you suspect a breach or
vulnerability, please email
support@c1-app.com.
9. Changes to this policy
We may update this policy from time to time. The “Last updated” date at
the top of this page reflects the current version. Material changes
will be communicated in-app before they take effect.
10. Contact
Questions or requests: support@c1-app.com.
C1 is provided for general informational purposes and is not a
substitute for professional medical, dietary, or fitness advice.