1. A signed-in user chooses SMS
SMS is an optional notification channel on eligible plans. Account creation, purchases, and core email notifications do not require SMS enrollment.
SMS consent
Transactional mobile alerts are optional and user-controlled.
This page documents the authenticated web-form opt-in used by Obsidian Guard. It is public so messaging providers and users can review the complete consent flow without signing in.
Opt-in workflow
Consent is separate from account access and billing.
2. The user gives affirmative consent
The consent checkbox begins unchecked. The verification-code action remains unavailable until the user enters a phone number and checks the disclosure.
3. The user verifies the destination
Obsidian Guard sends a one-time code. SMS notifications are not enabled until the user enters that code successfully.
4. The user remains in control
The user can disable SMS in settings or reply STOP. START or UNSTOP requests re-enrollment, and Obsidian Guard requires the number to be verified again.
Consent-screen demonstration
SMS mobile alerts
Transactional verification codes, approval requests, security alerts, and related account activity. SMS messages link back to authenticated Obsidian Guardpages and never contain approval credentials.
Demonstration only. This public page does not collect phone numbers or enroll visitors. The live control is available only to an authenticated user on an eligible plan.
Message purpose
Verification codes, approval requests, security alerts, and related account activity. SMS consent is not consent to marketing messages.
Frequency and cost
Message frequency varies with protected activity and notification preferences. Message and data rates may apply.
Help and opt-out
Reply STOP to opt out, START or UNSTOP to request re-enrollment, and HELP for help. Users may also disable SMS in product settings or email [email protected].