At Glimpzed, we take your privacy seriously. This Privacy Policy explains what information we collect, how we use it, how long we retain it, and your rights regarding your personal data. By using Glimpzed, you consent to the practices described in this policy.
We collect information you provide directly and information generated by your use of the App:
Profile Information: Your name (or display name), age, gender, pronouns, bio, photos, and preferences you enter when creating or editing your profile.
Location Data: Your real-time GPS coordinates, used to identify nearby users. We collect your location only when the App is in use (foreground) unless you have granted background location permissions.
Usage Data: Information about how you interact with the App, including connections made, profiles viewed, messages sent, and features used.
Device Information: Device type, operating system version, and app version, used for diagnostics and service improvement.
Communications: Messages you send through the in-app chat feature. Messages are stored securely in our cloud database and are accessible only to the participants in that conversation.
Trusted Contact Information: If you choose to designate one or more Trusted Contacts for Safe Meet and Emergency SOS, we store the name and phone number you enter. These are stored in our cloud database so they remain available across your devices and after reinstall. You can review, edit, or remove your Trusted Contacts at any time from Vibe → Trusted Contacts.
Safety-Feature State: When you activate Safe Meet, we store the matched user's identifier, your planned check-in time, the trusted contact you nominated (first name only), and the time you notified them. This record lives on your device and on our servers so you can manage the Safe Meet from anywhere in the App. It is automatically removed when you mark yourself safe, cancel, or 24 hours after the planned check-in passes (whichever comes first).
We use the information collected to:
We do not use your data for targeted advertising, and we do not sell your personal information to any third party.
Location is the core feature of Glimpzed. We use your location to:
You can revoke location permissions at any time via your device settings. This will prevent the App from showing your location to others or showing you nearby users.
Your profile data, account information, and settings are stored securely on Firebase (Google Cloud) servers. Data is retained for as long as your account is active. You may delete your account and all associated data at any time via Settings > Account > Delete Account.
In-app connections expire after 24 hours by design. Expired connections are retained for up to 48 hours for re-connection purposes, then permanently deleted.
Chat messages are retained until deleted by you or the other party. Disappearing messages are automatically removed after the duration you select.
After Account Deletion — Limited Safety-Audit Record: When you delete your account, all profile information, photos, messages, connections, knocks, beacons, and activity history are removed from our active systems. We do, however, retain a minimal "deletion record" indefinitely for the limited purpose of investigating safety incidents. This record contains: (a) your permanent Glimpzed user ID (an opaque identifier issued by Firebase Authentication that is never re-assigned to another user); (b) the time of deletion; (c) the cryptographic hash (SHA-256, one-way) of your lowercased email address; (d) cryptographic hashes (SHA-256) of each profile photo that was on file; (e) the sign-in method you used; and (f) a snapshot of your first name, age range, and gender only. The deletion record CANNOT be reversed to reconstruct your email, your photos, your full name, or any other personal data. Its only purpose is to allow law enforcement, with appropriate legal process, to confirm whether a user with a given Glimpzed ID existed and whether a photo they hold matches a photo this account had on file. If you wish to request deletion of this audit record as well, you may contact privacy@glimpzed.app — note that we may decline where retention is required by applicable safety, law-enforcement, or legal-hold obligations.
For troubleshooting, safety-incident investigation, and to satisfy lawful-process requests, we record a minimal audit log of actions you take in the App. Each entry contains: (a) the action type (e.g. "safe_meet_started", "sos_activated", "knock_sent", "match_created", "mode_changed"); (b) the time the action occurred; (c) the opaque Glimpzed user ID of the other party, when an action involves a specific user; and (d) a small set of non-identifying parameters (for example, the duration in minutes of a Safe Meet).
We DO NOT record in this audit log: the content of any message you sent, photo bytes or URLs (including Glimpses), the text of your Pulse / Beacon / knock notes, GPS coordinates or addresses, or any other free text you typed. The log is structured action metadata only.
Storage: entries are written to a private Firestore subcollection scoped to your account (app_log/{your-uid}/events/). Only you (when authenticated) can read your own log. Glimpzed staff may access logs in response to a verified law-enforcement request, in good-faith response to a credible imminent-harm report, or to diagnose a bug that you have explicitly reported.
Retention: audit-log entries are retained for two (2) years from the time of the action, after which they are eligible for automated deletion. Entries tied to an unresolved safety report or open legal hold may be retained longer. You may request deletion of your audit log by contacting privacy@glimpzed.app; we may decline where retention is required by applicable safety or law-enforcement obligations.
We do not sell, rent, or share your personal information with third parties for their marketing purposes.
We use the following third-party services to operate the App:
Firebase App Check (security attestation): Every API call from the App to our Firebase backend carries a short-lived "attestation token" that proves the call came from the genuine Glimpzed APK on a non-tampered device, not from curl, Postman, an emulator, or a modified build. The token contains no personal data — it is a cryptographic attestation only. This protects every Glimpzed user from API enumeration / scraping attacks.
Sharing Through Your Device: Certain safety features (Safe Meet share, Safe Meet modify/cancel follow-up, SOS "I'm safe" follow-up, and the photo share offered during SOS-during-Safe-Meet) compose a message on your behalf and hand it to your device's native SMS application or system share sheet. From that point forward the message — and any attached photo — leaves Glimpzed's control and is transmitted by your phone's carrier or chosen app under the privacy practices of those services. Except for SMS messages sent server-side via our SMS provider Twilio Inc. (see Section 5A below), Glimpzed does not transmit SMS, MMS, or share-sheet content directly.
Glimpzed sends SMS text messages on your behalf from Glimpzed's servers via our SMS provider, Twilio Inc. ("Twilio"), for the following safety-related purposes only:
Recipient consent — Trusted Contacts: By adding a phone number to your Trusted Contacts list within the Glimpzed app, you represent that you have obtained the contact's permission to send them safety-related SMS on your behalf. Trusted Contacts may opt out of receiving Glimpzed SMS at any time by replying STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT to any Glimpzed message. Once opted out, no further SMS will be sent to that number by Glimpzed for any account. To resubscribe, reply START. Recipients seeking help may reply HELP for an automated response or contact support@glimpzed.app.
Message frequency: Message frequency is entirely event-driven and depends on the account holder's safety-feature use. 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. Glimpzed does not send marketing, promotional, subscription, recurring, or bulk SMS of any kind.
Message and data rates may apply. Standard message and data rates from your mobile carrier may apply to any SMS message sent or received. Glimpzed does not charge you for SMS delivery.
Mobile phone number non-sharing: Phone numbers you designate as Trusted Contacts, and phone numbers used to sign in to Glimpzed, are used solely for Glimpzed authentication and Glimpzed-initiated safety-alert SMS. Glimpzed does not share, sell, rent, lease, disclose, or transfer mobile phone numbers or the consent associated with them to any third party for that third party's marketing or promotional purposes. Phone numbers are transmitted to Twilio only to the extent required to deliver a specific SMS message you or your Glimpzed account has authorized, and are processed by Twilio under Twilio's privacy policy and its role as our data processor.
Crash Reporting (Firebase Crashlytics): When the App crashes or encounters an unhandled error, we send a crash report to Firebase Crashlytics to help us fix bugs. Each report contains a stack trace, device model, OS version, app version, and (when you are signed in) your opaque Glimpzed user ID — NEVER message content, photos, location coordinates, or contact details. You can disable crash reporting at any time in Settings → Diagnostics → Send crash reports. Reports are processed under Google's Firebase data processing terms.
Trusted Contacts: The name and phone number you enter for each Trusted Contact is stored both on your device and in our cloud database (so the list survives reinstall and is consistent across your devices). Phone numbers are stored as you entered them (normalized for SMS dispatch) and are NEVER shared with other Glimpzed users. We use these phone numbers only to address SMS messages composed by you in your phone's native messaging app when you activate Safe Meet share, Emergency SOS, or follow-up messages.
Safe Meet Share: When you activate Safe Meet for an in-person meeting with another Glimpzed user, the App composes a message to your chosen Trusted Contact containing your first name, the matched user's first name only, the matched user's age range, the matched user's gender, and your intended check-in time. NO photos, NO bio, NO last name, NO exact location, and NO contact details of the matched user are included in this routine Safe Meet message. The message is handed to your device's SMS app — you must press Send for it to leave your device.
Emergency SOS During a Safe Meet — Identification of the Person You Are Meeting: If, and ONLY if, you activate Emergency SOS while a Safe Meet is active, the SOS message additionally includes the matched user's first name and the matched user's permanent Glimpzed user ID. After the SMS app is opened the App will OFFER (you must explicitly tap "Share photo" to proceed) to also share the matched user's profile photo with your Trusted Contact via your phone's system share sheet. This emergency-only escalation is intended to give a Trusted Contact, or law enforcement to whom the Trusted Contact passes the information, what they would need to identify the person you were meeting. The matched user's photo, when shared, leaves Glimpzed's control and persists in your Trusted Contact's phone subject to the privacy practices of the application your Trusted Contact uses to receive it. By using Glimpzed you consent to your own first name, age range, gender, Glimpzed user ID, and (during SOS escalation) profile photo being shared by another user with their nominated Trusted Contact for this limited safety purpose.
Active Safe Meet State: While a Safe Meet is in progress we store on our servers and on your device the matched user's identifier, your planned check-in time, the first name of the Trusted Contact you notified, and the time you notified them. This record is automatically deleted when you mark yourself safe, cancel, or 24 hours after the planned check-in (whichever comes first). It is never visible to the matched user.
What Glimpzed sends by SMS: When you activate Emergency SOS from within the App, or when a Safe Meet check-in you scheduled becomes overdue, Glimpzed's backend may send a text message to the Trusted Contacts you designated in the App. The message includes only the safety-relevant information described in Section 6 (Safe Meet Share and Emergency SOS During a Safe Meet).
Message frequency: Message frequency depends on your use of the safety features. In typical use, Trusted Contacts receive zero messages. If you activate Emergency SOS, one SMS is sent to each designated Trusted Contact. If a Safe Meet check-in becomes overdue, up to one SMS is sent per Safe Meet session per Trusted Contact. Glimpzed does NOT send marketing, promotional, informational, or any other category of SMS.
Message and data rates: Message and data rates may apply. Standard carrier message and data rates apply to any SMS a Trusted Contact receives from Glimpzed, per the recipient's mobile carrier plan.
Opt-out (STOP): Trusted Contacts can opt out of receiving future Glimpzed SMS at any time by replying STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT to any message received from Glimpzed. Opt-out is honored immediately by our SMS provider and no further messages will be sent to that number until they opt back in by replying START.
Help (HELP): Reply HELP or INFO to any Glimpzed SMS to receive a short informational reply with our support contact address.
Non-sharing of mobile numbers: Mobile phone numbers that Glimpzed account holders enter as Trusted Contacts are used ONLY to send the safety-related SMS described above and in Section 6. Mobile numbers are NEVER sold, rented, licensed, or shared with third parties for marketing, advertising, analytics, list-brokerage, or any other purpose. The only third party that ever processes these numbers is our SMS provider (Twilio) for the sole purpose of delivering the safety message. Twilio processes numbers under its own privacy policy at twilio.com/legal/privacy. Numbers may also be shared with law enforcement in response to a lawful process or in good-faith response to a credible imminent-harm report.
Consent: By adding a phone number as a Trusted Contact inside the Glimpzed App, the Glimpzed account holder represents that they have obtained permission from the owner of that phone number to receive safety-related SMS from Glimpzed on the account holder's behalf. Trusted Contacts who did not consent should reply STOP to any received message and contact privacy@glimpzed.app.
You have the right to:
To exercise any data rights or make a privacy inquiry, contact us at privacy@glimpzed.app.
Glimpzed is not intended for users under the age of 18. We do not knowingly collect personal information from minors. If you believe a minor has created an account, please contact us immediately at privacy@glimpzed.app and we will take appropriate action.
We take reasonable measures to protect your information from unauthorized access, disclosure, alteration, or destruction. Your data is stored on Firebase infrastructure which uses industry-standard encryption in transit and at rest. We recommend using a device passcode and keeping your OS updated to protect your device-side session.
We may update this Privacy Policy periodically. We will notify you of significant changes through the App. Continued use of the App after changes are posted constitutes acceptance of the updated policy.
If you have questions or concerns about this Privacy Policy, please contact:
Glimpzed (operated by Corey Hutchinson, sole proprietor)
privacy@glimpzed.app
7276 West Atlantic Boulevard, Suite 390
Margate, FL 33063
For A2P / SMS compliance inquiries and to request opt-out or non-sharing verification, please email the address above with the subject line "SMS Compliance".