Privacy Policy

SocialCue is a location-based social discovery platform for adults. Members see which nearby venues have people present, can attend meetups and events at those venues, and may optionally connect with other members they encounter there.

The core idea is simple. When you are physically inside a venue we have mapped, you may become visible to other members at that same venue. A member who has chosen Selector mode may send an Invitation to a member who has chosen Discoverable mode and is present. If the recipient accepts, the two of you become connected. Only then — and only if you each separately opt in — do your social media handles become visible to one another.

Everything on SocialCue is opt-in at every step. You choose whether to share your location, how you take part, whether to send an Invitation, whether to accept, whether to exchange contact details, and whether to meet in person. SocialCue does not have in-app messaging or chat.

This policy explains what personal information we collect, why, who we share it with, and what choices you have.

SocialCue, LLC (“SocialCue,” “we,” “us”) operates the SocialCue mobile application and websites. Registered address: 410 N. Jefferson Ave., Suite 398, Mount Pleasant, TX 75455. Contact: paulroberson@socialcue.co.

This policy covers the SocialCue app and our websites. It does not cover venues, events, or third-party services you reach through SocialCue. Venues listed in SocialCue are independent businesses and are not owned, operated, staffed, or supervised by SocialCue unless we explicitly state otherwise. SocialCue is available only to adults aged 18 and over.

Account information. We use Supabase as our authentication provider. When you create an account we collect your email address. If you register with a password, it is stored by Supabase in hashed form — we never see or store your plaintext password. You may instead sign in with Google, in which case Google shares basic account identifiers with us. You may optionally verify a phone number; codes are delivered by SMS through our provider, and we store the verified number and verification date.

Date of birth. When you register we ask for your date of birth and use it to determine whether you meet our minimum age requirement of 18. That check is made against the complete date, to the exact day, on our servers, before an account is created.

We do not keep your full date of birth. Once the age check is made we discard the day and keep only the month and year you were born. We keep those two so that the age range shown on your profile moves from one range to the next on its own as you get older, instead of staying at whatever it was on the day you joined. Because we do not keep the day, that change happens at the start of your birthday month. We also keep the outcome of the check itself: that it was performed, when, the method used, and the minimum age applied.

Text-message consent. If you choose to give us a mobile number so we can verify it, we record that you agreed to receive a verification code, when you agreed, the number your agreement covers, the wording you were shown, and where you gave it. We keep this so we can show that any verification message we sent was one you asked for.

Profile information. You provide: display name, gender (recorded as woman or man), age bracket (18–22, 23–27, 28–32, 33–37, 38–44, 45–54, 55+), home city and state, and optionally a temporary travel city and state, a relationship status, a short bio, interest tags, and up to five photos. Your profile age range is not your date of birth. If we hold your birth month and year, the range is worked out from them and keeps itself current, so you neither choose it nor edit it. If you joined before we began asking for a date of birth, you chose your range yourself and can still change it at any time. Either way it is a profile detail, not our age check (see “Date of birth” above). You may optionally add contact handles — Instagram, Snapchat, TikTok, Facebook, WhatsApp, and a phone number — used only as described in Section 5.

Photos. Photos are checked for file type, dimensions, and size. Location metadata (EXIF, including GPS coordinates) is stripped from every photo before storage. Photos are stored with unguessable file paths in a bucket that serves them over public URLs; anyone holding a photo’s URL can view it without signing in.

Location information. With your permission, the app reads your device’s location to determine whether you are inside a venue’s mapped boundary. Each accepted reading is stored as a coordinate pair with an accuracy value and timestamp. This includes readings taken when you are not inside any venue. Readings less accurate than 100 meters are discarded and not stored. We separately store which venue you are currently present at and when you were last seen there.

Home and temporary travel location. Your home city and state, and your optional temporary travel city and state, are typed by you in your profile and are used to choose which city’s venues and events we show you. They are a city-and-state preference only — not coordinates, not read from your device, and not the precise location described above. A temporary travel location is optional, never set automatically, does not expire on its own, and you can clear it at any time in your profile. It does not change your home city and state, and it is not used to determine whether you are present at a venue.

