A little clarity.
This notice covers the information you submit through this UpLeague website.
What we collect
When you contact us, we store your name, email address, inquiry topic, message, consent, and submission time. If you join an event interest list, we store your email address, selected event, and signup time.
How it is used
Contact details are used to review and respond to inquiries. Event interest signups are used for relevant launch announcements. Signing up does not register you for a competition or guarantee a place.
Your UpLeague account
Firebase Authentication, operated by Google, handles email/password and configured Google sign-in. UpLeague stores your Firebase user ID, email address, sign-in method, username, full name for certificates, and profile creation time in its hosted database. Signup does not collect a mobile number. Passwords and Google credentials are not stored in UpLeague’s participant database. Email ownership is not verified by our email/password signup flow. Numbers submitted through the earlier signup form may remain in existing records; you can request their removal through our contact form.
Event registration
Creating an account does not automatically enroll you. When you register, we record your user ID, event, registration reference, acknowledgement of the displayed rules and eligibility requirements, and registration time. We use your details to manage participation and prepare eligible certificates. Account creation does not subscribe you to marketing. This registration flow does not collect payment details.
Competition attempts
For Round 1, we store your submitted answers, review flags, question and rules version, start and deadline, save revision, submission time and score. These records support assessment delivery, private results and participation eligibility. Your browser keeps a recovery copy of answers, identified by account and attempt, so interrupted work can resume. Unsent answers cannot count after the deadline. Recovery copies remain on that device; on shared devices, sign out and clear site data when you no longer need recovery. Local organizer mocks use a separate ownership cookie and do not enter official results.
Reports and Round 2 payments
Neon stores your assessment report, score, shared rank and qualification after results are released. Your report is private to your authenticated account. PDF downloads are created in your browser from that report; no report files are uploaded to object storage. If checkout opens, Razorpay processes payment details. UpLeague stores purchase references, provider order and payment IDs, amount, mode, payment status, normalized audit events and access confirmation. UpLeague does not store card numbers, CVV or bank credentials. Test entitlements are separate from live access.
Sign-in and technical data
Firebase maintains sign-in state in your browser and processes authentication requests. Hosting providers process technical connection information; UpLeague uses hashed identifiers and short time windows to limit abusive account requests. Do not use a shared device without signing out. No password-reset or email-verification workflow is offered here.
Certificate verification
Looking up a certificate ID may display its recipient name, event, recognition, issue date, and status. Only details intended for certificate verification belong in this registry. The demonstration record is not a real award.
Storage and preferences
Submitted records are stored in the website’s hosted database. Your light or dark theme preference is stored locally in your browser. This site does not include advertising trackers. Hosting and access providers may process technical information as part of operating the website.
Your choices
You can request access, correction, deletion, or removal from event updates through our contact form. Include the email address used for the original submission so the team can identify your records.