Privacy Policy

Bodymap — training log

The short version

• You need an account to use Bodymap. It holds your email address and a copy of your training log, readable only by you, so a new phone picks up where the old one left off.
• There is no analytics or advertising code in this app. No Firebase, no ad SDK, no third-party tracker, no profiling, and nothing that follows you across other apps or websites.
• We never sell or share your data for advertising. There is no mechanism in the app to do so.
• Your training log is backed up to your account. On the free plan that happens once a day and when you sign out; with Bodymap Pro every change is synced as you make it.
• Workouts from other apps are opt-in and read-only. If you connect Health Connect, Bodymap reads the workouts apps like Strava and Garmin Connect saved there — type, time, distance and steps — and nothing else. It never writes to Health Connect. See §6.
• Food tracking is off until you turn it on. If you do, your food diary and calorie target are kept the way your training log is — readable only by you. The one thing anyone else sees is a food you choose to add to the shared food database, which every user can find, without your name. See §7.
• You can take everything with you at any time. Profile → Export produces a spreadsheet of every set and a full backup file — including anything the free tier does not display.

Contents

1. Who we are
2. What Bodymap stores
3. On your phone
4. Your account
5. Exercises you create
6. Workouts from other apps (Health Connect)
7. Food tracking and the shared food database
8. Subscriptions and payments
9. Who else is involved
10. Why we process it
11. Your rights and controls
12. Deleting your data
13. Retention and security
14. Children
15. Changes and contact

1. Who we are

Bodymap is a training log for phones. It records the sets you lift, shows which muscles you have covered in the last seven days, and tells you what you left out.

The controller of any personal data described here is Thomas Harris, Thailand. Reach us at thomasharris0147@gmail.com.

This policy covers the Bodymap mobile app. It does not cover the app stores you download it from, which have their own policies.

2. What Bodymap stores

This table is the whole inventory of what Bodymap holds, where it is kept, and who can see it.

What Bodymap does not collect at all: your location or routes, contacts, photos, microphone recordings, camera images, device advertising identifiers, your height, your full date of birth, your gender identity, your heart rate, or anything from Apple Health. The camera is used for one thing — reading a food barcode when you tap Scan — and the scanner runs on the phone: no image is kept or sent, only the digits of the barcode. From Google Health Connect it reads only the three kinds of workout data described in §6, and only if you connect it.

The Android permissions the app requests are: internet access; billing; the camera, only when you tap Scan to read a food barcode; saving an image to your photo library (Android 9 and below only, when you save a share card); and, only if you choose to connect Health Connect, reading exercise sessions, distance and steps.

Training, bodyweight and food records say something about your health. We treat them as sensitive: the copy in your account is readable only by you, is used for nothing except giving your log back to you, and is never shared, sold or analysed.

Sex and year of birth

Both are optional. Setup offers them on one screen with a Skip both button, and Profile → About you can change or clear either at any time. Left blank, the app behaves exactly as it did before the fields existed.

They feed four things and nothing else.

The first is the Schofield equation, used by the WHO and FAO, which estimates how many calories your body spends at rest. Every training calorie figure in Bodymap is reported net of that resting figure, so getting it closer to right makes training numbers slightly more honest — a few kcal on a session. If you keep a food diary, the same figure is the starting point of each day's burn and of any calorie target the app suggests (§7).

The second is which published strength standard your ranks are compared to, since those standards differ by sex. That comparison is a choice of peer group rather than a fact about you, so it is a separate setting you can change at any time in Profile → About you without touching the sex field — and leaving it alone simply uses the midpoint of the two.

The third applies only to food tracking: a weight-loss target is offered to adults only, so setting one needs a year of birth that says you are 18 or over.

The fourth is which figure the body map draws. Choosing female draws a female figure; anything else draws the original one. It changes the drawing and nothing else — the muscles, the targets and every number are the same — and a workout card you choose to share shows the figure you see in the app.

Three deliberate limits on what we ask:

• Sex, not gender identity. The equation's coefficients track lean-mass distribution, which is a fact about bodies rather than about identity. A gender field would be the more sensitive question to hold and the app would have no use for the answer. The one thing that changes with this field beyond the numbers is the body map's figure. "Prefer not to say" is a real option and simply averages the two curves.
• Year of birth, not date of birth. The equation works in broad age bands, so the year is all it needs. A full birth date is a much stronger identifier and would buy nothing.
• No height at all. The equations that use a height term move a session figure by well under one percent, which does not justify asking.

