Health Tech Innovators brought to you by Regeneron – Official Rules

NO PURCHASE OR PAYMENT NECESSARY TO ENTER OR WIN. A PURCHASE OR PAYMENT WILL NOT INCREASE YOUR CHANCES OF WINNING.

SUBMISSION OF ANY ENTRY CONSTITUTES AGREEMENT TO THESE OFFICIAL RULES AS A CONTRACT BETWEEN ENTRANT (AND EACH INDIVIDUAL MEMBER OF ENTRANT), THE HACKATHON SPONSOR, AND DEVPOST.

1. Dates and Timing

Submission Period: March 6, 2024 (10:00 am Eastern Time) – May 15, 2024 (10:00 pm Eastern Time) (“Submission Period”).

Judging Period: May 21, 2024 (10:00 am Eastern Time) – June 17, 2024 (5:00 pm Eastern Time) (“Judging Period”).

Winners Announced: On or around June 20, 2024 (2:00 pm Eastern Time).

2. Sponsor and Administrator

Sponsor: Regeneron Inc 777 Old Saw Mill River Road Tarrytown, NY 10591

Administrator: Devpost, Inc. (“Devpost”), 222 Broadway, Floor 19, New York, NY 10038

3. Eligibility

The Hackathon IS open to:

• US residents (including US Citizens, and non-US Citizens residing in the US at the time of their participation in the contest);
• Individuals who are at least eighteen years of age at the time of entry (“Eligible Individuals”);
• Teams of Eligible Individuals (“Teams”); and
• Organizations (including corporations, not-for-profit corporations, and other nonprofit organizations, limited liability companies, partnerships, and other legal entities) that exist and have been organized or incorporated in the United States at the time of entry.
• (the above are collectively, “Entrants”)

PLEASE NOTE: It is your sole responsibility to review and understand your employer’s policies regarding your eligibility to participate in trade promotions, including this Hackathon. If you are participating in violation of your employer’s policies, you may be disqualified from entering or receiving prizes. The Sponsor and Devpost (Administrator) disclaim any and all liability or responsibility for disputes arising between an employee and their employer related to this matter.

An Eligible Individual may join more than one Team or Organization and an Eligible Individual who is part of a Team or Organization may also enter the Hackathon on an individual basis. If a Team or Organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. By entering a Submission on behalf of a Team or Organization you represent and warrant that you are the Representative authorized to act on behalf of your Team or Organization.

The Hackathon IS NOT open to:

• Individuals who do not reside in the US at the time of the contest, or Organizations domiciled outside of the United States
• Any other individual involved with the design, production, promotion, execution, or distribution of the Hackathon, and each member of their immediate family or household*
• Organizations involved with the design, production, paid promotion, execution, or distribution of the Hackathon, including the Sponsor and Devpost (“Promotion Entities”).
• Government entities, including sovereign states and all governmental entities as well as quasi-governmental entities, including but not limited to Government corporations, state-owned or state-controlled enterprises, regional transportation authorities, or state-owned universities or hospitals (“Government Entities”).
• Employees, representatives, and agents** of such Promotion Entities, and all members of their immediate family or household*
• Any Judge (defined below) and all members of their immediate family or household* or company or individual that employs a Judge.
• Any parent company, subsidiary, or other affiliate*** of any organization described above.
• Any other individual or organization whose participation in the Hackathon would create, in the sole discretion of the Sponsor and/or Devpost, a real or apparent conflict of interest.

*The members of an individual’s immediate family include the individual’s spouse, children and stepchildren, parents and stepparents, and siblings and stepsiblings. The members of an individual’s household include any other person who shares the same residence as the individual for at least three (3) months out of the year.

**Agents include individuals or organizations that in creating a Submission to the Hackathon, are acting on behalf of, and at the direction of, a Promotion Entity through a contractual or similar relationship.

***An affiliate is (a) an organization that is under common control, sharing a common majority or controlling owner, or common management; or (b) an organization that has a substantial ownership in, or is substantially owned by the other organization.

