Glimpzed · A2P 10DLC Compliance

SMS Consent Flow

How Glimpzed captures explicit, unchecked-by-default consent before any safety SMS is sent to a Trusted Contact.

📋 Compliance documents — direct links

This SMS consent flow is governed by both documents below. Reviewers should open both directly:

📄 Privacy Policy — see Section 5A "SMS Communications (Twilio)". Contains: mobile-number non-sharing statement, message frequency, "message and data rates may apply", full STOP/HELP keyword handling.
📄 Terms of Service — see Section 11B "SMS Consent & Non-Sharing" and Section 11A on biometric / safety-feature data sharing.

Both are publicly accessible (no login), publicly indexed, and linked from the app's Trusted Contact add flow.

Required consent disclosures (repeated here from Privacy Policy §5A):

Message frequency: event-driven. Fewer than 5 messages per year in typical use. 1–3 messages in a short window during an active SOS or Safe Meet incident. No routine, scheduled, marketing, or promotional messages.
Message and data rates may apply. Standard carrier rates apply. Glimpzed does not charge for SMS delivery.
Non-sharing: Glimpzed does not share, sell, rent, lease, disclose, or transfer mobile phone numbers or messaging consent to any third party or affiliate for marketing or promotional purposes.
Reply STOP to opt out at any time. Reply HELP for support.

Overview

Glimpzed is a proximity-social + safety mobile app (iOS + Android). We use SMS only for two safety-critical purposes: Emergency SOS alerts and Safe Meet overdue check-in alerts. We never send marketing, promotional, transactional, or subscription SMS of any kind.

Because Glimpzed's SMS recipients (a user's Trusted Contacts) are added inside the mobile app rather than through a website form, this page exists to give A2P 10DLC campaign reviewers a public-facing description of the exact consent flow.

Who receives Glimpzed SMS

Only Trusted Contacts a Glimpzed user has explicitly designated inside the app receive SMS from Glimpzed. There is no bulk list, no marketing list, no subscription signup. A Trusted Contact is typically a family member, close friend, or roommate the account holder wants notified if they trigger SOS or become overdue on a Safe Meet check-in.

How consent is captured (step-by-step)

The account holder opens the Glimpzed app on their own device Glimpzed is a phone-authenticated app — the account holder verified their own mobile number via Firebase Phone Auth OTP at signup. They are 18+ (age-gated at signup; see our Terms of Service §2).

They navigate to Vibe → Trusted Contact → Add Contact This is a deliberate, multi-tap navigation path. No default contact is added on our end.

They enter the Trusted Contact's name and mobile number Either by typing manually or by picking from their device's Contacts (with explicit Contacts-permission prompt). The account holder is representing that this is a person they have permission from — see step 4.

They tick a required, unchecked-by-default consent checkbox The "Save" button is disabled until the checkbox is affirmatively ticked. The checkbox reads exactly as follows:

They tap "Save" The Trusted Contact record is stored on the user's device and in Glimpzed's Firestore backend. No SMS is sent at this point.

SMS is only sent when a safety event fires The Trusted Contact receives SMS only if (a) the account holder taps the Emergency SOS button, or (b) a Safe Meet check-in that the account holder scheduled becomes overdue. No SMS is sent on any other trigger.

Screenshots of the in-app consent dialog

Screenshots below show the exact Trusted Contact add dialog with the consent checkbox unchecked (Save disabled) and checked (Save enabled). Reviewers can verify that consent is affirmative, not preselected.

Add Trusted Contact dialog — consent checkbox UNCHECKED, Save button greyed out / disabled. Proves that consent is required before the account holder can complete the add-contact action. — Screenshot 1 — consent checkbox **UNCHECKED**, "Save" button disabled (greyed out).

Add Trusted Contact dialog — consent checkbox CHECKED, Save button active/blue. Proves that after the user affirmatively ticks the consent checkbox, and only then, they can complete the add-contact action. — Screenshot 2 — consent checkbox **CHECKED**, "Save" button active.

Screenshots taken 2026-07-11 from a live Glimpzed Android build. The verbatim consent text visible in both screenshots matches the app source at lib/screens/trusted_contacts_page.dart:611-615. Note that name/phone fields are shown empty for privacy — no real Trusted Contact PII is exposed.

Required disclosures

Message frequency Event-driven. A typical Trusted Contact receives fewer than 5 messages per year. During an active SOS or Safe Meet incident, a Trusted Contact may receive 1–3 messages in a short window. No routine or scheduled messages are sent.

Message and data rates Standard message and data rates from the recipient's mobile carrier may apply. Glimpzed does not charge for SMS delivery.

Mobile phone number non-sharing Glimpzed does not share, sell, rent, lease, disclose, or transfer mobile phone numbers or associated consent to any third party for that third party's marketing or promotional purposes. Numbers are transmitted to our SMS provider (Twilio Inc.) solely to deliver the specific message the account holder has authorized.

Purpose limitation SMS is used only for Emergency SOS alerts and Safe Meet overdue check-in alerts. Glimpzed does not send marketing, promotional, subscription, recurring, or bulk SMS of any kind.

Opt-out (STOP) and help (HELP) keywords

Trusted Contacts can opt out of receiving Glimpzed SMS at any time by replying STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT to any Glimpzed message. Opt-out is honored immediately by our SMS provider — no further messages will be sent to that number by Glimpzed from any account until they opt back in by replying START.

Recipients seeking help may reply HELP or INFO to any Glimpzed SMS to receive an automated informational response, or email support@glimpzed.app.

Sample SMS content

Emergency SOS

Glimpzed SOS: [First Name] triggered an emergency alert at [time]. Approximate location: [map link]. Reply STOP to opt out.

Safe Meet overdue check-in

Glimpzed: [First Name]'s Safe Meet check-in was due at [time] and has not arrived. Last known location: [map link]. Reply STOP to opt out.

Legal references

Privacy Policy — full data-handling terms, including §5A "SMS Communications (Twilio)" which duplicates the disclosures above for the account holder's own reference at signup
Terms of Service — §2 (18+ Age Attestation), §11A (biometric consent), and §Safety-Feature Use (Trusted Contact designation and consent representation)