Skip to content

Privacy

Flectra t/a Loveline.events (ABN 74 852 587 452) runs Loveline. This page says what we collect, why, who else sees it, and how to get it back or get rid of it. We handle personal information in line with the Australian Privacy Principles. Last updated 10 October 2026.

What we never do

We never sell your information.
We never give advertisers your name or anything from your profile. See "Advertising" below.
If we measure ticket sales or waitlist sign-ups from our ads, advertising platforms get your email address (and, for tickets, your phone number) only in scrambled (hashed) form. For a waitlist sign-up they also get your IP address and browser type, so they can match it to their ad.
Dates are never recorded.
Our analytics never receives your name, email or phone number.
Your approved primary photo is shown in the final 60 seconds of an eligible date. Only approved optional secondary photos and selected contact details unlock on a confirmed connection. Non-contact profile fields you agreed to share have the same visibility during dates and on connection profiles.

What we collect, and why

What
Email address
Why
Signing you in, and telling you about your event, including a short message from your host or Loveline staff on the event if you have not checked in yet
When
Sign-in
What
Mobile number
Why
Sending you a sign-in code by text, and service texts about events you book, such as reminders, changes, cancellations and time-sensitive final-choice reminders. We never send promotional SMS.
When
Sign-in and service communications
What
Date of birth
Why
Calculating your self-declared age and eligibility for event age ranges
When
Profile
What
First name and calculated age
Why
Shown during dates and on connection profiles; DOB itself stays private
When
Signup/profile
What
Optional bio, pronouns, orientation, broad location/suburb and has-kids answer
Why
Shared during dates and on connection profiles only where you affirmatively agreed to visibility. We do not ask for children's details or precise/live location
When
Signup/profile
What
Selected phone, email or Instagram
Why
At least one is selected before admission; only selected details are disclosed on a connection. Providing a sign-in contact is not sharing consent
When
Sharing setup
What
Saved game answers
Why
Current profile data and shared icebreakers only after a separate, unselected-by-default save/share choice; a common answer appears only if both partners opted in
When
Optional waiting game
What
Legacy prompt answer
Why
An optional old profile response; not required for admission or automatically published under new consent
When
Existing profile
What
A photo
Why
An approved primary photo is required for admission and shown in the final 60 seconds of an eligible date. Optional secondary photos are shared after a confirmed connection with separate consent
When
Profile and consent
What
Which dates you had, and when you joined and left each one
Why
Running the event and working out what went wrong when it does
When
During an event
What
Private first impressions, typed notes and final yes/no choices
Why
Helping you remember dates and confirming connections; a first impression never creates a connection
When
During and after an event
What
Technical numbers about each date's connection, and your answer if you rate the sound
Why
Finding and fixing bad connections
When
During an event
What
Messages your host or Loveline staff send during an event, and whether your browser fetched or dismissed them
Why
Running the event
When
During an event
What
Internal tags staff add to your account, short labels such as "might host"
Why
Running events, such as who to ask to host
When
When staff add them
What
Reports and blocks you make
Why
Keeping the events safe
When
When you use them
What
What you agreed to, and when
Why
Showing which consents you gave
When
When you give them
What
Your email, and your city and who you would like to meet
Why
Telling you when an event opens
When
If you join a waitlist or register interest
What
On the waitlist: your email; if you add them, your city, age band, whether you are a woman, a man or non-binary, and who you are looking for; and which friend's link brought you, if one did
Why
Opening nights where enough people want one, emailing you about the list, and working out referral rewards. See "The waitlist" below
When
If you join the waitlist
What
If you bring a friend: their first name and mobile number. If a friend brings you: yours, as they typed it
Why
Texting the friend once about the free seat, with your first name and your mobile number (if it is confirmed on your account) in the text so they know who it is from, and holding the seat against their number so only they can take it
When
When you bring a friend
What
If you ask us not to text you about a free seat: a coded copy of your mobile number (a hash, not the number itself)
Why
Never texting that number about a free seat again, whoever asks us to
When
When you tap Not interested in the text, or reply STOP
What
How you use the site and the app, and which site or campaign link brought you to us (the site's name and the link's campaign label, never the full address)
Why
Analytics, to work out what to fix and which of our promotions work
When
While you use them
What
Which ad, if any, brought you to our website, and what you did on its public pages, such as clicking Book tickets
Why
Measuring which of our ads work
When
On the public website, when we run ads
What
That you bought a ticket or claimed your place, for which evening, with your email and phone number scrambled (hashed)
Why
Measuring which of our ads work
When
When you buy a ticket or claim your place, when we run ads
What
That you joined the waitlist, with your email scrambled (hashed), and your browser's IP address and browser type
Why
Measuring which of our ads work
When
When you join the waitlist, when we run ads
Your profile and the events you choose may reveal your sexual orientation. We ask for your consent to collect this sensitive information. That is why we ask, separately and in plain words, rather than burying it in a tick box. You can withdraw consent in Settings, or by deleting your account.
We do not collect health information, we do not ask about your religion or politics, and we do not buy data about you from anyone.