4. How To Enter

Entrants may enter by visiting regeneron.devpost.com (“Hackathon Website”) and following the below steps:

• Register for the Hackathon on the Hackathon Website by clicking the “Join Hackathon” button. To complete registration, sign up to create a free Devpost account, or log in with an existing Devpost account. This will enable you to receive important updates and to create your Submission.
• Entry in the Hackathon constitutes consent for the Sponsor and Devpost to collect and maintain an Entrant’s personal information (e.g., name, email address, etc.) for the purpose of operating and publicizing the Hackathon, as well as maintaining the individual’s personal information for a period of [up to 5 years] to follow up regarding additional opportunities and contests.
• Complete and enter all the required fields on the “Enter a Submission” page of the Hackathon Website (each a “Submission” or “Project”) during the Submission Period and follow the requirements below.

Project Requirements

• What to Create: Entrants should aim to create digital, scalable solutions that improve patient care while also potentially accelerating clinical research, examples include but are not limited to consented data for observational research, or a warm base of patients for clinical trial recruitment.  Entrants can either submit a project to Track 1 or Track 2

• • Track 1: RTM and RPM for RWD (Remote Therapeutic Monitoring and Remote Physiologic Monitoring for Real-World Data)
    • Create a digital, scalable solution that brings patients and Healthcare providers (HCPs) closer by providing a modernized way to track and record symptom monitoring with remote monitoring and real-world data.
      • Example areas of Therapeutic Categories of interest:
        • Immunology & Inflammation, e.g., Asthma, Atopic Dermatitis, Chronic Obstructive Pulmonary Disease (COPD), Eosinophilic Esophagitis (EoE)
        • Oncology, e.g., B-cell non-Hodgkin lymphoma, Cutaneous squamous cell carcinoma (CSCC), Melanoma, Solid tumors
        • Rare Disease, e.g., Fibrodysplasia ossificans progressiva (FOP), Myasthenia gravis (MG)
        • We also welcome submissions for other Therapeutic Categories. For additional disease areas of interest please review Regeneron’s drug development pipeline: Regeneron Pharmaceutical's Research and Development Pipeline

• • Track 2: Accelerating Clinical Trials
    • Accelerating clinical trials means the process of speeding up the various stages of clinical trials, from design and patient recruitment to data collection and analysis. This can involve improving the efficiency of study design, enhancing patient recruitment and retention strategies, streamlining site selection and activation, and optimizing data collection methods. The goal is to reduce the time it takes to complete a clinical trial, thereby bringing potential new treatments to patients more quickly.
• Functionality: The Project must be capable of being successfully installed and running consistently on the platform for which it is intended and must function as depicted in the video and/or expressed in the text description.
• Compliance – Health Data Privacy Regulations: You agree to abide by and comply with all applicable federal, state, and local laws, regulations, and ordinances. Please see the privacy guidelines section of the Resources Tab.
• Platforms: A submitted Project must run on the platform for which it is intended, and which is specified in the Submission Requirements.
• New & Existing: Projects must be either newly created by the Entrant or, if the Entrant’s Project existed prior to the Hackathon Submission Period, you must include a text description of why this applies to this challenge's Submission Period. Additionally, if the product and/or service existed for potential business use, sale, or other funded arrangement prior to the start of the hackathon, Entrants must select “Commercial Class” as their submitter type and ensure that they have secured all permissions and consents necessary to submit the existing product to the Hackathon.
• Commercial -l Class submitters will not need to provide source code. A demo link must be provided.
• Third-Party Integrations: If a Project integrates any third-party SDK, APIs, and/or data, the Entrant must be authorized to use them.
• Testing: The entrant must make the Project available free of charge and without any restriction, for testing, evaluation, and use by the Sponsor, Devpost, and Judges until the Judging Period Ends.
• PROPRIETARY / 3RD PARTY: If the Project includes software that runs on proprietary or third-party hardware that is not widely available to the public, including software running on devices or wearable technology other than smartphones, tablets, or desktop computers, the Sponsor and/or Devpost reserve the right, at their sole discretion, to require the Entrant to provide physical access to the Project hardware upon request. 

