Privacy policy
AddPlate is a strength log and food tracker that keeps your log on your phone. There is no account, and no server holds your workouts, meals or weight. This policy says exactly what stays on your phone, what leaves it, who else is involved, and what you can ask of us.
The short version
- Your log (workouts, meals, weigh-ins, water, body stats) stays on your phone.
- A photo, a meal description or plan answers leave your phone only when you send them to be read by AI. We don't store them.
- Data from Health Connect stays on your phone and is never uploaded.
- A Garmin watch sends its heart rate to the app on your phone over Bluetooth. It doesn't pass through our server.
- This website sets no cookies and runs no analytics. If you join the waitlist, we keep your email until early access opens.
- We don't sell data, show ads, or share data with advertisers.
- Questions or requests: brmbota14@gmail.com
- 1. Who is responsible
- 2. What stays on your phone
- 3. What leaves your phone
- 4. Health Connect
- 5. A Garmin watch
- 6. Permissions the app asks for
- 7. What we don't collect
- 8. This website and the waitlist
- 9. Why we may use it
- 10. Who else is involved
- 11. International transfers
- 12. How long we keep it
- 13. Your rights
- 14. Children
- 15. Security
- 16. Changes
- 17. Contact
1. Who is responsible
AddPlate is published on Google Play and in Garmin's Connect IQ store by CodeInnovate, an independent developer, which is the controller of the personal data described here. In this policy, "we" and "us" mean CodeInnovate.
Contact for anything in this policy: brmbota14@gmail.com
2. What stays on your phone
Everything you log: workouts and sets, programs, cardio sessions (with the route GPS measured and the steps the phone counted, for an outdoor one, and the heart rate a Garmin watch sent), meals and foods, weigh-ins, water, the name you give the app (if any), body stats (height, weight, age, sex, and whether you are pregnant or breastfeeding, if you say), how active your day is, body measurements, progress photos, your goal and its pace, weight goal and calorie target, your answers to the plan questions (experience, schedule, equipment, pain or injury to work around, muscles to focus on, recent sets), your ranks and XP, and anything brought in from Health Connect. It is stored in the app's private storage on your device, works without an internet connection, and is not sent to us. We can't see it. Progress photos are kept in a part of that storage that is never included in any backup: not in the file you export, and not in Android's own device backup.
It leaves your phone only in a backup file you choose to export, which goes wherever you save it. The file includes your answers to the first questions, so a new phone can skip them. Progress photos are never in it. Uninstalling the app, or clearing its storage in Android settings, deletes all of it.
Some of this is information about your health. That is the reason it stays on your device.
3. What leaves your phone, and only when you use it
| Feature | What is sent | Where it goes |
|---|---|---|
| Food photo, describe a meal | The photo or the text you submit for that one request | Our server, which passes it to Anthropic (Claude) to read it and returns the result. We don't store the photo or the text. |
| AI plan builder | Your answers to the plan questions, including any pain or injury to work around, and the exercises they allow | Our server, then Anthropic. Not stored. |
| Barcode lookup | The barcode number | Our server, which asks Open Food Facts and caches the product. A product is not personal data. |
| Adding a missing product | The barcode and the product details you typed | Stored on our server and shown to other users who scan that product. |
| Ideas board | Ideas you post and votes you cast | Stored on our server. Ideas are shown to other users once reviewed. |
Nothing from your log is sent with these requests, apart from what you put into the request yourself. Label scanning and barcode scanning read the camera image on your phone. The image is not sent anywhere.
The install ID
Each request carries an install ID: a random code created by the app on your phone and deleted with the app's data. It is not linked to your name, email, advertising ID or hardware. We use it only to count AI uses against the free allowance and the daily limits, to stop one phone voting twice, and to stop someone confirming their own product entry.
Your IP address
Like any server, ours sees your IP address. We don't store it. To stop one person flooding product contributions or the waitlist, the server keeps a short, salted hash of the address (8 characters) for daily counting. The salt changes whenever the server restarts, so the hash can't be turned back into the address or linked across restarts.
No AI result in AddPlate is a decision with legal or similarly significant effects on you. Estimates are shown to you to accept, change or ignore.
4. Health Connect
On Android, AddPlate can connect to Health Connect, the shared health store that Google Fit, Samsung Health, Honor Health and other apps use. It is off until you turn it on in Profile → Integrations, and you choose each permission in Android's own dialog.
AddPlate reads
- Weight and body fat: a reading from a smart scale or another app becomes a weigh-in in AddPlate, so it moves your weight trend and calorie target.
- Steps: your daily total, shown on the Food tab, and the steps during an outdoor walk, run or hike, shown on that session's summary when the phone did not count them itself.
- Heart rate: what a watch recorded during a cardio session, read after it ends, to show its average, peak and time in each zone on that session's summary.
AddPlate writes
- Workouts: strength and cardio sessions you finish, with start and end time, the kind of activity and the session's name.
- Distance: how far a cardio session went, when GPS measured it or you typed it in from the machine.
- Food: calories, protein, carbs and fat for each item you log.
- Weight: the weigh-ins you enter in AddPlate.
- Water: what you log.
AddPlate reads only the last 30 days, and only while the app is open: when you open it and when you tap Sync now. It does not ask for background access or for older history.
Data read from Health Connect stays on your phone. It is never sent to our server or anyone else's, never sold, never used for advertising, never used to train AI models, and never shared, except in a backup file you export yourself. Nobody reads it but you, in the app.
AddPlate's use of information received from Health Connect adheres to the Health Connect Permissions policy, including the Limited Use requirements.
To stop: Profile → Integrations → Disconnect removes every permission, or change them in Health Connect at any time. Records AddPlate wrote stay in Health Connect until you delete them there. Weigh-ins it brought in stay in AddPlate until you delete them.
5. A Garmin watch
If you have a Garmin watch, you can install the AddPlate app on it from Garmin's Connect IQ store. During a cardio session it becomes the session's second screen and its heart rate sensor.
What goes between the watch and the phone
- From the watch: your wrist heart rate, every two seconds while the watch app is open, and a pause or resume when you press its START button.
- From the phone: the session's current block, the time left, what comes next, and the maximum heart rate the zones are worked out from.
This goes over Bluetooth, through Garmin Connect, Garmin's app on your phone that already holds the link to your watch. It doesn't pass through our server, and AddPlate asks for no Bluetooth permission of its own. The heart rate is stored on your phone with the session, to show its average, peak and time in each zone, like the rest of your log (section 2). The watch app keeps nothing once it closes.
On the watch, the app asks Garmin for two permissions: Sensor, to read the heart rate, and Communications, to talk to the app on your phone.
Nothing is sent unless the watch app is installed and open. To stop it, turn off Profile → Training → Cardio cues → Garmin watch, or remove the app from the watch. Garmin Connect, the Connect IQ store and the watch are Garmin's, and Garmin's own privacy policy covers them.
6. Permissions the app asks for
| Permission | Why |
|---|---|
| Camera | Scanning a barcode or a nutrition label, and taking a food photo, only while you have that screen open. A progress photo is taken with your phone's own camera app; AddPlate keeps it only in its private storage and never sends it anywhere. Some camera apps also keep their own copy in your gallery. A photo you choose from your gallery instead comes through Android's photo picker, which needs no permission. Barcode and label images are read on your phone and not sent anywhere. A food photo is sent only when you choose to have it read. |
| Notifications | The rest timer's alert between sets, a running cardio session with its Pause and Skip buttons, and, if you leave while a plan is being built, a note that it is ready. Nothing else is sent as a notification. |
| Location (precise) | Only for an outdoor cardio session you start, and only while it runs: GPS measures its distance and pace. Asked the first time you start one; if you say no, the session is timed instead. Never in the background otherwise. The route stays on your phone and is not sent to us or anyone else. |
| Physical activity | Only for an outdoor walk, run or hike you start, and only while it runs: the phone's step counter counts your steps. Asked the first time you start one; if you say no, the session works without steps. The count stays on your phone, with the session, and is not sent to us or anyone else. |
| Alarms, foreground service, start at boot, vibration, keeping the phone awake | Keep the rest timer and a cardio session's intervals on time with the screen off, survive a restart or an app update mid-rest, and beep or buzz when a rest or an interval ends. The phone is kept awake only while a cardio session runs. All of it runs on your phone. |
| Internet | Only the features in section 3: AI reading, barcode lookup, product entries, ideas, and the plan builder. Logging works offline. |
| Health Connect (weight, body fat, steps, heart rate, exercise, distance, nutrition, hydration) | Only if you connect it, as described in section 4. |
When you say a meal instead of typing it, AddPlate hands the request to Android's speech recognition (usually Google's), which handles the audio and returns text. AddPlate itself has no microphone permission and never receives audio.
7. What we don't collect
- No account, email or phone number in the app, and no login. The name you give, if you give one, stays on your phone.
- No location, except GPS during an outdoor cardio session you start (section 6), which stays on your phone.
- No contacts, and no access to your photo library or files. If you pick a food photo, a progress photo or a backup file, Android's own picker gives the app only that one item.
- No advertising ID, ads or tracking SDKs, and no analytics of our own.
- No payment details. If Premium is added, payments will go through Google Play, and we will never see your card.
8. This website and the waitlist
This website sets no cookies and runs no analytics, tracking pixels or third-party scripts. Its fonts and images are served from our own server, so a visit doesn't send your IP address to Google or anyone else.
The early-access waitlist
If you enter your email address, we store the address, the date, which form you used, and the wording you agreed to. We use it only to email you about AddPlate early access. We don't share it, sell it, or add it to other lists. Every email will tell you how to unsubscribe, and you can ask to be removed at any time by writing to brmbota14@gmail.com.
Hosting logs
Our hosting provider records standard request data, such as IP address, time, the page requested and browser type, for security and troubleshooting. These logs are kept for a short period under the provider's retention rules and are not used for anything else.
9. Why we may use it (legal bases)
| What | Legal basis |
|---|---|
| Reading a photo, description or plan answers you send; barcode lookups; product entries and ideas you submit | To provide the feature you asked for (GDPR Art. 6(1)(b)) |
| Health Connect reads and writes | Your consent, given and withdrawn through Android's permission settings (GDPR Art. 6(1)(a) and 9(2)(a)) |
| Heart rate from a Garmin watch | Your consent, given by installing the watch app and withdrawn by turning it off in AddPlate or removing it from the watch (GDPR Art. 6(1)(a) and 9(2)(a)) |
| Waitlist emails | Your consent, which you can withdraw at any time (GDPR Art. 6(1)(a)) |
| Install ID counters, the IP hash and hosting logs | Our legitimate interest in keeping the service available, secure and within its costs (GDPR Art. 6(1)(f)) |
Where another data protection law applies to you, we rely on the equivalent grounds it provides. Withdrawing consent doesn't affect anything done before you withdrew it.
10. Who else is involved
- Railway Corporation (United States) hosts our server, its database and this website.
- Anthropic, PBC (United States) reads food photos, meal descriptions and plan answers and returns the result. Under Anthropic's commercial terms, data sent through its API is not used to train its models.
- Open Food Facts (France) receives barcode numbers from our server, never from your phone, to look up products.
- Google provides Health Connect and ML Kit, which run on your phone. ML Kit, used for barcode and label scanning, may send Google anonymous diagnostics about the scanner itself, such as performance and errors (see ML Kit's terms). Emails you send us are handled by Gmail.
- Garmin provides the Connect IQ store, Garmin Connect and the watch. Heart rate and session details pass between your watch and the app on your phone through Garmin Connect, as described in section 5.
We share nothing with anyone else, except where the law requires it.
11. International transfers
Railway and Anthropic are based in the United States, so data handled by them may be processed there. Where that happens, it is protected by the safeguards these providers offer for transfers under the GDPR and other data protection laws that apply, such as standard contractual clauses.
12. How long we keep it
| Data | Kept for |
|---|---|
| Your log on your phone | Until you delete it or uninstall the app |
| Photos, descriptions and plan answers | Not stored by us. Held only while the request runs. |
| AI scan counts per install ID | 13 months, deleted automatically |
| AI usage counters per install ID | 90 days, deleted automatically |
| Daily limit counters, including the IP hash | 30 days, deleted automatically |
| Products you added | While useful to other users, or until you ask us to remove them |
| Ideas and votes | Until you withdraw them in the app, or the ideas board closes |
| Waitlist email | Until early access opens and the invite is sent, then deleted within 30 days. Sooner if you ask. |
| Hosting logs | A short period under the hosting provider's retention rules |
13. Your rights
You can ask us to give you access to your personal data, correct it, delete it, restrict or object to its use, or give it to you in a portable format, and you can withdraw consent at any time. Write to brmbota14@gmail.com. We answer within one month.
Because there are no accounts, we can't look you up by name. Server records are tied only to the random install ID. To find or delete them, tell us what you submitted, such as the product you added or the idea you posted, or simply uninstall the app: the install ID is deleted from your phone, and the remaining counters expire on the schedule above. Everything you logged is on your phone, under your control.
You also have the right to complain to the data protection authority where you live, where you work, or where you believe your rights were infringed.
14. Children
AddPlate is not directed at children under 16, and we don't knowingly collect personal data from them. If you believe a child has sent us personal data, write to us and we will delete it.
15. Security
All traffic between the app, this website and our server is encrypted (HTTPS). The keys to the AI provider live only on our server, never in the app. We keep as little as possible on the server in the first place, and access to it is limited to the developer.
16. Changes
If this policy changes, the date at the top changes with it. Anything that affects what leaves your phone will also be announced in the app before it takes effect.
17. Contact
CodeInnovate · brmbota14@gmail.com