Who sees what

Your date partner: your first name, calculated age and optional non-contact fields you agreed to share, including bio, pronouns, orientation, broad location and has-kids answer. Only deliberately saved and shared game answers can be shown; unsaved picks stay on the device and clear at event end. Your approved primary photo appears in the final 60 seconds of the date. Access ends when either person actually leaves or reports, and blocks, withdrawal or safety action can revoke it sooner.
A confirmed connection: the same consented non-contact profile, plus approved optional secondary photos and the phone, email or Instagram you selected. No event-finish wait applies. Both accounts gain access together, subject to consent and safety checks. DOB, unselected contacts, individual choices and private notes are not disclosed.
You can change or withdraw sharing in Settings. Removing all contact methods prevents new admission and disclosure until you select one again, while history, reporting and support stay accessible. Withdrawal or deletion removes saved answers from subsequent profile and icebreaker access. It also suppresses unsent messages. We cannot recall delivered emails, details or photos someone already saved.
If you bring a friend: they see your first name, and your mobile number if it is confirmed on your account, in their text. You see their first name, the last three digits of their number, and whether they took the seat. Nothing else from either profile.
The host running your event: your first name, whether you are in the room, who you are paired with, and reports made on the event. Hosts see this only for events they are running. For straight events, hosts also see the pairing side derived from the gender on your profile, or why a side could not be assigned, to organise dates. Older accounts may have a legal name on file from the former signup process; we no longer ask for one.
A small number of Loveline staff can see this information to run events and keep people safe, and a little more: which dates you had, the yes or no each of you gave, whether you both said yes, whether you joined, left early or dropped out, reports and blocks between you and the people you met, which consents you gave, and the technical numbers about how each date sounded. They cannot see what anyone said, because nothing is recorded and there is no chat. Staff can add short internal tags to your account, such as a label saying you might like to host, which you never see. Each time staff open someone's date history, or send them a sign-in link, it is logged with who did it.
Nobody else, apart from the advertising platforms named under "Advertising" below, in the limited form described there. We do not sell your information, and we do not put it in a marketing list you did not ask for.

The waitlist

We open events where enough people want one, and invite people from the waitlist on our homepage.
What we collect: your email. If you add them: your city, your age band, whether you are a woman, a man or non-binary, and who you are looking for. If a friend's link brought you, which friend's place it was.
Why: to open a night where both sides of it can fill, to email you about the list, and to work out referral rewards.
Who you are looking for may reveal your sexual orientation. It is optional: leave it out, change it on your status page, or remove your place altogether.
Your referral link carries a code, not your name or email. When a friend joins with it, we record that their place came from yours. You see how many friends joined and confirmed, never their emails, and they see nothing about you.
Rewards are half price on your first night, or that night free, as your status page explains with their terms. A half-price code is a code you use at Luma checkout. A free night is added to your Loveline account by email address when your night opens.
The emails we send: one welcome email with your referral link when you join (and your link again if you join a second time, at most once an hour), one reminder if you haven't added your details a day after joining, and one when you earn a reward. Nothing else comes from the list, and each email has an unsubscribe link.
Unsubscribe stops every email from the list. Your status page keeps working.
Remove me, on your status page, deletes your place, your details and your rewards straight away. Rewards a friend already earned from you stay theirs. Deleting your Loveline account also deletes a place on the list with the same email.
In your browser: a friend's referral code is kept for 30 days so it counts if you join later. The private link to your status page is kept only in the tab you opened it in, and taken out of the address bar.
Analytics counts joins, saved details, confirmations and which share button was pressed. It never receives your email, your city or who you are looking for.

