Privacy policy
Close to Full keeps track of what you eat, what you weigh and how your body works. That’s personal, so this page says plainly what we keep, why, who helps us run the app, and how you get it back or get rid of it.
The short version
- We keep what you tell the app so it can work out your target and show your day. Nothing more.
- We never sell your data, never show you ads and never collect an advertising ID.
- Your account and everything you log are stored in Frankfurt, Germany.
- Meal photos and meal descriptions go to our AI provider, Anthropic, to recognise the food. It doesn’t use them to train its models.
- Usage data (taps and crashes) is off until you say yes, and never includes what you eat or weigh.
- A group sees only what you switch on. Your weight is never shared.
- Delete your account in Profile and everything goes with it.
1. Who we are
Close to Full is made and run by Anitha Manikandan, an individual developer. In this policy “we” and “us” mean her. She decides how your personal data is used, which makes her the controller under the EU’s General Data Protection Regulation (GDPR) and the data fiduciary under India’s Digital Personal Data Protection Act, 2023 (DPDP Act).
For anything about your data, write to support@closetofull.app. A person reads every message.
2. What we keep and why
Each card says what the data is, what we use it for, and the legal ground that lets us use it.
-
Your account
Your email address and a password, or, if you sign in with Google, the name and email address on your Google account. Google’s Firebase stores the password in a form we can’t read. We use these to sign you in, to send password-reset emails and to answer you when you write to us.
Legal ground: we need it to provide the app you asked for (GDPR Article 6(1)(b)).
-
Your body and your plan
Date of birth, gender (or “prefer not to say”), height, weight, how active you are, how you like to eat, your goal and the daily calorie and macro targets worked out from them. We use them to calculate your target and to suggest foods you’d actually eat.
Legal ground: your explicit consent, given with the box on the target step (GDPR Article 9(2)(a)). See your health data.
-
What you log
Meals and the foods, portions and nutrients in them, foods and meals you save, water, weigh-ins, and the days you’ve logged. We use them to show your day, your diary and your trends.
Legal ground: your explicit consent (GDPR Article 9(2)(a)).
-
Meal photos, typed meals and spoken meals
When you photograph a plate, the photo is sent to Anthropic’s Claude model, which names the foods and estimates the grams. We don’t store the photo: once the foods come back, it’s gone from our servers. When you type or say a meal, the words are sent to Anthropic in the same way. Spoken meals are turned into text by your phone’s own speech recognition service (on most Android phones that’s Google’s), under that service’s terms, before they reach us. We don’t receive or keep recordings.
Legal ground: your explicit consent (GDPR Article 9(2)(a)), and we need it to provide the feature you used (Article 6(1)(b)).
-
Food search and barcodes
What you type into search and the barcodes you scan. Our servers look them up in the USDA’s FoodData Central and in Open Food Facts. Those services get the search words or the barcode and nothing that identifies you.
Legal ground: we need it to provide the app (GDPR Article 6(1)(b)).
-
Your profile in groups
The display name and picture (a photo or a fruit) you choose for your groups, stored with your account, which groups you’re in, what you’ve chosen to share with them, and any report you send about a group or a member.
Legal ground: we need it to provide groups (GDPR Article 6(1)(b)), and your explicit consent for anything health-related you share (Article 9(2)(a)).
-
Plus subscriptions
Google Play or the App Store takes your payment. We never see your card or bank details. RevenueCat, the service we use to manage subscriptions, tells us whether you have Plus and when it renews or ends, linked to an account number rather than your name.
Legal ground: we need it to provide Plus (GDPR Article 6(1)(b)), and the stores keep purchase records to meet tax law (Article 6(1)(c)).
-
Reminders
Meal and water reminders are scheduled on your phone. Your reminder times and app preferences (theme, units and similar) are kept on the phone and with your account.
Legal ground: we need it to provide the feature you turned on (GDPR Article 6(1)(b)).
-
Usage data, only if you say yes
If you agree to help improve the app, Google’s Firebase Analytics, Crashlytics and Performance Monitoring collect which screens you open and which buttons you tap, crash reports, how fast the app runs, and details such as your phone model, Android version and rough location by country. Never what you eat, what you weigh or your targets, and never your purchase amounts. It’s off until you say yes, and you can turn it off any time in Preferences.
Legal ground: your consent (GDPR Article 6(1)(a)).
-
Server records
Our servers write short technical records when something fails, so we can fix it, and count requests so nobody can overload the app or run up its costs. These can include your account number and, for a failed barcode lookup, the barcode.
Legal ground: our legitimate interest in keeping the app working and secure (GDPR Article 6(1)(f)).
We don’t use your data for advertising, we don’t build profiles to sell, and we don’t make decisions about you by automated means that have legal or similarly significant effects. Your daily target is calculated by a formula from your answers, and you can change it any time.
3. Your health data
Your weight, body details and what you eat count as data concerning health, which the GDPR treats as a special category. We only keep it because you’ve explicitly agreed to it, by ticking the box on the target step that says the app may keep your weight, body details and what you log to work out your targets.
You can withdraw that consent at any time by deleting your account in Profile, or by writing to us. Withdrawing doesn’t make what we did before unlawful, but the app can’t work out a target or keep a diary without this data, so withdrawing means closing the account.
5. Data that leaves the EU
Your account and logs are stored in Germany. Some processing happens in the United States: Anthropic recognises food there, RevenueCat runs there, and Firebase’s usage-data tools process data there if you’ve said yes.
When data goes outside the EU, it’s protected by the EU-U.S. Data Privacy Framework where the company is certified under it, or otherwise by the European Commission’s Standard Contractual Clauses. Write to us if you’d like a copy of the safeguards that apply.
6. Family and Friends groups
Nothing is shared until you join a group. When you join, members see your display name and picture, plus only the things you’ve switched on (progress, streak, calories, macros, water). One setting covers every group you’re in, and the join screen shows what you’re about to share before you accept.
Your weight and whether you’re losing or gaining are never shared, at any setting. Turn a category off and it disappears from every group. Leave a group and your shared information leaves with you.
Remember that people in a group can see what you share while you share it, and we can’t control what they do with it, for example taking a screenshot.
7. How long we keep it
- Your account, plan, logs and profile picture: until you delete them or delete your account. When you delete your account, we remove your data from the database, your sign-in, your group memberships and your record at RevenueCat. If one of those steps fails, we finish it by hand.
- Meal photos: not kept. A photo exists on our servers only while it’s being recognised.
- An entry or weigh-in you remove: deleted when you remove it.
- Typed and spoken meals: to answer the same sentence faster, the AI’s answer is kept for 30 days, filed under a scrambled version of the text and not linked to you.
- Server records: up to 30 days.
- Usage data: Analytics events for 2 months and crash reports for 90 days, then Firebase deletes them.
- Subscription events: 30 days in our records. Google Play and Apple keep purchase records as long as tax law requires them to.
8. Your rights
Wherever you live, you can:
- See it. Ask for a copy of the personal data we hold about you.
- Take it with you. Get your data in a machine-readable format.
- Correct it. Change your details in Profile, or ask us to.
- Delete it. Delete your account in Profile, under Account, or ask us to. How to delete your account has the steps.
- Restrict or object. Ask us to pause using your data, or object to uses based on our legitimate interest.
- Withdraw consent. Turn off usage data in Preferences, stop sharing with groups in Profile, or delete your account to withdraw consent to health data.
Write to support@closetofull.app from the email address on your account. We’ll answer within one month, and we won’t charge you. If we need to check it’s really you, we’ll say so.
If you’re in the EU or EEA and unhappy with how we’ve handled your data, you can complain to the data protection authority where you live or work. We’d be grateful for the chance to put it right first.
9. If you live in India
We process your personal data on the basis of your consent under the DPDP Act, and you can withdraw it at any time as easily as you gave it. As well as the rights above, you can:
- get a summary of the personal data we process and the companies we share it with;
- have your data corrected, completed, updated or erased;
- nominate someone to exercise your rights if you die or can’t act for yourself;
- have a grievance addressed by us. Write to support@closetofull.app with “Grievance” in the subject. If you’re not satisfied with our answer, you can complain to the Data Protection Board of India.
10. Keeping it safe
Everything travels encrypted between the app and our servers, and Google encrypts it where it’s stored. Access rules on the database let only you read your own entries. Members of your groups can read only what you’ve chosen to share. Our server keys are held in a secrets store, never in the app. We review the app’s security regularly.
No system is perfectly secure. If a breach puts your data at risk, we’ll tell you and the authorities as the law requires.
11. Adults only
Close to Full is for people aged 18 and over, and the app asks for a date of birth to check. If we learn that someone under 18 has an account, we’ll delete it and its data.
12. This website
closetofull.app sets no cookies and runs no analytics or trackers. Its fonts are served from this site, so your browser doesn’t contact Google to load them. If you switch the site to the light theme, that choice is saved in your browser and never sent to us. Cloudflare, which serves the site, briefly processes your IP address to deliver pages and protect the site from attacks.
13. Changes to this policy
When this policy changes, we’ll update the date at the top. If a change affects what we collect or who we share it with, we’ll tell you in the app before it takes effect, and ask for your consent again where the law requires it.
Questions?
Write to support@closetofull.app. You can also read our terms of use.