Submission Requirements.

Submissions to the Hackathon must meet the following requirements:

• Clearly identify what Track the Entrant is submitting the entry for i.e., Track 1, Track 2
• Clearly identify if the Entrant is submitting as an Enthusiast participant, or if the Entrant is an existing Commercial (e.g. Professional and/or Pre-Established) organization.
• Differences between the two categories of entrants: Non-Commercial Enthusiast vs. Commercial / Pre-Established
  • Non-Commercial Enthusiast category is intended for individuals or teams who are new to the field, experimenting, learning and/or developing entries that are non-commercially available at the time of submission. These participants may be students, hobbyists, or anyone interested in technology and innovation, and their Submission(s) may not be market-ready.
  • In contrast, the Commercial category is for experienced teams or companies who have developed or are developing commercially-available offerings. These participants may have a deeper understanding of the market and their Submission(s) are often polished and ready for commercial deployment. These solutions may be directly implemented in the market already at the time of submission, or variations on already-marketed solutions.
• Judges will hold final decision-making over the categorization of Entrants and Submissions.
• Include a Project built for either Track 1 or Track 2 and meets the above Project Requirements.
• Include a URL or some other means of access to your Project. Judges will need access to demo your project. Source code can be included but is not required. Judges must be provided with an environment to test the submission.
• Include a text description that should explain the features and functionality of your Project. The description must also include why someone would find it useful.
• Include a slide deck that explains your Project in detail, focusing on how the entry satisfies the judging criteria and aims of the challenge.  The slide deck should be 10 slides or less.
• Include a demonstration video of your Project. The video portion of the submission:
  • should be less than three (3) minutes
  • should include footage that shows the Project functioning on the device for which it was built
  • must be uploaded to and made visible to the judges on YouTube, Vimeo, or Facebook Video, and a link to the video must be provided on the submission form on the Hackathon Website; and
  • must not include third-party images, graphics, logos, trademarks, or copyrighted music, or other material unless the Entrant has permission to use such material.
• Specific Information for Track 1: RTM and RPM for RWD (Remote Therapeutic Monitoring and Remote Physiologic Monitoring for Real-World Data)
  1. 1. RTM and RPM (remote therapeutic and remote physiologic monitoring) are poised to change the way patients and healthcare providers manage conditions.  Additionally, with proper consent, the real-world data from these systems may change the landscape of clinical research. Submissions for Track 1 should clearly articulate and demonstrate how the solution achieves three main goals:
     2. Use RTM or RPM to gather patient-reported outcomes and/or physiologic/sensor data to improve the monitoring of patients’ health, particularly in a way compatible with health insurance coverage. Therapeutic categories of interest are outlined under Project Requirements Section
     3. Gather data to be useful for real-world data (RWD) driven clinical research, particularly Patient Reported Outcomes (PROs) and digital sensor data beyond Electronic Health Record (EHR) and health insurance claims data. Example uses and contexts for RWD include Phase 4 post-approval understanding of how certain medications work in the real-world setting, and data used to develop digital biomarkers that correlate with and/or predict traditional disease progression measures.
     4. Do this in a way that is compelling for patients (adults and/or pediatric), caregivers, and healthcare providers.

• Specific Information for Track 2: Accelerating Clinical Trials
  • Clinical Trials can be slow, expensive and resource-intense to run, placing potential new treatments further away from patients. For Track 2, submissions should focus on finding ways to accelerate clinical trials, from their inception in concept and study protocol design, to the monitoring and auditing of data gathered at clinical research sites.  Examples of submission focus areas that meet the aims of Track 2 will be included in the discussion board:
  • Submissions for Track 2 should clearly articulate and demonstrate how the solution would be feasible and could improve aspects of the quadruple aim of speed, quality, cost and experience for stakeholders including clinical trial participants and caregivers.

