1. Who we are
CalorieTap is made by [Company legal name], [address]. This policy explains what data the CalorieTap app collects, why, and what you can do about it. Questions go to privacy@calorietap.app.
2. No accounts, no names
CalorieTap does not ask for your name, email, phone number, or a password. When you first open the app, it generates a random identifier (a UUID) on your device. That ID is the only thing that ties your data together. We cannot look up a person by name, and we have no way to connect the ID to you unless you give us information that does.
Because the ID could still, in principle, be linked back to a device, privacy law treats data stored under it as personal data. We treat it that way too.
3. What we collect
We do not collect your name, contacts, photos, precise GPS location, or the advertising identifier (IDFA). We do not use any third-party advertising SDK.
4. Why we collect it
To run the app. Your profile and logs are what the app is for: calculating your target, showing your history, and syncing across devices.
To understand how it's used. Usage events let us see how many people use CalorieTap, which features matter, and where people get stuck. We look at these in aggregate. Nobody at CalorieTap sits down and reads one person's event stream.
To keep it working. Device info and crash reports help us find and fix bugs.
Where the law requires a legal basis (for example in the EU, EEA, UK, and Switzerland), we process profile and log data with your explicit consent, which you give in the app when you set up your profile and can withdraw at any time by deleting your data. We process usage events and device data under our legitimate interest in improving and securing the app, and purchase data to perform our contract with you.
5. What we never do
6. Who processes data for us
We use a small number of service providers who process data only on our instructions: [hosting provider] for storing your profile and logs, [analytics provider] for usage events, and [crash reporting provider] for crash reports. Apple handles payments and subscriptions. When you use "Just say it," the food name you say is sent to [nutrition data provider] to retrieve calories; it is sent without your ID.
7. How long we keep it
Your profile and logs stay as long as you use the app. If your ID has had no activity for 24 months, we delete everything stored under it. Usage events are kept in identifiable form for 14 months, then reduced to aggregate counts that contain no IDs. When you delete your data from the app, everything under your ID is removed from our servers within 30 days, including from backups.
8. Your choices
Delete everything. Settings → Delete my data wipes your ID and everything under it from your device and our servers. No email, no waiting on support.
Export your data. Settings → Export gives you your profile and full log history as a file.
Opt out of usage analytics. Settings → Share usage data. Turning it off stops usage events immediately. The app works the same either way.
Start fresh. Deleting the app and reinstalling creates a new random ID. Old data is not connected to it.
Depending on where you live, you may also have legal rights to access, correct, delete, or port your data, to object to or restrict processing, and to complain to a data protection authority. Because we can't identify you by name, the fastest way to exercise these rights is through the in-app controls above. For anything else, email privacy@calorietap.app from the device running the app so we can locate your ID. We will not discriminate against you for exercising any right.
9. Security
Data is encrypted in transit and at rest. Access to production systems is limited to people who need it to run the service. Your random ID is stored separately from any information that could identify a device. No system is perfectly secure; if a breach affects your data, we will notify you through the app and as required by law.
10. Children
CalorieTap is not for anyone under 16. If the birthdate you enter shows you are under 16, the app will not create a profile. If we learn we hold data from a child under 16, we delete it.
11. Where data is stored
Our servers are in [region, e.g. the United States]. If you use CalorieTap from elsewhere, your data is transferred there. Where required, we rely on standard contractual clauses or equivalent safeguards for those transfers.
12. Changes
If we change what we collect or how we use it, we will update this page and tell you in the app before the change takes effect. Continuing to use CalorieTap after that means you accept the updated policy.