Privacy Policy — How Event Flo Protects Your Data

Event Flo helps people find and host verified events: house parties, club nights, run clubs and meetups. This policy explains what we collect, why, who can see it, and what you can do about it. It is written to describe what our systems actually do. Event Flo is operated from Kalyani Nagar, Pune, Maharashtra 411014, India. For anything in this policy, write to support@event-flo.com. Last updated November 3, 2026.

1. What we collect

When you create an account:

Your email address and a password, or your Google account. If you sign in with Google, we receive your email address, name and profile picture and nothing else.

Your first and last name, date of birth, gender and city. We ask for your date of birth to confirm you are 18 or older and because hosts can set age limits on their events, and for your city so we can show you what is happening nearby.

Optional details you choose to add: a photo, a short bio, your neighbourhood, occupation, languages, interests and similar answers about yourself.

We do not ask account holders for a phone number.

Identity verification:

To host or attend most events, you upload one photo of a government-issued ID, such as a passport, Aadhaar card or driving licence. A member of our team reviews it by hand and marks your account verified or rejected. Section 4 explains how we store it.

We do not use selfies, face matching or any other biometric identification.

As you use Event Flo:

Events you create, requests to attend and their status, answers you give to questions a host has written, your tickets and QR codes, when you were checked in at a door, events you save, reviews you write, communities you join, and messages hosts send to their guests.

If a host adds you to a guest list:

Hosts can upload a guest list of names, email addresses and phone numbers for people who do not have an Event Flo account. If you received a ticket, an address email or a host’s update about their event from us without signing up, that is why. Section 8 explains what you can ask us to do.

Hosts’ notes about guests:

A host can add a guest to their own blocked list, or to a private VIP list, with a note explaining why. Those notes are visible to that host and to our staff.

When you contact us:

The name, email address and message you send through our contact form or by email.

Automatically:

Your IP address, browser and device information, and how you move through the site. Section 6 lists the companies involved.

We never collect payment card, bank account or UPI details. Guests pay hosts directly and Event Flo never handles the money.

2. Why we use it

To run the platform: create your account, show you events, process RSVPs, issue tickets and check you in at the door.

To keep events safe: verify identity, apply age limits a host has set, honour hosts’ blocked lists, and protect the exact address of house parties (section 5).

To contact you about what you signed up for: approvals, tickets, reminders, changes to an event, and the address of a house party you have been approved for.

To pass on a host’s updates: when a host adds you to their guest list, we email you the updates they send about that event. Each one has a link to stop that host’s updates.

To improve the product: see which features are used and where people get stuck.

To suggest events you might like, based on your city, your interests, the communities you belong to and events you have attended.

To send occasional promotional email, unless you have turned it off (section 8).

To meet legal obligations and respond to lawful requests.

3. Who can see your information

Anyone visiting the site can see your display name, photo, city, neighbourhood, bio, occupation, languages, interests, whether you are verified, and when you joined, along with any review you write. Public event pages are also visible to search engines.

Other signed-in members can additionally see your first and last name, gender and vibes. They cannot see who else is attending an event.

A host whose event you asked to join sees your name, email address, city, gender, verification status, your answers to their questions, your RSVP status, when you checked in, and whether you meet that event’s age limit. Hosts can download this as a spreadsheet. Hosts never see your ID document or your date of birth.

Door staff at an event see the guest list for that event: names, ticket codes, and whether entry is allowed.

Event Flo staff can see your account details, including your email address, date of birth and ID document, when reviewing verification, investigating a safety report, or providing support.

We do not sell your personal data, and we do not share it for advertising.

4. Your ID document

It is stored in private storage. It is not public and cannot be browsed or guessed at.

Only you and Event Flo staff can open it, through a temporary link.

Hosts never see it. They only see that your account is verified.

We review it by hand. We do not send it to any outside verification company.

We delete the image 7 days after your account is verified. If it’s rejected, it is deleted within a day. If you upload a newer one, the earlier image is deleted within a day. If you delete your account first, it goes with it. We keep the fact that you’re verified, but not the image.

5. Event addresses

For house parties, the exact address is protected by our systems, not just hidden on screen. It is released only to the host, our staff, that event’s door staff, and guests the host has approved, and only from two hours before the event starts. Before that, nobody else can read it, including through our public interfaces.

For other events, such as club nights at a venue, the address is public because the venue is.

