Privacy Policy
Hey, It’s You! (again) is operated by BluNET Holding Company, LLC. This policy describes how BluNET Holding Company, LLC handles information. The service is for adults aged 18 and over. Questions and privacy requests can be submitted through our contact form.
Information we collect
At sign-up we ask for your birth date to confirm you are 18 or older (counted by today’s date in Hawaii); if you are not, nothing is stored. The birth date you give pre-fills your profile and is not kept separately once your profile is saved. When you sign up in the app with an email link, the details you enter (email, names and birth date) are held for up to 24 hours until you tap the link, and your account is made only when you do; if you don’t, they are deleted within a day after that. If the birth date shows you are under 18, no account or link is made, and for 30 days we keep only one-way codes: one of the email address, one of the app install and, for a sign-up with a sign-in account, one of that account, never the email, name or birth date, so the same email or app can’t simply try again with another date. We store your email, password hash, first and last name, birth date, phone number, verification status, any requested email or phone change until it is verified, authenticator configuration (optional for members), staff recovery-code hashes, session information, and trusted devices (a hash of a random device token, a coarse browser and operating-system label, when it was added and last used). If you use Sign in with Apple or Sign in with Google, we keep the provider’s account identifier and the email it gave us (with Sign in with Apple, whether it’s a relay address) and, with Sign in with Apple, a token that lets us disconnect the sign-in when you delete your account; the provider never sees your messages or connections. We also store connections, messages, your per-conversation read position for unread badges, sharing choices, connection decisions, account-status requests, consent records, support requests, and staff security records. We store one current profile photo plus retained original copies of previous accepted uploads, upload times, safety-review results, meetup records, each member’s private notes and ratings, account-change and connection-event history, and moderation flags (including flagged message text). Each account receives a unique profile ID, visible to connections and searchable by authorized staff; it is not a login credential. Issued ID numbers remain reserved without their account link after account deletion. Government ID images reach us in two ways: one copy of the ID you show our identity provider (see “ID verification and biometric data” below), and an upload through the restricted upload page when our team asks for a flagged-account review. When you verify your ID (part of a membership, required before sharing contact details), Stripe checks your ID and selfie as described in “ID verification and biometric data” below; we keep the result and one copy of your ID document for safety (staff-only; never the selfie or biometric data), as that section describes. Do not send an ID through chat, the support form, or profile-photo upload. Delivery and hosting providers process technical information needed to operate their services. We use IP-based request limits to reduce abuse. When you open the sign-up page, our server looks up the US state of your IP address in an offline database to show the safety notice your state requires (New Jersey, Illinois and New York); the address isn’t stored or sent anywhere for this. IP location data: IP Geolocation by DB-IP, licensed under CC BY 4.0. We record observed IP addresses with new staff audit and member activity events and record registration, password-login attempts, two-step verification completion or failure, and sign-out for personal and staff accounts. Login history includes account identifiers, account email where matched, event outcome, and server time. Passwords, verification codes, and session tokens are not included. Failed login records include the entered email/
How we use it
We use information to create and secure accounts, check the stated age requirement, verify access to contact details, connect members, deliver messages, apply sharing choices, provide support, prevent abuse, and address documented legal obligations. Email or phone verification confirms access to that contact method; it is not an identity or background check.
For places listed in the app, we count how often each listing is shown and tapped, as daily totals that aren’t linked to you, so venues can see how their listing performs.
What others can see
You can add an optional preferred name (up to 40 characters, not verified, changeable at any time). Until you share your contact info with someone, people with your connection link and your connections see only your preferred name (your first name if you set none), marked “Their preferred name” when it differs from your legal first name; your legal first and last name are never sent to them. After you share your contact info with a connection, that person sees your legal first and last name, with your preferred name in parentheses when it differs, and your contact card includes your preferred name. Other members see your age, calculated by us from your birth date; your birth date itself is never shown or sent to them. Until a member passes the ID check, their name and age are the ones they entered; the ID check confirms the name and birth date, so a verified member’s age comes from their ID. Your full birthday and email stay private. Your connections can see your safety-approved profile photo and whether you are Verified (the badge, or “This person is not verified”); your ID documents are never shown. Connecting, chatting and planning meetups (and sharing meetup plans) need only a verified email; a member must be Verified (an active membership with the phone and ID checks) before sharing contact details. Your photo is shown clearly to your connections and to someone you’ve just met by scanning a code; it is never blurred. A photo that has been reported, is under review or was removed is never shown to others. Every chat message is checked by our server before it is stored: one that contains contact details (a phone number, email or street address, a link, a social, messaging or payment handle) is refused and never delivered; the attempt is kept in our audit log with the text, and repeated attempts are reviewed by our team. A message that asks for money or payment details (a payment app, handle or cashtag, a gift card, cryptocurrency, bank details, or a request to send money) is refused the same way and never delivered; the other person isn’t told. A blocked message is kept encrypted for 7 days so repeated attempts can be counted, and 2 or more money requests in 7 days are reviewed by our team with the blocked messages. If you think a message was blocked by mistake, tap “Ask for a review”: our team reads it and either delivers it or keeps it blocked, and a message under review or kept blocked is kept as a safety record.
Your connection code changes every 30 seconds and works for one scan. A scan means you met: it makes a pending connection for both of you right away, and each of you sees the other’s preferred name, age and photo (or initials, if the photo has been reported or is under review), and whether they’re Verified. It becomes a connection only if you both tap Add connection. If either of you removes it, or you don’t both add it within 12 hours, it ends quietly for both of you, and nobody is told who removed it. If either of you allows only verified members to connect, neither of you can add the connection until the other person is Verified, within the same 12 hours. If the person who scanned isn’t signed in, the scan is held for them for 12 hours from the scan, while they sign in or create an account; after that it ends quietly. We keep who scanned, when, and the outcome, and delete it with the rest of the connection records.
Choosing “I’m ready to share my info” shares your last name and verified phone number with that specific connection. The recipient can Call, Text, or Save their info as a contact card containing your name and phone number. Sharing is one way and sharing back is optional. Emails and social accounts are not shared. Turning sharing off blocks future access in the app, but cannot erase contacts, screenshots, or information already saved outside it. Editing your name, phone, or birth date clears your existing sharing choices.
Meetups and connection controls
Every meetup has a meet ID. We keep each meetup’s record (the meet ID, both Profile IDs, the time, the place, its changes and confirmations, and every time its details were shared, with the address they went to) for 10 years, including after an account is deleted. We don’t keep message contents in this record.
Once you both confirm a meetup, you can email its details to a friend or family member. You can also add up to 3 emergency contacts (a name and an email address) and choose to have your meetup details emailed to them automatically at 6:00 AM on the day of each confirmed meetup, in the meetup’s time zone. We email each emergency contact once when you add them, with a link to stop these emails; once they use it, we never email them about meetups again. These emails contain only both members’ first or preferred names, the date and time, the place and the meet ID: never last names, photos, profile links or contact details. When details are shared, the other person gets an email saying so, without who received them or how many. Our email provider tells us if one of these emails bounces or can’t be delivered, so we can show you it failed.
Connected, verified members can record a meetup’s scheduled time and place for both participants to see. Notes and thumbs-up/
Connection requests
Scanning a live code makes a pending connection for both people (described above): both see each other’s preferred name, age and photo, and it becomes a connection only if both tap Add connection within 12 hours. No connection or access to messages and shared contact details is granted before both have added it. We tell the owner about a new request in the app and, following their notification settings, by email or push notification.
Location: a few moments only
We record a device location only at these moments, and only with your device’s permission. When a code is scanned in the app, we save where each of you was with the connection, for safety: the scanner’s device at the moment of the scan, and the device showing the code, once, when the scan is registered. Check-in and rating locations recorded on the website before November 13, 2026 are kept as described below; the app doesn’t record them. Each record is the coordinates, their accuracy and the time. We never track location continuously, in the background or when a code simply refreshes, and everything works without location access. These records are visible only to authorized staff, for safety and legal review, and never to the other member or anyone else; a staff member viewing one is logged. Scan locations stay with the connection and follow its deletion and legal-hold rules; earlier check-in and rating locations stay with the meetup’s meet ID for 10 years, like meetup records. When you open Places or plan a meetup with location allowed, the app sends your approximate position to our server once to find partner places near you; we answer and keep nothing. When staff view a location, our server draws the map through a map service; the coordinates never leave the server to your browser or app. The nearby count uses a short-lived position, kept for 15 minutes at most and never as a history (see below).
Maps. When the app shows a partner place’s small map, the map is drawn by Google Maps, a service of Google LLC. To draw it, your phone connects to Google, which receives your device’s IP address and the map area shown, under Google’s own privacy policy. If you’ve allowed location, your own position is drawn on the map by your phone’s location services; Hey, It’s You! doesn’t send it to us or store it, and we don’t send Google your name or account.
Nearby count
Only Verified members see the nearby count, and only once they’ve set up Who I’d like to meet; for anyone else we keep no position for it. In the app, the nearby counter starts when you open the Dashboard and uses your device location only after you grant the app location permission. It sends your current coordinates to our server every few seconds while the dashboard is open. We keep only your latest coordinates for this feature and no history of where you have been. Once you’ve set up Who I’d like to meet, we count other Verified members who don’t have Hide my profile on, are sharing their location this way, match who you’d like to meet and whom you match, within both of your distances, and return only the total, and only when it is more than 10—never their names, locations, distances, or directions. Location readings are approximate. Readings stop counting after five minutes without an update and are deleted within 15 minutes. You can revoke location permission in your phone’s settings to stop future updates. This is separate from saved connection map pins and does not track your background location.
Out now
Out now. You appear in Out now once you finish setting up who you’d like to meet; turn on Hide my profile to stay out of it. If you use it, we keep the gender you choose for your profile (Woman, Man, Nonbinary or Prefer not to say) and Who I’d like to meet (the genders or Everyone, an age range and a distance). We use these, with your age from your verified ID and your location while you’re out now, only to show you to people whose choices you fit and who fit yours, and to count Verified members nearby. Other members never see your birth date, your location or your choices; they see your photo, preferred name, age and about how far away you are. Your location for Out now is kept for at most 15 minutes, with no history. Invites and their answers are kept for 30 days. Messages in an Out now chat are kept while it’s open and for 30 days after it ends; if you both add the connection, they move into your chat. Blocks are kept until your account is deleted. Reports are handled like other safety reports.
Message notifications
Message email notifications are enabled by default and can be turned off in Account settings without disabling security emails. When delivery is active, we send a generic alert for a new unread message to your verified account email. Alerts do not contain the message, sender name, or profile photo. Our email provider processes your address and delivery details. Pending alerts may be retried for up to 23 hours and delivery-job records are removed after seven days. Turning off alerts, reading the message, taking a break from the conversation or removing the connection can suppress pending alerts.
We save your push notification choices for each kind of notification. If you turn on notifications in the app, we store that phone’s push token with your account and remove it when you sign out or turn them off. Push notifications don’t show names or message text unless you turn on previews, and never a photo. Saving a choice does not grant device notification permission. We also save that you have dismissed the communication reminder for each connection so it does not repeatedly interrupt your conversation.
Communication safety
Our communication rules require polite, respectful, non-explicit conversations. Use Report profile if someone violates these rules or makes you uncomfortable. Reporting and safety review use the records and restricted staff access described below; reporting does not notify the other member or automatically start a break or remove your connection. Reports alone do not restrict the reported member, except that a nudity or sexual-content report hides the reported photo pending review, and reports of harassment or explicit content from at least two different members within 14 days automatically suspend the profile pending staff review (see the Terms).
Photo retention and safety review
You have one current profile picture at a time. Replacing it does not erase the previous upload: we keep every profile photo you upload (including replaced, removed, reported or staff-removed ones) for 10 years from its upload, for account integrity, safety review and documented legal preservation. Only our staff can see the old or removed ones; your connections only ever see your current approved picture under the rules above. These copies are deleted automatically when the 10 years are up, or with your account when you delete it (finished within 45 days of your request), unless a legal hold or a preservation request covers your account at that time. Failed or rejected upload requests that were never accepted are not guaranteed to be retained.
Messages are screened for potentially inappropriate content. Flagged attempts may be held before delivery, retained for review, returned to the sender with a warning, and displayed in the authorized staff safety queue. Uploaded photos are checked automatically when you upload them (see “Profile pictures” below) and may be reviewed by staff. Reports of nudity, sexual content, fake profiles, or impersonation immediately hide the reported photo from connections and alert staff for explicit-content or authenticity review. Authorized staff may approve or reject it. Approval is a photo review, not proof of identity. Message screening runs on our own servers; no outside service processes your messages or photos for screening. It uses rules and our own safety models. One rule keeps contact details out of chat, one keeps requests for money and payment details out of chat, and another stops a message with abusive language before it’s sent and asks you to rewrite it; the attempt is kept for our safety team’s review. Our safety models score each message before it’s delivered for things like harassment, threats, unwanted sexual advances, someone saying they’re uncomfortable, attempts to share contact details, and requests for money; a message they score as a request for money is refused like one the rules catch. The same check also notices when a message looks like you’re making plans to meet, so the chat can offer Plan a meetup, filled in with any place, day and time it understood. We keep only that a plan was noticed, with that place, day and time, until the suggestion is used, you both dismiss it, or 7 days pass; then only a code that stops the same plan being suggested again, deleted after 30 days. We never keep a copy of the message for this. If a message you send looks like it might not land well, we hold it and ask you to edit it or send it anyway; the other person isn’t told. If you send it anyway, we keep a note that you were asked (the category, not the text) for our safety team. We keep only the scores and the category they point to, stored with the message rather than as a copy of it, and delete them when the message is; scores are never shown to other members. If the check is slow or unavailable, your message is delivered and scored afterwards. We don’t use your messages to train these models. Screening can miss content or flag acceptable content, and does not guarantee safety. Contact support to request review of a moderation decision, or tap “Ask for a review” on a blocked chat message.
Staff access and scoped exports
Staff permissions separately control profile and photo previews, documented-reason chat review, moderation, account recovery, verification, and legal exports. Recovery may revoke sessions, force a password change, or require setting up two-step verification again. Staff sign in through Microsoft (Microsoft Entra ID, our organization’s work accounts): Microsoft checks the staff member’s password and multi-factor authentication and tells us who signed in (a Microsoft account identifier, sign-in name, display name and email) and that the staff role and multi-factor policy applied. We store that identifier, sign-in name and display name with the staff account and record each sign-in in the staff audit log. A new staff sign-in has no permissions until the Owner grants them. The @heyitsyouagain.com and @blunetgroup.com domains are reserved for staff and cannot create personal accounts; a company email alone does not grant access.
Authorized staff can produce separate exports for chat logs, profile photo history, connection/
Export tools do not themselves authorize disclosure. Any release to authorities or others must be reviewed for a valid legal basis and limited to the appropriate scope. Retained records, legal holds, and downloaded exports are not public. A downloaded export is a separate copy that cannot be recalled by deleting the active account; its authorized custodian must handle its security, permitted use, and retention under the applicable legal basis.
Service providers and disclosures
We never sell your personal information. We don’t sell, rent or trade it to anyone, and we don’t use it for advertising. To run the app we use a few service providers (for app performance and crash reports, maps, ID checks, email, texts and notifications), who may receive some of your data only to provide those services to us.
Our hosting, database, email, and verification providers process information needed to deliver the service. Twilio Verify sends and checks verification codes by text message, voice call or email: it processes your phone number (text and call codes) and your email address (email codes, including password-reset codes). All email from us, including those codes, is delivered by Twilio SendGrid. Stripe (Stripe Identity) performs ID verification (see below). Microsoft Entra ID handles staff sign-in (it does not process member accounts). Text messages. We text you only a verification code, and only when you ask for one: to verify or change your phone number, and, if you’ve turned on two-step verification, when a new device signs in. We never send ads or marketing by text. When you agree to receive codes, at sign-up or before a code is sent, we keep a record of your agreement: the exact wording you agreed to, its version, your phone number and the time. Standard message and data rates may apply. Reply STOP to stop our texts, or HELP for help. We do not sell personal information or share mobile numbers or SMS opt-in records with third parties for their marketing. SMS consent information is used only for verification delivery, related operational support, and necessary legal compliance. Disclosure to authorities requires review of a valid legal basis; merely requesting deletion does not result in disclosure.
Payments and membership
You make purchases in the app, such as a membership or a pack, through the App Store or Google Play. The store handles the payment: we never see or keep your card details.
To know what you’ve bought and keep your membership working, we keep: the store’s records of your purchases and subscription (which product or plan, when, the price and currency, and its renewal, grace and refund status); the store’s transaction and order references; and a random account token that we give the store with each purchase, so it can be matched to your account without sharing your name or email. We also keep your time zone as your device reports it, to show dates in your time zone. We keep your phone’s region setting (for example US) to show distances in miles or kilometers. When our team gives or ends complimentary access, we record who did it and when.
We keep a record of each payment for 10 years from the payment, for tax and legal reasons, and then delete it, even after you delete your account; a legal hold can keep it longer. That record holds your account ID, the product, the date and the store’s reference, never your profile, photos or messages. The store’s sales records (the product, price, currency and date of each sale) stay after you delete your account, without your account ID. They are deleted 10 years after the sale. Earlier website payments, if you made any, are kept the same way, with their amount and Stripe’s references instead of the store’s.
Introductory price ledger. So that the introductory price is offered only once per person, we kept a separate ledger of keyed hashes (HMAC-SHA256 with a dedicated secret key) of the account ID, the normalized email address and phone number and, for earlier website memberships, the Stripe customer ID and the payment card’s fingerprint (a Stripe identifier for the card, not the card number). We no longer add to it. It contains no readable personal data, is used only to decide whether the introductory price can be offered, survives account deletion and purge, and each entry is deleted 3 years after it was last used.
Voluntary contributions (“Support us”). We no longer take contributions. For one you made before, we keep only: the Stripe checkout and payment IDs, the amount and currency, the date, whether it was refunded and when, and your account ID if you were signed in. Contributions are not connected to your membership.
Suspension, deletion, and retention
Pausing your account hides it while preserving its data until reactivation or a deletion request. Requesting deletion hides the account immediately and starts a 30-day period in which you can cancel. During that period you can sign in, confirm a new device if needed, and explicitly cancel deletion. After the 30 days, cancellation is disabled and cleanup, which finishes within the next 15 days (by day 45 after your request) unless a legal hold applies, deletes the account and associated profile, authentication records, consent records, connections, conversations, meetup records, private notes and ratings, moderation flags, and member history. Original profile photo files are queued for storage cleanup; deletion may complete after the database purge and retry after a storage failure. Any ID verification sessions still held at Stripe are queued for redaction at Stripe. If you used Sign in with Apple, we also disconnect it. Deleting your account doesn’t cancel a membership you bought in the app: cancel it in your phone’s subscription settings, or it keeps renewing. The App Store or Google Play keeps its own payment records, and the introductory price ledger stays as described above.
Signing up again within 30 days. If you sign up with the email address or phone number of an account scheduled for deletion, nothing about that account is shown or confirmed until you verify that email or phone with a code. Then the scheduled deletion is canceled and the account is reactivated as a new sign-up: you set a new password, accept the current policies, verify your email, phone and ID again and complete your profile again (your new sign-up details replace the old ones); two-step verification, trusted devices and sessions are cleared. The account keeps its ID, its membership and purchase history, whether you used the introductory price, staff notes and its audit and safety history (reports, suspensions, ID reviews and legal holds); a suspended account stays suspended. Your previous connections, messages, meetups, notes and photos are deleted and not restored. If your email and phone match two different scheduled accounts, the most recently deleted one is reactivated and the other is linked to it for introductory-price and purchase history. We record that the account was reactivated and which identifier matched (email or phone), not the values.
Staff support notes record the reason for access, work performed, outcome, author, and time in the restricted audit trail and follow its 10-year retention rule. Corrections are appended rather than overwriting prior notes. A safety or legal hold keeps the records it covers, including connected conversations, for the length our team sets, up to a year at a time, and it is renewed while police or a court ask us to keep them. Nothing about a member under a hold is deleted while the hold lasts. When a hold ends, the records follow the rules in this section again. Access remains restricted while retained. Security/
The account deletion workflow does not waive your statutory privacy rights. Where applicable law requires earlier action or permits only narrower retention, that law controls. Use the contact form to request review, correction, access, portability, earlier deletion, or appeal. We may need to verify your identity and will explain any applicable limitation.
ID verification and biometric data
ID verification is part of a membership. It comes after your email and phone, and contact sharing, the Verified badge and unlimited messages and connections come only after it; you can connect, chat and plan meetups without it. Before you start, we show a notice and ask for your explicit consent, and record that consent with its version and time. Our processor Stripe, Inc. (Stripe Identity) then asks for a photo of your government-issued photo ID (driver’s license, passport or national ID card) and a live selfie, checks that the ID is genuine and compares your selfie with the ID photo. That comparison uses biometric identifiers and biometric information (a scan of face geometry). Stripe processes it on our behalf for this check only, under its privacy policy.
Stripe returns the name and date of birth read from your ID; we compare them with your profile (first given name and last family name, ignoring case, accents, hyphens and middle names; date of birth exactly; and 18 or older) and keep only the result: verified or not, which fields didn’t match (name, date of birth or age), the dates, the number of attempts, Stripe’s session reference and, for a check that didn’t pass, Stripe’s short reason codes (for example, that the ID had expired). For safety, we also keep one copy of your ID document images (front, and back if present), encrypted, visible only to our staff with ID access, never to other members: until a newer verified ID replaces it or you delete your account (finished within 45 days of your request), and at most 10 years from the check, unless a legal hold or a preservation request covers your account at that time. Each staff view is logged. We never copy your selfie: our team sees it only at Stripe, for the photo check (see below), and we never keep your face data, your document number, your address or the values read from your ID. After a verified name and date of birth are recorded, they are locked; corrections go through support. You can try up to 3 times a day and 5 times in total; after that our team may ask you to upload your ID for a manual review as described below. If an automatic check fails or can’t be completed, you can ask our team to verify you, with a reason. A check Stripe flags as a possible mismatch or manipulation (for example, a selfie that doesn’t match the ID) is declined and can’t be retried; you can contact us through Help, and our team reviews it there.
Retention and destruction: as soon as a check has a final result (verified, not matching, or canceled), and once our copy of a verified ID is taken, we ask Stripe to redact that session, which deletes the ID images, selfie and biometric data from Stripe’s records, except where a documented legal hold requires us to keep them until the hold ends. Our own copy of the ID document is kept as described above (until replaced or your account is deleted, at most 10 years); we take no copy of the selfie. One exception: when a check opens our team’s review of your profile picture, the selfie stays at Stripe until our team decides, and no longer than 24 hours after the check; then we ask Stripe to redact it. Sessions of deleted accounts are redacted too. Stripe may retain limited records as its own policy and the law require. In every case biometric data is permanently destroyed once the purpose of the check is satisfied and no later than 3 years after your last interaction with us. We do not sell, lease, trade or otherwise profit from biometric data, and we disclose it only to Stripe as our processor, with your consent, or when required by law, a valid warrant or subpoena. We protect it with the same or greater care as other confidential information.
Illinois residents: this section is our written policy and retention schedule under the Biometric Information Privacy Act, and the consent step is our written release. Texas and Washington residents: we collect biometric identifiers only with your notice and consent, for identity verification only, and destroy them within the time described above (Texas: within a year after the purpose expires; Washington: we do not use them for any other purpose or sell them). You can decline; without ID verification you can still connect, chat and plan meetups, but you can’t share contact details or get the Verified badge. You can also ask support about a manual review. Contact us to ask about or withdraw consent for future checks.
Profile pictures and flagged-account ID review
When you upload a profile picture, we check it automatically on our own servers to make sure it shows your face and isn’t explicit. The picture isn’t sent to any outside service for this check. A picture with no clear face, or an explicit one, isn’t accepted; when the check isn’t sure, our team looks at the picture, and your connections see your initials until then. An explicit upload is kept for our safety team’s review. A profile picture is optional for free members and required for the Verified badge. Once you have passed the ID check, our team checks your profile picture (your first, and each new one) before your connections see it; until then they see your previous approved picture, or your initials. For that check, our team may view the selfie from your ID check only while Stripe still holds it, no longer than 24 hours after the check (see “Retention and destruction” above). We never copy it, and after that it is gone. Stripe’s check compares your selfie with your ID. When you change an approved picture, we compare the new one with your current approved picture on our own servers. The comparison uses your face’s features for that purpose only; your photos aren’t sent to any other company, and we keep only whether they matched, never face data. A match goes up right away; otherwise our team looks at both pictures and may ask for a new ID check, whose selfie is held for their review the same way. Your connections keep seeing the approved picture until the new one is approved. If you’re a Verified member, your profile picture is also compared with the photos from your ID check, to make sure it’s you. Pictures remain subject to content safety review. Sending messages and planning meetups need a verified email on both sides (and any required account recovery). The phone and ID checks are collected only for a membership, after you start it, so we don’t ask for your phone number’s verification or start an ID check with Stripe before then; a phone number you give at sign-up is optional and used for contact sharing only once verified. Twilio Verify is used to verify a phone number when you first verify it and whenever you change it (a code by text message or voice call, as you choose), a new email address (a code by email), and — only if you turn on two-step verification — a new device the first time it signs in (a code by text, call or email to a phone number or email address already verified on your account). Two-step verification is optional for members and off by default; with it off, you sign in with your password and we email you whenever a new device signs in. Devices stay trusted until you remove them in Account settings; a password reset removes all trusted devices. Passkeys. If you add a passkey, your device checks your fingerprint, face, PIN or screen lock itself: no biometric data (fingerprints or face images) ever reaches us. We keep only what signs you in: the passkey’s credential ID and public key, its signature counter (to detect a copied passkey), how your device can reach it (transports), whether it syncs between your devices, the name you gave it, and when it was added and last used; plus a single-use sign-in challenge for 5 minutes. We email you when a passkey is added or removed. You can remove passkeys in Account settings; a password reset or a staff-issued temporary password removes them too. Our team gives a temporary password only after checking it’s you, with an eight-digit code we email you or with details from your verified ID, such as your birth date, which our server compares without showing it to our team; we record which check was used. They give it to you directly, or email it to your verified email address; you must change it when you first sign in. Passkeys are for member accounts only. After a password reset you verify your phone number again (the reset code already confirmed your email); after a staff-issued temporary password you verify your phone number again (our team already checked it’s you, so your email stays verified). Otherwise verification is asked again only when you change your email or phone number or when staff remove a verification — never for ordinary sign-ins, new devices or being signed out for inactivity. Once your email, phone number, first name, last name or birth date is verified, you change it yourself in Account settings. To change your email address or phone number, you first enter a code we send to the one already verified, then a code we send to the new one. Until the new one is confirmed, it shows as not verified, you stay Verified with the one you had, and your contact details aren’t shared with your connections. If it isn’t confirmed within 6 days, your account goes back to the verified one. When the change is complete, we let you know at your previous email address (a phone number change, at your verified email). A new first name, last name or birth date applies only after a new ID check that matches it; otherwise nothing changes. If you can’t get a code at your current email address or phone number, you can ask our support team instead: they review the request, may ask you to upload documents (such as a marriage certificate or a court document), and the new detail applies only once it’s verified. Other members see only your current verified details; the requested values are visible only to you and our support team. Documents you upload are stored in restricted storage that only authorized support staff can open, each viewing is recorded with its reason, and we delete them 30 days after the request ends unless the law requires us to keep them. Requests, decisions and their reasons are kept with your account history and audited. An authenticator app is optional for members. Staff sign in with Microsoft and its multi-factor authentication at every sign-in; only the Owner keeps an emergency password and authenticator sign-in, and every use of it is reported to our security contacts. Email/
Staff may flag an account for a documented identity, age, or account-integrity concern and request a copy of a government-issued photo ID. We use it to manually review document validity and match first name, last name, and birth date against the submitted profile, including the 18+ requirement. Messaging and contact sharing are restricted until approval. The request and upload page appear in your account. Failure or refusal to comply with required ID verification will result in permanent account suspension following staff review. Contact support if you cannot provide the document, dispute the request, or want to appeal a decision.
ID images are stored separately from profile pictures in restricted service storage. Only staff with ID-review permission may view them for a documented reason; access and decisions are audited. They are never displayed to connections, sent to any outside service, or included in profile-photo exports. A copy alone is not a live identity check and cannot guarantee authenticity.
Pending ID images remain until the review is decided or the account is deleted. Reviewed original ID images are queued for deletion 30 days after the decision, unless a documented legal hold applies. Replacement uploads queue the previous copy for removal; replacements are blocked while that document is held. Cleanup occurs on service activity and may retry after storage failures. Account deletion also queues ID originals for removal subject to legal holds. Review status, submitted name/
Member safety reports
You can report a connected profile for nudity, impersonation, harassment, threats, suspected underage use, scams, or other concerns. Reports include your account identifier, the reported account and connection, category, optional explanation, current photo-history reference, timestamp, and observed IP address. Authorized safety staff can review the report and relevant retained records. Reports are not shown to the reported member. Reporting alone does not start a break or remove a connection; you can choose either action afterward. Automatic actions (hiding a reported photo, suspending a profile pending review after reports from two members within 14 days) and staff decisions to restore, confirm, lift or convert them are recorded in the audit trail. A suspended member is notified by email and in the app. Reports survive removing a connection and follow the reported account’s deletion and legal-hold rules. Staff review decisions remain in the separate audit trail. Deleting the reporter’s account removes its live account link.
Child Safety Standards
Adults only. Hey, It’s You! is for adults 18 and over only. Minors aren’t allowed, and we remove any account we believe belongs to someone under 18.
Zero tolerance. We have zero tolerance for child sexual abuse and exploitation (CSAE) and for child sexual abuse material (CSAM), in profiles, photos and messages. That includes grooming (building trust with a minor in order to abuse or exploit them), sextortion (threatening to share sexual images to get more images, money or anything else) and any sexualization of minors, in words or images.
How to report. In the app, open the person’s chat or connection page, tap Report and choose “May be under 18”; our safety team treats it as urgent. On the website, use the form on our Help & contact page, or email legal@heyitsyouagain.com. If a child is in immediate danger, call 911 first.
What we do. We remove the content and the account right away and keep the evidence as the law requires. We report apparent child sexual abuse material to the National Center for Missing & Exploited Children (NCMEC) through its CyberTipline, as 18 U.S.C. § 2258A requires, and we cooperate with law enforcement (see our Law enforcement guide).
The law. We comply with the child safety laws that apply to us.
Our child safety contact. For questions about these standards or about child safety on Hey, It’s You!, email legal@heyitsyouagain.com.
People in our marketing
The people shown on our website, in our app store listings and in our ads are illustrations or models, not members, and their names are made up. We never use a member’s profile, photo or name in our marketing or advertising.
Security and cookies
We use secure session cookies, password hashing, two-step verification, and server-side access controls. Only staff with relevant permissions may access administrative tools. The app does not promise end-to-end encryption or absolute security. Essential session cookies keep you signed in; we do not use advertising cookies. We don’t use analytics cookies. On our website we may measure visits anonymously on our own servers: which pages are viewed, for how long, where visitors came from, and the type of device. We use no cookies for this, don’t store your IP address, and share it with no one. We don’t count a visit if your browser sends Global Privacy Control or Do Not Track. If you choose “All cookies”, a partner venue’s code can leave a cookie so the venue gets credit for bringing you to us. The app sends anonymous crash and performance reports, and, if you allow analytics, a few anonymous usage counts (for example, that a message was sent, never what it said), to the provider that builds and runs our app. They’re tied only to a random ID for this installation of the app, never to your name, email, messages, photos or location, and are deleted after 90 days. You can turn the usage counts off with “All cookies” in Your privacy choices. The app also sends crash and error reports to our own server, with the app version, device model, screen pattern and a short log scrubbed of emails, numbers and codes, never your name or messages; a problem report you send from Contact us is linked to your support request. These are deleted after 90 days. In the app, you stay signed in until 60 days after you last used it; the app doesn’t sign you out for inactivity, and a security change such as a new password ends the session at once. Members no longer sign in on the website. Staff are signed out of the staff tools after 10 minutes of inactivity, and always 8 hours after signing in.
Changes and contact
We will update the date above when this policy changes and obtain additional agreement when required. For general questions, email questions@heyitsyouagain.com. For help with your account and for privacy requests, contact BluNET Holding Company, LLC through Help & contact or email support@heyitsyouagain.com. Requests are routed through the service’s internal support tools. Your privacy rights, and how quickly we answer a request (within 45 days, or at most 45 more when we tell you we need longer), are on Your privacy choices.