Privacy

Agent Remote connects your Garmin watch or Edge to Anthropic's Claude, using your own Anthropic API key. This relay, run by Falkster.com (San Francisco, California, USA), runs Claude for you: it keeps only what that needs, for a short time, and sends each request to Anthropic under your own API account.

What you send with Agent Remote goes to Falkster.com, not to Garmin, and Garmin isn't responsible for it (the one exception: a workout you confirm for your Garmin Connect calendar, which goes to Garmin). The relay runs on Railway, in the US (US West). Your device reaches the relay over HTTPS through the Garmin Connect app on your phone. Agent Remote is offered in every country, so wherever you use it from, your data is processed where the relay runs, and by Anthropic as described below.

What is collected

• Vitals, only if you share them: heart rate, resting heart rate, stress, Body Battery, steps, calories, floors, intensity minutes, pulse oximetry and respiration rate.
• Recovery, only if you share it: recovery time and VO2 max. (Garmin does not give apps your sleep score or training status.) What you tell Claude about your sleep is kept in your training journal.
• Activities, only if you share them: start time, sport, duration and distance of workouts.
• Prompts: what you send from the device (quick prompts, follow-up taps, typed text, notes, "workout finished" messages, answers and pause/resume/cancel requests for Claude's tasks), with up to 200 characters of the message you're answering.
• No voice: this app doesn't record audio, because the Claude API doesn't take it. You type or tap a quick prompt.
• Preferences: your sharing and alert settings, quiet hours, coaching level, private display, sync interval, phone alerts, time zone offset, and the device's model, type, app version and whether it has a microphone.
• Your Anthropic API key, if you pair with Claude: encrypted at rest with a key kept outside the database. It is never shown again (the pages show only a hint like sk-…a1B2), never exported and never logged. Also your model choice, and the kind of the last error Anthropic reported (such as a rejected key), so the settings page can tell you.
• Memories: short facts you asked Claude to remember, or that Claude saved from what you told it.
• Automations: each one's name, time, days and the prompt Claude runs.
• Training plan: the sessions Claude keeps when you ask it to plan or tell it your plan (date, sport, title, purpose, duration and any workout steps), and whether each was done or skipped.
• Training journal: how a finished workout felt (your effort rating or answer) and any short note you add, kept with that workout and labelled as reported by you.
• What Claude sends back for your device: a status line, quick prompts, replies, cards, questions, tasks and an action history.
• Workouts and routes Claude sends to your device: their name, steps and targets, or a route's GPS points and stops. The file is deleted once your device has it; its name stays in the list and history.
• Ride screen, only if you add the Agent Remote Ride data field: a random ID for it, its model and type (watch or Edge), when it last checked in, and, while you share activities, when an activity starts and stops and its sport. After each activity it also sends its laps: each lap's time, distance, average heart rate, power and cadence, ascent, and for swims the pool lengths, SWOLF, stroke and rest, plus how many fuel reminders and cues it showed.
• Ride screen coaching: cues Claude prepared for your next activity (up to 6 short lines) and a planned workout you agreed to load, for up to 24 hours.
• Connections, only those you add on your settings page: your calendar's secret iCal address, a webhook address, and Garmin Connect's access tokens, each encrypted like your API key. Calendar events are fetched when Claude asks for them and kept in memory for at most 10 minutes, never stored.
• Garmin Connect, only if you link it on your settings page and tick its consent box: a fingerprint of Garmin's random ID for you, Garmin's access tokens (encrypted like your API key), which data you allowed at Garmin, and what Garmin then sends: daily summaries (sleep score and stages, overnight HRV, resting heart rate, stress, Body Battery, steps, intensity minutes, calories, floors, Pulse Ox, respiration, skin temperature change, VO2 max and fitness age) and each activity's summary and laps (time, distance, heart rate, pace, power, cadence, ascent, the device's name). Your watch's sharing choices apply to it too. Never Garmin's activity files, GPS tracks or your Garmin password.
• Sends and loads you confirm: what Claude proposed sending to your webhook (its title and text) or loading on your ride screen, your answer, and whether it worked.
• Usage counts for improving Agent Remote: which features were used and when (a card was posted, a workout reached the device, a card was rated useful), with timings such as minutes from a workout's end to its debrief, and your coaching context setting. Never what you or Claude wrote, and never a reading.

What you say or type, and what Claude writes, can include health or other personal details about you or other people. The relay stores it as described here.

