← Back to Hello IRL

Privacy notice

Waitlist privacy notice · updated 12 November 2026

The Hello IRL team manages this waitlist. At signup we collect your first name, email, age range, city, chosen gathering, consent choices, campaign source and any early-access code. A dating profile and photo are not required. Gender and dating preferences are collected only if you later choose to add them in your private profile. We use the code to record early-access interest and measure campaign signups; it is not a private login or a confirmed booking.

These details are used to manage the waitlist, plan the launch and contact you about it. Future-event marketing is optional. We do not display applications publicly, sell them, or add applicants to group chats.

Records are stored in the app’s hosted database, provided through Sites and Cloudflare, and are accessible to you through private access and to the authorised founder. Hosting and platform security logs may be processed outside India. This website uses no advertising pixels.

Your waitlist number and sharing link are public identifiers, not sign-in credentials or a guaranteed queue position. We record referrals and the early-access invitation used. Early-access members receive three single-use invitations, valid for 30 days. Counts do not reveal friends’ identities. A hash of the issuer’s email, invitation slots and used timestamps remain after deletion to prevent reuse, subject to the same manual retention review. An invitation is not identity verification.

A short-lived hashed network identifier limits automated submissions. Application records remain until deleted or cleared in a founder retention review. The founder should review and remove inactive records every 30 days and clear unneeded pilot records at day 90. This is a manual process.

Private account access lets you edit your details, download your data, manage optional emails, withdraw or rejoin the interest list, request cancellation of a recorded paid booking, or delete your application. We record when details, consent and status change, and when booking readiness, payments and check-ins are recorded. A cancellation request does not issue a refund. Deleting data does not refund a payment. Stopping marketing does not cancel essential updates about the gathering you applied for. Platform backups may remain under the provider’s retention policies. The Hello IRL team handles questions and data requests through the support form. You can request correction or deletion there without sending a sign-in code.

You may link your application with a single friend using a separate pair code. Both guests consent before their first names and pair readiness become visible to each other. Email addresses, dating preferences and sign-in credentials are not shared. Unused pair codes expire after seven days and are stored only as hashes. Either guest can remove the pair. Deleting either application removes it. Your data export includes your pair reference and timestamps. Pairing does not reserve seats or activate a discount. Founder mock payment records retain a pair reference and simulated amount after unlinking, without names or contact details.

After check-in, you may submit optional ratings and comments about the event. Feedback is linked to your application and visible to the organiser, not published publicly. You can edit or remove it, and it is included in your data export. Deleting your application also removes its feedback. Interest in another event does not change marketing consent.

After the event, the organiser may open a seven-day connection window. Checked-in guests with verified email can choose to show a display name, age band and short introduction to other participating guests. Gender and dating preferences are not shown. One-way likes remain private. A mutual like reveals each person’s verified email to the other. Removing a like, blocking, leaving connections, suspension or a closed window stops further contact access in the app; details already saved by another person cannot be recalled. Leaving removes the connection profile and all likes involving it. Blocks and submitted reports remain until application deletion. Reports are linked to the reporter and visible only to the authorised organiser; they are not monitored live. Your export includes your connection profile, outgoing likes, blocks and reports. Deleting the application removes these records, including reports involving that application. The same manual retention review applies.

Requesting a sign-in code sends your email address and a one-time six-digit code through Resend, our email delivery provider. We store the requested address, hashed access tokens, attempt count, expiry and provider outcome. Access expires after 15 minutes; expired records are removed on the next access request. Completed recovery clears the address and access hashes from that temporary record. Signing in opens your chosen signup, replaces its internal private credential and records email verification, without changing its booking or marketing choices. You do not need to save the internal credential. It stays in page memory and is cleared from the interface when you end the session; refreshing requires sign-in again. Provider delivery records may remain under its retention policies.

After signup, we send a waitlist confirmation through Resend. Resend receives your email address and a generic confirmation without your sign-in credentials or dating preferences. A delivery record stores the recipient, saved message, attempt count and provider outcome. Deleting the application also deletes this app-side record; a message already submitted to the provider cannot be recalled. Your export includes its delivery status. Provider records follow its own retention policies.

When email delivery updates are configured, signed provider notices record delivery, delays, bounces and spam complaints. We do not track opens or clicks. A bounce or complaint pauses further email to that address, including recovery codes. A minimal suppression record contains a hash of the address, the reason and timestamps. It remains after application deletion to prevent unwanted mail if someone signs up again. It does not contain your name, message content or dating preferences. Contact support if you need a delivery issue reviewed. Delivery to a mail server does not prove that an email was read.

Joining the waitlist is free. No tickets are on sale yet. An application does not guarantee a place, a compatible group, or a romantic match.

Support messages

The support form stores your reply email, optional name, topic, message and consent time in a private organiser inbox. We use these details only to handle your request, not for marketing. Only the authorised founder can read, update or delete requests. No automatic email or live chat is enabled.

Support messages are separate from your application. Deleting an application does not delete a support request. You can ask for removal through the form, quoting its reference, without sharing your private application code. The organiser can permanently delete the request after handling it. Avoid sensitive details and information about other guests.

House rules

Be 21 or older, single, and honest about why you’re here. Cohort eligibility will be stated before booking.

  • Respect a no, including a quiet or indirect one. Nobody owes you a conversation or contact details.
  • No harassment, discrimination, unwanted touching, pressure, or repeated contact after someone declines.
  • Ask before taking photos. No filming or tagging other guests without explicit permission.
  • Keep other guests’ identities and personal stories private.
  • Tell a host if you feel uncomfortable. Hosts may remove a guest for misconduct and prevent future bookings.
  • Stay in control of your own travel and belongings. Hosts cannot guarantee anyone’s conduct or compatibility.

The proposed singles party uses a public venue, music, a quieter conversation area and a non-alcoholic welcome drink. Final event details, support contact, and cancellation terms will be provided before payment.