Your data and your choices

Privacy Policy

Last updated: October 12, 2026

Zand is operated by The Syndicate Security (“we”, “us”). This policy explains how we handle information when you use the Zand mobile app, its connected service, and this website. For privacy questions or requests, email support@zand.fit.

Training kept on your phone

You can begin with a local account. Its profile, plans, workouts, measurements, and settings are stored on your phone, and ordinary local training is not synchronized to our account service until you connect an account. The phone’s own backup settings may include this app data.

Cloud Coach is a separate data flow. Coach can use a cloud service during setup or for a workout pick before you connect an account. The relevant answers and training context leave your phone when those cloud features are used, as described below.

Information Zand processes

  • Account information: your display name, email address, account identifier, invitation and verification records, sign-in sessions, and your chosen authentication method. Email/password accounts store a password hash. Apple or Google sign-in provides a provider identifier and may provide your name and email address, including an Apple relay address.
  • Training and profile information: exercises, sets, repetitions, loads, session dates and durations, workout notes, programs and templates, goals, equipment, sports, bodyweight and other measurements, and profile details you enter, such as birth year, sex, height, injuries, and training constraints. We also calculate training history, progress, and badges from these records.
  • Crew information: membership, invitations, shared training activity and plans, reactions, nudges, and sharing preferences. Details that reach other people depend on the Crew features you use and your sharing settings.
  • Cloud Coach information: your submitted questions and instructions, relevant profile and training context, generated suggestions and answers, and actions you choose to accept.
  • Technical information: device identifiers and push registration tokens where those features are used, plus request identifiers, timestamps, response status, and error information used to operate the service. Our infrastructure processes network addresses for communication, security, and rate limiting.
  • Support information: your email address, message, and any screenshots or files you choose to send us.

How we use information

We use this information to keep and synchronize your training, authenticate accounts, deliver verification and recovery emails, provide Crew features and notifications, produce Coach responses, calculate progress, investigate problems, and protect the service from abuse.

Who receives information

Connected account data is processed on infrastructure hosted by Hetzner. Account emails are delivered using Resend. Messages you send to support are handled through our Google Workspace mailbox. These services receive the information needed for hosting, delivery, or support.

If you choose Apple or Google sign-in, that provider processes the authentication request under its own policies. Push notifications use Apple Push Notification service on iPhone and Firebase Cloud Messaging on Android. The push provider receives the device registration and notification payload needed for delivery.

Crew members can see your display name, chosen tile, activity, and exercise names. Sharing levels control additional session numbers; the highest level also shares bodyweight. Activity remains visible at every level. Leave the Crew to stop sharing through it.

Other people may keep their own copies of information you shared. A workout copied by another person becomes part of that person’s training records.

Cloud Coach

Cloud Coach may use OpenAI, Google (Gemini), Anthropic, or DeepSeek to produce a response. Each request is sent to the provider configured for that Coach service. Depending on the feature, the request can include your setup answers, goals, injuries or constraints, workout notes, plans, recent sessions, measurements, progress summaries, and additional training history requested while preparing the response. Free text can include identifying or sensitive information if you enter it.

For connected Coach jobs, Zand stores the submitted instructions, a snapshot of relevant training history, visible answers and follow-up questions, generated drafts, usage records, and accepted actions. The local-account previews and initial plan read do not create that connected-job history on our service, but their request content is still sent to the cloud model.

To count the two free Coach previews, Zand sends a device identifier to its server and stores it as a hash with allowance counts. This identifier is separate from your account and is not included in the model’s training-context request. Hashing it does not make all Coach information anonymous.

The provider’s handling and retention of requests depend on the applicable API service terms and account settings. Provider-held copies are separate from Zand’s account records; deleting a Zand account does not itself erase them. Information about these services is available in OpenAI’s API data controls, Google’s Gemini API terms, Anthropic’s API retention information, and DeepSeek’s API documentation.

Avoid entering information you do not want processed by a cloud service. Contact support if you have questions about a Coach request.

Your controls

  • Keep ordinary training local by using the app without connecting an account. Connecting uploads the local account’s training to the service for synchronization.
  • On iPhone, AI Coach starts off. You can enable it during onboarding or with the AI Coach toggle in Zand’s Settings. Turning it off stops future cloud Coach calls from that phone and attempts to cancel unfinished account requests. It cannot recall information already shared with a provider. Other devices have their own choice.
  • Use Crew sharing controls to choose additional session detail, including per-person detail levels. Your activity remains visible at every level; leave the Crew to stop sharing through it.
  • Change notification permissions in your phone’s Settings and notification preferences in Zand.
  • Use Settings → Export your data to save a copy of your training.
  • Use Settings → Delete account to delete a local or connected account. Signing out or uninstalling the app does not delete a connected account.
  • Email support to request help with access, correction, or deletion, including if you cannot sign in. We may verify account ownership before fulfilling a request.

Retention and deletion

A local account’s training stays on the phone until you remove it or delete the local account. Signing out of a connected account clears its cached account data from that phone, while the account remains on the service. Manage copies in device backups or exported files through the service or storage location where you keep them.

Connected records are kept while your account exists. Deleting a connected account removes its owned training, profile, authentication, push, and Coach job records from the active service. Other people’s copied workouts remain in their accounts with the original account’s attribution detached. Deletion cannot retrieve screenshots, exports, or other copies someone already made.

If you canceled a connection after a server account was created, deleting the local account clears only this phone’s copy. Zand warns that the server account remains accessible by signing in. Sign in to delete that connected account, or contact support for help.

Server backups can retain deleted records. Routine backups keep up to 48 hourly snapshots and 35 days of daily snapshots. Some release and recovery backups are preserved without scheduled expiry. An account deletion does not automatically erase these preserved backup copies.

The hashed device record used to count free Coach previews is kept separately from account records. It currently has no automatic expiry and is not removed by account deletion or uninstalling the app.

Technical and support records may be kept to resolve requests, investigate security incidents, or meet applicable obligations. Contact support with a specific retention or deletion question.

This website

These public pages use no cookies, analytics scripts, advertising pixels, or third-party embedded content. Visiting them still sends ordinary connection information, such as your network address, to the hosting infrastructure. Emailing support shares the contents of that email with us and our mail service.

Updates and contact

We will update this page when our practices change and revise the date above. For questions about your data or this policy, contact The Syndicate Security at support@zand.fit.