Dates are never recorded

There is no recording feature in Loveline. There is no recording running underneath it, at us or at the company that carries the audio. Of the date itself, we keep the time you joined, the time you left, the reason it ended, and technical numbers about the connection: how much of the audio was lost or arrived late, the delay, the bitrate, how often the connection dropped and came back, and whether any sound was arriving. Your browser measures these every few seconds and, during the date, keeps one running summary for it up to date with us. They contain no sound, no words and nothing anyone said. If you answer "How was the sound on that date?", we keep your answer with them. We use them to find and fix bad connections, on the event and afterwards.
We cannot stop another attendee recording you on a second device. Recording someone else breaches our guidelines and we remove people for it, but we would rather you knew than felt tricked.

The services we use, and where they are

We use other companies to run parts of Loveline, including for analytics. Some of them store information overseas, including in the United States, South Korea and Singapore, which means your information may be handled outside Australia. We stay responsible for it.
Company
Supabase
What they handle
Our database, sign-in and photo storage
Where
South Korea
Company
LiveKit
What they handle
Carries the audio for your dates. Sees a room code and an anonymous id, never your name. No audio is recorded
Where
[region to be confirmed]
Company
Stripe
What they handle
Historical verification records, if you used the former verification process
Where
United States and Ireland
Company
Luma
What they handle
Your ticket and payment
Where
United States
Company
Resend
What they handle
The emails we send you
Where
United States
Company
Twilio
What they handle
Sends verification codes, factual service texts about booked events, and the one text telling a friend about a free seat
Where
United States
Company
PostHog
What they handle
Analytics
Where
United States
Company
Vercel
What they handle
Hosting the app
Where
South Korea, and worldwide for the public site
Company
Railway
What they handle
Hosting the server
Where
Singapore
Company
Google Tag Manager
What they handle
May load the advertising tools below on our public website
Where
United States
Company
Google (Analytics and Ads)
What they handle
Advertising, and measuring which of our Google ads work
Where
United States
Company
Meta (Facebook and Instagram)
What they handle
Advertising, and measuring which of our Meta ads work
Where
United States
Company
OpenAI
What they handle
Advertising, and measuring which of our ads in ChatGPT work
Where
United States

Advertising

We may advertise Loveline with the platforms named above, and use their tools to see which ads lead to bookings. Loveline itself shows no ads. This is everything they can get from us, and it only happens while we are running ads with them.
On our public website. On the public pages, such as our evenings and the FAQ, these platforms' code, loaded directly or through Google Tag Manager, can set cookies and record what you do there: for example, that you looked at an evening or clicked Book tickets. Like any website code, it also sees your browser, your IP address and the page address, which can name the evening. It is never loaded on sign-in, in the app, on your dates or on your profile.
When you buy a ticket or claim your place. Our server can tell these platforms that it happened, which evening it was for and which of their ads you came from, if any. It sends your email address and phone number in scrambled (hashed) form, so a platform can only match them to an account it already has. We never send your name, your date of birth, your profile, your orientation or anything about your dates.
When you join the waitlist. Our server can tell these platforms that you joined, and which of their ads you came from, if any. It sends your email address in scrambled (hashed) form, and the IP address and browser type your browser used to join, which a platform needs to match a website sign-up to an account it already has. It does not send your name, your phone number or anything else you typed.
What that can say about you. Some of our evenings are for particular groups of people, so a platform that knows you looked at or booked one could infer something about your sexual orientation. That is why we keep what they get to a minimum.
Where it goes. These platforms are in the United States. We do not sell your information to them, or to anyone.
Opting out. Each platform's own ad settings control how it uses what it gets. Blocking cookies, or using your browser's tracking protection or an ad blocker, stops the website part. You can also write to hello@loveline.events and we will stop sending your email and phone number to them. We keep a scrambled copy of each, so our server can recognise them and leave you out.

