Trust & Safety at Event Flo | How We Protect You

Learn how Event Flo keeps you safe with ID verification on by default, data encryption, and anti-fraud measures. Your safety is our top priority.

Frequently asked questions

Is Event Flo safe?

Yes. Event Flo checks government ID for every host of a public or members-only event. A private event can go live right away: until the host is verified, guests join by invite or at the door. Guest ID verification is on by default, so a guest who signs up through the event page is confirmed only after their ID is verified. This creates full accountability, with no anonymous RSVPs when verification is on.

How does ID verification work on Event Flo?

You upload a photo of your government ID (Aadhaar, passport, or driver's license). Our team manually reviews each submission. Once verified, you can access all events. Verification is a one-time process.

What data does Event Flo store about me?

Event Flo stores your display name, email, and verification status. Your ID document is reviewed for verification and then handled per our privacy policy. We do not sell your data to third parties.

How can I report unsafe behavior at an Event Flo event?

Email safety@event-flo.com with the event name and what happened. Hosts can also decline or block a guest from their future events, and guest ID verification is on by default, so a report about a verified guest is tied to a real person.

Can hosts see my personal information?

Hosts of an event you ask to join see your name, email address, city, gender, verification status, your answers to their registration questions, your RSVP and check-in status, and whether you meet the event’s age limit, and they can download that as a spreadsheet. They never see your ID document: only the Event Flo team reviews it, and it is deleted 7 days after you are verified.

What privacy controls do I need for guest data?

Collect only what the event needs, limit who can see it, and delete what you no longer need. Event Flo is built that way: hosts see a guest's name, email, city, gender, verification status and answers to their registration questions — never the ID document, which only the Event Flo team reviews and which is deleted 7 days after verification. For house parties, the exact address goes only to approved guests, starting 2 hours before the event. Door staff phones cache only ticket codes, names and entry flags — no emails or phone numbers.

What is the safest way to collect guest information online?

Use a platform that verifies identity without handing documents to you. On Event Flo, guests upload a government ID once to Event Flo rather than to each host; a person on the Event Flo team reviews it, and the image is deleted 7 days after approval. You collect only what you ask in your registration questions, the answers stay in your event dashboard, and you never receive passport or Aadhaar photos over WhatsApp or a Google Form. Hosts can export their guest list as a spreadsheet, so keep that file as private as the event itself.

How does event verification build safer communities?

It removes anonymity, which most bad behaviour at in-person events depends on. On Event Flo, hosts of public and members-only events verify a government ID, as do community members, and guest ID checks are on by default for events, so a report is tied to a real person and a new account still needs a real ID to get in. A private event can go live before its host is verified, with guests joining by invite or at the door. People behave differently when they know they are known — and hosts can approve who joins, scan tickets at the door, and block a guest from an event when something goes wrong.