Garmin MCPby
WhatsAppFree Garmin service · Sign in to connect
SECURITY
Learn how your Garmin connection is protected and what to do if a connection looks unfamiliar.
Your browser and assistant connect to Geekist over HTTPS, and Geekist connects to Garmin over HTTPS. Your Garmin data is processed by Geekist and sent to the assistant you authorise; it is not end-to-end encrypted between Garmin and your assistant.
Garmin may ask you for a verification code when you sign in. We use your password and any code to complete sign-in and do not store your password. We encrypt your Garmin session tokens and any Personal API key you add using AES-256-GCM before storing them.
Your connection is kept separate from other users’ connections. An assistant needs your permission to connect. Read and write permissions are separate, and supported changes require your confirmation. Only approve an app when you recognise it and started the connection.
Owner and administrator tools require a separate Cloudflare Access verification. Access is limited to approved people and the current assistant connection, and expires after 15 minutes.
An app supplies its own name, so a familiar name alone does not prove who made it. Check the destination shown on the approval screen. Some desktop apps return to a local address on your own device. If you did not start the connection or are unsure, choose Deny and contact us.
We limit repeated connection and sign-in requests. We keep a private, limited record of app registrations and connection decisions to investigate security concerns, whether or not you contact us. Redirect query strings, passwords, access tokens and Garmin health records are excluded. These records are kept for up to 30 days, subject to a 1,000-event limit.
Disconnect your Garmin account from Geekist to remove its saved connection and stop existing assistant connections. Remove the connection in your assistant too. If you added a Personal API key, revoke it in Garmin Connect. Change your Garmin password if you think it was exposed.
Contact us by email or WhatsApp using the support page. Tell us what happened and which assistant you were using. Do not send passwords, verification codes, access tokens or health records.