What the app stores
Account details, training logs, check-ins, routines, and other member state that power the product.
Privacy
Last updated March 27, 2026This 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.
Account details, training logs, check-ins, routines, and other member state that power the product.
To sync your account, generate coaching context, and show planning and progress views.
Only when you explicitly use provider-backed coaching or voice features.
Contact support from your account email if you need help, removal, or privacy clarification.
Data categories
Figoat stores the information you add to your account and the app state needed to make planning, logging, and coaching work across sessions.
Why the app uses it
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
Signed-in member state is stored in Supabase so the app can persist and sync your data. Provider-backed coaching and voice requests are only sent when you explicitly use those features.
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.
Your choices
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.