Privacy policy

1. Information we handle

• Account information: your email address, display name, account identifier and authentication information when you create or use an account. Firebase Authentication handles email/password sign-in, password resets and account verification.
• Training and preferences: programs, exercises, sets, repetitions, weights, RIR, rest times, workout dates and duration, cardio details, schedules, goals, equipment, experience, units, time zone and any body measurements, notes or feedback you enter. Optional effort, energy and pain feedback may reveal information about your health.
• Community information: posts, comments, likes, friendships, reports, profile information and training summaries you choose to publish through social features. Posts and comments, including your display name, are visible to signed-in community members. You control participation in rankings.
• Technical information: account-session information, request timestamps, subscription access, service errors and usage counters needed to provide the app, prevent abuse and manage service limits. Hosting, authentication and connected providers may receive IP addresses and device information as part of their services.

Guest records and offline copies use device storage. Signed-in account records can also be stored in Google Firebase so your training can follow you between devices. Imported files add the information you select to your training records.

2. Why we use information

We use account and training information to provide the features you request: save and synchronize training, show progress, maintain schedules, suggest training changes and provide chosen community features. Account processing is necessary to provide the requested account service. Security checks and request limits support our legitimate interest in operating a reliable service and preventing abuse.

Optional information and sharing remain under your control. Where processing relies on consent, you can withdraw it through the relevant feature or by contacting us. Withdrawing consent does not affect processing that occurred before withdrawal. Applicable privacy law may provide additional protections for information that reveals health.

3. AI coaching

When you send a question to the Pro AI coach, your question, a bounded set of recent chat turns and any pending proposal you ask it to revise are sent to OpenAI. Generated replies and proposed changes are checked for safety using the same provider before they are shown. If you choose training sharing, the request also includes bounded goals, preferences, programs, planned sessions and recent completed training, including selected performance and optional effort, energy and pain feedback. A separate choice controls sharing the current Strava activity view.

The automatic training summary excludes dedicated account identity, email, profile name and body-measurement fields, routes, credentials and ordinary workout/set notes. Shared program, workout and session names, coaching feedback notes and cardio-session notes are included and can contain personal details you entered. Information you type into chat is sent as part of your question, so choose what you include in these fields.

AI suggestions evaluate shared training and preferences to propose programs, exercises, targets, cardio and schedules. You can revise, discard or accept them. Accepted changes become part of your saved training records.

Trainee does not routinely save chat text or pending proposals in its account database; the conversation clears when you leave the coach or change accounts. It retains account usage counters to enforce limits. Requests disable OpenAI Responses storage. OpenAI may still retain abuse-monitoring data, ordinarily for up to 30 days, subject to its published controls and exceptions. See OpenAI API data controls and OpenAI's privacy policy.

Explicit AI reports

If you use Report this reply, only the selected assistant reply and your reason are submitted to a private, bounded review queue with your account identifier and submission time. This explicit report excludes your prompts, chat history, training context and proposals.

4. Strava connections

When the Strava connection is available and you authorize it, Trainee uses Aeternum's shared Strava application. Aeternum's secure server maintains the provider authorization. Trainee stores connection metadata, including your Strava athlete identifier and the granted permissions; provider tokens stay on the shared server.

The activity view contains bounded activity summaries such as type, name, date, duration, distance, elevation and available heart-rate information. Private and “only me” activities are filtered from the Trainee view. The view expires within ten minutes; expired summaries are excluded from display and coaching, and cleared as the app runs or resumes. Disconnect and sign-out clear the view. It is not saved in Trainee account backups, charts, rankings or social posts.

If you separately choose Strava sharing for an AI request, bounded activity type, date, duration and distance are sent to OpenAI. Expiring the activity view does not erase a question, response or accepted plan already created from that request.

Disconnecting removes Trainee's link. Aeternum's own link remains if you also use that product. You can separately manage application authorization in Strava settings. Strava also handles information under its privacy policy.

Age and guardian choices

Guest training is available without an age choice. A neutral birth-date entry derives only an age band: under 13, 13–15, 16–17 or 18 and over. The birth date itself is discarded and is never saved or sent. The band is kept in the current device workspace. Until a known band of at least 13 is chosen, the app does not initialize Firebase account services. Under-13 use remains in the guest workspace.

When you sign in, the server stores the account’s declared age band, permission status and revision. For teen accounts, online training sync, community, friends and rankings, AI, Strava and purchases remain off until a parent or legal guardian approves the selected features. Approval uses a short-lived, one-time code generated in the teen account, the guardian’s own adult account with a verified email, and their explicit acknowledgement of parental or legal-guardian responsibility. Email verification confirms control of that email; it does not verify legal guardianship or identity.

The server stores the linked account identifiers, selected permissions, approval acknowledgement and relevant timestamps. Approval codes are hashed on the server. Guardians can change or revoke permissions in Settings; new server requests check the current permissions. The guardian does not receive access to private training records. Privacy export and account deletion remain available to pending or revoked account owners. Contact support to correct an account age declaration.

