HackathonHub

Legal

Privacy policy

Last updated 4 September 2026

The short version: we store your email, your name if you give one, a hash of your password, and what you bookmark. We do not sell it, share it, or run advertising or third-party analytics. Ask and we delete it.

1. Who is responsible

This service is operated by an individual (Manan Maisheri), not a company. Contact for any privacy matter: mananmmaisheri23@gmail.com.

2. What we store, and why

  • Email address — to identify your account and process your access request. Required.
  • Name — optional, used only to address you in the interface.
  • Password — stored only as a bcrypt hash. We cannot read it.
  • Access request note — if you write one when requesting access, so the operator can decide.
  • Bookmarks, recently viewed events and preferences — to power your dashboard and deadline reminders.

If you sign in with GitHub or Google, we receive your email, name and avatar from that provider. We never receive your password for those accounts.

3. What we do not do

No advertising. No third-party analytics or tracking pixels. No selling or sharing of personal data. No marketing email — the only email that would ever be sent relates to your account or a deadline you asked to be reminded about.

4. Where it lives

Data is held in a PostgreSQL database hosted by Supabase in the United States, and the application runs on Vercel. Both act as processors on the operator's behalf. Sessions are held in a signed cookie in your browser.

5. How long we keep it

For as long as your account exists. Delete the account and the associated personal data — bookmarks, view history, preferences, notifications — is deleted with it.

6. Your choices

You can ask for a copy of your data, correction of it, or its deletion, by emailing mananmmaisheri23@gmail.com. We aim to respond within 30 days. There is no charge, and you do not need to give a reason.

7. Hackathon listings are not personal data about you

The event listings on this site come from public third-party platforms and describe events, not visitors. How that data is collected is documented separately in the content and sourcing policy.

8. Changes

If this policy changes materially, the date above changes and account holders are told in-app.