Organization Clock - Eastern Time (ET) ()
Hack University Hacker Guide

Code of Conduct

The event is built to be safe, useful, and inclusive for everyone. This applies to in-person spaces, Zoom sessions, live demos, social media, GitHub, Discord, and every other official event channel.

Our Commitment

The hackathon is committed to providing a safe and comfortable, harassment-free experience for everyone.

Gender Gender identity and expression Age Sexual orientation Disability Physical appearance Body size Race Ethnicity Nationality Religion Political views Hackathon experience Computing experience Programming language or tech stack

Zero Tolerance

Harassment Is Not Accepted

Harassment of hackathon participants is not tolerated in any form, including during demos, team collaboration, workshops, presentations, or online communication.

  • Hacks and project workspaces
  • Talks, presentations, and demos
  • Workshops and side events
  • Associated parties or networking spaces

Applies Online Too

This standard also applies to social platforms and event tooling.

  • Social media
  • Discord and chat spaces
  • GitHub comments and repos
  • Any other online media connected to the event

Important

Participants violating these rules may be sanctioned or expelled from the hackathon without a refund, if applicable, at the discretion of the organizers.

Respect Across Every Competition Type

These expectations apply equally to the Technical Competition, Start-Up Competition, and Analytics Competition.

Respect People

  • Respect judges, mentors, volunteers, organizers, and other teams.
  • Keep communication professional even under deadline pressure.
  • Do not create a hostile or exclusionary environment.

Respect the Work

  • Credit AI tools, external datasets, open-source code, and outside help.
  • Do not misrepresent what your team built, coded, analyzed, or designed.
  • Do not hide limitations that matter to judges.

Respect the Review Process

  • Present honestly in the repo, slides, Devpost page, and videos.
  • Keep links public and accessible.
  • Use a clear, truthful demo and explain the project accurately.