PRIVACY

What we store, and who can reach it.

Apple Health (HealthKit)

XR Fit can read from and write to Apple Health on your iPhone and Apple Watch, with your permission. You grant or revoke each category yourself in the Health app, and XR Fit cannot read anything you have not allowed.

What we read: workouts, heart rate, resting heart rate, active energy, steps, walking/running distance, cycling distance, running speed, VO2 max, cycling FTP, body mass, body fat percentage, lean body mass, height, and sleep analysis.

What we write back: workouts you complete in XR Fit, along with their active energy and their walking/running, cycling or swimming distance.

Where it goes. Health data does not stay only on your phone. A completed workout — including the heart rate and calorie figures read from Apple Health — is stored on your XR account on our servers so it is available on your other devices and on the web. If you connect Strava and push a workout to it, those same heart-rate and calorie figures are sent to Strava through our servers.

What we do not do with it. XR Fit contains no advertising or tracking software, and your Health data is not used for advertising.

Signing in with Google or Apple. If you sign in with Google, Google's sign-in software sends sign-in information to Google, which can include your name, email address, an account identifier and basic device and usage information; Google handles that under its own privacy policy. Apple handles Sign in with Apple under Apple's own privacy policy.

XR Health and Apple Health. XR Health reads sleep and exercise time from Apple Health only when you choose Fill from Apple Health, and never writes to Apple Health. The values are saved in that day's check-in. Check-ins stay on the phone unless your account has XR Health sync, which is not yet open to the public; for an account that has it, check-ins, including these values, are stored on our servers. For an account that has XR Health sync, you can also view and change your doses, check-ins, inventory, protocols and stacks on the XR website. Changes made there are stored on our servers in the same way.

Camera and photos

XR Fit can read a workout written on paper, a whiteboard or a screen from a photo of it, and can work out what equipment a gym has from photos of the gym. You can take the photo with the camera or choose one you already have; scanning a gym uses photos you choose.

What we read: only the photos you hand over for that one job. Choosing an existing picture goes through Apple's own picker, which runs outside XR Fit and returns just what you selected, so the rest of your library is not visible to the app.

What we do with it. The photo is analysed by an AI model, which reads the written workout into an editable plan you review before anything is saved, or lists the equipment it can see so a session can be built around it. That analysis does not run on your phone.

Where it goes. The photo is sent to our servers inside the request and forwarded from there to the AI provider that performs the analysis — a company outside XR. We do not keep the image: it is not written to our file storage and it is not saved with your workout. What we record is that a request was made, and for which feature.

Motion (Apple Watch)

The XR Fit app on Apple Watch reads how the watch is moving in order to count your reps. The iPhone app does not read motion at all.

What we read: the watch's acceleration and orientation, sampled about fifty times a second while a set is running, and only while a set is running. XR Fit does not read your step count and does not use your watch's all-day activity data.

What we do with it. The watch turns that movement into your rep count and how fast the bar moved — a speed for each rep and an average for the set. The calculation happens on the watch as you lift.

Where it goes. The movement samples themselves are used to count the reps and then discarded; they are never stored. The results are kept: your reps, the per-rep speeds and the average bar speed are sent to your iPhone, saved with that set, and stored on your XR account on our servers along with the rest of the workout.

iCloud (your own Apple account)

XR Fit on iPhone keeps its training database in iCloud as well as on the device. That means a second copy of your training data sits in your own Apple account, separate from the copy on your XR account on our servers.

What syncs: the app's training database — your workouts and every set in them. That includes the heart-rate and calorie figures read from Apple Health and saved with a completed workout, and it includes the pain rating and the pain note you type against a set.

What it is for. The copy keeps your training history in step across the Apple devices signed in to your Apple account.

Where it goes. Into the private area iCloud gives an app for one person's own data, under your Apple account. It is held by Apple under your account rather than by us, we cannot read it, and it is covered by Apple's terms for iCloud rather than by this page.

AI coaching

When you use coaching, photo import or gym-equipment scanning in XR Fit, what you send goes to our server, and our server calls Anthropic using a key we own. Your device does not talk to Anthropic directly. We record that a call happened: which app, which feature, which AI provider and model, how many tokens, whether it succeeded, and a short error code if it did not. We keep it so we can see cost and reliability. That record contains no text you wrote. It is tied to your account, and no other account can read it.

And for coaching features that search our training library, we also store the question you asked, in full, linked to your account. We keep it to improve how well the library answers. It is not readable by you or by any other account — only our servers reach it. It is deleted automatically once it is 90 days old (see How long we keep it).

