Dev Role

SMS Compliance

Public documentation for transactional SMS consent and privacy controls.

1. Overview

MyBoatOS sends transactional SMS only. Current primary recipients are operators, captains, and crew using authenticated MyBoatOS workflows.

2. Opt-in Process

The active opt-in flow is inside authenticated user onboarding and settings. Users provide or confirm mobile numbers and explicitly consent to SMS in-product.

  • Operator onboarding: `/onboarding`
  • User profile phone confirmation: `/settings/profile`
  • SMS preferences and consent: `/settings/notifications`

By providing your mobile number, you agree to receive operational text messages (SMS) from MyBoatOS about assignments, trip operations, schedule changes, and critical alerts. Message frequency varies. Message and data rates may apply.

Public opt-in details URL: /sms-opt-in

Note: authenticated app routes are not used as reviewer proof URLs; this page contains the externally accessible evidence set.

3. Example Messages

  • “Crew assignment updated for tomorrow’s trip.”
  • “Schedule change: trip check-in moved to [time].”
  • “Operational alert: review trip instructions in MyBoatOS.”

4. Opt-out

Reply STOP to unsubscribe from SMS messages.

Reply HELP for assistance.

Support contact: support@myboatos.com.

5. Privacy

Mobile data is used only for authenticated operational communication and trip coordination.

No mobile information will be shared with third parties/affiliates for marketing/promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

6. Visual Proof

Settings profile page showing phone input and SMS consent disclosure
Authenticated profile flow: phone confirmation with visible SMS consent disclosure.
Settings notifications page showing SMS opt-in checkbox and consent language
Authenticated notification preferences flow: explicit SMS consent and STOP/HELP language.