Age confirmation

You confirm you are 18 or over when signing up. Your age is based on the date of birth you give us. Your saved DOB is locked. If it is wrong, ask support to correct it; we record the decision.
If you used our former verification process, historical references and results may remain on your account. Stripe holds anything submitted to it under its own privacy policy. Account deletion still requests redaction of an existing Stripe record.

How long we keep things

Reports: 12 months from when they were made.
Records of when you joined and left a date: 90 days.
Technical date quality numbers, and your answer about the sound: 90 days after the event.
Messages your host or Loveline staff send during an event, and whether your browser fetched or dismissed them: 90 days after the event.
Records of dates changed by a removal, block or account deletion: user IDs, date and room references, and removal details are kept for 365 days after the event, for pairing history and reviewing removals.
A friend's first name and mobile number from bring a friend, and the first name and number in their text: 90 days after the event.
The coded copy of a number that asked us not to text it: for as long as we send these texts, because it is what stops the next one.
Usage numbers: 12 months.
Saved game answers: until replaced, deleted, sharing consent is withdrawn or the account is deleted; we keep no answer-history archive.
Restricted enforcement records: only for as long as their rule requires, as described below.
Your place on the waitlist, your details and your rewards: until you remove them from your status page, or delete your Loveline account.
Other ordinary account information: until account deletion or 24 months without attending.

Deleting your account

Settings, then Delete my account. It takes effect immediately and it cannot be undone.
We delete your public profile, photos, saved game answers and ordinary account/contact data, and, if you used the former verification process, we ask Stripe to redact that record. Some restricted records stay: reports involving you for 12 months; protected contact-matching identifiers, the locked date of birth and restriction references for as long as their safety, repeat-exclusion or ban purpose requires; anonymised date history; anything you gave an evening's waitlist or the interest form until you ask us to remove it (a place on the Loveline waitlist with your email is deleted with your account); and analytics about how you used Loveline under a random id until it expires.
Internal tags on your account, and the date quality numbers from your phone, are deleted. The log of what staff did keeps that something happened, but no longer says it was about you.
The email on a ticket for an event that has not finished stays until 90 days after that event, so the same ticket cannot be claimed twice.
Protected contact identifiers and DOB remain personal information. We protect DOB separately and restrict access. These minimal records enforce the DOB lock, blocks, final confirmed noes, previous connections, the 12-calendar-month repeat rule and manual bans, including re-registration with the same confirmed contacts. They contain no profile content or images and are deleted when their rule no longer requires them. Previously delivered contact details and saved photos cannot be recalled.

Seeing your information, or correcting it

Write to hello@loveline.events and we will send you what we hold within 30 days, free. If something is wrong, tell us and we will fix it. Most of it you can change yourself in the app.

If something goes wrong

If information about you is exposed and it could cause you serious harm, we will tell you and the Office of the Australian Information Commissioner as soon as we can, and we will say what happened, what was involved, and what to do about it. We will not sit on it.

Complaints

Write to hello@loveline.events with "Privacy complaint" in the subject. A person will answer within two working days and we will resolve it within 30. If we do not, or you are not happy with the answer, you can take it to the Office of the Australian Information Commissioner: oaic.gov.au, 1300 363 992.

Contact

Flectra t/a Loveline.events, ABN 74 852 587 452 [postal address to be confirmed] hello@loveline.events