XR Fuel sends its AI requests to our servers too. When you chat with the Fuel coach, describe a meal out loud or send a meal photo, what you send goes to our coach service, and our server calls Anthropic using a key we own. As in XR Fit, your device does not talk to Anthropic directly. The XR Fuel section below says what Fuel stores and what it sends.

XR Kitchen does not use AI.

XR Health does not use AI at all. Its coaching engine declares no network endpoints and needs no API key, and there is no network call anywhere in that feature. Nothing you enter in XR Health is sent to an AI provider.

We have not independently confirmed what Anthropic or Voyage AI retain of what they receive, or for how long.

Who else touches your data. For these features, the AI companies involved are:

Errors and logs. Our server keeps three kinds of record when something happens, and they hold different things:

We want to be exact about that last point’s limit. The filter works by label, not by content. It cannot recognise personal information inside free text. An error message raised by an underlying system is recorded as it arrives, so if such a message ever quoted something you entered, the filter would not remove it.

XR Fuel

XR Fuel is the food and macro tracker. This is what Fuel stores, and what it sends where.

What we store on your XR account: your food log, your saved meals, your macro targets, and the body measurements you type in. These are held on our servers, under the same per-athlete isolation as the rest of your records.

What we read from Apple Health: your weight and your body composition, read on your phone for a chart on your phone only. Those readings are not sent to our servers.

What goes to our coach service. Your chat messages, the text of a meal you describe out loud, and the meal photos you send go to our coach service so the coach can answer you, and our server calls Anthropic with them using a key we own. Workout summaries that Fuel brings in from XR Fit through the sync can go with them, as part of what the coach is told about your training. When you describe a meal out loud, speech may be processed by Apple. We have not independently confirmed what Anthropic retains of what it receives, or for how long.

Looking up a food (Open Food Facts). When you search for a food by name or scan a barcode, the words you type or the barcode number are sent to Open Food Facts, a public food database, to find the food. We send no account information with it — no account identifier and no sign-in token.

Errors and logs. When our servers hit a problem handling Fuel, in the sync or in the coach, a technical error report is recorded. These are the operational records described under AI coaching above.

What we do not do with it. None of your Fuel data is used for advertising or tracking.

Saved races (the Fuel Calculator)

Shared race details stay in your browser until you press Save this race or Save updates. Private fuel-plan saving is a separate account feature described below. When the page opens it reads the public list of saved races from our server, so you can pick one; that request carries nothing you typed. This is what the Save button does.

What a saved race holds: the race itself — its name, the organization putting it on, the year, and the legs with their distances, ascent, access points and any meal or sleep stop, plus expected temperature, humidity and elevation. Nothing about you: not your body weight, not your paces, not your adjustments, not your plan, and no account or device identifier. There is no field for any of it.

Anyone can add a race, so every saved race is community-entered. Every saved race is shown as community-entered and not verified by XR, and keeps that label for good — before and after anyone here reads it. Reading a race means a person looked at it, not that we measured its legs, so the label never comes off. We do not check a race before it appears. Anyone can save edits to its legs, expected conditions and length class using the same share link; identity and visibility remain controlled separately.

What reading a race does change: the organization's name. Until someone here has read a saved race, the organization putting it on is hidden from everyone — that field is where a person's name would end up, so nobody sees it until a human has. Once we have read the race, that name becomes public. That is the only thing reading a race changes.

What we keep about the person who saved it: nothing. We store no IP address, no hashed IP, no account identifier and no device identifier against a saved race. To stop one person flooding the catalog we count recent saves in memory for a few minutes and then forget them; nothing about that count is written down.

What our hosting platform may keep. Our hosting platform may record ordinary request metadata, including your IP address, in its own access logs under its own retention — as it does for every request to any site. That is outside what we store and outside our control. Our own logs for the catalog keep counts and statuses only.

The captcha (Cloudflare Turnstile). When you press Save this race, we load Cloudflare Turnstile to check that you are a person. It is loaded at that moment and not before, and it looks at signals from your browser to make that check. Nothing you enter here is sent anywhere through shared race saving, and Turnstile is not loaded, until you press the button — the page reads the public race list when it opens, and that request carries nothing you typed.

Opening a shared race link. A link to a saved race carries that race's public identifier. Opening it makes one request to our server with that identifier and nothing else, so the page can show the race as it stands now — including whether it has been verified, corrected or withdrawn.

Sharing a course and planned water. Share this race copies a view-only URL. A saved-race link includes the public race identifier; an unsaved-race link includes the race name, year, distance unit and legs instead. Both can include paces and selected plain-water amounts with a course fingerprint. Foods, organizer, weight, target adjustments and planning conditions are excluded. Anyone with the link can read its contents. Browsers do not send its fragment in normal page requests, but the URL can remain in browser history, a clipboard or messages. Opening a typed-course link does not request a catalog race; the page still loads its normal assets and services.

