THE HACKATHON IS VOID WHERE PROHIBITED BY LAW. BY PARTICIPATING, YOU AGREE TO THESE OFFICIAL RULES.
a. The Hackathon is designed to solve one or more healthcare problem(s), the details of which will be announced during the Healthcare Hackathon Opening Ceremony on Friday, July 19, 2019.
b. Event Participation will take place July 19 to 21, 201 at Dempster Hall at Southeast Missouri State University in Cape Girardeau (814 N Henderson, Cape Girardeau, MO 63701), with finalist judging taking place on Sunday, July 21, 2019 and announcement of the final top winners also on July 21, 2019. All times in these Official Rules are in Central Time.
c. In these Official Rules, the term “we,” “us,” or “our” refers to The Marquette Tech District Foundation, Inc. ("MTDF") and the term “you” refers to you, the entrant, both as an individual and as part of your team.
d. Certain MTDF 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 MTDF sponsor(s).
i. The Hackathon is sponsored and administered by Marquette Tech District Foundation, Inc., located at 338 Broadway, Suite 601, Cape Girardeau, MO 63701.
f. These rules were last updated on March 6, 2019.
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 Marquette Tech District Foundation, 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) 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 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, July 19, 2019. 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, July 19, 2018. 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 9:00 AM on Saturday, July 20, 2019. 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.
a. You must submit your team’s Entry by 10:00 AM on July 21, 2019, except as noted below. A team may only submit one Entry. Incomplete entries may be disqualified. Your Entry consists of:
i. Your application;
ii. App title;
iii. App tagline;
iv. 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 July 1, 2019, 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.
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
i. Throughout judging, 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; (c) execution; and (d) problem-solution fit. 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. Judging: Judging will start at approximately 10:30am on Sunday, July 21, 2016. Beginning at that time, you must have a team member available throughout the judging period to demonstrate your Entry. Judging will be conducted in a presentation format, with teams being alloted 3-5 minutes. Your Entry will be judged by a group of judges. Please be ready to do your demonstration when your team is called upon. If you or a teammate are not readily available within 5 minutes of your team being called, you will not receive a score. Judging is scheduled to conclude at approximately 1:30pm on Sunday, July 21, but the judging period may be extended by us for any length of time, in our discretion. You will need to provide a mobile device or laptop and accessories for the demonstration.
c. 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.
i. Three prizes will be awarded. Cash prize amounts are as follows: $30,000 for First Place, $15,000 for Second Place, and $5,000 for Third Place.
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 August 31, 2019 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 MTDF logos or brands or rights in any MTDF IP.
10. General Terms
a. By registering and participating in the Hackathon, you indicate your full and unconditional agreement to these Official Rules, the MTDF 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 and may clarify these Rules on the Discussion Forum located on DevPost. 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 MTDF 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 the Marquette Tech District Foundation, Inc., Saint Francis Healthcare System, Codefi LLC, 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 Cape Girardeau, 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