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.

Plain-language overview7 policy areasPublic 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

Account-removal requests

Members and trainers can send an account-removal request through the account deletion page. The form creates a support enquiry; the team reviews the request, may ask for information needed to identify the account, and explains the removal and record-handling steps that apply.