Private calculator fuel plans

You can plan without an account. Signing in with Apple or Google happens in this same tab and brings you straight back to the calculator you were on, and the page then checks automatically whether you are signed in. Pressing Save fuel plan stores the race snapshot, selected food labels, quantities and leg/packing assignments privately under your account.

These private saves exclude weight, speeds, personal notes, food source URLs and the rest of your food library. They are separate from the public race catalog and do not publish your food choices. Other accounts cannot read or change them. Later public race or food-library edits do not change a saved copy. Deleting your account removes these saved plans.

If you sign in from the calculator, your unsaved plan, including your weight if you entered it, is kept in this browser tab only for up to 15 minutes so it is still there when you return; it is never sent to us and is deleted when restored or when the tab closes.

What we store

The training, nutrition, meal-planning and lab data you enter. A profile you build up — your goals, training background, injuries you tell us about, and performance times for your sports. Your email address and an identifier from whichever sign-in provider you used. If you connect Strava, we store the connection and a record of which of your workouts we uploaded there.

Two of the things you enter are about pain and injury, and are named here rather than left inside that general description: when you log a set you can record how much pain you felt, as a rating from 0 to 10, and a note about it in your own words; and your athlete profile holds a free-text description of injuries, niggles or movement restrictions that you write yourself. All of it is kept on your XR account, on our servers, not only on the phone or browser you entered it from. The pain rating and the pain note also sit in the iCloud copy of the training database described above; the profile description does not.

We do not buy data about you, and we do not combine your records with data from other sources.

Sign in with Apple and Google

Sign-in runs through Apple or Google. We receive a token confirming who you are; we never see your password.

Those are the only two ways in. An email-and-password method existed on our authentication service until 2026-09-22 and was never used by any account; it is now switched off.

Who can reach your records

You. Isolation is enforced at the database itself, not by application code: every table carries a row-level rule tying each record to the account that owns it, so a query for another athlete's data returns nothing even if a bug asks for it. This is structural, not a policy promise.

Xtreme Race staff can reach the underlying database for support and operations.

XR Health lab data specifically

Lab markers and adherence records entered into XR Health are treated as the most sensitive data in the system. XR Health does not provide medical advice, does not recommend protocols and does not surface doses.

Supplement label photos (XR Health)

Supplement label photos. If you save a photo of a supplement's nutrition label against its barcode, that photo is shown to every XR Health user who scans the same barcode. Your name and account are never shown with it. Before a photo is stored we remove its location and other hidden information, and an automated check by Anthropic, an AI service, confirms it shows a nutrition label and no people; only the photo is sent for that check, never your account or the barcode, and a photo that fails is not stored. A newer photo replaces the current one; we keep the one before it so a bad photo can be rolled back. Please photograph the label only and leave out people and anything personal. Any user can report a photo, and we review reports and remove photos that are wrong, offensive or show a person or personal information. We keep a private record of which account saved or reported a photo for 90 days, only to handle abuse and limits; it is never shown to other users. A photo you saved stays after you delete your account unless you ask us to remove it, using the contact details on this page or the report button.

Looking up a supplement (XR Health)

When you look up a supplement in XR Health, the supplement name you type is sent to the U.S. National Institutes of Health's public Dietary Supplement Label Database (DSLD) to find its label. We send no account information with it — no account identifier and no sign-in token — and the service can see your device's network address. We do not control how long it keeps requests, and we have not measured it.

Fuel Calculator

The Fuel Calculator keeps your food library in your browser on this device. When shared catalog access is enabled, typing two or more characters in a new item's name or brand sends that product query to search approved foods. Saving a new custom item, or pressing Submit to shared database for an existing custom item, sends only that item's product name, brand, serving, nutrition and category with a fresh Cloudflare Turnstile verification token for review. Pending items are not public; only approved items appear in shared search. Your complete local food library, personal notes and race details are not included in these submissions.

How long we keep it

We keep your data for as long as your account exists. One exception is in place: a nightly job deletes the questions you ask the coaching library once they are 90 days old. Nothing else is deleted or expires automatically today.

Children

The apps are not intended for children, and we do not knowingly collect data from them. We will state a specific minimum age here once our legal review of it is complete.

Contact

support@xr-gear.com for access, correction, export, deletion, or a complaint.

Changes

We will update this page when the product changes, and date it. This version: 31 October 2026.