Testing: Access must be provided to an Entrant’s working Project for judging and testing by providing a link to a website, functioning demo, or a test build. If Entrant’s project is private, Entrant must include login credentials in its testing instructions. The Entrant must make the Project available free of charge and without any restriction, for testing, evaluation, and use by the Sponsor, Administrator, and Judges until the Judging Period ends. Judges are not required to test the Project and may choose to judge based solely on the text description, images, and video provided in the Submission.

If the Project includes software that runs on proprietary or third-party hardware that is not widely available to the public, including software running on devices or wearable technology other than smartphones, tablets, or desktop computers, the Sponsor and/or Administrator reserve the right, at their sole discretion, to require the Entrant to provide physical access to the Project hardware upon request.  For Projects running on widely available smartphones, tablets, or desktop computers, Entrants may make their Project available using one of the following methods: 

• Android Applications:
  • Upload an .apk file on the Enter a Submission form or provide a link for downloading the Project in the “Testing Instructions” field on the Enter a Submission form.
• iOS Applications:
  • If your Project is available on the iTunes App Store provide a link on your submission form. If you charge a fee for downloading your Project, you must provide a promo code.
  • If your Project is not yet publicly available on the iTunes App Store, you must send a test build to testing@devpost.com before the end of the Hackathon Submission Period iTunes TestFlight: https://developer.apple.com/testflight/ TestFlight / iTunes Connect: Enter the Administrator’s email address to share a build for testing. The Administrator’s TestFlight account email is: testing@devpost.com.
• Web/Mobile Web: Provide a link for accessing your Project on the “Testing Instructions” field on the Enter a Submission form.

Multiple Submissions: An Entrant (whether participating as an individual, team or entity) may submit more than one Submission, however, each submission must be unique and substantially different from each of the Entrant’s other Submissions, as determined by the Sponsor and Devpost in their sole discretion. Each eligible Entrant may only win one Early Submission prize. See Section 8 for details.

Public Distribution: The Entrant may make the Project available to the public via a website or online store but is not required to do so.

Language Requirements: All Submission materials must be in English or, if not in English, the Entrant must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted.

Team Representation: If a team or organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. The Representative and all team members must meet the eligibility requirements above. By entering a Submission on the Hackathon Website on behalf of a team or organization you represent and warrant that you are the Representative authorized to act on behalf of your team or organization. 

Technical Support: An Entrant may contract with a third party for technical assistance to create the Submission provided that, except as otherwise provided herein, the Submission components are solely the Entrant’s work product and the result of the Entrant’s ideas and creativity, and the Entrant owns all rights to them. An Entrant may submit a Submission that includes the use of open source software or hardware, provided the Entrant and their Submission each complies with applicable open source licenses and, as part of the Submission, creates software that enhances and builds upon the features and functionality included in the underlying open source product. Entrant should ensure that Submission is still viable if elements of any open source product included in such Submission are no longer available. By entering the Hackathon, you represent, warrant, and agree that your Submission meets these requirements.

Financial  Support and Conflicts of Interest: A Project must not have been developed, or derived from a Project developed, with financial support or conflict of interest from the Sponsor or Devpost. Such Projects include, but are not limited to, those that received funding or investment for their development, were developed under contract, or received a commercial license, from the Sponsor or Devpost any time prior to the end of Hackathon Submission Period. The Sponsor, at their sole discretion, may disqualify a Project, if awarding a prize to the Project would create a real or apparent conflict of interest.

5. Submission Modifications.

• Draft Submissions: Prior to the end of the Submission Period, you may save draft versions of your submission on Devpost to your portfolio before submitting the submission materials to the Hackathon for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your submission, but you may continue to update the project in your Devpost portfolio.
• Modifications: After the Submission Period. The Sponsor and Devpost may permit you to modify part of your submission after the Submission Period for the purpose of adding, removing or replacing material that potentially infringes a third-party mark or right, discloses personally identifiable information, or is otherwise inappropriate. The modified submission must remain substantively the same as the original submission with the only modification being what the Sponsor and Devpost permit.

