Skip to main content

Exported data format

This page describes the data you can export from Athleex, the formats, the file structure and the known technical limitations, as required by Art. 26 of Regulation (EU) 2023/2854 (Data Act) and Art. 20 GDPR. The conditions for switching to another provider are in section 10 of the Terms.

Last updated: 28 September 2026

How to export

From Settings » Export my data choose JSON (structured, to transfer your data) or PDF (readable summary). For security we ask you to confirm your password; the file downloads immediately from the app, after signing in.

For the full copy of the data processed on behalf of a PT, including workouts logged by athletes and, within the limits of their consent, shared health data, or for help switching to another provider, write to info@athleex.com: we provide it within 30 days, free of charge.

Formats and standards

  • JSON (RFC 8259) in UTF-8: a single object per account, with field names in English.
  • Dates and times in ISO 8601 (UTC); countries as ISO 3166-1 alpha-2 codes; languages as ISO 639-1 codes.
  • Body measurements in metric units (kg, cm, %); goals include the unit chosen.
  • Files (photos, avatar, videos, attachments, invoices) in their original format (JPEG, PNG, WebP, MP4, PDF), listed in the JSON as links that open after signing in with the same account.

Structure of the JSON file

  • exportDate, platform, gdprArticle, fileLinksNote: information about the file.
  • profile, subscription, preferences: account, subscription and settings.
  • consentLogs, dataAccessLogs, dsarRequests: consents, access to your health data and requests about your rights.
  • biometrics, assessments, progressPhotos, nutritionalDiaries: health data, only if you consented.
  • goals, workoutLogs, workoutVideos, workoutVideoComments, exerciseMaxes, workoutDiaries, weeklyReports, workoutFeedback: goals and training.
  • mealPlans, nutritionalAdvice, supplements, supplementReminderLogs: nutrition and supplements.
  • messages, messagesReceived, whatsAppMessages, notifications: communications.
  • achievements, customAchievements, xpEvents, duels, challengeParticipations: points, challenges and leaderboard.
  • forecasts, churnScores, churnInterventions: Athleex Score, forecasts and Churn Radar.
  • relationships, trainerNotes, invoices, calendarEvents, reviewsWritten, reviewsReceived: relationships with the PT, notes, invoices, calendar and reviews.
  • usageDays: internal usage statistics.
  • trainer (PTs only; null otherwise): public page and its files, athletes and relationship data, programs with exercises, versions and assignments, exercises and templates, meal plans, advice, recommended supplements, Churn Radar interventions, challenges, messages sent to all athletes, contacts received, invite codes, Instagram connection.

What is not included

Only data internal to the functioning of the service that you did not generate, and whose disclosure would put Refreesh's security or trade secrets at risk, is not exportable: security and access logs, anti-abuse counters, cryptographic hashes of passwords and codes, tokens for connections to external services, the code and calculation models of Athleex Score, Athlete Twin and Churn Radar (the results concerning you are included).

Known technical limitations

  • Files are not inside the JSON but linked: download them before deleting your account, because the links stop working after deletion.
  • The PDF is a readable summary and does not contain the PT section: use the JSON to transfer your data.
  • There is no automatic import into other services: the new provider imports the JSON. When common interoperability specifications for this kind of service are published (Arts. 30 and 35 of the Data Act), we will adapt the format.