This page documents the opt-in methods used by SafetyCheck to obtain consent from recipients before sending automated SMS messages. This page is provided for carrier compliance verification.
SafetyCheck obtains SMS consent exclusively through the mobile app onboarding process. There are two categories of SMS recipients, each with a distinct opt-in flow shown below. No website forms, keyword opt-in, or paper forms are used.
| Requirement | Flow 1 — App user | Flow 2 — Emergency contact |
|---|---|---|
| Phone number field at point of opt-in | ✓ Yes | ✓ Yes |
| Consent language adjacent to number field | ✓ Yes | ✓ Yes |
| Checkbox required | Accept via button | ✓ Explicit checkbox |
| Privacy Policy linked at point of opt-in | ✓ Yes | ✓ Yes |
| Terms of Service linked at point of opt-in | ✓ Yes | ✓ Yes |
| STOP instruction disclosed at opt-in | ✓ Yes | ✓ Yes — in opt-in SMS |
| Opt-in confirmation SMS sent | ✓ Yes | ✓ Yes |
| Website form opt-in | Not used | Not used |
| Keyword text opt-in | Not used | Not used |
All recipients can manage their SMS preferences by replying with these keywords to any SafetyCheck message:
STOP response: SafetyCheck: You have been removed and will no longer receive safety alerts. mysafetycheck.app
HELP response: SafetyCheck: Emergency contact alerts only. No marketing. To opt out reply STOP. Support: [email protected]
Frequency: Event-driven only. Emergency contacts receive 0–2 messages per month on average. Messages only fire on genuine safety events (missed check-in or SOS). No promotional or broadcast messages.
Rates: Message and data rates may apply. Recipients are responsible for carrier charges.
Sender: US messages use a 10DLC-registered long code. UK/EU/AU use alphanumeric sender “SafetyCheck”. West/East African destinations (CI, CM, NG, GH, SN, ET) use WhatsApp for reliable delivery.