6. Judges & Criteria.

Eligible submissions will be evaluated by a panel of judges selected by the Sponsor (the “Judges”). Judges may be employees of the Sponsor or third parties, 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 Sponsor.

Stage One) The first stage will determine via pass/fail whether the ideas meet a baseline level of viability, in that the project reasonably fits the theme and reasonably applies the required APIs/SDKs featured in the Hackathon.

Stage Two) All submissions that pass Stage One will be evaluated in Stage Two based on the following equally weighted criteria (the “Judging Criteria”):

Entries will be judged on the following equally weighted criteria, and according to the sole and absolute discretion of the judges:

Judging criteria for all tracks (Track 1 and Track 2):

Original and Creative:

• Design: Is the user experience and design of the project well thought out?

Potential Impact:

• Improve Patient-Physician Relationship: How well does the solution enhance the relationship between patients and their healthcare providers in a compelling way?
• Promote Patient Engagement: How does the solution ease and encourage patients’ participation, e.g. sharing their data, healthcare providers access to the data, and promote better understanding and communication around the targeted health conditions
• Driving Clinical Research: How well does the solution advance and accelerate clinical research and/or clinical trials?
• Enhance Data Availability and Quality:  Improve the volume and quality of data collected for use in both care and in research.

Technical Readiness: Compliance, Ease of Use, Scalability:

• Ensure Data Privacy, Security, and Consent: Ensure the data is collected with the full consent of the patients and stored and utilized in compliance with all applicable laws and regulations.
• Ensure Ease of Use: Ensure the solution or application is intuitive and easy to use to promote widespread use.
• Facilitate Scalability: Provide a path to growing, scaling, and adapting to more patients/healthcare providers/users and populations.

The scores from the Judges will determine the potential winners of the applicable prizes. The Entrant(s) that are eligible for a Prize, and whose Submissions earn the highest overall scores based on the applicable Judging Criteria, will become potential winners of that Prize.

Tie Breaking. For each Prize listed below, if two or more submissions are tied, the tied submission with the highest score in the first applicable criterion listed above will be considered the higher-scoring submission. In the event any ties remain, this process will be repeated, as needed, by comparing the tied Submissions’ scores on the next applicable criterion. If two or more submissions are tied on all applicable criteria, the panel of Judges will vote on the tied submissions.

7. Intellectual Property Rights.

By submitting an entry, each Entrant (whether participating as an individual, a team or entity) represents and warrants that they are sole author or owner of, or has the right to use, any works that the Submission comprises, that the works are wholly original (or is an improved version of an existing work that the Entrant has sufficient rights to use and improve), and that the Submission does not infringe any patent, copyright, trademark, contract, or any other rights of any third party of which the Entrant is aware.  The Entrant further represents and warrants that (a) submitted content is not copyrighted, protected by trade secret or otherwise subject to third-party intellectual property rights or other proprietary rights, including privacy and publicity rights, (b) the Entrant has permission from their rightful owner to submit the content; and (c) the content submitted does not contain any viruses, Trojan horses, worms, spyware or other disabling devices or harmful or malicious code.

All submissions remain the intellectual property of the Entrants. who submitted them.

By submitting an entry, the Entrant grants to the Sponsor, Devpost, and Judges a fully paid-up, non-exclusive license to use such entry for screening, evaluation, and judging the entry and for the purposes specified in these Official Rules.

By participating in this Hackathon, each Entrant, if selected to win a prize, grants to the Sponsor an irrevocable, perpetual, fully paid-up, royalty-free non-exclusive worldwide license to reproduce, publish, post, link to, share, and display publicly the title and executive summary or other components of the Submission on the web or elsewhere. of the Submission on the web or elsewhere.

8. Prizes.

IMPORTANT NOTES ON MULTIPLE PRIZE ELIGIBILITY:

