Privacy

Privacy Policy

Version 1.1 · Effective 15 September 2026 · Applies to the Hyperion AI Trainer Android app and the website at hyperion-pt.netlify.app. v1.1 names the current AI inference provider and its jurisdiction, replacing the v1.0 wording.

Hyperion AI Trainer is a strength and wellness trainer. It needs to know about your training and your recovery to coach you, so this policy explains in plain language what we collect, why, who else sees it, how long we keep it, and how to remove it.

We collect the minimum needed to run the coaching. We do not sell your information, we do not use it for advertising, and we do not use your health information for any purpose other than the features described here.

Who we are

Hyperion AI Trainer is published by Fit Life Apps (the developer account for this app on Google Play), based in Australia. For anything in this policy — questions, access requests, corrections or deletion — contact hyperionptdev@gmail.com. We reply to privacy requests within 30 days.

What we collect and why

Information	Why we have it	Where it comes from
Account details email address, password (stored only as a hash), user ID	To create your account, sign you in, and keep your training attached to you rather than to a device.	You, when you register.
Profile details name, age, weight, height, training experience, goal, injury notes, personal bests	To build training that suits you and to scale loads sensibly. Injury notes are optional.	You, during onboarding and in Profile.
Training records programs, planned and completed workouts, exercises, sets, weights, repetitions, RPE, notes, personal records	The core of the app: logging training, seeing history and progress, and generating the next session.	You, as you train.
Wellness records daily check-ins (mood, energy, stress), sleep logs, journal reflections, guided session records	To read your recovery context and adapt volume, intensity and recommendations.	You, or Health Connect when you connect it (see below).
Sleep data from Health Connect sleep sessions imported from your device's Health Connect store — read-only	To fill in sleep duration and quality so recovery guidance is based on real sleep rather than guesswork.	Android Health Connect, only after you grant the `READ_SLEEP` permission.
Progress photos photos you choose to take or upload	To show visual progress over time. Stored in private storage you alone can read.	You, using the camera or gallery from Photos.
Coach conversations messages you send to the AI coach, and its replies	To answer you with continuity instead of restarting the conversation each time.	You, in the Coach tab.
Device information push notification token, app version, platform	To deliver reminders you enable and to keep the app working on your device.	Your device, automatically.

What we do not collect

No advertising identifiers, and no advertising or marketing use of your data.
No location data, contacts, SMS, call logs, calendar or microphone access.
No Health Connect data beyond sleep, and no write access to Health Connect — the integration is read-only and only runs while the app is open.
No third-party analytics or crash-reporting SDKs. If that changes, this policy will be updated before they ship.

Health Connect sleep data

Sleep is read-only, optional and revocable

If you connect Health Connect on Android, the app requests the single permission READ_SLEEP. It reads sleep sessions so your recovery context reflects actual sleep. It never writes to Health Connect, never reads any other Health Connect data type, and never imports sleep in the background.

Consent: the import only happens after you grant the permission, and you can disconnect the app inside Health Connect at any time.
On our servers: imported sleep summaries are stored with your account so they can be shown alongside manual logs across your devices.
Not for advertising: Health Connect data is never used for advertising, marketing, or any purpose unrelated to the recovery features in the app, and it is never sold or shared with data brokers. This is a Google Play Health apps requirement and a commitment we keep.
AI context: sleep summaries are included in AI coaching context only when you turn that on in Profile → Wellness data. It is off by default.
Deletion: disconnecting removes future imports; asking us to delete your account deletes imported sleep records too.

AI coaching and what leaves our servers

Coaching is generated by a large language model. To produce a response, the app sends a projection of your data to a model provider — never your whole record, and never your email address, user ID or device tokens. The one thing that does travel is the display name you entered, because the coaching addresses you by it; that is spelled out below.