Readings go with each sync (every 5 to 60 minutes, as you set), one sample each time. When you first share workouts, the last 2 days are sent. Before pairing, the device sends only its settings; pair only with the code your own device shows.

The app shows your next item (up to 24 characters) as a "Next from Claude" complication that any watch face on your watch can display; with private display on it shows "New update". The Agent Remote Face sends nothing: it only shows that line and Garmin's own readings on your watch.

The relay identifies your device by a random ID. It stores only fingerprints (SHA-256 hashes) of the device's access tokens and of your settings page link, never the tokens themselves. It does not ask for your name, email or Garmin password: if you link Garmin Connect, you sign in at Garmin itself. Your IP address is used, in memory only, to rate-limit registering, pairing and the settings page; it isn't saved. The relay keeps no request log of its own; the hosting provider logs each request (time, address requested, result) and keeps those logs for 30 days. The logs don't include what you send.

What Claude sees, and Anthropic

Each time you ask something, or an automation is due, the relay sends Claude the recent conversation (the last 24 hours, up to 12 messages), your settings, memories, automations, open questions and tasks. The Garmin data you share is sent only when Claude asks for it with a tool, for example before training advice, and the same goes for laps, your calendar events and what Garmin Connect sent. When Claude searches the web for you, it does so through Anthropic's web search, under the same terms.

When you tap Add it on your watch for a workout Claude proposed for your Garmin calendar, the relay sends that workout (its name, purpose and steps) to Garmin Connect, which then handles it under the Garmin Connect privacy notice and syncs it to your Garmin devices. Answers Claude writes from Garmin Connect data say so: "Insights derived in part from Garmin device-sourced data."

When you tap Send on your watch for something Claude proposed, the relay posts exactly that text to the webhook you added, and the service behind it (Slack, Zapier and so on) handles it under its own terms. The relay never sends anything there without that tap, and never sends your readings as data.

These requests go to Anthropic under your own API account. The Claude API keeps no conversation: the relay sends the context it needs each time. Anthropic's commercial terms and privacy policy govern what Anthropic does with the requests; see anthropic.com/legal/commercial-terms. Anthropic bills your API account for them.

If you pair your own agent instead of Claude, no API key is stored and the relay doesn't run Claude for your device. The agent you connect can read everything listed above for your device through its token, and once it has, its provider's terms apply, not this policy.

Why, and on what basis

So Claude (or your own agent) can answer you, coach you and act on your requests with context from your device, and so its replies, questions and progress reach your wrist. Nothing is sold, used for advertising, or shared with anyone other than as described here. The relay processes your data to provide the service you set up between your device and Claude.

Health data (vitals, recovery and workouts) is processed only with your explicit consent (GDPR Art. 9). Before anything is shared, the app shows what is shared, why, who receives it and for how long, and asks you to agree. The relay records when you agreed and to which version of this text, and stores no health data without that record. You can withdraw consent at any time by turning sharing off on the device; the relay then deletes the readings it holds.

You're in control

• Health data is off until you turn it on. On the device you choose, per category, whether vitals, recovery and activities are shared. Turning a category off stops new data and, at the device's next sync, deletes the readings the relay holds for it. Messages that mention them, like "Finished running: 8.1 km" or a card from Claude, are deleted on the schedule below.
• Your settings page shows your training plan, your training journal, what Claude remembers and the automations it runs; delete any of them there. You can also replace your API key or change the model there.
• To disconnect Claude, choose Settings > Reconnect on the device. Your API key and settings link are deleted at once and your ride screen is unlinked. Your other data stays until it expires, and whoever pairs next with the new code can read it.
• To delete your data, choose Settings > Delete my data. The relay deletes your device, its data, your API key and its tokens at once, overwriting them in the database; a linked ride screen is only unlinked. Backups of the relay's storage, where the hosting provider keeps any, hold deleted data until they expire. The relay can't delete what Anthropic (or your own agent) already received. The app then starts over as a new device and keeps your sharing choices, so turn sharing off first if you want nothing sent again.
• To disconnect Garmin Connect, use Disconnect on your settings page, or remove Agent Remote in Garmin Connect. Either way the relay deletes what Garmin Connect sent and its tokens, and Garmin stops sending. Reconnecting or deleting the device also tells Garmin to stop.
• Removing the app deletes nothing on the relay by itself: a device that stops checking in is deleted after 180 days. To have it deleted sooner without the device, contact falk@falkster.com.

How long it's kept

