Data use when connecting an AI assistant
This page supplements the FITsociety privacy policy for MCP connections, including ChatGPT. The assistant receives the FITsociety records needed for the actions you request within your approved permissions. Those records can include account and booking information, invoices and credits, training and nutrition records, measurements, goals and self-reported health information, documents, and private messages or coach notes. Sensitive modules require the separate consents described below. FITsociety uses the connection to carry out your requested coaching or fitness workflows. Your selected AI provider receives the requested results and handles them under its own terms and privacy policy. Enabled actions can also send data to intended message recipients, connected Google calendars, configured webhook recipients, or push and email delivery providers; those effects are stated in the relevant tool descriptions. Sharing is limited by the connection’s account, company, module, and action permissions. You can review or revoke your AI connection in FITsociety’s connection settings. Revocation blocks future access; it does not recall results already shared with your AI provider or notifications already delivered. Use the contact details in the FITsociety privacy policy for data-rights requests. There are two access surfaces:- Company/coach grants are approved by a Manager or Admin coach.
- Client AI grants are approved by the authenticated client and are bound to that one client. They require the client to be connected to the company and to have client AI access enabled for that relationship, with the company MCP integration feature enabled.
Company scoping
Every MCP credential is bound to one company through its grant. The AI client cannot switch to another company by passing a different company ID. Client AI grants also havesubjectType: "client" and a fixed subjectClientId.
All reads and writes stay on that client.
Feature gates
All grants require the company MCP integration feature. Client AI grants additionally require client AI access for the client-company relationship and the company client MCP policy. If any of these gates is disabled later, the grant can still exist for audit and revocation, buttools/list and tools/call are blocked.
Grant owner checks
Each company/coach grant is owned by the coach who created the API key or approved the OAuth connection. Access requires the owner to retain active company access and aManager or Admin role.
If the owner is removed, deactivated, or demoted, the grant stops working.
Client AI grants are not coach-owned; they are revoked by the client and are
runtime-bound to the approved client subject.
Read-only default
MCP grants are read-only by default. Read-only grants can list, search, inspect, and summarize allowed data, but cannot create or update records.Explicit write tools
Write access requires two separate choices:- The grant must not be read-only.
- The specific write tool must be listed in
allowedWriteTools.
idempotencyKey argument
or params._meta.idempotencyKey. An exact retry with the same key returns the
completed result without applying the change twice.
A timeout or error does not always mean a write failed to save. Keep the same
key when retrying an unchanged request and check the affected record before
starting a new write.
The current write-tool registry is documented on the
Tools & Modules Registry page. It includes company/coach write
tools such as:
create_clientcreate_bookingupdate_attendance- nutrition-plan and nutrition-log editing tools
- recipe create/update/archive tools
- training template, assignment, session, performance, preset, and equipment tools
- WOD create, update, publish, archive, and settings tools
client_ai_log_my_food,
client_ai_log_my_measurement, client_ai_book_my_event, and client_ai_send_message_to_my_coach when the
client approved those tools.
Health data consent
Modules marked withhealth sensitivity require explicit health data consent.
Without that consent, those modules are omitted from tools/list and cannot be
called.
Health-sensitive modules include:
- company/coach modules:
measurements,intake,checkups,habits,goals,documents,nutrition_plans,nutrition_logs,workout, andwod - client AI modules:
client_ai_nutrition,client_ai_measurements,client_ai_habits,client_ai_goals,client_ai_checkups,client_ai_workout, andclient_ai_wod
Company records and external-data grants
Company-owned nutrition records and measurements require an accessible client/company relationship and the MCP connection’s health-data consent. Their reads and writes stay scoped to the connected company; the caller’s date filters and applicable nutrition-plan dates remain enforced. External-data grants are separate permissions for authorized external data sources. Empty, revoked, or date-limited external-data grants do not block or restrict company-owned nutrition records and measurements. Do not grant external-data access to work around an unrelated MCP permission error.Private communication consent
Modules marked withprivate_communication sensitivity require explicit
private communication consent.
Private communication modules include:
conversationsclient_notesclient_ai_documentsclient_ai_messages
Audit logging
Every authenticated MCP request is logged for review. The audit log stores generic execution metadata such as:- grant
- tool name
- status
- error code
- duration
- request IP
- user agent
- argument key names
- identifiers of changed records where available
Request controls
Bearer credentials are accepted in theAuthorization header only.
Requests
must use the supported server host and an allowed browser Origin when one is
supplied.
IP and credential rate limits, per-grant query budgets, and temporary
tool restrictions can reject requests.
See Connection & Protocol
and Troubleshooting & Errors for the public request limits
and retry guidance.