diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md
index d83c8c7..2a2bf9b 100644
--- a/docs/ROADMAP.md
+++ b/docs/ROADMAP.md
@@ -618,13 +618,15 @@ Deferred deliberately, in rough priority order:
 - **Migrate Calendula and Agendula onto `core-prefs` + `core-di`**: tracked in
   the kit's roadmap, not here.
 - **Wear OS companion** ([#27](https://codeberg.org/jlmakiola/clockula/issues/27)):
-  blocked on a privacy decision. A watch that shows and controls the phone's
-  timers and next alarm needs a phone-to-watch channel. The usual one, Google
-  Play Services' Wearable Data Layer, is a proprietary dependency that
-  `docs/PRIVACY.md` §2 rules out and that would ship in every channel, since
-  there is one build and no flavours. A channel of our own avoids the
-  dependency but is still a new way for data to leave the phone, which
-  `PRIVACY.md` would have to document next to Auto Backup and crash reports.
-  A standalone watch app with its own timers and alarms and no sync avoids the
-  question, but doesn't control the phone and has no F-Droid route onto a
-  watch.
+  blocked on a privacy and distribution decision. A watch that shows and
+  controls the phone's timers and next alarm needs a phone-to-watch channel.
+  The usual one, Google Play Services' Wearable Data Layer, is a "third-party
+  service" that `docs/PRIVACY.md` §2 rules out, and with one build and no
+  flavours it would also be a non-free dependency in the build F-Droid makes.
+  A channel of our own (Bluetooth, since there is no INTERNET permission)
+  avoids the dependency but adds permissions and a new way for data to leave
+  the phone, which `PRIVACY.md` §5 currently says only crash reports do.
+  Two routes need no channel in Clockula: a third-party watch app can already
+  drive Clockula through the `AlarmClock` intents (ARCHITECTURE §17), and a
+  standalone watch app with its own timers and alarms doesn't touch the phone,
+  though it has no F-Droid route onto a watch.