What the SOS Community Alert app accesses and why
This notice explains phone permissions and data flows for the SOS Community Alert mobile app. Read this before installing and granting permissions.
| Permission | Why we need it | When data leaves your phone |
|---|---|---|
| Location (While Using) | Coarse location check until 15 mph, then a closer check during a ride. A map point is attached only when you send or confirm an alert. | Only when you send or confirm an alert |
| Location (Always) | Same check with the screen off. The closer check runs during a ride. After the bike has been still for 15 minutes, the watch pauses until the phone moves. | Processed on-device for ride logic; GPS sent only on alert |
| Notifications | Ride monitoring status; crash countdown when app is backgrounded | Not sent externally — local notifications only |
| Motion sensors | On-device impact / sudden-stop detection while riding | Not sent unless an alert is triggered |
| Field | Stored on phone | Sent to Discord when alerting |
|---|---|---|
| Display name | Yes | Yes — shown in alert embed |
| Discord user ID | Yes | Yes — used for @mention |
| Relay token | Yes (encrypted) | Sent to relay for authentication only — not shown in Discord |
| GPS coordinates | Temporarily during ride | Yes — map links in alert message |
Anyone in your Discord server with access to SOS channels can see alert content, including your name, @mention, and location links. Treat SOS channels as sensitive community spaces.
You can revoke location and notification permissions in your phone Settings at any time. You can leave the Discord server to stop receiving community alerts.