GlobalHack VI Rules


1. Overview

a. The Hackathon is designed to solve one or more civic technology problem(s), the details of which will be announced during the GlobalHack VI Opening Ceremony on Friday, October 21, 2016.

b. Event Participation will take place October 21 to 23, 2016 at Chaifetz Arena (1 S Compton Ave, St. Louis, MO 63103), with finalist judging taking place on Sunday, October 23, 2016 and announcement of the final top winners also on October 23, 2016. All times in these Official Rules are in Central Time.

c. In these Official Rules, the term “we,” “us,” or “our” refers to GlobalHack, Inc. and the term “you” refers to you, the entrant, both as an individual and as part of your team.

d. Certain GlobalHack sponsors may also offer prizes during the Hackathon. We are not responsible for providing those prizes, however, and we do not have any role in the determination of winners. If you have any questions about those prizes, please contact the applicable GlobalHack sponsor(s).

e. Sponsor

i. The Hackathon is sponsored and administered by GlobalHack, Inc., located at 911        Washington Ave, Suite 657, Saint Louis, MO 63101.

f. These rules were last updated on October 18, 2016.

2. Eligibility

a. The Hackathon is open to registered participants who are at least 13 years old. Participants who are considered minors in the jurisdiction where they reside, must have a parent or legal guardian sign the Participation Agreement and note their relationship to the minor.

b. The following people, however, are not eligible to participate: individuals who (a) are, or at any point since July 1, 2012 have been, employed by GlobalHack, Inc., Tito, or DevPost; (b) are the immediate family (spouse, parents, siblings, and children) and household members of any of those employees or former employees in (a) above; (b) are current employees of Saint Louis University, the Title-level sponsor of the Hackathon; (c) individuals who are residents of, or organizations domiciled in, a country, state, province or territory where the laws of the United States or local law prohibits participating or receiving a prize in the Hackathon (including, but not limited to, Myanmar (f/k/a Burma), Cuba, Iran, North Korea, Sudan, Syria and any other country designated by the United States Treasury’s Office of Foreign Assets Control); or (d) any Judge (defined below) of the Hackathon.

c. If you are an employee of a corporation, government agency, or an academic institution, you are responsible for ensuring that your participation in the Hackathon complies with any policies your corporation, agency, or institution may have regarding participation in contests of this type. We are not responsible for any disputes arising between you and your employer.

d. Teams formed with the primary intention of recruiting participants at the Hackathon will be disqualified and barred from the event. Only approved sponsors may send recruiters to the Hackathon.

3. Registration and Check-in

a. In order to participate in the Hackathon, you must register at by 9:59 PM on Friday, October 21, 2016. Registration may be closed earlier if we reach capacity.

b. You must also check-in onsite and in-person at the Hackathon between 12:00 PM and 10:00 PM on Friday, October 21, 2016. If you do not check-in onsite and in person during these times you will not be allowed to participate in the Hackathon.

c. A maximum of eight eligible individuals will be permitted per team. Your entire team must register as a team on DevPost by 1:00 AM on Saturday, October 22, 2016. Pick your team members carefully because after this point, you will not be allowed to switch teams, or add or remove team members. We are not responsible for, and will not assist in resolving, any disputes between team members.

4. Entry

a. You must submit your team’s Entry at by 9:00 AM on October 23, 2016, except as noted below. A team may only submit one Entry. Incomplete entries may be disqualified. Your Entry consists of:

i. Your application;

ii. Selection of the division you are competing in: Youth, College, or Professional;

iii. App title;

iv. App tagline;

v. App description (should be approximately 500 words);

vi. App screenshots or image, with a maximum size of 5mb; format should be JPG, PNG or GIF with a 3:2 aspect ratio;

b. By submitting an Entry, you represent and warrant that:

i. Any code you supply for your Entry was newly written (as defined in Section 5(a)) by you or your team during the Hackathon;

ii. If applicable, any code that has been copied by you and included as part of your Entry is publicly available in accordance with the General App Requirements below; and

iii. You have fully complied with these Official Rules.

c. We reserve the right to disqualify any Entry that is offensive, as determined by us, in our sole discretion. Please ensure your Entry is appropriate for all viewing audiences.

