Project rules

Remember that hackathons are like marathons. Some people go to compete, but most people take part to improve themselves and have fun. Whatever the reason is, you’re at a hackathon! Make sure you’re embracing the hacker spirit by collaborating with other teams, helping others, and having fun.

  1. Participants and teams must be made up exclusively of high school students from the Greater Toronto Area who are not organizers, judges, sponsors, or in any other privileged position at the event.
  2. Participants are allowed to seek advice and support from organizers, volunteers/mentors, sponsors, and others.
  3. Teams are limited to a maximum of four people.
  4. Each individual can only be part of one team.
  5. Participants may only work on their submission during the allotted hacking time (10:00PM June 25th, 2021 to 11:00AM June 27th, 2021).
    • Participants can use libraries, frameworks, or open-source code in their projects.
      • They may not plagiarize another participant’s or person’s code or design.
      • It is prohibited to work on a project or library prior to the start of the hackathon (10:00PM June 25th, 2021), and open-source it for the hackathon.
    • Participants must properly disclose any parts of their creation that they did not make themselves.
  6. A functional creation must be made; an idea/concept will not suffice.
    • Example of what’s allowed: An application that detects if you are in risk of a natural disaster that takes information from the internet and implements it so that the program functions properly (alerts the user if they are at risk of a natural disaster).
    • Example of what’s not allowed: Making an application that helps you navigate hiking paths based on how other users navigate them, but instead is a static map with some lines drawn through them. This is a concept and it does not include the use of the aforementioned data based on how other users navigate.
  7. Teams are not allowed to keep working on the project once the time limit is reached. Working on the project after the time limit has passed will result in immediate disqualification.
  8. Recess Hacks will not use participants’ projects in any way without permission except for displaying them on the Devpost site for public voting and for the project showcase. Participants reserve complete ownership of their intellectual property.
  9. In order to be judged and receive prizes (except for the students’ choice prize) participants must present their project live to a panel of judges, after which the judges will be able to ask questions.
  10. Participants’ presentations may be no longer than 3 minutes. This does not include the time frame where judges may ask questions regarding the project.
  11. Violating the Recess Hacks Code of Conduct may result in a disqualification and barring from the event.
  12. Teams can be disqualified from the competition at the organizers' discretion. Reasons might include, but are not limited to: breaking the Competition Rules, breaking the Code of Conduct, and other unsportsmanlike behaviour.
  13. The organizers have the final say in any matter or argument regarding the rules.
  14. If you have any questions regarding the rules, please email