What is sent: your profile (the display name you chose, age, height, weight, training experience, goal, personal bests, and any injury or medical notes you entered), recent workouts and performance, task inputs you choose (for example a wellness outcome and duration, or your current mood and energy), and the message you typed. Sleep summaries and wellness check-in values are included according to the switches below.
What is removed: your email address, user ID, push notification token and other direct identifiers are stripped before anything leaves, at every depth of the payload. The one exception is the display name you entered, which coaching uses to address you — so if you would rather the model never sees it, set the name in Profile to a first name or a nickname. It can be changed at any time.
Your switches: daily check-in values (mood, energy, stress, readiness) are included in coaching by default and can be turned off in Profile → Wellness data. Journal reflections and Health Connect sleep summaries are off by default and only included if you turn them on. Injury and medical notes stay in the coaching context because they are what keeps programming safe; delete them in Profile if you would rather not share them.
Providers: coaching runs on our managed model provider (DeepSeek, via the DeepSeek API) under our own account and key. Prompt content is sent only to produce a completion. We strip your email address, user ID, push token and other direct identifiers first, and the sensitive parts are yours to control — but we cannot promise that the provider does not learn from what it processes. DeepSeek's privacy policy states that user inputs may be used to train and improve its models and technologies, and that it processes personal data in the People's Republic of China, so sending a prompt is a cross-border transfer and the provider's own terms (not ours) govern how it uses what it receives. That is a deliberate, disclosed trade-off: it is why we strip identities, why journal reflections and Health Connect sleep summaries are off until you switch them on, and why a bring-your-own-key provider option is on the roadmap. If you would rather not accept the provider's terms, leave AI features unused — tracking, logging and Health Connect sync all work without them.
Bring your own key (BYOK) is not available yet. If it ships, prompts will go directly to the model provider you choose, under your own account and their terms, with your key stored on your device rather than on our servers. This policy and our Google Play disclosures will be updated before that change reaches you.
Conversations: chat history is stored with your account so the coach has context, and is deleted with your account.

How your information is stored and protected

Data is stored with Supabase (Postgres database, private file storage) and served over HTTPS; the website is hosted by Netlify. Both act as our service providers and are bound to process data only on our instructions.
Traffic is encrypted in transit. Photo storage is private: images are served through an authenticated endpoint that checks the photo belongs to the signed-in account.
Access to your records requires your signed-in session; server-side access is restricted to the app's own backend functions.
Uploaded photos are validated server-side (format, size and image structure) before being accepted.

Retention

We keep your information for as long as your account exists, because that is what makes your history and coaching useful. There is no separate archive and no expiry that removes data behind your back.

Delete your account and the account row, training records, wellness records, journal entries, coach conversations, measurements, progress photos and imported sleep sessions are deleted from live storage.
Deletion is immediate and irreversible. Brief backups may retain encrypted copies for up to 30 days before being overwritten in the normal backup cycle.
If you ask us to delete specific records rather than the account, we action it within 30 days.

Deleting your account

Two ways to delete

In the app: Profile → Account → Delete account. You confirm with your password and a typed confirmation phrase. Everything listed above is deleted immediately.

On the web: if you cannot sign in, use the account deletion page or email hyperionptdev@gmail.com from the address on the account. We verify the request and delete the account within 30 days, and confirm when it is done.

Your rights

Under the Australian Privacy Act 1988 (and, where it applies, the GDPR) you can ask for a copy of your information, ask us to correct it, ask us to delete it, or object to how it is used. You can also ask us to stop including wellness data in AI coaching — that switch is in Profile → Wellness data. Write to hyperionptdev@gmail.com and we will action the request within 30 days. If you are not satisfied with our response you can complain to the Office of the Australian Information Commissioner (oaic.gov.au).

Children

Hyperion AI Trainer is intended for adults and is not directed at children. We do not knowingly collect personal information from children under 13 (or the minimum age in your jurisdiction). Accounts must not be used by children. If you believe a child has provided us with their information, contact hyperionptdev@gmail.com and we will delete it.

Changes to this policy

If we change how the app handles your information — for example by adding a crash reporter or a new data source — we will update this page and change the version and effective date above before that change reaches you. Material changes will also be surfaced in the app.