The city and neighbourhood on your profile are visible to everyone.

Event pages include an embedded Google map, and hosts see address suggestions from Google as they type a location. Both send data to Google (section 6).

6. Cookies, analytics and other companies

We use these companies to run Event Flo. Some of them process data outside India, including in the United States and the European Union.

Supabase stores your account, profile, events and ID document, and handles sign-in.

Cloudflare serves the site, sees your IP address and request details, and briefly caches public pages.

Resend sends our email and receives your email address and the contents of each message.

PostHog (United States) receives product analytics: your user ID and email address, pages viewed, clicks and form interactions, searches you type, performance data and error reports.

Crisp (France) runs our support chat: it receives the messages and files you send in the chat, any email address you give it, your IP address, device details and the pages you visit.

Google Analytics and Google Tag Manager receive pages viewed, the referring site, your IP address and device details.

Google Maps receives the addresses and city names you type into address and city fields (creating an event, signing up, organizer settings, your venue page) with your IP address, to suggest places, and the venue address plus your IP address when a map loads on an event page.

goQR.me (Germany) receives your ticket’s code to create the QR image in ticket emails.

Unsplash sees your IP address when one of its stock photos loads on our pages.

We and these companies set cookies and store small amounts of data in your browser for sign-in, security, keeping your support chat conversation, remembering your preferences, and analytics. Analytics cookies are set when you visit the site; you can block them with your browser settings or a blocking extension.

7. How long we keep it

Your account and its contents stay until you delete your account.

Records of emails we sent you are deleted after 30 days.

Your ID document: deleted 7 days after verification, or within a day of a rejection or a newer upload (section 4).

Door check-in records and guest lists uploaded by hosts stay with the event, until the host or the account is deleted.

If you stop a host’s updates, we keep your email address on that host’s do-not-send list so we can keep honouring it, until the host deletes their account.

Contact form messages are kept so we can follow up. Email us to have yours deleted.

8. Your choices and rights

Delete your account:

In Settings, choose Delete account. This removes your profile, your ID document, your photos, the events you created together with their guest lists and tickets, the communities you created together with their member lists, the venue pages you created together with their documents, your RSVPs and saved events, and finally your sign-in. If you host events, run communities or list a venue, deleting your account also deletes them for your guests and members.

Some things remain after deletion, and we want to be straight about it:

Door check-in records, with your identity removed where possible.

Messages you sent us through the contact form, unless you ask us to delete them.

Copies of public pages already cached, for up to an hour.

Our analytics provider’s record of your activity. Email us and we will have it removed.

Guest lists a host has already downloaded, or that sit on a door staff member’s phone, are outside our control.

Correct your details:

In Settings. Date of birth and city can be changed but not left empty, because events rely on them.

Stop promotional email:

One switch in Settings. It stops promotional messages. You will still get service messages: ticket confirmations, approvals, reminders, changes to an event you are attending, and the address of a house party you are approved for.

Withdraw from an event:

At any time, from your ticket.

Ask for a copy of your data:

Email support@event-flo.com and we will put it together for you.

If a host added you without an account:

Every update a host sends you through us has a link to stop that host’s updates, and it works without an account. To be taken off the guest list altogether, email us and we will remove you and stop emailing you.

Complaints:

Write to our Grievance Officer, Anil Kumar, at grievance@event-flo.com. We acknowledge within 24 hours and resolve within 15 days; our Grievance Redressal page explains the process. Once you have used it, you can complain to the Data Protection Board of India, or, depending on where you live, to the data protection authority in your country.

9. Age

Event Flo is intended for adults. We ask for your date of birth when you sign up, and hosts can set an age limit on any event, which we enforce when you ask to attend. If you believe someone under the age required by their local law is using Event Flo, email us and we will act on it.

10. Security

Your data sits with established providers, in private storage, and access is limited by role: hosts see their guests, door staff see their door, and only our staff can open ID documents. We use encrypted connections throughout. No service can promise perfect security; if a breach affects you, we will tell you.

11. Changes

If we change this policy in a way that matters, we will update the date at the top and tell you by email or in the product.

12. Contact

support@event-flo.com · TFY Management Services Private Limited, Kalyani Nagar, Pune, Maharashtra 411014, India

Grievance Officer: Anil Kumar, Compliance Officer · grievance@event-flo.com