3. On your phone

The app works from a copy of your log on your phone, so it runs offline and nothing waits on a connection.

That copy is written to your phone's own app storage, under keys such as vessel.state.v1 — the internal prefix keeps the project's original name, because renaming a storage key would orphan an installed app from its own log. It is included in whatever device backup you have configured with Google or Apple, so that reinstalling Bodymap or setting up a new phone can bring your training back; that backup is your own, held in your Google or Apple account under their policies rather than this one, and we cannot read it. On Android the app asks for only the one file its log lives in to be included — not the caches its payment provider keeps.

Uninstalling Bodymap deletes everything it wrote to the phone; the copy in your account stays until you delete the account (§12). Whether a copy remains in your own device backup afterwards is a matter for Google's or Apple's settings, and you can turn that backup off there. Nothing here is a substitute for Profile → Export, which is the copy you hold yourself.

4. Your account

You need an account to use Bodymap. Creating one stores your email address, and a display name and picture if you provide them or sign in with Google. That is the whole profile.

If you used Bodymap before accounts were required, the log already on your phone becomes your account's the first time you sign in.

Free accounts are backed up

On the free plan, your training log is copied to your account as a single encrypted-in-transit document once a day, and again when you sign out. It is put back when you sign in on a phone that has no log of its own — a new phone, or the same one after signing out. A phone that already has a log keeps it.

Pro accounts sync

With Bodymap Pro, every change is mirrored to your account so your other devices can read it. Your device copy stays the source of truth while the app is running; uploads are batched rather than sent on every tap.

If you sign in with Pro on a phone that already has training on it and your account also has a log, Bodymap asks which one to keep rather than silently discarding either.

Signing out

Signing out saves your log to your account first, then removes the copy on that device, so the next person to sign in on it starts from their own account.

5. Exercises you create

Bodymap ships with a library of exercises, and you can add your own — a movement the library does not cover, or a variation you prefer.

Exercises you create are private to you. They are part of your training log, so they are stored on your device and backed up to your account with the rest of it (§4) — but they are not published, and not visible to anyone else. There is no way in the app to share one with another user.

More broadly: nothing you write in Bodymap is shown to another user, with one exception you choose. Not your exercise names, not your notes, not your sets, not your food diary. The exception is a food you add to the shared food database (§7): that food — its name, brand, barcode and figures — can be found by everyone, without your name on it. Apart from that, the only content that travels between users is the built-in exercise library and the food reference data, which we maintain.

When you create an exercise, the app may look for a matching illustration in an open exercise database — see §9 for exactly what that sends.

6. Workouts from other apps (Health Connect)

Bodymap can bring in workouts you record in other apps — Strava, Garmin Connect, Runkeeper, MapMyRun and any other app that saves workouts to Google's Health Connect on your phone. This is off until you switch it on in Settings → Connected apps, and it only works on the phone you switch it on for.

What it reads. With your permission, Bodymap reads three kinds of data from Health Connect:

• Exercise sessions — the type of workout (a run, a ride, a swim), when it started and finished, and which app recorded it.
• Distance — how far the workout covered, as measured by the app that recorded it.
• Steps — steps taken during the workout.

It reads workouts from the period you choose when connecting (from that day, or up to 30 days before) and from then on. It does not read routes or location, heart rate, calories, sleep, or any other health data, and it never writes anything to Health Connect.

How it is used. Each workout becomes a cardio entry in your training log, on the day it happened, so it counts toward your burn, your history and your weekly picture exactly like one you typed in. Strength sessions and workout types Bodymap has no activity for are left out. That is the only use: the data is not used for advertising, is not sold, is not shared with anyone, and is not used to train any model.

Where it is stored. Imported workouts are part of your training log, so they are stored the same way — on your device, and backed up to your account (§4). Health Connect data is never sent anywhere else.

Your control. You can remove any imported workout from your log, and it will not be imported again. Disconnect in Settings → Connected apps stops importing and gives back Bodymap's Health Connect access; you can also change or revoke access at any time in Health Connect's own settings. Disconnecting does not delete workouts already imported — delete those individually, or use Clear all data.

Bodymap's use of information received from Health Connect adheres to the Health Connect Permissions policy, including its Limited Use requirements.

7. Food tracking and the shared food database

