1. Each team must comprise 2-4 members. As a participant, you should make sure to check how many prizes are available per team. There is usually a limited number of prizes for each challenge. So if you form a large team and win a challenge, there might not be enough prizes for everyone on your team.

2. Each team is eligible to win one prize at the host institution where the team participates at the hackathon. The judging panel at each host institution shall decide the recipient team for each prize available at the host institution.

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

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

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

6. Teams are encouraged to bounce their idea off the teams in the partner host institution during the hackathon. Each team should acknowledge any idea and/or advice received from participants in the partner host institution at their solution pitch at the Pitch Event.

7. All work on a project should be done at the hackathon.

8. Teams can use an idea they had before the event.

9. 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.

10. Teams can work on an idea that they have worked on before, but the work needs to address one of the given AI/ML challenges. You must make clear which parts of the submitted solution have been carried out during the hackathon.

11. 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.

12. Adding new features to existing projects is allowed. Judges will only consider new functionality introduced or new features added during the hackathon in determining the winners.

13. 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 demonstrating 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. 14. Projects that violate the Code of Conduct are not allowed.

15. 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, or other unsporting behaviour.