← Back to Athevia

ATHEVIA

Privacy Policy

This policy explains what information Athevia handles, why it is used, and when it may leave your device.

Effective September 20, 2026

1. Privacy at a glance

2. Information Athevia handles

Account information

If you choose Sign in with Apple, Athevia receives an Apple-linked user identifier and, when Apple provides it, your email address. If you use Apple's Hide My Email feature, the address may be an Apple private relay address.

Athlete profile and training plan information

This can include your display name, experience level, training start date, unit preference, pool length, goals, sport preferences, availability, planned workouts, completed workout status, custom workout templates and training parameters.

Health and fitness information

With your permission, Athevia can import workout information from Apple Health. Depending on the workout and available sensors, this may include workout type, start and end times, duration, distance, heart rate, elevation, cadence, speed, running power, stride metrics, cycling power, functional threshold power, swimming metrics and Apple workout effort values.

Feedback and recovery information

When you provide it, Athevia may store workout RPE, pain score, pain location, recovery feeling, soreness, energy level, symptoms and free-form workout notes. This information is used to present your training history and help adapt future training.

Precise location and route information

For supported outdoor running and cycling workouts recorded with Athevia, the app can collect GPS coordinates, altitude and timestamps to calculate distance, speed and a route. When location permission and background workout tracking are enabled, location updates may continue while an active workout is running with the screen locked or the app in the background. Athevia does not use workout GPS tracking to continuously monitor your location outside an active workout.

3. How the information is used

Athevia uses this information to provide its core training functionality, including:

4. Apple Health

Apple Health data is accessed only after you grant permission through Apple's HealthKit authorization flow. Athevia uses HealthKit information for fitness and training features and does not use HealthKit data for advertising, marketing or data brokerage.

HealthKit remains the source of truth for imported Apple Health workouts. Athevia stores a normalized copy of workout values needed for its training and history features.

5. Cloud backup

When you sign in with Apple and use cloud backup, Athevia uses Supabase to store authenticated backup revisions associated with your account.

A backup can include your athlete profile, training plans, workout templates, completed workout summaries, workout metrics, feedback and recovery check-ins. If an Athevia-recorded workout contains a GPS route, that route can also be included in the backed-up workout metrics.

Signing out does not delete your local training or existing cloud backups. This allows training to remain available for later restore.

6. Workout sharing

Workout sharing is initiated by you. A generated share card can contain information such as workout type, date, distance, duration, pace or speed, and a visual representation of the GPS route when available. Athevia does not automatically publish your workouts. If you use the iOS share sheet, the destination you select will handle the shared content under its own privacy practices.

7. Service providers

These providers may process information as necessary to provide their services and are subject to their own privacy terms.

8. Data retention and deletion

Local Athevia data remains on your device until it is removed through the app, the app's storage is cleared, or the app is deleted, subject to iOS behavior and any copies you have separately backed up.

Cloud backup revisions and account-related information may remain in Athevia's backend until they are deleted. Signing out by itself does not delete those records.

To request deletion of cloud account data, use the developer contact published on Athevia's App Store product page or the support method published on this website. Do not send health or location information through a public channel.

9. Security

Athevia is designed so cloud backup access is tied to the authenticated account, and backend authorization rules restrict a user to that user's backup data. No method of electronic storage or transmission can be guaranteed to be completely secure.

10. Children

Athevia is not specifically directed to children under 13. If you believe personal information from a child has been provided to Athevia inappropriately, contact the developer so it can be reviewed.

11. Changes to this policy

This policy may be updated when Athevia's features or data practices change. The effective date at the top of this page will be updated when material changes are published.

12. Contact

For privacy questions, visit the Athevia Support page. Do not include health, location or other sensitive information in public support requests.