• Vitals and recovery: 7 days. Activities: 30 days.
• Prompts, conversation messages and the inbox Claude reads from: 7 days.
• Cards: until they expire (at most 3 days), then deleted 7 days later. Questions: deleted 7 days after they expire.
• Tasks: 30 days after their last update. Action history: 30 days.
• Memories and automations: until you or Claude delete them, or the device is deleted.
• Training plan: 120 days after a session last changed. Training journal: a year. Either sooner if you or Claude delete it, or when the device is deleted.
• Laps: 120 days. Ride screen cues and a workout you agreed to load: up to 24 hours, deleted a day later. Sends and loads you were asked to confirm: 30 days. Usage counts: 180 days.
• Connections: until you remove them on your settings page, or the device is deleted.
• From Garmin Connect: daily summaries 60 days, activities 30 days, laps 120 days; all of it at once when you disconnect Garmin Connect.
• Your encrypted API key: until you replace it, reconnect or delete your data.
• Your status line, quick prompts, preferences and phone alert topic: as long as the device exists.
• Which alerts were sent to your phone: 24 hours, so none is sent twice.
• Workouts and routes: the file is deleted once your device has it, or after 7 days; the record of it 7 days later.
• A ride screen is unlinked when you reconnect or delete the device, and deleted after 180 days without checking in.
• A device that hasn't checked in for 180 days is deleted with all of its data. One that registered but was never paired is deleted after a day.
• The hosting provider's request logs: 30 days. Backups of the relay, if any: 7 days.

Your rights

• A copy. On your settings page, choose "download everything the relay holds for your device", or write to falk@falkster.com. (An agent you connected yourself can also fetch it with export_data.) Your API key is never included.
• Correction. Change your settings and sharing on the device, and memories and automations on your settings page. Readings come from your Garmin; if one is wrong, or something Claude wrote about you is, write to falk@falkster.com and it will be corrected or deleted.
• Deletion. On the device with Settings > Delete my data, or, if you no longer have the device, by writing to falk@falkster.com.
• Withdrawing consent. Turn sharing off on the device at any time; it doesn't affect what was done before.

The relay holds no name or account, so in a request say which device it was (Settings > About shows its ID) and roughly when you last used it. Requests are answered within 30 days. If you're in the EU or UK, you can also complain to your data protection authority.

Phone alerts

Off unless you turn on phone alerts on your device. Then, when Claude sends something worth an alert (a reply, question, task update or card), the relay sends that alert's title and short text to the ntfy server at ntfy.sh, which delivers it to the ntfy app on your phone under its own terms. The text is the start of what Claude wrote, so it can include your health numbers (a briefing often starts with them); the relay never sends your vitals, recovery or activities as data. On your phone alerts page you can switch to a fixed line, titled “Agent Remote”, that only says what kind of alert it is: “New reply from Claude. Open Agent Remote.” for a reply, “Claude has a question. Open Agent Remote.” for a question, “New card from Claude. Open Agent Remote.” for a card, and “A task needs you. Open Agent Remote.” or “Task update from Claude. Open Agent Remote.” for a task. With private display on, only “Something needs you. Open Agent Remote.” is sent, whatever that setting. Anyone who knows your alert topic can read your alerts and post to it, so keep it private. Turning phone alerts off stops this at the device's next sync and discards the topic; alerts already sent stay with ntfy and on your phone under ntfy's rules.

Not medical advice

Agent Remote and Claude give coaching and general wellness information, not medical advice. Garmin's readings are estimates. Talk to a doctor about health concerns, and in an emergency call your local emergency number.

This website

agent.falkster.com uses Google Analytics, through falkster.com’s Google Tag Manager, to count visits and see which pages help. It runs under Google Consent Mode. Until you accept, no analytics cookies are set and Google receives only cookieless signals (such as the page, the time, the browser type and a rough location from your IP address), which it uses for aggregate counts. If you accept, Google Analytics sets cookies on falkster.com to recognise repeat visits. There are no ads, nothing is sold, and nothing tracks you across other sites. The pairing page, where you type your API key, and pages with tokens or alert links never load it.

Your choice is stored in a cookie for six months and covers every falkster app site. Change it at any time with Cookie settings at the bottom of every page (without JavaScript, nothing is loaded at all). Google describes its processing in How Google uses information from sites that use its services. The site’s host, Railway, logs each request (time, address requested, result) to run the service.

Contact

Questions or requests: Falkster.com, San Francisco, California, USA, falk@falkster.com.

Last updated 7 November 2026. See also the terms of use.