• A Project can only win up to one (1) overall prize and up to one bonus prizes. The bonus prizes are the Early Submission Prize, Most Helpful Community Members Prize, and Popular Choice Prize.

1. Substitutions & Changes: Prizes are non-transferable by the winner. Sponsor in its sole discretion has the right to make a prize substitution of equivalent or greater value. Sponsor will not award a prize if there are no eligible submissions entered in the Hackathon, or if there are no eligible Entrants or submissions for a specific prize.
2. Verification Requirement: THE AWARD OF A PRIZE TO A POTENTIAL WINNER IS SUBJECT TO VERIFICATION OF THE IDENTITY, QUALIFICATIONS AND ROLE OF THE POTENTIAL WINNER IN THE CREATION OF THE SUBMISSION. No submission or submitter shall be deemed a winning Submission or winner until their post-competition prize affidavits have been completed and verified, even if prospective winners have been announced verbally or on the competition website. The final decision to designate a winner shall be made by the Sponsor and/or Devpost. Deadline for Returning Required Forms: ten (10) business days after the Required Forms are sent. Failure to return the required forms may result in disqualification. Failure of the winner to return the paperwork in more than three months will result in forfeiture of the prize.
3. Prize Delivery: Prizes will be payable to the Entrant, if an individual; to the Entrant’s Representative, if a Team; or to the Organization, if the Entrant is an Organization. It will be the responsibility of the winning Entrant’s Representative to allocate the Prize among their Team or Organization’s participating members, as the Representative deems appropriate. A monetary Prize will be mailed to the winning Entrant’s address (if an individual) or the Representative’s address (if a Team or Organization), or sent electronically to the Entrant, Entrant’s Representative, or Organization’s bank account, only after receipt of the completed winner affidavit and other required forms (collectively the “Required Forms”), if applicable. Failure to provide correct information on the Required Forms, or other correct information required for the delivery of a Prize, may result in delayed Prize delivery, disqualification or the Entrant, or forfeiture of a Prize. Prizes will be delivered within 60 days of the Sponsor or Devpost’s receipt of the completed Required Forms.
4. Fees & Taxes: Winners (and in the case of Team or Organization, all participating members) are responsible for any fees associated with receiving or using a prize, including but not limited to, wiring fees or currency exchange fees. Winners (and in the case of Team or Organization, all participating members) are responsible for reporting and paying all applicable taxes in their jurisdiction of residence (federal, state/provincial/territorial and local). Winners may be required to provide certain information to facilitate receipt of the award, including completing and submitting any tax or other forms necessary for compliance with applicable withholding and reporting requirements. United States residents may be required to provide a completed form W-9. Winners are also responsible for complying with banking regulations in their respective jurisdictions and reporting the receipt of the Prize to relevant government departments/agencies, if necessary. The Sponsor, Devpost, and/or Prize provider reserves the right to withhold a portion of the prize amount to comply with the tax laws of the United States or other sponsor jurisdiction, or those of a winner’s jurisdiction.

9. Entry Conditions and Release.

