Code of Conduct

Building a safe, inclusive, and ethical hackathon community

TL;DR

Be kind, be inclusive, and build ethically. No harassment, discrimination, cheating, or unsafe behavior. Report issues to staff immediately at dfw.hackz@gmail.com or +1 (972) 249-7263 (text/voice). We'll act quickly and fairly.

Who This Applies To

All participants, volunteers, mentors, judges, sponsors, vendors, speakers, and guests at any DFW Hacks venue or online space (Discord/Slack, email, social media), including after-hours activities connected to the event.

Our Values

Respect

Treat everyone with dignity.

Learning First

Support beginners and celebrate curiosity.

Integrity

Build honest projects, cite sources, and follow rules.

Safety

Keep yourself and others physically and emotionally safe.

Expected Behavior

  • Use welcoming language; respect names/pronouns.
  • Offer help generously; accept feedback graciously.
  • Keep venues clean; follow staff and facility rules.
  • Ask before photographing/recording individuals; honor "no photo" indicators.

Unacceptable Behavior

Harassment of any kind, including but not limited to:

  • • Offensive comments related to race, color, ethnicity, national origin, religion, disability, neurodiversity, body size, age, sex, gender identity/expression, sexual orientation, or any protected status.
  • • Intimidation, stalking, doxxing, or sustained disruption of talks/workshops.
  • • Unwelcome sexual attention or physical contact; deliberate misgendering/deadnaming.
  • • Inappropriate imagery or content in projects, presentations, or chat.

Cheating/Misconduct

Plagiarism, falsifying data, sabotaging others' work, or violating API/terms-of-service.

Substances & Weapons

No alcohol, vaping, illegal drugs, or weapons on site.

Safety & Minors

This is a high school–focused event.

  • • Follow check-in/out procedures.
  • • Observe posted quiet hours/curfews.
  • • Use the buddy system when leaving main areas.
  • • In an emergency, call 911 first, then notify staff.

Project & Integrity Policy

Originality

Build your project during the event. You may use prior libraries/snippets, but clearly disclose reused work.

AI Tools

Allowed if you disclose where/how AI was used (README/slides). No automated entry spam or synthetic metrics.

Plagiarism

Copying another team's work or submitting prior projects as new is prohibited.

Data & Ethics

Use only legally obtained datasets/APIs; respect licenses, rate limits, and privacy. No malware, unauthorized access, or harm.

Hardware

Follow lab/soldering safety; no high-voltage, open flames, or drones indoors without explicit staff approval.

Judging & Fair Play

  • Teams must meet submission deadlines and demo live.
  • Judges score by published criteria; their decisions are final.
  • Bribing judges or disrupting other teams' demos is prohibited.

Privacy, Media & Recording

  • • DFW Hacks may photograph/record the event for promotional use.
  • • We provide photo-opt-out indicators; staff will honor them.
  • • Ask consent before recording individuals or private screens.

Reporting a Problem

If you experience or witness a violation:

Contact staff immediately: look for volunteers with "DFW Hacks Staff" badges, or use:

+1 (972) 249-7263 (text/voice)

We'll acknowledge receipt, assess risk, and act. We strive to protect reporter privacy; no retaliation is tolerated.

Enforcement

Depending on severity/context, staff may:

  • • Issue a verbal/written warning
  • • Remove a person from a session/activity
  • • Disqualify a team from prizes
  • • Eject from the event without refund
  • • Notify school/parents (for minors) or venue security/law enforcement

Accessibility & Accommodations

Need accommodations (dietary, mobility, sensory, prayer space, etc.)? Email dfw.hackz@gmail.com —we're happy to help.

Project Ownership

You own your work. By demoing/submitting, you grant DFW Hacks permission to display your project for event operations, judging, and promotion.

Scope & Updates

This Code applies during the event and in related online spaces. We may revise it to improve clarity and safety.

Last updated: Sept 1, 2025.