Opt-in UI evidence screenshots
Current SMS opt-in views used for consent-flow verification and compliance documentation.
Click either screenshot to view a larger version.
This page documents EmberDeck SMS opt-in behavior, consent language, and compliance-facing evidence requirements.
Current SMS opt-in views used for consent-flow verification and compliance documentation.
Click either screenshot to view a larger version.
Last Updated: March 12, 2026
This page documents the EmberDeck SMS opt-in flow and consent language for messaging compliance review.
Business and brand:
Program purpose:
Settings > Notifications > SMS.Save SMS settings.YES to complete enrollment (double opt-in).YES confirmation is received.Displayed at opt-in:
I agree to receive recurring transactional SMS alerts from EmberDeck (event outcomes, account/security notices, version or service updates, and reminders). Message frequency varies. Msg and data rates may apply. Reply STOP to opt out and HELP for help. Consent is not a condition of purchase.
Enrollment confirmation:
EmberDeck: Reply YES to confirm SMS enrollment for account and event alerts. Msg frequency varies. Msg and data rates may apply. Reply HELP for help, STOP to opt out.
Transactional example:
EmberDeck: Event [event_name] for project [project_id] failed at [time_utc]. Error: [error_code]. Reply HELP for help, STOP to opt out.
Security example:
EmberDeck Security: New sign-in detected at [time_utc]. If this was not you, contact support@emberdeck.xyz. Reply HELP for help, STOP to opt out.
STOP.HELP.START or YES, where required).Text messaging originator opt-in data and consent are not shared with third parties or affiliates for their own marketing or promotional purposes.