1. By entering the Hackathon, you (and, if you are entering on behalf of a Team, Organization each participating members) agree(s) to the following:
1. The relationship between you, the Entrant, and the Sponsor and Devpost, is not a confidential, fiduciary, or other, conflict of interest.
2. You will be bound by and comply with these Official Rules and the decisions of the Sponsor, Devpost, and/or the Hackathon Judges which are binding and final in all matters relating to the Hackathon.
3. You release, indemnify, defend and hold harmless the Promotion Entities, and their respective parent, subsidiary, and affiliated companies, the Prize suppliers and any other organizations responsible for sponsoring, fulfilling, administering, advertising or promoting the Hackathon, and all of their respective past and present officers, directors, employees, agents and representatives (hereafter the “Released Parties”) from and against any and all claims, expenses, and liabilities (including reasonable attorneys’ fees), including but not limited to negligence and damages of any kind to persons and property, defamation, slander, libel, violation of right of publicity, infringement of trademark, copyright or other intellectual property rights, property damage, or death or personal injury arising out of or relating to a Entrant’s entry, creation of Submission or entry of a Submission, participation in the Hackathon, acceptance or use or misuse of the Prize (including any travel or activity related thereto) and/or the broadcast, transmission, performance, exploitation or use of the Submission as authorized or licensed by these Official Rules.
2. Without limiting the foregoing, the Released Parties shall have no liability in connection with:
1. Any incorrect or inaccurate information, whether caused by the Sponsor or Devpost’s electronic or printing error or by any of the equipment or programming associated with or utilized in the Hackathon;
2. Technical failures of any kind, including, but not limited to malfunctions, interruptions, or disconnections in phone lines, internet connectivity or electronic transmission errors, or network hardware or software or failure of the Hackathon Website;
3. Unauthorized human intervention in any part of the entry process or the Hackathon;
4. Technical or human error which may occur in the administration of the Hackathon or the processing of Submissions; or
5. Any injury or damage to persons or property which may be caused, directly or indirectly, in whole or in part, from the Entrant’s participation in the Hackathon or receipt or use or misuse of any Prize.

The Released Parties are not responsible for incomplete, late, misdirected, damaged, lost, illegible, or incomprehensible Submissions or for address or email address changes of the Entrants. Proof of sending or submitting the aforementioned will not be deemed to be proof of receipt by the Sponsor or Devpost. If for any reason any Entrant’s Submission is determined to have not been received or been erroneously deleted, lost, or otherwise destroyed or corrupted, the Entrant’s sole remedy is to request the opportunity to resubmit its Submission. Such a request must be made promptly after the Entrant knows or should have known there was a problem and will be determined at the sole discretion of the Sponsor.

10. Publicity.

By participating in the Hackathon, Entrant consents to the promotion and display of the Entrant’s Submission, and to the use of personal information about themselves for promotional purposes, by the Sponsor, Devpost, and third parties acting on their behalf. The Entrant further irrevocably grants to the Sponsor and Devpost the right to photograph, film, videotape, use the Entrant’s name, likeness, voice,  opinions, comments, and related biographical materials (collectively, “Image”) in any manner or form deemed appropriate by the Sponsor and Devpost, to use the Image, or any part thereof, throughout the world in perpetuity for the purposes of publicity and promoting the Hackathon in any medium whatsoever without restriction as to manner, frequency or duration of use and without any future payments to the Entrant or consideration or right of review, unless prohibited by law. Authorized use includes but is not limited to advertising, social media, internal Sponsor communications, and future promotional purposes, etc.

11. General Conditions.

