SMS compliance documentation

Match’a SMS Alerts Consent

Match’a sends SMS alerts only to users who explicitly opt in from inside their logged-in Match’a account.

SMS consent is optional. Users can continue using Match’a without enabling SMS alerts.

How users opt in

  1. A logged-in user sees the “Enable text alerts” button inside Match’a.
  2. The user taps “Enable text alerts.”
  3. Match’a opens the user’s SMS app with a prefilled message: MATCHA VERIFY [one-time token].
  4. The user must manually send this text to Match’a’s Twilio number.
  5. SMS alerts are only enabled after Match’a verifies the one-time token and links the phone number to the logged-in Match’a account.

Message frequency varies, typically up to 4 messages per month. Message and data rates may apply. Reply STOP to opt out. Reply HELP for help.

Match’a does not send private match details, names, or relationship information by SMS.

Legal links

Review the Privacy Policy and Terms.

Sample SMS messages

Sample 1

Match’a: text alerts are now on for new intro alerts only. Msg frequency varies. Msg&Data rates may apply. Reply STOP to opt out, HELP for help.

Sample 2

Match’a: a new intro is ready. Open Match’a to review it: https://www.match-a.app/dashboard/matches Reply STOP to opt out.

Opt-in flow evidence

Match’a opt-in screen showing the new intro alerts card and text alerts button.
Logged-in user sees the text alerts CTA.
SMS app with MATCHA VERIFY and a one-time token prefilled.
SMS app opens with MATCHA VERIFY and a one-time token prefilled.
Match’a notification settings showing text alerts on for a verified phone number.
SMS alerts are enabled after the user manually sends the text and Match’a verifies the token.