GFD is in private development, is not open for public registration and does not yet process real athlete data. This page records the intended private-alpha privacy boundary in plain language; it must be reviewed again before the first real athlete and before any broader alpha.
Information GFD is designed to handle
For an explicitly authorised athlete, GFD may handle account identity, goals, availability, training plans, workout completion and feedback, performance evidence, consent choices, and health or restriction information the athlete deliberately supplies. Connected-provider data is not active in the current environment.
Why it is used
Information is used to provide the athlete-facing account, planning, progress, safety, export and deletion functions the athlete requests. Provider connection does not itself change plan authority or permit unrelated profiling, advertising, marketing or population learning.
Storage, access and security
GFD uses managed cloud, authentication, database and private object-storage services. Technical controls include encrypted transport, scoped access, revocable sessions, private objects, audit evidence and tested export, deletion and recovery procedures. No security control is described as an absolute guarantee.
Retention, export and deletion
GFD is designed to provide exact-athlete export, consent withdrawal and an account-deletion workflow with a cooling-off period. Retention choices for real users still require Owner and professional review. Minimal payload-free audit or deletion evidence may be retained only where the approved policy permits it.
Current development state
Only synthetic staging data is currently authorised. No Google Calendar, fitness-provider or athlete-facing AI connection is active. This disclosure will be re-reviewed against the exact deployed product before Athlete #1.
Privacy questions from an authorised tester should use the private contact route supplied during onboarding. No public support inbox or public signup is active.