Privacy notice
HackForChrist, BeachHack S08 · Version 2026-10-v9 · Updated 24 October 2026
This notice explains how the BeachHack organisers handle your personal data when you register for HackForChrist. Registering means you have read it and consent to the processing described here.
1. Who we are
The data fiduciary is the BeachHack organising team, CODe, Christ College of Engineering (“we”, “us”). We process your data on the basis of your consent under India’s Digital Personal Data Protection Act, 2023.
2. Information we collect
- Account. Your name, email address and profile photo from Google sign-in. We never receive your password.
- Eligibility. The domain and batch year of your college email, to confirm you are a current student. If an address is refused, we record only the reason and the domain or batch year, not the address.
- Profile. First and last name, age (never your date of birth), country of residence, phone number, department, year of study, gender, GitHub username, LinkedIn profile, an optional portfolio link, skills, a short written response, T-shirt size and food preference. Your school and level of study are recorded as the same for everyone: Christ College of Engineering, undergraduate.
- Consents. Which declarations you ticked, including Major League Hacking's, when, and the version of this notice you read.
- Team. Team name, track, project title and description, and the pitch deck.
- Activity. When you complete your profile, create or submit a team and last visit, and any action the organisers take on your team.
- Security. A one-way hash of your network address and a random browser identifier, used only to limit repeated submissions and sign-in attempts.
- Notifications. Messages in your Updates list, your device's push address if you enable notifications, and the browser type of each new sign-in.
- Help requests. Your question and its topic, the page and browser it was sent from, and your name, email and phone number so we can reply.
We use five strictly necessary cookies: your sign-in, Google sign-in security, a team invite code, an organiser’s replacement link and form rate-limiting. Unsaved answers are kept only in your browser. We do not collect government ID (including Aadhaar), passwords or location, and we use no analytics or advertising trackers.
3. How we use it
- To confirm that you are a current B.Tech student of Christ College of Engineering and a member of only one team.
- To review applications and tell each team its result, on its ticket and in its Updates.
- To plan catering and T-shirts. Gender is shown to organisers only as totals and in data exports, never on a team's page or to reviewers.
- To share your registration with Major League Hacking, as described in section 4, when you give permission on the form.
Apart from Major League Hacking, we do not share your data with sponsors, sell it or use it for advertising.
4. Who can access it
- Your teammates see your name, department and whether your profile is complete, but not your phone number, email or written response.
- Organisers and reviewers see your application except your gender, which appears only in data exports. Pitch decks are stored privately, open through links that expire within minutes, and every view is logged.
- Service providers process data only on our instructions: Vercel (hosting), Neon (database, located in Ohio, United States), Cloudinary (pitch decks) and Google (sign-in). If you turn on notifications, your browser's push service (Google, Apple or Mozilla, depending on the browser) delivers them. All data is encrypted in transit.
- Major League Hacking (MLH) is BeachHack Season 8’s league partner, based in the United States. With the permission you give on the form, we share your name, email, phone number, age, school, level of study, country of residence and which of MLH’s boxes you ticked, whether or not your team is selected, and may include your team’s name and result. This is for event administration, ranking and MLH administration, including linked accounts on MLH and DEV. MLH then handles it under the MLH Privacy Policy. MLH and DEV email you only if you tick their optional box.
5. How long we keep it
We keep your registration: your profile, your team and its pitch deck, your Updates and any help requests, whether or not your team submits or is selected. Nothing is deleted automatically. We delete your data when you ask us to (section 6).
A sign-in lasts 30 days on a device and renews while you keep using it, until you sign out. What has already been shared with MLH is kept by MLH under its own policy; deleting it here does not delete it there.
6. Your rights
- While registration is open and your team has not submitted, you can edit your profile or leave your team.
- The declarations you tick are kept as given, and a submitted team is locked. To access, correct or delete your data, or to withdraw consent, email beachhack@cce.edu.in with your team name. Withdrawing consent also withdraws you from HackForChrist.
- To withdraw what you shared with MLH, or stop MLH and DEV emails, contact MLH as its privacy policy describes, or ask us and we will pass it on.
7. Grievances
Email beachhack@cce.edu.in with “Privacy” in the subject line. If you are not satisfied with our response, you may complain to the Data Protection Board of India.
8. Changes to this notice
Any change to this notice updates the version shown above. The version you accepted is recorded with your registration.
Questions: beachhack@cce.edu.in · Event rules