d. Please see Section 9 for information about how we may use your Entry.

e. To be eligible for any of the monetary prizes at the Event, you must agree to open source your Entry. You only have to open source newly written code created at the event. You may participate in the event without open sourcing your Entry, but you will not be eligible to win any prizes.

5. General App Requirements

a. Except for publicly available code of the type referred to in the Other Technologies section below, all code submitted as part of your Entry must have been newly written by you or your registered team members during the Hackathon. “Newly written” means that you cannot in any way copy code that already privately exists, and submit it as part of your Entry; you may however attempt to recode it from memory. The idea for your Entry may have existed before the Hackathon, or as an app that you are aware of or worked on previously. Note that where the same or a similar idea, functionality, or app already exists, your Entry will likely not be judged as highly as it would have been otherwise.
b. All materials related to the Entry must be in English.
c. In order to win any prize money, you must agree to open source your Entry. However, you only have to open source newly written code at the event.

6. Allowed Technologies:

a. Other Technologies: You are also able to use source code, sample code, libraries, SDKs, and APIs as long as these technologies are:

i. Made publicly discoverable and available for public use in developing applications as of October 1, 2016, and are still public as of the event.
ii. Be indexed and reachable through Google’s search engine,
iii. Be easily accessible (i.e., anyone can download or access if signup is required, access must be granted in less than 1 hour).

Examples of common technologies that meet our requirements as allowable are Angular.js, jQuery, Bootstrap, D3, Hadoop, MySQL, Lucene, Twilio, Google Talk, Weather Underground. Our intention is to provide you with the full suite of tools available to software developers in a professional setting, but barring teams from utilizing commercial grade technology that other participants do not have access to, whether developed by the team or by others. As a rule of thumb, if a particular technology provides an unfair advantage to one team it is likely disallowed.

b. We reserve the right to assess your eligibility and compliance with these Official Rules at any point during the Hackathon. If we require any assistance in order to assess your compliance, you must promptly provide that assistance. If you do not provide the requested assistance in a timely manner, or if we have reason to believe that you are not complying with the Official Rules, you may be disqualified, in our sole discretion.

7. Judging

a. Eligible Submissions will be evaluated by a panel of judges selected by the Organizer (the “Judges”). Judges may be employees of the Organizer or external, may or may not be listed individually on the Hackathon Website, and may change before or during the Judging Period. Judging may take place in one or more rounds with one or more panels of Judges, at the discretion of the Organizer.

b. Judging Process (Youth, College, Professional)

i. Throughout each judging round, judges will evaluate each Entry based primarily on the demo according to the following Judging Criteria, each of which will be scored on a scale of between 0 to 10 points: (a) user interface; (b) creativity; and (c) execution. In the event of a tie, judges will deliberate to determine the winner. The judges may or may not reference the additional materials which you submit in your Entry listed Section 4(a)(ii) through (vi) above.

ii. Round 1 (Qualifying): Judging will start at approximately 10:00 AM on Sunday, October 23, 2016. Beginning at that time, you must have a team member available at your designated location throughout the judging period to demonstrate your Entry. Judging will be conducted in a “science fair” format, so judges may arrive at your location at any time during the judging period. Your Entry will be judged once, by a group of three judges. The judges will be identified to you and they will ask you to demonstrate your Entry. Please be ready to do your demonstration when the judges arrive. If you or a teammate are not at your location when the judges arrive, you will not receive a score. Round 1 Judging is scheduled to conclude at approximately 12:00 PM on Sunday, October 23, but the judging period may be extended by us for any length of time, in our discretion. You will be given up to three minutes to publicly demonstrate your App in front of the three judges. You may utilize no more than one presentation slide as part of your demonstration. You will need to provide a mobile device and accessories for the demonstration.

iii. Round 2 (Semifinals): You will be notified if your Entry has been selected to move on to Round 2 of the judging as a finalist competing for places first through fifth in your respective division. Judging for this Round will start at approximately 12:00 PM on Sunday, October 23. Teams selected for Round 2 judging will be given up to five minutes, consisting of a three-minute demonstration of their Entry, followed by a two-minute question-and-answer period, to publicly demonstrate their Entry in front of a panel of five judges. At least one team member must be present at the demonstration. Teams will be provided with projector/monitor to present their demo to the panel of judges. Teams must provide any connectors or devices necessary for their presentation.

