Before finalizing these rules, organizers should consult a legal professional to ensure compliance with local regulations, venue policies, and sponsor requirements.
All participants must also follow the event’s Code of Conduct during the entire hackathon.

1. Eligibility

Participants must be registered for the hackathon prior to check-in.
Teams may have 1 to 4 members.
All work must be created exclusively during the hackathon period.

2. Project Requirements

Projects must be submitted before the official Devpost deadline.
Submissions must be original and created during the event.
Use of pre-existing code, datasets, or assets is allowed only if clearly declared and not the core functionality of the project.
All hardware used must be legally owned or borrowed.

3. Conduct

All participants must adhere to the event’s Code of Conduct, which includes guidelines on respect, harassment-free participation, and safety.
Any behavior that disrupts the event or threatens participants may result in disqualification.

4. Judging

Projects will be judged based on creativity, technical difficulty, functionality, and presentation.
Judges’ decisions are final.
Teams may only submit one project for judging.

5. Intellectual Property

Participants retain ownership of what they create.
By participating, teams grant organizers and sponsors permission to display and promote project submissions for event-related purposes.

6. Prohibited Actions

Participants may not:

Work on the project before the hacking period begins.
Interfere with other teams’ work or hardware.
Violate any law, policy, or venue rule.

7. Safety & Venue Rules (for in-person events)

Participants must follow all venue safety instructions, including equipment use guidelines and emergency procedures.
Sleeping areas, food distribution, and restricted zones must be respected.

8. Disqualification

Organizers reserve the right to disqualify any team or individual for rule violations, unsafe behavior, plagiarism, or failure to comply with staff instructions.