Bodymap can keep a food diary: what you eat, by meal, against a daily calorie target if you set one, and — on Today — against what you burned. It is off until you turn it on on the Food tab, after a screen that says what it keeps. Turning it on is your consent, and nothing about your food is stored before you give it.

What it keeps. Each food you log — its name and brand, the day and meal, how much, and its calories, protein, carbohydrate and fat, copied in at the moment you log it. Your calorie target if you set one, the weekly pace it was worked out for, how active your day is apart from training, any foods you have hidden from your searches, and the day you turned food tracking on. All of it is part of your log, stored on your device and in your account like the rest (§4) — backed up daily on the free plan and synced as you go with Pro — readable only by you, and never shared, sold, used for advertising or used to train any model.

What you eat, held against your weight, is information about your health. Data protection law treats it as a special category — and Thai law as sensitive data — and we process it only on your explicit consent, which you give by turning food tracking on and can withdraw at any time by turning it off.

Searching. What you type into the food search is sent to Bodymap's food database (hosted by Supabase, §9) to find matching foods. It is not stored against your account.

Barcodes. When you tap Scan, the camera opens in a scanner that runs entirely on your phone. No image is kept or sent; only the digits of the barcode are used. Those digits are looked up in Bodymap's own database first and, if it does not have the product, on Open Food Facts, which receives the barcode number and your IP address and nothing else (§9).

The shared food database. If a food is missing, any user — free or Pro — can add it, after agreeing to the database's rules and the terms of use. A food you add — its name, brand, barcode, serving and figures — can then be found by everyone who uses Bodymap. Your name and email address are never shown with it. We do store which account added it, which only we can see, so that we can deal with misuse: remove what someone has added, or stop an account adding more. We may correct or remove any food, and we check what is added after it appears.

Foods you add stay if you delete your account, because other people's diaries were logged from them. The link to your account is removed when the account is deleted (§12), and nothing left in the database identifies you.

Reports. You can report any food someone added — wrong figures, something offensive, a duplicate — with an optional note. The report is stored with your account so that one person cannot report the same food over and over; only we can read it, and if you delete your account the report stays without the link to you.

Turning it off. Settings → Food → Turn off food tracking stops it, removes the target, and asks whether to delete your food log as well — the two are separate choices. Foods you added to the shared database are not affected.

8. Subscriptions and payments

We never see your card details. Payment is handled entirely by the app store you bought through — Google Play or Apple — who act as merchant of record. No payment information reaches Bodymap or its servers.

Subscription state is managed for us by RevenueCat, which records a purchase identifier, which plan you bought, whether it renews, and when the current period ends. We store the same facts against your account so the app knows to unlock Pro features. Buying before you create an account is supported; the purchase is attached to your account when you sign in.

Cancelling or letting a subscription lapse never deletes anything. You keep every session you logged, on the device and in your account; it simply stops syncing.

9. Who else is involved

Five services, and each one is here for a specific job.

• Supabase — hosts the account system and the database. Data is held in ap-southeast-1. Database rules restrict every row of your log to the account that owns it. The shared food database (§7) is readable by every signed-in user; a food in it can be added by any signed-in user but changed or removed only by us.
• RevenueCat — subscription management, as described in §8.
• Google — Play Billing for purchases; Google Sign-In, but only if you choose it; and Google Fonts, which the app contacts on first launch to download the typeface it is drawn in. That font request reveals your IP address to Google, and happens whether or not you have an account.
• wger.de — an open exercise database. When you create your own exercise, the app may send that exercise's name to wger to look for a matching illustration. Nothing else is sent: not your account, not your log, not the sets you did.
• Open Food Facts — an open, non-profit database of packaged food. When you scan a barcode Bodymap's own database does not know, the app sends that barcode number to Open Food Facts to look the product up, with a header identifying the app. Nothing else is sent: not your account, not your log. Open Food Facts sees your IP address, as any website does, under its own privacy policy.

Bodymap's food database also contains reference data published by the US Department of Agriculture (FoodData Central). That is a copy we hold; nothing is ever sent to the USDA.

There is no analytics provider, no crash reporter, no advertising network and no data broker in this list, because the app contains none. The barcode scanner is open-source code (ZXing) that runs on the phone and contacts no one.

10. Why we process it

For anyone covered by UK or EU data protection law, our lawful bases are:

• Performing our contract with you — running your account, backing up and syncing your log, unlocking what you paid for, and publishing a food you choose to add to the shared database under the terms of use.
• Your consent — reading workouts from Health Connect, which is off until you switch it on. You can withdraw it by disconnecting (§6), and ending the account altogether by deleting it (§12).
• Your explicit consent — keeping a food diary, which is information about your health and off until you turn it on (§7). You can withdraw it by turning food tracking off, with or without deleting what it holds.
• Our legitimate interests — keeping the service secure and working, moderating the shared food database, and defending against abuse, balanced against your interest in not being over-collected from. This is why there is no analytics.
• Legal obligation — retaining what tax and consumer law requires us to retain about a purchase.

11. Your rights and controls

Depending on where you live you may have the right to access, correct, delete, restrict or object to our use of your data, to receive a portable copy, and not to be discriminated against for exercising any of them. We do not sell personal information or share it for cross-context behavioural advertising, as those terms are used in California law.

Built into the app

• Export — Profile → Export produces a CSV of every set you have logged, a CSV of your food diary if you keep one, and a complete JSON backup. It always covers your entire history, including sessions older than the ninety days the free tier displays. No request needed.
• Correct — every session, set, weigh-in and food entry can be edited or removed in the app, including back-dated ones. Sex and year of birth can be changed or cleared in Profile → About you.
• Food tracking — Settings → Food → Turn off food tracking stops it, and offers to delete the food log (§7).
• Clear all data — Profile → Clear all data erases the log on the device and the copy in your account, leaving the account itself in place.
• Delete account — Profile → Delete account removes the account, your email address and everything logged, immediately. See §12.
• Sign out — saves your log to your account and removes it from the phone (§4). Cancelling Pro stops live sync; the daily backup carries on.

By request

For anything else — a copy of your account record, or deletion if you can no longer reach the app — write to thomasharris0147@gmail.com. We will respond within 30 days. You can also complain to your local data protection authority; in the UK that is the Information Commissioner's Office.

12. Deleting your data

In the app. Profile → Delete account removes the account, your email address, your profile and everything you have logged — on the device and on the server. It is immediate: there is no grace period and nothing is recoverable, which is why the app offers you the export first. Workouts in Health Connect belong to the apps that recorded them and are not affected — Bodymap only ever read them.

Without the app. If you have changed phone or uninstalled it, email thomasharris0147@gmail.com from the address on the account. We will confirm and complete it within 30 days. Full instructions are at Delete your account.

Deleting your account does not cancel a Bodymap Pro subscription. Billing runs through Google Play, which knows nothing about your Bodymap account — cancel it in the Play Store first, or you will keep being charged.

Two things survive deletion, and we would rather say so plainly. Records of a purchase are kept as long as tax law requires, typically six to seven years. And foods you added to the shared food database stay in it, as do reports you made about other foods, because other people's diaries depend on the first and moderation on the second (§7). All of these are detached from the deleted account and no longer identify you to us.

13. Retention and security

Data on your device is kept until you remove it or uninstall. Account data is kept while the account exists, and removed within 30 days of deletion apart from the exceptions in §12. Server logs are kept for a short operational period by our hosting provider.

Foods in the shared database are kept until they are corrected or removed in moderation.

Everything sent to our servers travels over TLS. Access is restricted at the database itself: every row of a training log or food diary is readable only by the account that owns it, foods in the shared database can be added but never changed or deleted by an app client, food reports cannot be read by any app client, and subscription records cannot be written by any app client at all — only by the payment provider's verified webhook. Passwords are hashed by the authentication provider and are never visible to us.

No system is perfectly secure, and we would be misleading you to claim otherwise. If a breach affects your data we will notify you and the relevant regulator as the law requires.

If you are outside ap-southeast-1, your data will be transferred there and protected by appropriate safeguards, such as the UK and EU standard contractual clauses.

14. Children

Bodymap is not directed at children and is not intended for anyone under 13, or under 16 where local law sets that age for consent. We do not knowingly collect data from them. If you believe a child has created an account, contact us and we will delete it.

Weight-loss targets in the food diary are offered only to users whose year of birth says they are 18 or over.

15. Changes and contact

If this policy changes materially — a new third party, a new category of data, a new purpose — we will update the date at the top and tell you in the app before the change takes effect. Minor clarifications will just be dated.

Thomas Harris 257/158 Hang Dong Ban Waen Chiang Mai Thailand 50230 thomasharris0147@gmail.com

Bodymap — a training log that reads your week and tells you what you left out.