Advertising stays off when age is unknown or below 18: the app does not request UMP consent, ATT authorization or advertising SDK startup for those settings. Clearing the setting cancels pending advertising work and removes an existing banner. You can review the device setting in Settings. Strava heart-rate context is excluded for the 13–15 band, even when Strava permission is approved. Provider age requirements and local requirements still apply.

5. Advertising and purchases

The Free native app uses Google AdMob. Verified Plus and Pro access removes app banners. Browser versions do not request AdMob ads. Ad requests use non-personalized advertising and are gated by the adult age setting and Google's User Messaging Platform consent status.

On iOS, the app also waits for your system App Tracking Transparency choice before starting the advertising SDK. Allowing tracking permits advertising identifiers to be used for advertising measurement. Declining or restricting tracking keeps training available and permits non-personalized ads without IDFA access. You can change this choice in iOS Settings. Publisher first-party advertising IDs are disabled.

Google's advertising SDK may collect or share IP addresses, device or advertising identifiers, ad interactions and diagnostic information for ad delivery, measurement and fraud prevention. Non-personalized ads can still use identifiers for these purposes. Trainee does not include your account identity or training records in its ad requests. You can revisit Ad privacy choices in app settings when Google requires that option, and use your device's advertising/privacy controls. See Google's privacy policy and its advertising SDK data disclosure.

When in-app purchases are enabled, the applicable app store handles payment and RevenueCat verifies subscription access using account and purchase information, such as product identifiers, transaction records and subscription status. Trainee does not receive your full payment-card details. Store and subscription providers retain their own transaction records. See RevenueCat's privacy policy. Deleting your Trainee account does not cancel a store subscription; manage it through the store.

6. Providers and international processing

Google Firebase provides authentication, cloud storage, hosting and server functions. OpenAI provides the requested AI coaching service. Strava supplies authorized activity information. Google AdMob supplies native advertising. App stores and RevenueCat support purchases when enabled. Community posts and comments are shared with signed-in community members, and exported files go where you choose to save or share them.

Uncached exercise illustrations may load from GitHub. Opening a tutorial or another external link connects you to that website, such as YouTube, which handles information under its own policy. Trainee does not install a separate advertising or analytics tracker on this privacy page.

These providers may process information outside your country, including in the United States. Their published privacy, processing and international-transfer terms describe their safeguards. Contact Aeternum for information about the arrangements applicable to your data. See Firebase privacy and security information.

7. Storage, retention and deletion

Saved training and account information remain while you use the account or device workspace, until removed through app controls or account deletion. Synchronization keeps record identifiers and deletion markers so removed records do not reappear on another device. Older synchronization snapshots may remain until account deletion.

When upgrading from the previous Trainee app, compatible cloud training is recovered only for the same signed-in account. Original records from that app remain until account deletion. Removing a recovered item through the new app does not erase its original source copy; contact us if you want selected source records removed while keeping your account.

Use Export training data in settings to save a copy. A signed-in owner can also choose Export account privacy data in age and guardian controls. This includes account and approval metadata, current training and preserved source records, submitted reports, authored posts and comments, reactions, preferences and friend relationships. It excludes provider credentials and other users’ private records. This export remains available while permissions are pending or revoked.

You can edit or remove your training records and published material. Delete account requires fresh authentication and removes your Firebase sign-in account, cloud training records, authored posts, comments and likes, friendships, reports you submitted, account age and approval records, ranking entry and Trainee connection metadata. Deleting a guardian’s account revokes linked teen permissions while preserving the teen’s own records. Connected Strava cleanup must succeed before account deletion completes. Account deletion instructions and contact options are available without signing in.

A minimal hashed account deletion marker and timestamps remain to prevent deleted accounts from being recreated by delayed requests. The marker contains no profile or training records, email address, raw account identifier or provider tokens.

Account deletion clears the local account cache on the device performing it. Other devices, exported files, screenshots, copies held by other users and records retained independently by service or store providers require separate handling. Deleting an app or clearing its browser storage removes local copies but does not by itself delete a cloud account. For guest records, manage your device/app storage or contact us for help.

Temporary Strava views expire within ten minutes. Chat and unaccepted proposals clear on leaving the coach. Account usage counters remain with the account. Some identifiers in purchase-verification metadata, moderation history, shared connection controls or other users' reports and block/mute preferences can remain outside the deleted account records. Providers' operational logs and records follow their own retention terms. Contact us about retained records or copies.

8. Your choices and rights

Depending on applicable law, you may request access, correction, deletion, restriction, portability or objection to processing, and withdraw consent where it applies. Send requests to marcussen.business@hotmail.com. We may need to verify that the request concerns your account. You can also use the app's export, editing, deletion and sharing controls.

You may complain to your local data-protection authority. For the EEA, the European Data Protection Board lists national authorities. Parents or guardians can contact us about information a child has entered into Trainee.

9. Security and updates

Account access, server authorization checks and encrypted service connections protect information. Provider credentials are kept on servers. No system can guarantee absolute security; contact us if you suspect unauthorized access.

We may update this policy as features or data practices change. The date at the top identifies the current version. Where required, material changes will be brought to your attention and additional choices requested.