Legal · 01
Privacy policy
ITBG Fit is built by one person who hates getting tracked. This policy spells out exactly what data we hold, why we hold it, where it goes, and what you can do about it. No dark patterns, no marketing list, no resale.
01Who we are
ITBG Fit is operated by ITBG LABS PTY LTD, an Australian proprietary limited company based in Perth, Western Australia (in this policy, "we", "us", "our"). We are responsible for the personal information collected through the ITBG Fit web app, the installed (Home Screen) version of it, and the marketing site at itbglabs.fit.
For privacy questions, contact privacy@itbglabs.fit.
02What this policy covers
This policy applies to:
- The marketing website at itbglabs.fit and any related subdomains.
- The ITBG Fit app, including offline use and what it keeps on your device.
- The automated health feeds, reports and insights that run behind the app (section 03).
- Email correspondence you send us about your enquiry, account, or training.
It does not apply to third-party sites or services that ITBG Fit links to. When we receive data from a third party on your instruction (for example Oura, or Apple Health through the Health Auto Export app), their own privacy policy governs how they handle your data on their end.
03Data we collect
Account data
- Your email address, a username and display name, and your unit preferences (kilograms or pounds).
- If you sign in with a password, a password hash held by our authentication provider (we never see the password). If you sign in with Google, the name, email address and basic profile details Google shares with us. If you use an emailed sign-in link, the address it went to.
- Sign-in times, IP address and browser details recorded by our authentication provider for security.
Enquiry data
- What you submit through the access form: name, email, primary use case, interest in a custom programme, and your notes.
- Your browser's user agent and a shortened one-way hash of your IP address, used to spot abuse. We do not store the IP address itself with the enquiry.
- A short entry (name, email and your choices) in our hosting provider's server log when the form is received.
Training data
- Workouts and sets: exercise, weight, reps, set type and side, and, if you log them, reps in reserve, rate of perceived exertion and a whole-session effort rating.
- Programmes, your weekly schedule, custom exercises, notes, cardio and timer sessions, personal records, and weekly volume targets per muscle.
- Your gyms and their equipment: the bar weight, the plates available, and the dumbbell and cable steps. For each gym and exercise, any machine settings you save (seat, pad or pin position, grip and a short note).
- Niggles you log: the body area or joint, the side, a severity from 1 to 3, the movements that aggravate it if you know them, and the dates it started and cleared. There is no free-text field.
Body and health data you enter
- Weight, height, and tape measurements (for example waist, hips, chest, arms, legs, wrists and ankles).
- Body fat scan references you add to calibrate the tape estimate: the date, the method (DEXA or InBody) and the body fat percentage. We do not store the scan report itself.
- Blood pressure readings you enter by hand: systolic, diastolic and, if you add it, pulse, with the time.
- Nutrition you log by hand (energy, protein and other daily totals).
- Daily check-ins, every field optional: how your energy, mood, sleep, soreness, appetite and any nausea or stomach upset felt on a 1 to 5 scale, whether your food diary is complete, whether you were unwell, travelling or drank alcohol, and a note of up to 500 characters.
- Your current phase (a cut, a bulk or maintenance) with its start date, target rate, calorie and protein targets and goal weight, and dated markers you add, such as an illness, travel, or a medication. A medication marker holds the name, dose and dates you type in; if you log injections, each one is a dated marker with the dose in its note. The app records these and shows them back to you. It never suggests a dose or a schedule.
- A schedule of blood tests: test names and due dates.
- Lab results you enter, if you use Labs: for each report, the collection date and time, the lab's name, the specimen and the lab's comments; for each result, the test name, value and unit exactly as printed, with the lab's own reference range and flag. Each report can also carry pre-test context: whether you were fasting, hours since hard training, illness in the week before, a hydration issue, and recent medication or supplement changes. There is no field for a Medicare number, Individual Healthcare Identifier, medical record number or doctor's details, and the form asks you to leave them out. If you upload a pathology PDF, we keep the file with its report, in Sydney, until you delete the report or your account; the results we read from it are unconfirmed until you confirm them.
- Progress photos, if you take them: the photo, the pose (front, side or back), the date, and its size. Photos are stored in a private storage area that only your account can read (section 11), and location and other camera details are removed before the photo is stored (section 05).
Health data from connected sources
Every source is optional. You turn each one on in Settings, Connections, which records your consent for that source; withdrawing it there stops new data from that source being accepted.
- Apple Health, sent from your iPhone by the Health Auto Export app: steps, active energy, exercise minutes, stand hours, VO2 max, heart rate, resting heart rate, heart rate variability, weight, body fat, blood pressure and sleep. This includes data other apps write into Apple Health, such as a Garmin or Withings scale, a Withings blood pressure cuff or sleep mat, iHealth and Whoop.
- Nutrition from Cronometer, through Apple Health: daily energy, protein, carbohydrate, fat, fibre, sodium, caffeine and alcohol totals.
- Apple Watch workouts, through Apple Health: activity type, start and end time, duration, energy, distance, average and maximum heart rate, and heart rate minute by minute.
- Oura, through Oura's own connection once you authorise it: sleep duration and stages, sleep and readiness scores, heart rate variability, resting heart rate, respiratory rate, body temperature deviation, activity scores and steps.
- History imports, if you ask for them: a one-off Apple Health export, which can include past nutrition from apps such as MyFitnessPal, and a one-off export of past workouts.
- Upload keys and records. The keys Health Auto Export uses to send your data (we store only a one-way hash of each key, with its name and dates), and a record of each large upload: when it arrived, its size and whether it was processed.
Data we compute from yours
- Trend weight and rate, estimated energy expenditure, a calibrated body fat estimate, personal baselines (for example your usual heart rate variability), projections with their ranges, weekly volume per muscle, and findings ("insights") about your training, recovery, body and nutrition. Each finding is labelled as an observation, an association, a possible explanation, a suggestion to try, or something worth raising with your GP.
- Which findings you dismiss, and, when you choose "I'll try this" on a suggestion, the dates of the trial and the answer you give when it is reviewed.
- A short daily report, a weekly review and a weekly chart built from the above.
- The status of each feed (when it last ran and whether it worked).
Raw feed archive
- An untouched copy of every delivery from a connected source, kept in private storage so a processing mistake can be fixed and the day replayed.
Consent and privacy records
- Each consent you give or withdraw (to this policy, the terms, health processing and each source): what it was, the version, when, and how (the screen, your browser's user agent and a salted one-way hash of your IP address).
- A log of privacy actions on your account, such as data exports and consent changes.
Device and usage data
- Inside the app, page views counted by Vercel Web Analytics, which does not use cookies and reports in aggregate. The marketing and legal pages run no analytics.
- Request logs kept by our hosting provider (IP address, browser, the address requested and the time), used for debugging and security.
- If you turn on the rest alert (section 07): the push address your browser gives us for each device, and when your current rest ends.
- We do not currently use a crash-reporting service.
04Why we collect it
We only collect personal information that is reasonably necessary to provide ITBG Fit and its related services. Specifically:
- To run your account. Authenticate you, sync your data across devices, and send service emails (sign-in links, password resets, important security notices).
- To deliver the product. Show your training history, calculate volume and progression, round suggested loads to your gym's equipment, flag exercises that load a niggle, run timers, and turn your body and health data into trends, projections, reports and insights.
- To keep it working. Diagnose bugs, monitor that each feed is still arriving, and improve the app based on aggregate usage.
- To respond to enquiries. Process your access request, decide whether to invite you, and reply to your email.
- To show what you agreed to. Keep a record of your consents and privacy actions, so you and we can see them.
- To meet legal obligations. Respond to lawful requests from Australian authorities and to comply with the Australian Privacy Principles (APPs) under the Privacy Act 1988 (Cth).
Reports and insights are worked out by fixed, tested calculations that we wrote. We do not send your data to AI services, we do not use it to train AI models, and we do not sell it. We do not run a mailing list or remarketing pixel.
05Health and sensitive information
Body measurements and photos, heart rate, blood pressure, sleep, nutrition, check-ins, medication and injection markers, illness markers, niggles, lab results and blood test schedules, and training load are health information, which is sensitive information under the Privacy Act 1988 (Cth). We collect it only with your consent: you give it when you accept this policy and turn on health processing, and separately for each connected source. You can withdraw consent in Settings, Connections, delete any entry you made by hand, or delete your account (section 10).
Reports, insights and projections are information to help you train. They are not medical advice, a diagnosis or a treatment plan. Where the app notices that two things tend to move together in your data, it calls that an association, not a cause. Lab results are only ever shown as within or outside the performing lab's own range, and a result outside it says to talk to your GP.
Progress photos. The app re-draws each photo on your device before it is uploaded, which leaves out location (GPS) and other camera details, and our server removes any such details again before storing it. Photos are never public, are shown to you through links that expire after 5 minutes, and the app never saves a copy to your camera roll.
In plain English
You can use ITBG Fit without entering any body or health data, and every connected source is optional. If you do share it, it lives in your account, is encrypted in transit and at rest, and is never shared without your instruction except as this policy describes.
06Service providers and connected sources
ITBG Fit relies on a small set of infrastructure providers. We only share the minimum data needed for the service to work.
| Provider | Purpose | Data involved | Region |
|---|---|---|---|
| Supabase | Database, sign-in, private file storage (progress photos and the raw feed archive), and the function that receives large health uploads | All account, training, body and health data, progress photos, and encrypted Oura access tokens | Sydney, Australia |
| Vercel | Web hosting and the app's server functions: receiving the health feeds, reading Oura, computing reports, insights and the weekly chart, and sending rest alerts. Also domain name service, request logs and Web Analytics in the app | Health data while it is processed (not stored there), requests passing through (IP, browser, address), enquiry log entries, aggregate page views | Server functions in Sydney; global edge network for request routing |
| Our automation server (n8n, self-hosted on a Hostinger virtual server) | Starts the scheduled jobs that run in Sydney and checks they worked. For the founder's own account only, it relays his report messages and weekly chart to his phone. Until 9 October 2026 it also remains as a fallback for the founder's Apple Health feed and holds his Oura connection tokens (section 08) | Job status and counts; the founder's own report text and chart. No other member's health data | Jakarta, Indonesia |
| Health Auto Export (opt-in) | An iPhone app you install, which sends your Apple Health data to ITBG Fit | The Apple Health metrics and workouts you choose to send | From your phone to our servers in Sydney; see the app's own policy |
| Oura (opt-in) | Source of ring data, read with your authorisation | Oura sends us your ring data; we send nothing about you to Oura | Per Oura |
| Apple, Google or your browser's push service (opt-in) | Delivers the rest alert to a locked phone | An empty notification and when it was sent. No training or health content | Per the push service (usually outside Australia) |
| Google (optional) | Sign in with Google | Name, email, basic profile | Per Google |
| Apple iMessage (founder only) | Delivers the founder's daily and weekly reports as text messages, sent from a Mac we operate | Report text and the weekly chart, which include health figures | Apple's network, end-to-end encrypted |
Report messages go only to the founder's own number; members see their reports and insights in the app. If a feed or report fails, our own alerting tool, running on the automation server, notifies us; those alerts describe the failure and can include error details.
This list is current as of the date above. If we add or change a provider, we will update this table and, where the change is material, notify you by email.
08Where data is processed and stored
Your health data is received, processed and stored in Sydney, Australia. The app's server functions run in Vercel's Sydney region, and your account, training, body and health data, progress photos, lab results and any pathology PDFs you upload, the raw feed archive, encrypted Oura access tokens, and computed reports and insights are stored in the Supabase Australia (Sydney) region, as are its backups. Vercel's global edge network may handle request metadata (such as your IP address and the address requested) in other regions.
A transition that ends on 9 October 2026. Before 2 October 2026, the health feeds were received by our automation server, a virtual server in Jakarta, Indonesia. Until 9 October 2026 that older route remains as a fallback for the founder's own Apple Health feed and holds the founder's Oura connection tokens. On 9 October 2026 it is retired and those tokens are deleted. No other member's health data has been sent to it.
What stays overseas after that. The automation server in Indonesia keeps starting the scheduled jobs that run in Sydney; it receives job status and counts, not your health data. For the founder's own account only, it relays his report text and weekly chart to his phone over Apple's iMessage network. Rest alerts pass through Apple's, Google's or your browser maker's push service, which may be overseas, and carry no content.
10Retention and deletion
We keep personal information only for as long as we need it for the purposes set out in this policy.
- Account, training, body and health data. Kept while your account is active. You can delete any entry you made by hand from inside the app; readings from a connected device are shown read-only, and go when you delete your account.
- Deleting your account. Settings, Account, Delete account. In order, it removes: your upload keys and Oura access tokens (so no source can send or fetch anything more), any Oura connection tokens held on the older automation server, your raw feed archive, your progress photos, your uploaded pathology PDFs, and then your account and everything linked to it in the database, including workouts, measurements, check-ins, medication markers, lab results, niggles, insights, consent records and your privacy log. If any step fails, nothing after it runs, your account stays, and you can try again.
- What deletion leaves. Copies in the database provider's automatic backups, until they expire on the provider's backup cycle, within 7 days. Report messages already delivered to the founder's phone. And a deletion record that holds a salted one-way hash of your account id, the date, and how many rows were removed from each table, with no name, email or other personal information, so we can confirm a deletion happened if asked.
- Raw feed archive. Kept for 90 days, then deleted. Within that window a day can be replayed after a processing fix. Anything still held is deleted with your account.
- Enquiries. Kept for 12 months, or sooner on request, then deleted.
- Privacy log. Each entry (for example an export or a consent change) is kept for 12 months, then deleted, or sooner with your account.
- Server logs. Kept by our hosting provider for 1 day under its standard log retention, then discarded.
- Financial records. If you become a paying customer, we retain billing records for 7 years as required by Australian tax law.
11Security
We protect your data using:
- TLS for all data in transit.
- Encryption at rest on the database and storage layers, and a separate layer of encryption on Oura access tokens, whose key is never stored in the database.
- Row-level security policies that restrict your data to your account. Progress photos sit in a private storage area where each member can reach only their own folder, read through links that expire after 5 minutes. The raw feed archive has no member access at all.
- Upload keys stored only as one-way hashes, shown to you once and revocable in Settings, Connections.
- Hashed passwords (we never see them in plaintext).
- Run history switched off on the automation flows that handle tokens or report text.
- Principle of least privilege for any human admin access.
No system is perfectly secure. If a notifiable data breach occurs, we will tell you and the Office of the Australian Information Commissioner (OAIC) as required under the Notifiable Data Breaches scheme.
12Your rights
Under the Privacy Act 1988 (Cth) and the Australian Privacy Principles, you have the right to:
- Access the personal information we hold about you.
- Correct information that is inaccurate, out of date, or incomplete. Entries you made by hand can be edited in the app.
- Export your data at any time from Settings, as a JSON file. It holds every table of your data: your profile, training, gyms and machine settings, body and health data, check-ins, medication and other markers, lab results, niggles, body fat references, insights and your trial answers, consent records and privacy log. Progress photos are included as download links that work for 24 hours; export again for fresh ones. Two things are listed but not inlined: the raw feed archive, which we send on request (email us from your account email and we will send a download link within 30 days), and your upload keys and Oura access tokens, which are credentials rather than information about you.
- Delete your account and the associated personal information, from inside the app (section 10) or by emailing us.
- Withdraw consent for health processing or any connected source in Settings, Connections, and turn off the rest alert in Settings.
- Lodge a complaint with us, and if we cannot resolve it, with the OAIC.
To exercise any of these rights, email privacy@itbglabs.fit. We will respond within 30 days.
13Children
ITBG Fit is not intended for anyone under 16. We do not knowingly collect personal information from children. If you believe a child has created an account, contact us and we will delete it.
14Changes to this policy
We may update this policy from time to time. The date and version at the top of the page tell you when it was last revised. If a change is material (for example a new category of data, a new third-party processor, or a change to your rights) we will notify account holders by email at least 14 days before the change takes effect, and the app will ask you to accept the new version the next time you open it.
15Contact and complaints
ITBG LABS PTY LTD
Perth, Western Australia
Email: privacy@itbglabs.fit
If you are not satisfied with our response, you can lodge a complaint with the Office of the Australian Information Commissioner (OAIC).