Privacy Policy
Last updated: 3 November 2026
Eveora (“we”) is a student web-design project for browsing and reserving events. This policy explains what information the website uses, why, and who can see it.
1. Information we collect
- Google account details: when you sign in with Google we receive your name, email address and profile picture. We only request these basic profile details.
- Reservation details: your phone number, the event, the number of tickets and the amount.
- Payment proof: the UTR / UPI reference number and the payment screenshot you upload. We never ask for card numbers, UPI PINs or bank passwords.
- Preferences: your light/dark theme choice, kept only in your browser.
2. How we use it
Only to manage your reservation: to verify your payment, issue your ticket, show your booking status and contact you about your booking if needed.
3. Where it is stored and who can see it
Reservations and payment proofs are stored in Google Firebase (Cloud Firestore). Security rules ensure that you can see only your own bookings. Eveora's administrators can see all reservations and payment screenshots in order to verify payments. We do not sell or share your information with anyone else.
4. Third-party services
- Google Identity Services & Firebase – sign-in and data storage (Google Privacy Policy).
- Google Fonts, Unsplash (images), cdnjs (QR code library) and GitHub Pages (hosting) may receive standard technical information such as your IP address when your browser loads their resources.
5. Cookies
Eveora does not set advertising or tracking cookies. Google and Firebase use browser storage to keep you signed in.
6. Your choices
- Sign out at any time from the profile menu.
- Cancel a reservation from My Bookings while it is under verification.
- Ask us to delete your reservations and payment proofs by opening an issue on the GitHub repository below.
- Remove Eveora's access to your Google account at myaccount.google.com/connections.
7. Children
Eveora is not directed at children under 13.
8. Changes and contact
We may update this policy and will change the date above when we do. Questions? Open an issue on the GitHub repository.