Privacy

Remote for Muse connects your Garmin watch or Edge to Meta's Muse agent. This relay, run by Falkster.com (San Francisco, California, USA), sits in between and keeps only what the two need to talk to each other.

What you send with Remote for Muse goes to Falkster.com, not to Garmin, and Garmin isn't responsible for it. 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. Remote for Muse is offered in every country, so wherever you use it from, your data is processed where the relay runs.

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.)
• 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, approvals and pause/resume/cancel requests for Muse's tasks), with up to 200 characters of the Muse message you're answering.
• Voice messages: the audio you record on the device, and its transcript if one is made.
• 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.
• What Muse sends back for your device: a status line, quick prompts, replies, cards, questions, approvals (with the recipient, cost and details Muse fills in), tasks and an action history.
• Workouts and routes Muse 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 Remote (Ride) for Muse 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.

What you say or type, and what Muse 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 Muse" complication that any watch face on your watch can display; with private display on it shows "New update". The Remote Face for Muse 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 and Muse's access tokens, never the tokens themselves. It does not ask for your name, email or Garmin account. Your IP address is used, in memory only, to rate-limit registering and pairing; 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.

Why, and on what basis

So Muse can 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.

You use Remote for Muse with Meta's Muse and under Muse's terms; the relay processes your data to provide the connection you set up between your device and Muse.

Health data (vitals, recovery and workouts) is processed only with your explicit consent. 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 Muse, are deleted on the schedule below.
• To disconnect Muse, choose Settings > Reconnect Muse on the device. Its token stops working at once and your ride screen is unlinked. Your 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 and its tokens at once, overwriting it 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 Muse already read; do that in Muse. 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.
• 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, transcripts, conversation messages and the inbox Muse reads from: 7 days. Voice recordings: 3 days.
• Cards: until they expire (at most 3 days), then deleted 7 days later. Questions and approvals: deleted 7 days after they expire.
• Tasks: 30 days after their last update. Action history: 30 days.
• 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. Ask Muse for "a copy of my Remote for Muse data": it gets everything the relay holds for your device as a file. Or write to falk@falkster.com.
• Correction. Change your settings and sharing on the device. Readings come from your Garmin; if one is wrong, or something Muse wrote about you is, write to falk@falkster.com and it will be corrected or deleted. Muse can also update or remove its own cards and tasks when you ask it.
• 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.

Muse and Meta

Muse can read everything listed above for your device through its connector to this relay. Once Muse has read something, Meta processes it under Muse's terms and privacy policy, not this one.

Speech-to-text

This relay does not currently transcribe voice messages; Muse receives the recording itself.

Phone alerts

Off unless you turn on phone alerts on your device. Then, when Muse sends something worth an alert (a reply, question, approval, 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 Muse 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 that only says what kind of alert it is, like "Muse needs your approval. Open Remote for Muse.". With private display on, only "Something needs you. Open Remote for Muse." is sent. 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

Remote for Muse and Muse 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

w.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 a code, 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.