1. Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, religion or political views, sexual images in public spaces, deliberate intimidation, stalking, following, photography or audio/video recording against reasonable consent, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.

2. Any form of photography during the contest is not encouraged unless with permission from the contest’s administration.

3. Participants asked to stop any harassing behavior are expected to comply immediately.

4. As this is a contest, we like to explicitly note that the entries created at our contest are equally subject to the anti-harassment policy.

5. Sponsors and partners are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Sponsor representatives (including volunteers) should not use sexualized clothing/uniforms/costumes or otherwise create a sexualized environment.

6. If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of the hackathon staff immediately.

7. Hackathon staff will be happy to help participants contact any local security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the hackathon. We value your attendance.

8. If a participant engages in harassing behavior, the hackathon organizers may take any action they deem appropriate. This includes warning the offender, expulsion from the hackathon with no refund (if applicable), or reporting their behavior to local law enforcement.

9. We expect participants to follow these rules at hackathon and workshop venues and hackathon-related social events.

10. Fresh Code Rule
All code written at the hackathon MUST be written THAT DAY. You can use information gathered from the workshops (and that will be looked at very highly). Code that cannot be written prior to the competition includes:
• Mockups
• User flows
• User personas
• Color themes and palettes
• Team Name/App Name
• Team logo/App logo
• Outlined notes
• Anything else that isn’t coded itself

11. Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.

12. Exercise consideration and respect in your speech and actions.

13. Attempt collaboration before conflict.

14. Be mindful of your surroundings and of your fellow participants. Alert the organizers of the hackathon if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.

15. If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify one of the organizers with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies.