Skip to main content

Trust centre / Privacy

Privacy principles for the Atlas ecosystem.

A human-readable overview of how information moves across discovery, member and trainer workflows, safety and account controls.

Last updated 14 August 2026Retention and deletion disclosedPublic and authenticated surfaces

Data handling

What Atlas uses—and why.

This page describes verified product behavior in readable form. It does not invent uses for information outside the current Atlas ecosystem.

01

Information used to provide Atlas

Atlas collects account and profile details, authentication identifiers, gym memberships, trainer relationships, workout and diet-plan activity, attendance, progress records, messages, notification preferences and support requests needed to provide the member and trainer apps.

02

Messaging safety records

Chat safety records can include acceptance of messaging rules, user blocks, reports, selected report reasons and any message linked to a report. Authorized personnel may review reported conversations and related account information to investigate abuse, enforce the Terms, protect users and meet legal obligations.

03

Health, activity and location permissions

With a member’s permission, Atlas Member can read step count, walking or running distance, active calories and approximate or precise location. Health information is used for the member’s activity dashboard and sync, while location is used to find nearby gyms. Atlas does not sell health or location information.

04

Photos and documents

Photos or documents selected through the system picker are uploaded only for user-requested profile, progress or trainer-certification features. Atlas does not request broad access to the device photo library.

05

Public and private information

Public pages expose only intentionally published gym profile data. Private member, trainer, billing and gym-operations data stay outside public discovery surfaces. Gym listing controls determine pricing visibility, contact visibility and trial availability on the public website.

06

Contact and support requests

Contact submissions are stored so the team can respond to user, gym, trainer or support enquiries and keep follow-up context tied to the original request.

07

Data retention schedule

Atlas keeps account, profile, membership, coaching, workout, diet, progress, activity and notification data while an account is active so the requested services can be provided. After a verified deletion request, personal data is deleted or de-identified from active systems within 30 calendar days. Residual copies in encrypted backups expire through the normal backup cycle within 90 days and are not restored except for disaster recovery.

Support and deletion-request records are retained for up to 24 months after closure so Atlas can document the request and its resolution. Safety reports, fraud-prevention records and security or audit logs may be retained for up to 24 months after account closure. Transaction, membership and statutory records may be retained for up to 8 years where needed for tax, accounting, contractual, dispute or other legal obligations. Data subject to a legal hold is kept only for the required period, access is restricted, and it is deleted or de-identified when the obligation ends.

08

Account and data deletion

Members can submit a request from Settings > Delete Account or the Atlas Member deletion page. Trainers can use Settings > Delete account or the Atlas Trainer deletion page. The request must use the email connected to the Atlas account. Support may reply to that address for information reasonably necessary to verify ownership and prevent deletion of the wrong account.

After verification, Atlas deactivates access and deletes or de-identifies the account profile, authentication links and tokens, notification tokens, uploaded profile and progress media, synced activity data, and personal workout, diet and progress records from active systems within 30 calendar days. Where a record also belongs to a gym, trainer, another user, a safety investigation or a legal obligation, Atlas removes or de-identifies the requesting user’s personal information where possible and retains only the minimum record required under the schedule above.

Atlas sends confirmation to the submitted email when processing is complete. If part of the request cannot be completed because retention is legally required, Atlas explains the category retained, the reason and the applicable period. A deletion request can also be sent to the support email shown below.