Background location. If arrival reminders are enabled for your account and you grant Android background-location permission, the app may read your device’s location while it is not open, for one purpose only: to determine whether you have arrived at a participating venue and, if so, to send you a reminder naming that venue. Android tells the app when you reach one of the venues it has registered; the app then takes a short, limited sequence of location readings to confirm, and our servers check the venue’s mapped boundary. An arrival reminder does not make you present at a venue and does not make you visible to other members. That happens only if you open SocialCue yourself, through the in-app location described above. Background location is not used for any other feature.

Your control over background location. Background location is off unless you grant it, and you can change or revoke it at any time in your Android settings. If you deny or revoke it, arrival reminders that rely on background location will not work. Nothing else in SocialCue changes — the map, venues, events and presence all continue to work using location while the app is open. Arrival reminders are currently available on Android only.

Device and notification information. If you enable push notifications, we store a push token issued by Apple or Google, the platform, and the last time we saw it. We do not collect device identifiers, advertising IDs, device model, or operating system version.

Usage information. We keep a small first-party activity log recording a limited set of events: that you opened the app on a given day, and that a notification or reminder was sent, opened, or tapped.

Advertising — what we do not do. SocialCue does not use third-party advertising cookies, advertising SDKs, tracking pixels, or ad networks. We do not use Google Analytics, Meta Pixel, session-replay tools, or any third-party analytics product. We do not sell personal information, and we do not share it for cross-context behavioral advertising.

Cookies. We set only four cookies, none for advertising:

• Supabase session cookie — keeps you signed in. Approximately one hour, refreshed while active.
• sc_ref — remembers a referral code from an invite link. 30 days.
• sc_acq — remembers how you first arrived (campaign parameters). 30 days.
• sc_native_signin_email — holds your email during passwordless sign-in. 10 minutes.

All four are host-only and are not shared across our domains. sc_ref and sc_acq record only your first visit and are deleted once you complete onboarding.

Referral information. Every account receives a referral code. If you were invited, we record which account invited you.

Membership, credit, and payment information. Subscriptions are billed by the Apple App Store or Google Play. We never receive your payment card details. We store a transaction identifier, the billing period end date, and renewal status. We also maintain an in-app credit balance and a ledger of credit transactions.

To authenticate you; show you as present at a venue; operate the Invitation and connection features; deliver notifications; apply membership entitlements; credit referral rewards; respond to reports; enforce our Terms; and keep the service safe and working.

With other members — the most important section.

• Your display name, age bracket, photos, bio, interests, and relationship status may be seen by other members when you are visible at a venue.
• Your exact location is never shown to another member. Members see only that you are present at a venue — never your coordinates, and never a live headcount.
• Your contact handles are disclosed only after you and another member are connected AND you have each separately chosen to share them. One person opting in discloses nothing. These fields are returned by no other part of the service.
• Event attendance is shown only as an aggregate count of women and men, never as a list of names.
• Reports you submit are never shown to the person you reported, and your identity as a reporter is never disclosed to them.

With service providers. Supabase (authentication, database, photo storage), Vercel (hosting), Mapbox (maps), Apple and Google (push delivery and billing), and our SMS provider for phone verification.

Mobile information. Mobile information will not be shared with third parties or affiliates for marketing or promotional purposes. Your mobile number is shared only with the SMS provider that delivers your verification code, and only so that it can be delivered. Text-message consent is never sold, rented, or passed on for anyone else’s marketing. SocialCue sends one-time account verification codes and does not send marketing, promotional, or recurring text messages of any kind.

For legal reasons. Where we believe in good faith it is required by law, or necessary to protect the rights, safety, or property of members, the public, or SocialCue.

Business transfers. If SocialCue is involved in a merger, acquisition, or sale of assets, your information may transfer as part of that transaction.

SocialCue helps people discover one another in public venues. Whether you meet anyone in person is entirely your decision.

• You choose whether to meet. Nothing in SocialCue obligates you to meet, respond, or share contact details.
• Meet in public. We strongly recommend that any first meeting happen in a public place, during business hours, with other people present.
• Tell someone. Consider telling a friend where you are going and who you are meeting.
• Use your judgment. Trust your instincts. Leave any situation that feels unsafe.
• We do not supervise in-person meetings. SocialCue does not attend, monitor, chaperone, moderate, or supervise any meeting between members. We have no staff present at venues.
• We do not verify identity. We do not run background checks, criminal-records checks, or identity verification of any kind. We do not confirm that a member is who they claim to be, that their photos depict them, or that their profile is accurate.

