Mobile App SMS Opt-In Process for Golizia

This document outlines the in-app SMS opt-in flow for users of the Golizia mobile application. This process is specifically for obtaining user consent to receive transactional SMS messages, such as Two-Factor Authentication (2FA) verification codes, as part of our security procedures. This page is provided for review by The Campaign Registry (TCR) and other relevant parties.

Step 1: User Initiates Action Requiring Verification

The user initiates an action within the Golizia mobile application that requires phone number verification. This typically occurs during:

New account registration.
Logging into an existing account (if 2FA is enabled or triggered).
Performing sensitive account changes (e.g., password reset).

The application screen clearly indicates that verification is required to proceed.

Golizia app screen triggering 2FA or showing context for phone verification

Step 2: Age Verification (Age Gate)

Before proceeding to phone number verification for features like 2FA, the user encounters an age verification step. This ensures compliance with our community guidelines which require users to be 18 years or older.

The user is prompted to select their date of birth.

A button, typically labeled "Select Date of Birth" or similar, is presented.
Upon tapping this button, a calendar or date picker interface appears.
Important: This calendar is designed to only allow the selection of dates that would result in the user being 18 years of age or older as of the current date. Dates that would make the user younger than 18 are not selectable or are greyed out.

Golizia app age gate - initial prompt or button to select date of birth

Golizia app age gate - calendar/date picker interface with restricted dates

There is also a button or link, such as "Cannot find my date of birth?" or "Age Requirement Info".

If the user taps the "Cannot find my date of birth?" button, an explanation is displayed:

"Please note that our community is for individuals aged 18 and up. The calendar will only display dates that result in an age of 18 or older."

Golizia app age gate - explanation message after tapping 'Cannot find my date of birth?'

Only after successfully selecting a valid date of birth (confirming they are 18+) can the user proceed to the next step.

Step 3: User Provides Phone Number

After successful age verification, the user is presented with a screen or a modal dialog prompting them to enter their mobile phone number for 2FA. The interface clearly states that the phone number will be used to send a one-time verification code via SMS for security purposes.

For example, the text near the input field might read: "Your phone number will be used to receive a one-time verification code via SMS, MESSAGES AND DATA RATES MAY APPLY."

Golizia app screen for phone number input for 2FA

Step 4: User Explicitly Requests the SMS Code

After entering their phone number, the user must take an explicit action to request the SMS verification code. This is typically done by tapping a button.

The button is clearly labeled with text such as:

"SEND VERIFICATION CODE"
"SEND"
"VERIFY NUMBER"
"CONTINUE" (if the context is clear that the next step is SMS verification)

This action signifies the user's direct consent to receive a single, transactional SMS message containing the verification code to the phone number they provided.

Golizia app screen showing the 'Send Code' button for 2FA SMS

Step 5: User Receives SMS Verification Code

Upon requesting the code, the user receives an SMS message containing the one-time verification code. The message clearly identifies Golizia as the sender and provides the code.

Example SMS message content:

Your Golizia verification code is 123456.

The user then enters this code into the app to complete the verification process.

User Consent and Message Nature

The opt-in for these SMS messages is explicit and user-initiated within the Golizia mobile application, following successful age verification. Consent is obtained at the point where the user provides their phone number and actively requests the verification code by tapping a button.

These messages are strictly transactional and are sent for the sole purpose of user identity verification and account security (e.g., Two-Factor Authentication). They are not used for promotional or marketing purposes without separate, explicit consent obtained through a different mechanism.