Website policy
Privacy policy
This policy describes the information collected by this website and the Latency ticketing system operated by the event organizing team.
Last updated 6 October 2026
Information we collect
When you visit the site, we may record the page path, time, IP address when our hosting proxy provides it, browser user agent, a pseudonymous visitor identifier, and actions such as opening checkout or attempting staff login. On the Latency registration page, we record the name, USN or attendee identifier, phone number for outside attendees, branch or organization, email, selected ticket slab, and entered field progress, including if you leave without paying. Paid ticket records also contain payment references, ticket status, and entry scan time. Staff account and access activity is recorded separately.
Why we use it
We use this information to reserve limited seats, prevent duplicate identifier bookings, confirm payments, issue and email tickets, check admission, synchronize the organizer's ticket register, troubleshoot errors, and investigate suspected misuse. Activity records are visible through an owner-only panel. Authorized ticket administrators can view the ticket roster; authorized entry staff can check ticket validity and attendee identity.
Services involved
Razorpay handles checkout and payment processing. Supabase stores ticket, staff, and activity records. Resend sends ticket emails. Google Sheets holds an organizer ticket register. Our hosting provider serves the website. Sponsorship enquiries submitted through the separate sponsor form are sent to Web3Forms. Each service handles the information needed for its role under its own terms and privacy practices. The website does not collect or store full card details.
Cookies and browser storage
We use a visitor identifier cookie for activity and rate limiting, a short-lived checkout cookie to return you to your order, and a staff session cookie for authorized team members. The checkout page also stores its current order identifier in your browser so you can check payment status after a reload. Razorpay may use its own browser technology while checkout is loaded.
Retention and security
Activity logs, including unpaid registration progress, are retained until the owner manually deletes them; there is no automatic deletion period. Ticket, payment, and check-in records are managed separately. Access to activity logs is limited in the website to the designated owner account; a person with database administration access may also access them. We use access controls, server-side payment checks, and single-use admission checks, but no online system can guarantee absolute security.
Questions or requests
To ask about your information or request a correction or deletion, contact the event team through the contact page. Some payment and ticket records may need to be retained to resolve a transaction, dispute, or applicable obligation. Please include enough information to identify your registration, but do not email card numbers or account passwords.