Privacy Policy and Terms

We collect the information users provide during registration, login, event creation, attendee booking, QR check-in, profile updates, and support interactions. This may include name, email address, phone number, country, address, password hashes, event details, booking references, attendance records, and uploaded assets such as banners.

Data is used to authenticate users, assign organizer or admin access, create and manage events, display public registration forms, generate booking references, verify QR scans, record attendance, show reports, and send operational notices. We do not use attendee data for unrelated purposes.

Organizers can access only the events and attendee records they manage. Admin users can access the full platform for oversight, support, security, and product administration.

Camera permission is requested only when a user opens the QR check-in screen or starts scanner mode. The camera is used solely to read QR codes and is not stored or transmitted as a video recording by the application.

Event records, registrations, attendance timestamps, and audit trails are retained for operational and reporting purposes. Passwords are stored as secure hashes. Where possible, we keep data only as long as needed for the platform, legal obligations, security, and support.

The application uses role-based access, authenticated sessions, validated forms, and guarded check-in actions. Users are responsible for keeping login credentials private and for protecting their devices during live check-in.

Users must provide accurate information, keep credentials secure, and use the platform only for legitimate event operations. Organizer accounts are for managing their own events, while admin accounts are reserved for platform oversight.

The system may not be used for unlawful activity, unauthorized access, automated abuse, fraudulent attendance marking, or attempts to interfere with the check-in and booking workflow.

Public event pages may collect attendee details requested by the organizer. Those fields are presented to attendees before submission and are used only for that event's registration and attendance process.

The interface and data handling are designed to support international use, responsive layouts, and multilingual-ready structures. Any local compliance obligations remain the responsibility of the event owner or organization.