Privacy Policy · Body Lab

This policy explains how Boulder Creek Body Lab (“Body Lab”, “we”, “us”) handles information when you use bodylab.lol, the Body Lab iPhone app, its API, and its connections to other apps. Questions go to support@bodylab.lol.

What we collect

Your account

Email address, which is how you sign in. There are no passwords: we email you a six-digit code.
Sign-in codes, and the network (IP) address each was requested from, so we can limit how many codes one address or network can request. Codes and those addresses are deleted within a day.
Sessions. Signing in on the web sets one encrypted cookie that keeps you signed in for 30 days. Signing in from an app or device stores a token (hashed, so it can't be read back) and the device's name.
Which version of this policy and the Terms of Service you signed up under, and the latest notice of a change to them you've dismissed.

The beta waitlist

While Body Lab is in beta, entering an email address that doesn't have an account adds it to our waitlist instead of sending a code. We keep the address, when it first and last asked to join and how many times, and the network (IP) address of its latest request, which we delete within a day. We use the address only to email you once when there's a spot for you; we don't send marketing to it. Once you're let in, the entry is kept with your account and deleted when you delete your account. To be taken off the waitlist at any time, email support@bodylab.lol and we'll delete your address.

Your profile

What you enter during setup or in Settings: an optional display name, time zone, preferred units, the sports you do, and — all optional — sex, birth year, height, weight, maximum and resting heart rate, threshold heart rate and functional threshold power (FTP). We use these to turn heart rate and power into training load and zones.

Your training and health data

Activities you type in or upload, including uploaded FIT and GPX files and what they contain: times, durations, distances, GPS routes, heart rate, power and other sensor readings.
Strength sessions: exercises, sets, reps, weights and effort ratings.
Recovery readings: resting heart rate, heart-rate variability, time asleep, sleep score and device energy scores.
Test results: FTP tests, VO2max, threshold heart rate, weigh-ins.
Lab results you choose to enter from a blood test (see Lab results).
Plans you commit to, and what Body Lab derives from all of the above: training load, fitness and fatigue, readiness, power bests, how a session compared with its plan, and recommendations.

Much of this is health information. We treat it as sensitive: it's used to provide Body Lab to you and for nothing else.

Connected services

If you connect a service that records your training or recovery, you sign in to that service to let Body Lab read from it. Any password you enter for it is sent to the service once and is not stored. We keep the sign-in tokens it issues, encrypted, and use them to import your activities (with their recordings), recovery readings and test results. We also keep what the service sent us, as it arrived, so your history can be recalculated without asking the service for it again. Disconnecting stops imports; what was already imported stays in your history until you delete it.

Apple Health

If you connect Apple Health in the iPhone app, Body Lab reads, with your permission: your workouts (type, times, duration, distance, energy, the heart rate recorded during them, and the weather and climb Apple Health notes for them), and, only if you separately allow it, their routes; sleep, heart-rate variability, resting heart rate, VO2max and weight. For heart-rate variability, resting heart rate, VO2max and sleep, it only reads what Apple's own devices measured. Nothing is read until you connect, and you choose which types to allow in iOS; you can turn any of them off at any time in Settings → Health → Data Access & Devices → Body Lab. Body Lab never writes to Apple Health.

Data from Apple Health is used only to provide Body Lab to you, the same as the rest of your training data. It is never used for advertising or marketing, never sold, and never shared with anyone except as described in Who we share it with: our hosting provider, and apps you choose to connect.

Workout routes

A route is where an outdoor workout went. It's precise location data: every location your watch or phone recorded during the workout, each with its time, altitude, speed and direction, and how accurate each of those was. Body Lab reads routes only if you allow it, which it asks for on its own, when you tap “Allow reading workout routes” in the app's Apple Health settings, and never when the app opens. Indoor workouts aren't asked for one.

We use routes to:

show a map and elevation profile of each workout;
work out the altitude you trained at and, from where your workouts start, the altitude of home, so your targets can account for training well above it;
suggest routes you've done before.

We keep each route with its workout, as it was recorded, the same way we keep a file you upload from a GPS device, so your map and altitude can be worked out again as Body Lab improves. We also keep what's worked out from it: a simplified line for the map, the elevation profile, the altitude, and where the workout started. Routes are sent from your phone to our servers encrypted in transit. They aren't written to our logs or included in error reports.

Routes are part of your training data everywhere else in this policy: they're included in your data download, and deleted when you delete the activity or your account. An app you connect to Body Lab, such as an AI assistant, can read whether an activity has a route and, when it suggests routes for today, the areas where your past routes start (a point averaged over the starts in each area, and a place name taken from your activity names) with each route's name, length, climb and when you last did it, but not the line of the route itself. Turning route access off in iOS stops new routes being read; routes already imported stay with their workouts until you delete those activities or your account.

Where you are today

Altitude lowers the power you can hold, so Body Lab can suggest adjusting today's watt targets when you look to be well above or below home. It only uses your location if you allow it:

In the iPhone app, if you allow location access while using the app. Body Lab asks for approximate location only, and asks from Today or Settings, never when the app opens. Once you've allowed it, the app checks your location when you open Today, unless you've already set today's altitude or dismissed today's suggestion. It never reads your location in the background.
On the web, only when you press “Check with my location” and your browser asks you to allow it.

Each time, your location is sent to Body Lab, used to work out an altitude, and then discarded. We don't store it, keep a history of where you've been, or write it to our logs or error reports. To work out the altitude we use, in order: the altitude your device measured, if it reports one accurate enough to use; your own activities that started nearby; and only if neither answers, elevation data for the surrounding area from a public dataset hosted by Amazon Web Services. That request comes from our server, not your device, and doesn't identify you. It names up to four map squares around your location, several kilometres across in most places, rather than your position.

Nothing changes until you confirm. When you do, we keep the altitude, how it was worked out, and the date — not the location — as part of what you told Body Lab about that day. It's included in your data download, and removed with your account. You can take it back from Today, and turn location access off at any time in your phone's or browser's settings.

Lab results

You can record the results of a blood test yourself. It's optional: nothing is collected until you type a result in.

For each result, we keep what you enter from the report: the marker (such as ferritin or LDL cholesterol), its value and unit, the lab's range and any flag the lab printed, and the method or assay if you add them. For each blood draw, we keep its date and, if you give them, the time, the lab's name, and your answers to a few questions about the draw: how long since you last ate, whether you were recently ill, whether you took iron, biotin or creatine beforehand, whether you take hormonal contraception or other hormone medication, where you were in a menstrual cycle, and the altitude you were living at. Each question is asked only when the results you entered depend on it, and you can skip any of them.

We use lab results only to show them back to you over time: each one beside the lab's range and any published guideline limit, with whether a change between two draws is bigger than normal variation. To judge whether two draws can be compared, Body Lab also works out, when you view them, how long before each draw your last recorded workout ended; that isn't stored. Lab results are never used to change your training: nothing that recommends a session reads them. They aren't a diagnosis.

Lab results are part of your health data everywhere else in this policy. They're included in your data download, and deleted when you delete a draw or your account. Values and marker names aren't written to our logs or included in error reports. Apps you connect to Body Lab, such as AI assistants, can read or add lab results only if you tick those permissions when you connect them; they can't change or delete them.

Body composition scans

You can record the results of a body composition scan, such as a DEXA scan, by giving it to an AI assistant you've connected to Body Lab, and read it on the web and in the iPhone app. It's optional: nothing is collected until you add a scan.

For each scan, we keep what's entered from the report: its date and time, where it was done and the scanner model if they're given; your total, fat, lean and bone mass, body fat percentage, visceral fat, and your whole-body bone density with any percentiles the report prints; and the same figures for each region the report measures. Your total mass is also recorded as a weigh-in for that day, alongside weights from anything else you use — it never replaces one you entered yourself.

We use scans only to show them back to you over time, noting when two were done by a different company or on a different machine. Body composition scans are never used to change your training: nothing that recommends a session reads them. They aren't a diagnosis. Bone density from a whole-body scan isn't a diagnostic bone density test, and a percentile is a comparison with other people, not a diagnosis either. Ask a clinician about either.

Scans are part of your health data everywhere else in this policy. They're included in your data download, and deleted when you remove a scan or your account. Values aren't written to our logs or included in error reports. Apps you connect to Body Lab, such as AI assistants, can read or add body composition scans only if you tick those permissions when you connect them; they can't change or delete them. Nothing can edit a scan — to correct one, remove it and record it again.

Connected apps and AI assistants

If you connect an app, such as an AI assistant, to Body Lab, we record which app you approved, what you allowed it to do, and when it was last used. The app receives the Body Lab data it reads on your behalf (see Who we share it with). If you allow an app to add lab results or body composition scans, what it adds is saved and handled exactly like a result you enter yourself.

On your device, and in our logs

A strength session in progress is saved in your browser so a closed tab doesn't lose it.
When you dismiss today's altitude suggestion, that's remembered for the day in your browser or on your phone. The location isn't.
The iPhone app keeps its sign-in in the iOS Keychain, and a record of how far it has synced Apple Health, on your phone. Signing out removes both.
Our servers keep limited technical logs, such as errors, which can include an account identifier or network address.

We don't use analytics or advertising trackers, and we don't set cookies other than the sign-in cookie.

How we use it

To provide Body Lab: calculate training load and recovery, prescribe sessions, and show your history.
To sign you in, keep your account secure, and prevent abuse.
To import from services you connect, and answer apps you connect.
To email you sign-in codes and, rarely, important notices about your account or these policies.
To email you once when there's a spot in the beta, if you joined the waitlist.
To diagnose problems and improve how Body Lab works.

We don't sell your information, use it for advertising, or share it with anyone to use for their own purposes. We don't use it to train AI models.

Only these, and only as needed to run Body Lab:

Our hosting provider runs Body Lab's servers, database, stored files and backups, in the United States.
Our email provider sends sign-in emails and the beta access email, so it processes your email address and each code; a copy of each email stays in our mail account.
Services you connect receive the sign-in you provide and our requests for your data, under their own privacy policies.
Apps you connect, such as AI assistants, receive the Body Lab data they read for you, including data that came from Apple Health, and only after you approve the connection. What they do with it — including whether it's kept, or used by the company behind the app — is governed by that company's terms and privacy policy, not ours. You can disconnect an app at any time in Settings.
Amazon Web Services, which hosts the public elevation data, receives our server's requests for the map squares around a location you asked Body Lab to check, when neither your device nor your own activities gave an altitude (see Where you are today). The requests come from our server and carry nothing that identifies you.
An error-monitoring service receives technical reports when something breaks — an account identifier and what went wrong, never your health data — so we can find and fix it.
When the law requires it, such as a valid legal order, or to protect people from harm.
If Body Lab changes hands, to the new owner, who must honor this policy; we'll tell you first.

How long we keep it

We keep your information for as long as you have an account. You can delete individual activities, readings, test results, lab results and strength sessions whenever you like.

Deleting your account (Settings → Account) removes your profile, activities, readings, lab results, sessions, connected services and connected apps from our database immediately, and deletes your uploaded files. Copies can persist briefly in two places: deleted files remain recoverable in our file storage for 30 days, and nightly database backups are kept for 30 days. After that, they're gone.

Security

Connections to Body Lab are encrypted. Tokens for connected services are encrypted at rest, the tokens that keep devices and connected apps signed in are stored hashed, sign-in codes expire after 10 minutes, and stored files are private. No system is perfectly secure; if we learn of a breach affecting your information, we'll tell you promptly.

Your choices and rights

See and correct your data in the app, and download a copy of it from Settings.
Delete anything, or your whole account, in the app.
Disconnect connected services and apps in Settings.

Depending on where you live (for example, in the European Union, the United Kingdom or California), you may have further rights, such as to object to or restrict processing or to data portability. Email support@bodylab.lol and we'll respond within 30 days. You can also complain to your local data protection authority.

Your information is processed in the United States. If you use Body Lab from elsewhere, you understand it will be transferred there.

Children

Body Lab isn't for anyone under 16. If you believe someone younger has an account, email support@bodylab.lol and we'll delete it.

Changes to this policy

We may update this policy. Each updated version is posted on this page, at bodylab.lol/privacy, with the date it takes effect shown at the top.

If you keep using Body Lab after an updated version takes effect, that version applies to your use of Body Lab from then on.
If a change is material — for example, collecting a new kind of information, sharing it with someone new, or using it for something new — we'll tell you before it takes effect: in the app, and by email where it matters.
Continuing to use Body Lab is never how you agree to us using information we already have in a materially different way from what this policy said when we collected it. If we ever want to do that, we'll ask you first, clearly and separately, and we won't use your existing information that way unless you say yes.

What has changed, newest first:

September 21, 2026 (Privacy Policy): Body composition scans are now called DEXA scans. The Privacy Policy no longer says which screen or which app to find a kind of data in, since that changes as the app does; what we collect and what we do with it is unchanged.
September 20, 2026 (Privacy Policy): Lab results and body composition scans moved out of Settings into a Data section on the web, so the Privacy Policy's directions to them now say Data rather than Settings.
September 19, 2026 (Privacy Policy): The Privacy Policy now covers body composition scans, such as DEXA: what we keep from one, that your total mass is also recorded as a weigh-in, that scans never change your training and aren't a diagnosis, and that apps you connect can read or add them only if you tick those permissions.
September 18, 2026 (Privacy Policy): The Privacy Policy now covers the beta waitlist: what we keep when you join it, that we email you once when there's a spot, and how to be removed.
September 17, 2026 (Privacy Policy): Apps you connect to Body Lab, such as AI assistants, can now read or add your lab results, but only if you tick those permissions when you connect them. They can't change or delete lab results.
September 16, 2026 (Privacy Policy and Terms of Service): The Privacy Policy now covers two features you can choose to turn on: estimating today's altitude from where you are, and reading workout routes from Apple Health. It also covers recording lab results from blood tests (what's kept, that they never change your training, and that they're in your data download and deleted with your account), and credits the elevation data used. Both documents now explain how updates take effect, and that we'll ask before using information we already hold in a materially different way.

Credits

Elevation data: Terrain Tiles on the Registry of Open Data on AWS, from ArcticDEM terrain data (DEM(s) were created from DigitalGlobe, Inc., imagery and funded under National Science Foundation awards 1043681, 1559691, and 1542736); Australia terrain data © Commonwealth of Australia (Geoscience Australia) 2017; Austria terrain data © offene Daten Österreichs – Digitales Geländemodell (DGM) Österreich; Canada terrain data contains information licensed under the Open Government Licence – Canada; Europe terrain data produced using Copernicus data and information funded by the European Union - EU-DEM layers; Global ETOPO1 terrain data U.S. National Oceanic and Atmospheric Administration; Mexico terrain data source: INEGI, Continental relief, 2016; New Zealand terrain data Copyright 2011 Crown copyright (c) Land Information New Zealand and the New Zealand Government (All rights reserved); Norway terrain data © Kartverket; United Kingdom terrain data © Environment Agency copyright and/or database right 2015. All rights reserved; United States 3DEP (formerly NED) and global GMTED2010 and SRTM terrain data courtesy of the U.S. Geological Survey.

Contact

Boulder Creek Body Lab — support@bodylab.lol