Garmin MCPby
WhatsAppFree Garmin service · Sign in to connect
SERVICE PRIVACY
This policy explains how Geekist handles your data when you connect Garmin to your AI assistant.
When you sign in through Geekist, we use your Garmin password and any verification code to complete sign-in. We do not store your password. We encrypt your Garmin session tokens and any Personal API key you add so the service can access your account.
When your authorised assistant requests records, we retrieve them from your connected Garmin account and send them to that assistant. Those records can include activity and health information, including sensitive menstrual cycle data if it is available in Garmin Connect. Your assistant provider’s privacy policy and your account settings govern how it handles the records it receives.
Disconnect in Geekist to remove your stored Garmin connection credentials from the service and stop new requests through that connection. Copies may remain in hosting backups until they expire. Manage records already sent to your assistant through the assistant provider. If you added a Personal API key, you can revoke it separately in Garmin Connect.
Garmin’s own privacy policy explains how Garmin handles the data in Garmin Connect, including health and menstrual cycle information. You can use Garmin’s Account Management Center to access, export, correct or delete the data in your Garmin account.
Geekist counts tool outcomes, active hosted accounts and connection actions to understand how the service is used. We use the network country Cloudflare provides when your browser grants assistant access. Adults can choose to share an age range, gender or both on the Connect page. We count each answer separately and keep grouped totals without account identifiers. The service owner can see demographic groups only when at least five accounts contributed to a group. Daily counts expire after 30 days. Monthly counts expire 30 days after the month ends. Survey participation is optional and does not affect your connection.
Do not send health records, passwords, verification codes or access tokens to support.
To investigate suspicious connections, we record app registration details and connection decisions, including app names, client identifiers and callback addresses without query strings. These records are separate from product analytics, restricted to the service owner, retained for up to 30 days and limited to the most recent 1,000 events. Do not include passwords, verification codes, tokens or health information in app names or callback addresses.
Read our plain-English guide to how connections are protected and what to do if something looks wrong.