1. Sponsor and Devpost reserve the right, in their sole discretion, to cancel, suspend and/or modify the Hackathon, or any part of it, in the event of a technical failure, fraud, or any other factor or event that was not anticipated or is not within their control.
2. Sponsor and Devpost reserve the right in their sole discretion to disqualify any individual or Entrant if it finds to be actually or presenting the appearance of tampering with the entry process or the operation of the Hackathon or to be acting in violation of these Official Rules or in a manner that is inappropriate, unsportsmanlike, not in the best interests of this Hackathon, or a violation of any applicable law or regulation.
3. Any attempt by any person to undermine the proper conduct of the Hackathon may be a violation of criminal and civil law. Should the Sponsor or Devpost suspect that such an attempt has been made or is threatened, they reserve the right to take appropriate action including but not limited to requiring an Entrant to cooperate with an investigation and referral to criminal and civil law enforcement authorities.
4. If there is any discrepancy or inconsistency between the terms and conditions of the Official Rules and disclosures or other statements contained in any Hackathon materials, including but not limited to the Hackathon Submission form, Hackathon Website, or advertising, the terms and conditions of the Official Rules shall prevail.
5. The terms and conditions of the Official Rules are subject to change at any time, including the rights or obligations of the Entrant, the Sponsor, and Devpost. The Sponsor and Devpost will post the terms and conditions of the amended Official Rules on the Hackathon Website. To the fullest extent permitted by law, any amendment will become effective at the time specified in the posting of the amended Official Rules or, if no time is specified, the time of posting.
6. If at any time prior to the deadline, an Entrant or prospective Entrant believes that any term in the Official Rules is or may be ambiguous, they must submit a written request for clarification.
7. The Sponsor or Devpost’s failure to enforce any term of these Official Rules shall not constitute a waiver of that provision. Should any provision of these Official Rules be or become illegal or unenforceable in any jurisdiction whose laws or regulations may apply to an Entrant, such illegality or unenforceability shall leave the remainder of these Official Rules, including the Rule affected, to the fullest extent permitted by law, unaffected and valid. The illegal or unenforceable provision shall be replaced by a valid and enforceable provision that comes closest and best reflects the sponsor’s intention in a legal and enforceable manner with respect to the invalid or unenforceable provision.
8. Excluding Submissions, all intellectual property related to this Hackathon, including but not limited to copyrighted material, trademarks, tradenames, logos, designs, promotional materials, web pages, source codes, drawings, illustrations, slogans, and representations are owned or used under license by the Sponsor and/or Devpost. All rights are reserved. Unauthorized copying or use of any copyrighted material or intellectual property without the express written consent of its owners is strictly prohibited. Any use in a Submission of Sponsor or Devpost’s intellectual property shall be solely to the extent provided for in these Official Rules.

12. Limitations of Liability.

By entering, all Entrants (including, in the case of a Team or Organization, all participating members) agree to release the Released Parties from any and all liability in connection with the Prizes or Entrant’s participation in the Hackathon. Provided, however, that any liability limitation regarding gross negligence or intentional acts, or events of death or body injury shall not be applicable in jurisdictions where such limitation is not legal.

13. Disputes.

1. Except where prohibited by law, as a condition of participating in this Hackathon, Entrant agrees that:
1. Any and all disputes and causes of action arising out of or connected with this Hackathon, or any Prizes awarded, shall be resolved individually, without resort to any form of class action lawsuit, and exclusively by final and binding arbitration under the rules of the American Arbitration Association and held at the AAA regional office nearest the contestant;
2. The Federal Arbitration Act shall govern the interpretation, enforcement and all proceedings at such arbitration; and
3. Judgment upon such arbitration award may be entered in any court having jurisdiction.
2. Under no circumstances will Entrant be permitted to obtain awards for, and Entrant hereby waives all rights to claim, punitive, incidental or consequential damages, or any other damages, including attorneys’ fees, other than contestant’s actual out-of-pocket expenses (i.e., costs associated with entering this Hackathon), and Entrant further waives all rights to have damages multiplied or increased.
3. All issues and questions concerning the construction, validity, interpretation and enforceability of these Official Rules, or the rights and obligations of the Entrant and Sponsor in connection with this Hackathon, shall be governed by, and construed in accordance with, the substantive laws of the State of New York, USA without regard to New York choice of law rules.

SOME JURISDICTIONS DO NOT ALLOW THE LIMITATIONS OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATIONS OF LIABILITY MAY NOT APPLY TO YOU.

14. Additional Terms.

Please review the Devpost Terms of Service at https://info.devpost.com/terms for additional rules that apply to your participation in the Hackathon and more generally your use of the Hackathon Website. Such Terms of Service are incorporated by reference into these Official Rules, including that the term "Poster" in the Terms of Service shall mean the same as "Sponsor" in these Official rules." If there is a conflict between the Terms of Service and these Official Rules, these Official Rules shall control with respect to this Hackathon only.

15. Entrant’s Personal Information.

Information collected from entrants is subject to both Devpost’s Privacy Policy, which is available here: https://info.devpost.com/privacy  and Regeneron’s Privacy Notice available at Privacy Notice: https://www.regeneron.com/privacy-notice

For questions, send an email to support@devpost.com.