Swipe or use the arrow keys to scroll when more options are out of view.
Applications are now closed.
HackTheBurgh

Code of conduct

The MLH Code of Conduct applies to everyone at HackTheBurgh.

Everyone taking part must follow the MLH Code of Conduct. The HackTheBurgh rules below supplement that code. If the two conflict, the MLH Code of Conduct takes precedence. This does not override applicable law or University and venue safety requirements.

HackTheBurgh is intended to be a fun, safe, and inclusive environment for hackers. To ensure that every hacker is given an equal opportunity in a welcoming environment, everyone taking part must follow the MLH Code of Conduct and the additional rules below.

These requirements apply to participants, organisers, volunteers, sponsors, speakers, mentors, judges, vendors and MLH staff, at the venue, related social events, event-provided transport and in event-related online spaces and communications.

Taking part

We ask that all attendees approach HackTheBurgh with good intentions, kindness and a spirit of fun. Be welcoming and helpful to everyone, even if you’ve not met them before. Above all, make it a great experience for you and everyone else!

  • Respect other people’s boundaries, privacy and property.
  • Follow reasonable safety instructions from organisers and venue staff.
  • Respect people’s photography and recording preferences. Ask if their preference is unclear, and stop if asked.
  • Be kind to our volunteers, organisers and vendors. HackTheBurgh is entirely student run.

Competition restrictions

Participants must be current students or have graduated within the last 12 months, and must be at least 18 years old when the event starts. This includes undergraduate, postgraduate, vocational and other forms of education.

  • Only work built during the official hackathon period will be considered for prizes.
  • Publicly available open-source code and libraries may be used. Follow their licences and clearly identify what your team has built.
  • Generative AI and other AI tools may be used. Disclose their use in your submission and explain what your team has built.
  • Organisers, volunteers, judges, sponsor representatives and others in privileged event roles must not compete.
  • Submitting another group’s or individual’s work as your own is cheating and may result in disqualification.
  • Disclose pre-existing code, APIs, libraries and other external contributions. Declaring work built before the event does not make it eligible for prizes. Misrepresentation of your hack, accidental or not, is considered cheating.
  • Follow the published submission deadlines and any additional rules for the challenges you enter.

You retain any intellectual property rights you hold in your project. Applicable submission and prize terms must explain any permission to publish or promote it, and any public-code requirements. Keep credentials and other private information out of public repositories.

The HackTheBurgh team will work with MLH to investigate suspected cheating under the MLH Cheating Response Procedure. Projects may be disqualified under the applicable competition rules. Raise concerns privately with an organiser or MLH rather than making public accusations. Ask an organiser before submitting if you are unsure whether something is permitted.

Harassment

HackTheBurgh follows the University of Edinburgh’s Dignity and Respect Policy. Harassment includes offensive conduct, inappropriate behaviour and unwelcome sexual attention, including improper verbal behaviour related to gender, race, age, sexual orientation, disability, nationality or religion.

Everyone attending the hackathon is expected to comply with this policy. Sponsors are subject to the same standards as hackers and volunteers. Threats, stalking, unwanted physical contact and sharing someone’s private information without permission are also unacceptable.

Reporting a concern

You can report directly to MLH.

Contact incidents@mlh.io or call 0800 808 5675 in the UK. You have the right to remain anonymous. Organisers must immediately involve the on-site MLH representative or MLH Incidents Team when an incident is reported, following the MLH Reporting Procedures.

If you feel that you are being harassed, observe another person being harassed, or have any other concerns, speak to an organiser or email hello@hacktheburgh.com. You do not need to confront the person involved. If your concern involves an organiser, you can speak to another organiser or venue staff.

Reports will be handled sensitively. Information will be shared only where needed to respond to the concern, protect someone’s safety or meet a legal obligation. We cannot promise absolute confidentiality.

For immediate danger or a medical emergency, call 999. University of Edinburgh Campus Security can be reached on 0131 650 2257. Further reporting and support options are available through Respect at Edinburgh.

How organisers may respond

MLH may take action under its Code of Conduct, including a warning or expulsion without eligibility for reimbursement or refund. Our response and any review of an MLH decision must follow the applicable MLH procedures.

If a participant engages in inappropriate conduct, the HackTheBurgh team may issue a warning, restrict participation, disqualify a project or require someone to leave, working with MLH under its procedures.

Where everyone is physically safe, police or security will be involved only at the affected person’s request, unless a legal duty requires otherwise. If anyone’s safety is in doubt, we will seek urgent help. This follows the MLH Incident Response Procedure.

Failure to follow this code may also affect eligibility for future events. Any consequences for prizes or travel reimbursement must follow the applicable event terms. Where it is safe and practical, organisers will explain their decision and give the person concerned an opportunity to respond. Immediate action may be needed to protect others.

You can ask for a HackTheBurgh decision to be reviewed by emailing hello@hacktheburgh.com. To appeal an MLH temporary suspension or permanent ban, email incidents@mlh.io with [Appeal] in the subject and relevant evidence, following the MLH Disciplinary Policy. A local review does not suspend or overturn an MLH decision. Reporting a concern in good faith must not lead to retaliation.

Questions and updates

Please contact hello@hacktheburgh.com with questions about this code. Any changes will be published on this page and material changes communicated to attendees.

Acknowledgements

MLH policies and procedures referenced in this code:

Adapted from the HackTheBurgh XI Code of Conduct, which took inspiration from the IC Hack ‘25 Code of Conduct and HackMIT 2024 Code of Conduct.

Last updated 14 September 2026.