SusHacks is built on trust, creativity, and collaboration. These guidelines exist to make the event safe and enjoyable for every crewmate — we expect all participants to follow them without exception.
Be kind. Build original things. Don't be sus. Anyone who makes the event unsafe or unfair for others will be ejected.
Treat every participant, mentor, judge, sponsor, and organiser with respect. Harassment, intimidation, or discrimination based on gender, sexual orientation, disability, race, ethnicity, religion, age, or any other characteristic will not be tolerated.
SusHacks is for everyone. Welcome participants of all skill levels, backgrounds, and disciplines. Help newcomers feel at home. Avoid gatekeeping — this is a space to learn and grow together.
All code and design submitted must be written during the hackathon. You may use open-source libraries, public APIs, and existing datasets. Using AI tools is permitted but must be disclosed. Pre-built projects or plagiarised submissions will be disqualified.
Team size is strictly 1–4 members. All team members must be registered. You may not work with, or share code with, members outside your registered team. If you need to change your team, contact an organiser before the hacking begins.
VIIT is our host. Keep spaces clean, do not damage property, follow all campus rules, and be mindful of noise levels in collaboration areas. Any damage caused will be the responsibility of the individual.
Do not engage in any illegal activity including but not limited to: unauthorised network access, creating malware, alcohol or drug use on campus, or any other activity that violates local law. Violations will result in immediate removal and may be reported to authorities.
If your project involves security research, it must be conducted only on systems you own or have explicit permission to test. Do not probe, scan, or attack event infrastructure or other participants' systems.
Accept judging decisions gracefully. Judges' decisions are final. Do not attempt to bribe, influence, or lobby judges. Constructive feedback is encouraged — disputes should be raised with organisers calmly and privately.
Organisers have the final say on violations. If you witness or experience a violation, report it immediately to any organiser or email us.
First violation: verbal or written warning from an organiser.
Serious or repeated violation: removal from the event without refund.
Submission violations (plagiarism, out-of-window code): team disqualified from prizes.
Severe violations: permanent ban from future SusHacks events.