Zero tolerance policy on racism, sexism, homophobia, abuse, or anything inappropriate. If you would like to report any misconduct, please do so here: https://forms.gle/fesB8qdpSaCRiyAD7 

There is a maximum team size of 4, no minimum team size.

Teams should be made up exclusively of students who are not organizers, during-event volunteers, judges, sponsors, or in any other privileged position at the event.

All team members should be present at the event. Leaving the venue for some time to hack elsewhere is fine.

Teams can of course gain advice and support from organizers, volunteers, sponsors, and others.

All work on a project should be done at the hackathon (do not start having before 12pm on Saturday, 4/29 or after 12pm on Sunday, 4/30)

Teams can use an idea they had before the event.

Teams can work on ideas that have already been done. Hacks do not have to be “innovative”. If somebody wants to work on a common idea they should be allowed to do so and should be judged on the quality of their hack. These days it’s hard to find something that’s fully original and teams might not know an idea has been done before anyway.

Teams can work on an idea that they have worked on before (as long as they do not re-use code).

Teams can use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.

Teams must stop hacking once the time is up. However, teams are allowed to debug and make small fixes to their programs after time is up. e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it's okay to fix that. Making large changes or adding new features is not allowed.

Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, or other unsporting behavior.