GlobeHack Season 1: Official Rules

Disclaimer: These rules are for internal planning purposes. Please have a qualified professional or ASU legal counsel review these before publishing.

1. Dates & Deadlines
  • Event Dates: April 18–19, 2026.

  • Registration Deadline: April 15, 2026, at 11:59 PM MST.

  • Project Submission Deadline: April 19, 2026, at 11:00 AM MST. No late submissions will be accepted.

  • Awards Ceremony: April 19, 2026, at 3:00 PM MST.

2. Eligibility
  • Participation: Participation is open to all currently enrolled Arizona State University (ASU) students.

  • Team Size: Teams must consist of 1–4 participants. Solo participants are permitted but encouraged to join a team during the Saturday morning formation session.

  • Disqualification: Any attempt to manipulate voting, use unauthorized code, or violate the Code of Conduct will result in immediate disqualification.

3. Project and Submission Requirements
  • Originality: All work must be developed during the hackathon. Pre-existing code/projects are prohibited, though use of standard libraries, public APIs, and frameworks is permitted.

  • IP Ownership: Participants retain all rights to their intellectual property. By submitting to GlobeHack, participants grant the event organizers and event sponsors a non-exclusive license to use project materials for promotional and event-related purposes.

  • Submission Criteria: Must include a GitHub/GitLab repository, a 5–7 slide GTM strategy deck, and a 1-minute demo video via Devpost.

4. Prizes
  • Awarding: Prizes are non-transferable. Internship prizes are subject to company-specific hiring/internship policy and eligibility requirements.

  • Taxation: Any monetary prizes or gift cards valued over a certain threshold may be subject to tax reporting in accordance with U.S. law.

  • Sponsor Discretion: Internship prizes are subject to the sponsor's standard interview and hiring processes.

5. Judging Criteria

Projects will be evaluated by industry judges on a scale of 1–5 across the following pillars:

  • Technical Complexity: Functionality, stability, and effectiveness of the prototype.

  • Business Logic: Clarity of the GTM strategy and economic model.

  • Go-To-Market Strategy: Target audience definition and acquisition potential.

  • Presentation Quality: Pitch clarity and demonstration effectiveness.

6. GlobeHack Code of Conduct (In-Person)

GlobeHack is dedicated to providing a harassment-free experience for everyone. We do not tolerate harassment in any form.

  1. Be Kind and Respectful: Treat all participants, mentors, judges, and sponsors with respect. We have zero tolerance for discriminatory language, actions, or imagery.

  2. Professionalism: While we encourage fun, we maintain a professional environment. Ensure that all event spaces (including bathrooms and quiet zones) are kept clean and shared responsibly.

  3. Inclusivity: We believe technology is for everyone. Encourage diverse participation and welcome team members from all disciplines, skill levels, and backgrounds.

  4. No "Hacking" the Event: Do not tamper with others' equipment, disrupt presentations, or engage in any form of cyber-harassment against other teams.

  5. Emergency Procedures: In the event of an emergency, immediately notify an organizer in a neon-colored vest or security personnel on-site.

  6. Reporting: If you witness a violation of this code, please report it immediately to an organizer. Reports will be handled with discretion and prompt action will be taken, up to and including removal from the event without refund/award eligibility.