Privacy
Last updated 29 September 2026
Hacksy is a platform for running university hackathons. This page describes what it stores, who can see it, how long it is kept, and how to have it removed.
What is collected
| Data | Where it comes from |
|---|---|
| Name, email address | Your Google account, when you sign in with Google |
| Email address | You, when you sign in with email |
| Your age, as a range (18-99), or that you chose not to say | You, the first time you sign in |
| Your school | You, when you apply or register |
| Application answers | You, on an organizer's form |
| Uploaded files, such as a résumé | You, if a form asks for one |
| Attendance and activity scans | Organizers scanning your badge at an event |
| Points and achievements | Earned at events you attend |
Hacksy does not collect payment details and does not use advertising or third-party analytics trackers.
Your age
Hacksy is for college students who are 18 or older, so we ask your age the first time you sign in. The question is a range from 18 to 99, or "prefer not to say" — never a birthdate, and never a specific day, month or year. We ask it once and keep whichever answer you gave; you are not asked again unless these terms change in a way that requires it.
Consent records
Hacksy keeps a record of a small number of things you were asked and how you answered: your agreement to these terms and to this Privacy Policy, your age answer above, and — only at events that are Major League Hacking (MLH) Member Events — the three MLH checkboxes described below. These records are added to, never edited or removed: if you change your mind about something later (for example, an MLH marketing checkbox), that is recorded as a new answer, and both the old and new answers stay on file so there is an accurate history of what you were asked and when.
Who can see it
Your data is visible to the organization running the event you applied to or registered for — and to no other organization. That separation is enforced by the database, not only by the application in front of it.
A profile is private unless you choose to make it public. Making it public shares your display name and the achievements you have earned, at a link you control.
Who else processes it
- Google — sign-in. Hacksy requests your name, email address and profile picture. If your Hacksy account has no photo yet, a copy of the picture is saved as your profile photo; you can replace it with your own at any time, and a later sign-in never changes a photo you chose.
- Auth0 — brokers that sign-in, and, if you sign in with email, sends the one-time code that proves the address is yours. No password is ever set, by you or by anyone else.
- Cloudflare — serves this site and stores uploaded files.
- Firebase Cloud Messaging — delivers notifications, if you turn them on.
Hacksy does not sell personal data and does not share it with anyone beyond the processors above and the organization whose event you joined.
MLH Member Events
Some events on Hacksy are run in partnership with Major League Hacking (MLH) as an "MLH Member Event." At those events, and only at those events, you are shown three checkboxes before you register or submit an application, in MLH's own fixed wording:
- Agreeing to the MLH Code of Conduct.
- Authorizing your application or registration information to be shared with MLH for event administration and ranking, and with MLH and DEV (dev.to) for their own administration — which includes creating a linked account for you on both MLH and DEV — under the MLH Privacy Policy, and agreeing to the MLH Contest Terms and Conditions and the MLH Privacy Policy. This one is required to register or apply at an MLH Member Event.
- Optionally authorizing MLH and DEV to email you about their own events, career opportunities and community announcements. This one is never required, and answering no to it does not affect your registration or application.
Whether an event is an MLH Member Event, and this wording, are both fixed by the platform — an organizer cannot edit or remove these checkboxes, and Hacksy does not add its own commentary to MLH's words. Your answers to these three checkboxes are recorded per event, alongside the other consent records described above.
How long it is kept
Uploaded files are deleted automatically twelve months after the event they were submitted to ends. An organization may choose a shorter period. This is deliberate: files such as résumés are the real privacy liability, and leaving them indefinitely is the mistake this platform was built to avoid.
Applications, scans, achievements and audit records persist, because your attendance history and profile depend on them.
Your choices
- See your data. Your profile and applications are visible to you in the app at any time.
- Delete your account. Deleting anonymizes it: your name, email and photo are removed, and what remains is an anonymous record so an event's attendance counts and an organizer's audit trail stay accurate.
- Notifications. Email and push preferences are per organization, and can be turned off without leaving an event.
Contact
For any question about your data, or to request its deletion, email [email protected].