Your analyst, not your cheerleader.
Everybody has an awesome body.
This app helps you make yours more awesome.
AwesomeBody connects your training, nutrition, body composition, and wellness — and tells you, every week, exactly what's working and what to change.
Four demo accounts, each with a year of real-looking data.
No signup. Real data. Roll-back after 4 hours.
14 days free. No card up front.
£9.99/mo if you stay.
First AI brief generates after 7 days of logging.
Fourteen tightly integrated modules, each feeding data into the others. No silos. No guesswork.
When you first sign in, a short setup wizard walks you through your profile (date of birth, sex, fitness level), your goals, the supplements you take, and your training split - everything the app needs to give you personalised insights from day one. Takes under two minutes. You can update any of it any time from Settings.
AwesomeBody is actively developed. Here's what landed recently.
Run multiple named training programmes simultaneously. Keep a cutting split, a bulk split, and a deload week all saved side-by-side. Switch between them in seconds — choose whether to restart from Day 1 or continue mid-cycle. Your current split is never overwritten.
AI-generated plans, a curated programme library (PPL, 5/3/1, StrongLifts, and more), and your full history — all in one three-tab modal. Apply any programme from the library with starting weights pre-filled from your logs. Each application creates a new split group, leaving your existing training intact.
A front-and-back body diagram on the Training page lights up as you log sets — primary muscles bright green, secondary muscles dimmer. Updates in real time as you log. Falls back to your most recent session if today is empty.
Every card on the Dashboard, Training, and Insights pages can be collapsed with the ▼ button and dragged into any order. Your layout and collapsed state persist across sessions and devices — you only ever see what matters to you.
A 0–100 daily recovery score combining sleep, recent training load, yesterday's mood and energy, and hydration. Resting heart rate adds the most precision — import it from Apple Health or log it manually. Without HR data the score still runs, using a neutral baseline for that component.
An AI-written plain-English story of your month across training, nutrition, body composition, and wellness. Generated on demand for any past month. After a few months of consistent logging, reading back through your narratives is one of the most motivating things you can do.
A full backup of all your data is now taken automatically every day, and before any bulk operation. Up to 30 daily snapshots are retained per user. Combined with Supabase's 7-day Point-in-Time Recovery at the infrastructure level, years of health data are protected by two independent safety nets — with no action required from you.
Most apps log your data and stop there. AwesomeBody puts it together - so you stop guessing and start knowing.
Most fitness apps track one thing well and ignore the rest. AwesomeBody is built around the connections between them.
Every other app asks what you lifted.
We ask why it was better than last week.
AwesomeBody is built for individuals, but designed to grow with your household. A single family membership keeps everyone on the same plan - at a fraction of the cost of separate subscriptions.
One primary account holder plus up to three additional family members. Each member gets their own private data store - nobody sees anyone else's health data unless they choose to share it.
The primary account holder pays the full subscription. Each additional family member added to the plan is charged at 50% of the standard rate. No hidden fees.
Parents can create and manage accounts for children aged 13–16. The account is linked to the parent, who can monitor activity. Full AwesomeBody functionality - age-appropriate defaults applied automatically.
The account holder starts with a Solo plan (£9.99/month or £99.99/year). Each additional family member is £4.99/month (or £49.99/year) - exactly half the solo rate. See the full Pricing section for details, or email with any questions.
Jump into a fully loaded real account. Everything works - log workouts, food, body data, and wellness. Explore freely; your session is private and rolls back automatically.
🔒 Fully isolated session · edits save to a private demo database · session rolls back automatically after 4 hours · no account, no email, no tracking
One subscription. Every feature. No hidden tiers or locked modules.
No fluff. Just your data, working harder than it ever has.
Start your 14-day trial →14 days. No card up front. £9.99/mo if you stay. Cancel any time.
AwesomeBody is operated as a private application. The data controller is the individual or organisation operating this instance of AwesomeBody. They are responsible for how your data is collected, stored, and used under the UK GDPR and the EU GDPR.
Supabase Inc. acts as a data processor on behalf of the operator - they provide the cloud database infrastructure on which your data is stored, but do not own or control it. The operator has a Data Processing Agreement (DPA) in place with Supabase covering GDPR obligations.
If you have questions about how your data is handled, or want to exercise any of your rights, contact the operator directly.
AwesomeBody only collects data that you actively enter. There is no passive tracking, no behavioural analytics, and no advertising infrastructure. Here is exactly what is stored and why:
The legal basis for processing this data is contract performance (Article 6(1)(b) UK/EU GDPR) - you provide this data to receive the tracking and analysis service. Certain data categories - specifically injury & pain logs, blood markers, body composition data, menstrual cycle data, and menopause/perimenopause symptom data - are classified as special category health data under Article 9 GDPR. These are processed under explicit consent (Article 9(2)(a)). This consent is obtained via a dedicated, unticked checkbox at account creation - separate from the general privacy policy acceptance - which clearly identifies the categories of health data involved and the purposes for which they are processed. The timestamp of both consents is recorded in our database. You may withdraw consent at any time by deleting your account, which permanently removes all your data.
Menstrual cycle data and menopause/perimenopause symptom logs are treated as the most sensitive category of health data in the application. The following guarantees apply absolutely to all Women's Health data and cannot be changed by any settings toggle:
On self-hosted (node server) installations all Women's Health data is stored exclusively in the user's local SQLite database and never leaves their own server. On Supabase-hosted installations, data is encrypted at rest (AES-256) and protected by Row Level Security.
The Apple Health import feature processes your Apple Health export file entirely inside your browser. The export file - which may be hundreds of megabytes in size - is never uploaded to AwesomeBody's server or transmitted to any third party at any point. It is unzipped and parsed locally in your browser tab, in small chunks, and only six categories of extracted numeric values are then sent to your AwesomeBody account as individual small records. Everything else in the export file is discarded without ever leaving your device.
Exactly what is extracted from your Apple Health export - and nothing else:
What is never extracted or transmitted: Location data and GPS routes, heart rate time-series traces, ECG recordings, blood oxygen readings, medication records, medical conditions and diagnoses, personal identifiers (Apple ID, name, phone number, email), environmental exposure data, mindfulness and meditation logs, wheelchair or assistive device data, reproductive health records (other than what you manually log in AwesomeBody's own cycle tracking), and any data from outside the date range you select in the import dialog. The raw export ZIP file is never transmitted to AwesomeBody's server, to Anthropic, or to any other party under any circumstances.
All your data is stored in a Supabase PostgreSQL database. Supabase is a cloud database platform built on AWS infrastructure. The specific data region is determined by the operator's Supabase project configuration (EU regions are available and preferred for GDPR compliance).
Three technical controls protect your data:
Access to your data by the operator is strictly controlled. The operator can access data only through Supabase's authenticated dashboard using their secure operator credentials - the same AES-256 encrypted data store described above. The operator does not have a plaintext copy of your data, does not share it with any third party, and does not use it for any purpose other than providing and maintaining the service. You can further restrict even this in-app access at any time using the privacy toggle in Settings. Your device also stores a local copy in your browser's localStorage to support fast loading and offline use - this copy stays on your device and is never transmitted to the operator or any third party.
Two third parties may receive your data:
Supabase - hosts the database that stores all your health and fitness data on AWS infrastructure. Supabase acts as a data processor under a formal DPA with the operator. They are SOC 2 Type 2 certified and GDPR compliant. All data is encrypted at rest (AES-256) and in transit (TLS). Supabase does not access your data for their own purposes, and the AES-256 encryption at the storage layer means that physical infrastructure access would not expose readable data. Their privacy policy is at supabase.com/privacy.
Anthropic - receives data only when you actively trigger an AI feature, and only the specific content listed below is sent. Your training history, food logs, measurements, and all other stored data are never sent to Anthropic.
Anthropic retains API inputs and outputs for up to 30 days for safety and trust purposes, after which they are automatically deleted. API data is never used to train AI models. If content is flagged for a usage policy violation, Anthropic may retain it for up to 2 years - but all AwesomeBody AI submissions are either anonymised numeric statistics or your own health photos, neither of which could constitute a violation. Anthropic does not receive your name, username, or any data you haven't actively submitted for that specific query. All requests are made over an encrypted HTTPS connection. Full details at anthropic.com/privacy.
If you do not use any AI feature, Anthropic receives nothing at all. Your stored health data lives in Supabase only, as described above.
The operator may need to access your data to provide support or resolve technical issues. They do this through the Supabase dashboard using their authenticated operator credentials - not by reading a local file. By default, this access is permitted. You can control it at any time using the "Allow support access" toggle in the app's Settings page - when this toggle is off, the operator's in-app admin export tools are blocked from accessing your data. You can turn it back on to grant temporary access for troubleshooting, and turn it off again when support is complete.
This toggle controls in-app tool access only. The operator, as Supabase project owner, retains the ability to access data directly via the Supabase dashboard regardless of this setting - the toggle does not override that. It is not a waiver of any legal rights. The operator remains legally obligated to respond to Subject Access Requests, law enforcement requests, and other legal compulsions as required by law.
Progress photos and Women's Health data are always excluded from support access, regardless of the toggle state. Photos are stored in a private Supabase Storage bucket and are never accessible through any in-app admin tool, export function, or support mechanism. Women's Health data (menstrual cycle logs and menopause symptom logs) is architecturally excluded from all admin, export, and support tools - there is no mechanism by which support staff can access this data through the application. The privacy toggle has no bearing on either.
You have the following rights regarding your personal data. These rights cannot be waived and apply regardless of any settings or agreements:
You also have the right to lodge a complaint with the relevant supervisory authority - in the UK, that is the Information Commissioner's Office (ICO) at ico.org.uk. In the EU, contact your national data protection authority.
Your data is retained for as long as your account is active. Session tokens expire after 7 days and are automatically cleaned up. You can delete individual records at any time within the app. You can export and permanently delete your complete dataset at any time from Settings → Your data.
What happens when you delete your account: Your data is removed from the active database immediately and completely. All food logs, training sessions, weigh-ins, measurements, progress photos, supplements, sleep and hydration records, mood logs, vitals, injury logs, blood markers, menstrual cycle logs, menopause symptom logs, profile data, settings, and your account credentials are permanently erased. This includes all special-category health data processed under Article 9, satisfying the right to erasure for that data.
A note on database backups: Supabase retains encrypted database-level backups for a limited period - typically 7 days on most plans - for the sole purpose of disaster recovery (i.e. catastrophic data loss affecting all users). These backups are not accessible to individual users and cannot be used to restore a single user's deleted data. They are not a substitute for your own export. Following a deletion request, the operator will not attempt to restore your data from any backup. These backups will expire and be purged automatically within the retention window. For all practical purposes, deletion through the app is permanent.
Under the GDPR right to erasure (Article 17), the operator is also obligated to take reasonable steps to ensure your personal data is removed from any backup copies they control within a reasonable timeframe, consistent with the backup rotation schedule.
Access to AwesomeBody requires a username and password, authenticated through Supabase Auth. Passwords are never stored in plaintext - Supabase handles credential storage using industry-standard hashing (bcrypt). All data in transit is encrypted via HTTPS/TLS. All data at rest is encrypted using AES-256 by Supabase's underlying AWS infrastructure. Row Level Security (RLS) enforces data isolation at the database level so that no user can query another user's records. Failed login attempts trigger automatic lockout protection within the app.
What encryption means for infrastructure providers: The AES-256 encryption at rest is enforced at the AWS storage layer. This means that even Supabase or AWS infrastructure staff who had access to the physical storage hardware would see only encrypted, unreadable data. Your data can only be deciphered through the authenticated Supabase database service - and Supabase's SOC 2 Type 2 certification and Data Processing Agreement contractually prohibit them from accessing your data for any purpose other than providing the service. TLS encryption in transit means your data cannot be intercepted between your device and the server.
No security system is infallible. If you believe your account has been compromised, contact the operator immediately to have your credentials reset and your session invalidated.
AwesomeBody is available to users aged 16 and over. This threshold is set at 16 because it is the age at which individuals can give their own valid consent for the processing of personal data - including special-category health data - under UK GDPR and EU GDPR. Users under 13 are prohibited in any jurisdiction; users aged 13–15 would require verified parental or guardian consent, which AwesomeBody does not currently support.
Age verification at sign-up: When creating an account, users are required to enter their date of birth. This is checked in the browser to confirm the user is 16 or over. The date of birth entered at this stage is not transmitted to or stored on our servers - it is used solely for this client-side age check and is discarded immediately afterwards. This is distinct from the optional profile date of birth that users may choose to provide during the first-login setup wizard (described in section 2), which is stored and used for AI personalisation purposes as explained there.
If you are aware of a user under the age of 16 accessing the service, please contact the operator to have their account removed.
AwesomeBody uses one cookie and one browser local storage entry. Neither is used for tracking, profiling, advertising, or analytics of any kind. This section sets out what each is, why it exists, what it contains, how long it lasts, and how it is protected - addressing the transparency, purpose limitation, data minimisation, and security obligations under UK/EU GDPR Article 5 and Article 13.
Session cookie - name: session
Purpose. The session cookie exists solely to maintain your authenticated login session. When you sign in, the server generates a cryptographically random token and stores it in a server-side database alongside a timestamp. The same token is placed in a cookie in your browser. On each subsequent request, the server reads the cookie, looks up the token, confirms it has not expired, and uses it to identify which account you are logged in as. Without this mechanism, you would be required to enter your password on every page load. The cookie is used for no other purpose - it is not used for analytics, behavioural tracking, cross-site identification, advertising, or any processing beyond confirming that you are the person who signed in.
Legal basis. Processing the session token is necessary for the performance of the service you have contracted to use (Article 6(1)(b) UK/EU GDPR). You cannot be kept logged in without it. It is also a strictly necessary cookie under PECR, which means consent is not required - but we disclose it here in full to meet our transparency obligations under GDPR.
What it contains. The cookie value is a 64-character hexadecimal string generated by a cryptographically secure random number generator (256 bits of entropy). It contains no personal information - not your name, email address, IP address, or any readable data. It is a pseudonymous identifier: meaningless on its own, but linkable to your account on the server. On the server side, the token is stored in a sessions table alongside your account identifier and the time it was created, so that it can be validated and eventually expired.
Data minimisation. The cookie contains the minimum information needed to maintain a session - a single random token. No personal data is stored in the cookie itself. The 7-day expiry is the shortest period that provides a practical experience without requiring you to sign in repeatedly; sessions are also deleted immediately on sign-out.
Security. Four measures protect the session token: (1) HttpOnly - the cookie cannot be read by JavaScript in the browser, protecting it if a cross-site scripting vulnerability were ever present; (2) SameSite=Lax - the cookie is not sent in cross-site requests, protecting against cross-site request forgery attacks; (3) the token is 256-bit cryptographically random, making it computationally infeasible to guess; (4) expired tokens are purged from the server database automatically at each server start.
Retention. The cookie expires 7 days after it is issued, or immediately when you sign out - whichever comes first. Server-side session records are deleted on expiry or sign-out.
Local storage. The app also caches a copy of your health data in your browser's localStorage. This is your own data - the same records stored in the database - held locally so the app loads instantly and functions offline. It stays on your device, is never transmitted to any third party, and is not a cookie. It is cleared when you clear your browser storage or sign out. No pseudonymous token or identifier is stored in localStorage.
Consent. Because the only cookie used is strictly necessary for authentication, no cookie consent banner is required under PECR or UK/EU GDPR. Strictly necessary cookies are exempt from the consent requirement at Regulation 6(1) PECR. We are not required to offer an opt-out for this cookie - doing so would make the service non-functional - but you can delete it at any time by signing out or clearing your browser cookies.
If this policy changes in a material way, users will be notified via the app. The "Last updated" date at the top of this document reflects the most recent revision.
To exercise any of your rights, request deletion of your data, or ask questions about how your data is handled, contact the operator of this AwesomeBody instance directly. Contact details are available within the app.