iv. Round 3 (Finals): 10-20 finalist teams will do a 2-3 minute presentation of their Entry on stage. At least one team member from each team announced as a finalist must be present and ready to demonstrate their Entry onstage at 2:00 pm on Sunday, October 23, 2016.

c. Judges will not be GlobalHack employees. If a judge or participant identifies to us a conflict of interest prior to judging, that judge will be recused from judging the Entry with the conflict. An alternate judge will be identified as a substitution for the judge with the conflict.

d. Entries may be subject to a due diligence review at any time for eligibility and compliance with these Official Rules. Determination of eligibility and compliance is at our sole discretion, and may result in your personal disqualification and/or the disqualification of your team’s Entry. Our decisions and those of the judges are final.

8. Prizes

a. Division Prizes

i. Five prizes will be awarded in each main category (Professional, College, and Youth). Cash prize amounts in the Professional Division are as follows: $125,000 for First Place, $100,000 for Second Place, $50,000 for Third Place, $25,000 for Fourth Place, and $10,000 for Fifth Place. Cash prize amounts in the College Division are as follows: $100,000 for First Place, $50,000 for Second Place, $25,000 for Third Place, $15,000 for Fourth Place, and $5,000 for Fifth Place. Cash prize amounts in the Youth Division are as follows: $50,000 for First Place, $25,000 for Second Place, $10,000 for Third Place, $5,000 for Fourth Place, and $2,500 for Fifth Place

ii. The highest scoring qualifying team finalist Entry among the three main divisions will be declared the Grand Prize Winner, and awarded an additional $150,000.

iii. $2,500 will be given to the team with the Best Team Spirit, as determined by GlobalHack staff and volunteers.

b. The prize money will be divided evenly among all registered team members. The prize money will be sent to the winners via check or wire transfer, no later than November 30, 2016 provided the receipt of all necessary forms from members of a winning team.

c. Each member of the winning teams will be required to sign an Affidavit of Eligibility and a Liability and Publicity Release, and if applicable a W-9 tax form (for U.S. residents) or W-8BEN tax form (for non-U.S. residents) in order to receive a prize. If you do not sign the required forms or provide the required information within thirty days following our request we may disqualify you from receiving a prize.

d. Taxes shall be the sole responsibility of each winning team member. We shall have no responsibility for any taxes associated with any prize. Each member of the winning teams may be responsible for paying income or other taxes on the prize.

9. How Your Entry May be Used

a. You do not transfer ownership of your Entry (or any part of it). However, by submitting an Entry, you grant us an irrevocable, royalty-free, worldwide rights and license to: (a) use, review, assess, test, and otherwise analyze your Entry and all its content in connection with the Hackathon; and (b) feature your Entry and all its content for promotional purposes (including, but not limited to, in advertisements, press releases, presentations, and trade shows) in all media, now known or later developed. You also agree to sign any necessary documentation that may be required for us and our designees to make use of the rights you granted.

b. You acknowledge that we, other entrants or others may have developed or commissioned materials similar or identical to your Entry, or may develop something similar in the future, and you waive any claims you may have resulting from any similarities to your Entry.

c. You understand that we cannot control the information you disclose to us or our representatives in the course of participating in the Hackathon, or what we or our representatives will remember about your Entry. You also understand that we will not restrict work assignments of representatives who have had access to your Entry. By participating in the Hackathon, you agree that we may use any information in our representatives’ unaided memories in the development or deployment of our products or services without liability or compensation to you. You understand that you will not receive any compensation or credit from us for use of your Entry in connection with this Hackathon. This provision does not limit any compensation you may receive through us or third parties as a result of your use or marketing or profiting from the application beyond this Hackathon or as provided in these Official Rules. We are not responsible for any unauthorized use of your Entry by those accessing or viewing your Entry.

d. Please note that after the Hackathon, you and/or your Entry may be publicized in advertisements related to the Hackathon. These advertisements may be distributed online and posted on our site or third-party websites.

