Last updated: 9 August 2026
GRITFIT uses processors to operate the service. The exact product, region and data scope depend on the approved production configuration.
| Function | Provider or service category | Data involved | Purpose |
|---|---|---|---|
| Authentication, application hosting, database and private object storage | Google Cloud and Firebase services | Account identifiers, app records, private media and technical security data | Sign-in, server operation, storage and security |
| Private-beta email and operational email | Brevo | Email address, subscription status and delivery data | Requested beta and service communications |
| Website abuse prevention | Google reCAPTCHA | IP address, browser/device and interaction signals | Protect forms from automated abuse |
| GRITFIT Coach language generation | Contracted third-party commercial large language model (LLM) infrastructure provider | Coach request content and purpose-specific structured training context | Generate language output within GRITFIT’s controlled workflow |
| Apple Health or Health Connect | Apple or Google platform service selected by the user | Health categories authorised by the user | Optional connected-health import |
The production language-model provider identity, processing locations and contract controls must match GRITFIT’s verified processor register before this list is authorised for publication.
Material processor changes will be reflected here and notified where required. Questions may be sent to support@gritfit-ai.com.