Where your gym’s data lives, who can access it, and the hosting options available to you. Explained in plain language.
See where data goes
Shared platform, gym-specific access
Each service has its own data location.
Gymplify GmbH is based in Buochs. A Swiss company address does not mean all data stays in Switzerland.
Our database and uploaded files are stored in the US. Gymplify and branded apps share this Firebase infrastructure.
Need a separate backend or a specific data region? We can scope a dedicated setup with you.
Our backend is the technology that saves information and runs tasks behind the app. We use Google Firebase, built on Google Cloud, for its core services. Storage and processing can happen in different countries.
Member profiles, memberships, training records and gym settings.
Our database uses Google’s nam5 location: full data copies in Iowa and Oklahoma, with a supporting witness replica in South Carolina that does not hold the full data.
Images and other files uploaded to the app.
Our file-storage bucket uses Google’s US location. Files are stored across locations in the United States; this setting does not identify one particular city.
Account details and the credentials used to sign in.
Google operates Firebase Authentication in the US. Choosing another database region does not move this service.
Server-side actions such as account administration and billing workflows.
Our backend is configured to run in Google Cloud’s us-central1 region. These actions can process data stored elsewhere.
Connection and online status used by the app.
The shared platform’s configured Realtime Database endpoint is in us-central1.
Transactional messages, such as invitations and account emails.
Email sending is configured in AWS us-east-1. Delivery also involves the recipient’s email provider.
Access follows the person’s role and the information needed for the feature or service.
Members access their own account and training information. Content they choose to share can be visible to others, depending on the feature.
Gym owners and authorized staff can access member information according to their roles. The gym owner manages who receives those roles.
Authorized Gymplify administrators have technical access to customer data. We use that access for support and debugging.
Google and the other providers we use process data to deliver their services. Google restricts employee access to people with a business need and logs that access.
Firebase encrypts data in transit and encrypts stored data for services including Firestore, Authentication and Cloud Storage. Encryption protects the data; authorized users and services can still access it. Read Google’s security explanation.
Start on our shared infrastructure, or talk to us about a separate environment for your organization.
Have a specific requirement? Tell us the country, the data involved and what your organization needs.
Talk to usNo. Our Firestore database and uploaded files are stored in the United States. Sign-in is also US-based, and backend processing is configured in Iowa. Swiss regional storage can be discussed as part of a dedicated setup, with other services reviewed separately.
By default, branded apps use the same Gymplify backend. Your own app name and design do not automatically include a separate database or a different hosting region. A dedicated backend is an additional option.
We can plan a dedicated setup in regions supported by the services you need. We first check availability and any services that process data elsewhere. This is a tailored project, rather than an instant country switch.
We can assess a migration with you. Moving existing records, files, sign-in and integrations needs a coordinated plan. We agree the scope, timing, access responsibilities and costs before work begins.
This page explains our infrastructure and hosting options. The app’s privacy policy covers how personal data is handled. For access or deletion requests, contact your gym or email hello@gymplify.com.
Learn more from our infrastructure providers
Firebase privacy & securityDatabase locationsFile-storage locationsProcessing locations