e. While we reserve the rights set forth above, we are not obligated to use your Entry for any purpose, even if it has been selected as a winning Entry.

f. If you do not want to grant us these rights to your Entry, please do not enter this Hackathon.

g. Nothing in these Rules shall be interpreted as granting you permission to use or display any of the GlobalHack trademarks (including any logo or brand) or rights in any GlobalHack IP.

10. General Terms

a. By registering and participating in the Hackathon, you indicate your full and unconditional agreement to these Official Rules, the GlobalHack Code of Conduct, and other instructions related to the Hackathon, as well as to our decisions regarding the Hackathon, which are final and binding. Winning a prize is contingent upon fulfilling all requirements in these Official Rules.

b. We may modify any provision of these Official Rules, at any time, by posting updated rules at and may clarify these Rules on the Discussion Forum located at You are responsible for checking these sites regularly. We may also modify any timeline, start date/time or end date/time set forth in these Official Rules in our sole discretion without posting updated rules or clarification; however where such a modification would negatively affect Hackathon participants broadly we will endeavor to give you notice of the change via the Discussion Forum and/or e-mail. Because we will endeavor to provide important notices to you via Discussion Forum and/or the e-mail address you have provided at registration, it is important that you regularly check that e-mail address and the Discussion Forum.

c. Without limiting our rights and remedies, we reserve the right, in our sole discretion, to disqualify any individual or team who: (a) fails to comply with any provision of these Official Rules or the GlobalHack Code of Conduct; (b) cheats or tampers with the operation of the Hackathon, or otherwise acts in a disruptive or inappropriate manner; or (c) engages in conduct that is unlawful, offensive, or otherwise leads us to conclude, in our sole discretion, that public association with you could cause controversy or embarrassment to us or our partners.

d. In the event that the operation, security, or administration of the Hackathon is in our judgment impaired in any way, we may, in our sole discretion, without limitation: (a) suspend the Hackathon to address the impairment and then resume the Hackathon; (b) award the prize according to the criteria set forth above from among the eligible entries received up to the time of the impairment, (c) extend any deadlines, or (d) take any other reasonable action as we deem necessary and appropriate to the circumstances.

e. By entering, you agree to release, defend and hold harmless GlobalHack, Saint Louis University, our respective parents, subsidiaries, affiliates, and each of their respective officers, directors, employees, and agents (the “Released Parties”) from and against any claim or cause of action arising out of your participation in the Hackathon, including, but not limited to: (a) unauthorized human intervention in the Hackathon; (b) technical errors that may impair your ability to participate in the Hackathon; (c) errors in the administration of the Hackathon; (d) any claim or allegation that your participation in this Hackathon, or your Entry, was in violation of these Rules, or that your Entry infringes any copyright, trademark, or any other intellectual property right; (e) disputes between team members; (f) disputes between team members and their employers; and (g) claims relating to damage to persons or property relating in any way to your participation in the Hackathon.

f. Except where prohibited, you agree that any and all disputes, claims, and causes of action arising out of, or connected with, the Hackathon or any prize awarded shall be resolved individually, without resort to any form of class action, and exclusively by the appropriate court located in St. Louis, MO. All issues and questions concerning the construction, validity, interpretation and enforceability of these Official Rules, your rights and obligations, our rights and obligations connection with the Hackathon, shall be governed by, and construed in accordance with, the laws of Missouri, without giving effect to any choice of law or conflict of law rules (whether of Missouri or any other jurisdiction), which would cause the application of the laws of any jurisdiction other than Missouri.

g. Our failure to enforce any term of these Official Rules shall not constitute a waiver of that provision. The Hackathon is subject to federal, state, and local laws and regulations and is void where prohibited.

11. Privacy and Publicity

a. Information you submit to us when you participate in the Hackathon will be treated in accordance with our Privacy Policy. In addition, when you submit information on a website run by a third party in connection with this Hackathon, your information may be used by that third party in accordance with its privacy policy.

b. These are all the documents that are referenced: Code of Conduct, Participant Waiver, and Privacy Policy.

Sign up for our newsletter and stay connected with GlobalHack.

Close this popup