If someone behaves inappropriately, report them in the app. If you are in danger, contact local emergency services first.

Venues shown in SocialCue are independent third-party businesses. Unless we explicitly identify a venue as operated by SocialCue, we do not own, control, staff, endorse, or supervise it, and we have no agreement with it. Venue listings are compiled by our staff and do not imply any partnership or affiliation.

Events listed in SocialCue are created by our staff. Attending any event is voluntary and at your own risk, and is subject to the venue’s own rules, admission policies, and legal requirements.

Ghost Mode. Turning on Ghost Mode immediately deletes your current presence records and stops you appearing at any venue. It takes effect at once rather than fading out.

Location permission. You may revoke location access at any time in device settings. Without it, presence and venue features will not work.

Notifications. You may disable push notifications in device settings.

Photos and profile. You may add, reorder, or delete photos and edit most profile fields at any time. Display name may be changed once.

Blocking. You may block another member. Blocking is silent — the blocked person is not told.

We keep your information for as long as your account exists.

Location history is retained for the life of your account. We do not currently operate an automated schedule that deletes stored location readings before account deletion. Deleting your account deletes them.

Records we keep for safety, dispute-resolution, or financial-record purposes — including Invitation and connection records, reports, and credit ledger entries — are retained after account deletion in the reduced form described below.

You can delete your account in the app. When you do:

Permanently deleted: your photos and their stored files, your location history and current presence, your push notification tokens, and your notifications. Your sign-in identity is deleted, releasing your email address for reuse.

Erased from your record: display name (replaced with “Deleted user”), bio, interests, home city and state, temporary travel city and state, relationship status, verified phone, and all contact handles.

Retained: a minimal, de-identified account record so records involving other people remain intact — Invitations, connections, reports, subscription records, event RSVPs, credit ledger entries, and the limited activity log. Your gender, age bracket, and account creation date remain on that record.

We also keep a one-way cryptographic fingerprint of your email address, and of your phone number if verified, to prevent repeated free-trial signups. These fingerprints survive account deletion by design. They cannot be reversed to recover your email or phone number.

Accounts with staff or founder privileges cannot be self-deleted; contact us instead.

Database access is denied by default and permitted only through validated server routes. Contact handles are protected at the database level so they cannot be read except through the connection flow. Authentication cookies are HTTP-only. Photo uploads are validated and stripped of location metadata.

No system is perfectly secure, and we cannot guarantee absolute security.

SocialCue is intended solely for adults aged 18 and over. It is not directed to children, and we do not knowingly collect personal information from anyone under 18. Registration asks for your date of birth and refuses to create a profile for anyone under 18, however you register — including with Google, where we ask for it immediately after Google signs you in and before any profile exists. We check the date on our servers, so the check cannot be skipped from your browser or phone. Persons under 18 are prohibited from creating an account or using the service in any capacity.

We do not verify age with identity documents. Age is self-declared as a bracket at registration.

If we learn that an account belongs to someone under 18, we will disable and delete it, and delete the associated personal information, without notice.

Parents and guardians. If you believe a person under 18 has created an account or provided us personal information, contact us immediately at paulroberson@socialcue.co with the account’s display name or email address and a description of your relationship to the minor. We will investigate promptly, remove the account, and delete the associated personal information. We may ask for limited additional information to locate the account and confirm the request; we will use it only for that purpose.

Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of your personal information. Most are available directly in the app. For anything else, contact paulroberson@socialcue.co. We do not sell personal information or share it for cross-context behavioral advertising.

This Privacy Policy, and any dispute, claim, or controversy arising out of or relating to it or to our collection, use, or disclosure of your personal information — whether in contract, tort, statute, or otherwise — is governed by the laws of the State of Texas, United States, without regard to its conflict-of-laws rules.

You and SocialCue agree that the exclusive venue for any such dispute is the state or federal courts located in Texas, and you consent to the personal jurisdiction of those courts.

Where the law of your own jurisdiction grants you rights that cannot be waived by agreement, nothing in this section removes those rights.

We will post changes on this page and update the “Last updated” date. Material changes will be communicated in the app.

SocialCue, LLC · 410 N. Jefferson Ave., Suite 398, Mount Pleasant, TX 75455 · paulroberson@socialcue.co