Privacy

Last updated August 21, 2026

How figoat handles member data

This page explains the data categories the app uses to operate. It is written for clarity first, so you can understand the product without digging through internal terms.

What the app stores

Account details, training logs, check-ins, routines, and other member state that power the product.

Why it is used

To sync your account, generate coaching context, and show planning and progress views.

When providers are involved

Only when you explicitly use provider-backed coaching or voice features.

Your control

Delete your account from the app at any time, or contact support for help and privacy questions.

Data categories

What figoat collects to run the product

figoat stores the information you add to your account and the app state needed to make planning, logging, and coaching work across sessions.

  • Account details such as your email address and basic profile information.
  • Training logs, cardio sessions, meals, hydration entries, and recovery check-ins.
  • Saved routines, goals, reminders, and the planning context tied to your week.
  • Feature-specific data such as Crew discovery settings if you choose to use them.

Why the app uses it

The product uses your data to support the core fitness workflow

The stored data is used to keep your account in sync, show your recent activity, personalize the coach context, and help you review routines and progress over time.

figoat does not need a public social feed or a follower graph to operate, and discoverability features stay opt-in rather than on by default.

Infrastructure and providers

Some features rely on third-party services only when you use them

Signed-in member state is held by our managed hosting and database provider so the app can persist and sync your data. Coaching and voice requests are sent to specialist processing providers only when you explicitly use those features, and only for as long as it takes to return your result.

Generated daily brief audio is stored in a dedicated storage bucket when you create it, because playback needs a retrievable file rather than a transient response.

Apple Health

Health data is optional and only read with your permission

On iOS, figoat can read the weight, sleep, resting heart rate, heart rate variability, steps, active energy, Exercise and Stand minutes, and workouts you choose to share from Apple Health, including readings synced from Apple Watch. This is optional and off by default on each device. You choose the data types to share in Apple’s permission sheet.

The Health progress view reads data on your device without uploading those readings. If you confirm a suggested weight or sleep value in a recovery check-in, that saved check-in becomes part of your account history and may be sent to the AI coaching providers described above when you use coaching. Health data is never used for advertising or marketing and is never sold. You can stop reads in figoat or revoke access in Apple Health at any time, and the app keeps working without it.

Retention and deletion

Your data lives as long as your account, and you can delete both

figoat keeps your account data for as long as your account exists so your training history and coaching context stay available to you. When your account is deleted, your stored member state — training logs, check-ins, goals, routines, and profile — is deleted with it. Active web subscriptions are cancelled during account deletion. App Store subscriptions must be cancelled separately in your Apple subscription settings.

You can delete your account yourself, from Settings → Account on the web or Settings → Delete account in the iPhone app. Either route cancels an active web subscription with it. You can also ask us to do it by writing to support from your account email.

Your choices

You can ask questions or request account-data help

If you need help with account data, privacy questions, or removal requests, contact support@figoat.com from the email tied to your account so the request can be verified.

If a feature includes a discoverability or sharing setting, treat the in-product setting as the first control surface and contact support if you need additional help.