1. POSTER

The Poster is the sponsor and entity responsible for the Hackathon. Other “sponsors” identified on the Hackathon Website are providing material or promotional support or prizes, and are not responsible for the administration of the Hackathon.

Winners Announced: On or around July 21st, 2015 (10:00am Eastern Time)

The Poster will be the official timekeeper for the Hackathon.

3. ELIGIBILITY

A. The Hackathon IS open to:

individuals who are at least 13 years of age as of the time of entry

teams of eligible individuals

(the above are collectively, “Makers”)

An individual may join more than one team, and an individual who is part of a team may also enter the Hackathon on an individual basis.

If a team 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 must meet the eligibility requirements above. By entering a Submission on the Site on behalf of a team, you represent and warrant that you are the Representative authorized to act on behalf of your team.

B. The Hackathon IS NOT open to:

individuals who are residents of 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, Brazil, Quebec, Italy, and Cuba, Sudan, Iran, North Korea, Syria and any other country designated by the United States Treasury's Office of Foreign Assets Control)

employees, representatives and agents* of any organization involved with the design, production, paid promotion, execution, or distribution of the Hackathon (such organizations are “Promotion Entities”), and all members of their immediate family or household**

any other individual involved with the design, production, promotion, execution, or distribution of the Hackathon, and each member of their immediate family or household**

any Judge (defined below)

any other individual whose participation in the Hackathon would create, in the sole discretion of the Poster, a real or apparent conflict of interest

*Agents include individuals or teams 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.

**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 that shares the same residence as the individual for at least three (3) months out of the year.

4. SUBMISSION REQUIREMENTS

Makers must do the following to participate in the Hackathon:

Register for the Hackathon on the Hackathon Website by clicking the “Register for this Challenge” button. To complete registration, sign up to create a ChallengePost account, or log in with an existing ChallengePost account. There is no charge for creating a ChallengePost account. This will enable you receive important updates and access the “Enter a Submission” page.

Create a video that includes footage that clearly explains your application’s features and functionality through a comprehensive demonstration.

Complete and enter all of the required fields on the “Enter a Submission” page of the Hackathon Website (each a “Submission”) during the Hackathon Submission Period, and follow the requirements below.

A. Language Requirements

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

B. Application Requirements

(i) What to Create: Makers must create a working software application that helps it's users connect with sports teams / activities or athletes.

(ii) Functionality: The Application 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.

(iii) Platforms: A submitted Application must run on at least one of the following:

other hardware (including, but not limited to, wearable technology, open source hardware, or proprietary hardware)

(iv) New & Existing: Applications must be either newly created by the Maker or, if the Application existed prior to the Hackathon Submission Period, must have modified after the start of the Hackathon Submission Period. Modifications made during the submission period should be explained in the application description.

(v) Testing: The Maker must make the Application available free of charge and without any restriction, for testing, evaluation and use by the Poster and judges during the Hackathon and until the Judging Period ends.

If the Application 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 Poster reserves the right, at their sole discretion, to require the Maker to provide physical access to the Application hardware upon request.

For Applications running on widely available smartphones, tablets, or desktop computers, Makers may make their Application available using one of the following methods:

a. Android Applications:Upload an .apk file on the Enter a Submission form or provide a link for downloading the Application in the “Testing Instructions” field on the Enter a Submission form.

b. iOS Applications:

If your Application is available on the iTunes App Store provide a link in the “Website URL” field on “Enter a Submission” form. If you charge a fee for downloading your Application, you must provide a promo code.

If your Application is not yet publicly available on the iTunes App Store, you must send a test build to the Administrator before the end of the Hackathon Submission Period using one of the following methods:

You may send the Administrator a beta test via Crashalytics. Use the Administrator’s testing email (testing@challengepost.com) and UDID’s to provision a build and send the Administrator a link via the “Share Links” button. Add the testing link to the Enter a Submission form under “iOS Build Link”. Beta by Crashalytics is a free service. Please review the how-to for their Beta Distribution tool.

Enter the Administrator’s email address to share a build for testing. The Administrator’s TestFlight account email is: testing@challengepost.com. Please note that if you add the Administrator as an “External Tester” your Application will need to go through Beta App Review before you can send your build. This could lead to delay and in order for your Submission to be eligible, you must send your test build before the end of the Hackathon Submission Period. To learn more about TestFlight via iTunes Connect, please review the iTunes Connect Developer Guide and the TestFlight Video Tutorial.

c. Windows Phone applications:Upload an .xap file in the Enter a Submission form or provide a link for downloading your Application in the “Testing Instructions” field on the Enter a Submission form.

d, Windows PC:Upload the appropriate installation files (.exe) on the Enter a Submission form or provide a link for downloading your .exe file in the “Testing Instructions” field on the Enter a Submission form.

e. BlackBerry:Upload the appropriate installation files on the Enter a Submission form or provide a link for downloading your installation file in the “Testing Instructions” field on the Enter a Submission form.

f. Mac OS:Upload the appropriate installation files on the Enter a Submission form or provide a link for downloading your installation file in the “Testing Instructions” field on the Enter a Submission form.

g. Web/Mobile Web:Provide a link for accessing your Application on the “Testing Instructions” field on the Enter a Submission form.

h. Kindle: Upload the appropriate installation files on the Enter a Submission form or provide a link for downloading your installation file in the “Testing Instructions” field on the Enter a Submission form.

(vi) Public Distribution: The Maker may make the Application available to the public via a website or online store, but is not required to do so.

(vii) Multiple Submissions: A Maker may submit more than one Submission, however, each Submission must be unique, as determined by the Poster and/or the Administrator.

(viii) SDKs, APIs, & Data: Applications may integrate SDKs, APIs and data, provided the Maker is authorized to use them.

(ix) Intellectual Property: Your Submission must: (a) be your (or your team’s) original work product; (b) be solely owned by you or your team with no other person or entity having any right or interest in it; and (c) not violate the intellectual property rights or other rights including but not limited to copyright, trademark, patent, contract, and/or privacy rights, of any other person or entity. A Maker may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Maker’s work product and the result of the Maker’s ideas and creativity, and the Maker owns all rights to them. A Maker may submit a Submission that includes the use of open source software or hardware, provided the Maker 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. By entering the Hackathon you represent, warrant, and agree that your Submission meets these requirements.

(x) Financial or Preferential Support: An Application must not have been developed, or derived from an Application developed, with financial or preferential support from a Promotion Entity. Such Applications 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 a Promotion Entity any time prior to the end of Hackathon Submission Period. The Poster, at their sole discretion, may disqualify an Application, if awarding a prize to the Application would create a real or apparent conflict of interest.

C. Text Description, Image, and Video Requirements

(i) Text Description: The text description should explain the features and functionality of your Application.

(ii) Images: The image(s) should be photographs or screenshots of your working Application.

(iii) Video: Makers may submit a video, but are not required to do so. If a Maker chooses to submit a video, the video:

a. should be less than five (5) minutes;

b. should include footage that clearly explains the Application’s features and functionality through a comprehensive demonstration;

c. must be uploaded to YouTube, Vimeo, or Youku, and a link to the video must be provided on the submission form on the Hackathon Website; and

d. must not include third party trademarks, or copyrighted music or other material unless the Maker has permission to use such material.

5. SUBMISSION RIGHTS

A. Maker Rights: Subject to the licenses described below, any applicable intellectual property rights to a Submission will remain with the Maker.

B. Poster Rights:By entering the Hackathon, you grant to the Poster, and any other third parties acting on the Poster’s behalf, a royalty-free, non-exclusive, worldwide perpetual license to display publicly and use for promotional purposes the Submission, in perpetuity. This license includes, but is not limited to, posting or linking to the Submission on Poster’s and partners’ websites and applications, including the Hackathon Website, and display and promotion of the Submission in any other media, worldwide.C. Submission Display:The following Submission components may be displayed to the public: name, description, images, video URL, website, URL, team members, the Submission category and platform, and submitter type. Other Submission materials may be viewed by the Poster, Promotion Entities, and Judges for screening and evaluation.Makers represent and warrant that the Poster and Promotion Entities are free to use Makers’ Submission in the manner described above, as provided or as modified by Poster, without obtaining permission or license from any third party and without any compensation to Makers.

6. JUDGING

A. Judges: Eligible Submissions will be evaluated by a panel of judges selected by the Poster (the “Judges”). Judges may be employees of the Poster 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 Poster.

B. Criteria: The Judges will score eligible Submissions using the following criteria (the “Judging Criteria”):

(i) Quality of Idea (Includes creativity and originality);

(ii) Implementation of Idea (Includes how well the idea was executed by the developer); and

(iii) Potential Impact (Includes the potential impact on users).

The Judging Criteria above may not apply to every Prize. See section 7 below for the Judging Criteria that apply for each Prize. The Maker(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.

C. Submission Review: JUDGES are not required to test the Application and may choose to judge based solely on the text description, IMAGES and video provided in the Submission.

D. Tie Breaker: For each Prize listed in Section 7 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. PRIZES

A. Hackathon Prizes

Only Makers entering eligible Submission to this Hackathon are eligible for the following Prizes:

8. VERIFICATION OF POTENTIAL WINNRS

A. 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. The final decision to designate a winner shall be made by the Poster.

B. Required Forms: Potential winners will be notified using the email address associated with the ChallengePost account used to enter the Submission (the submitter is the “Representative” in the case of a team). In order to receive a Prize, the potential winner (including all participating team members in the case of a team) will be required to sign and return to the Poster affidavit(s) of eligibility (or a similar verification document) and liability/publicity release(s), and any applicable tax forms (“Required Forms”).

Deadline for Returning Required Forms: ten (10) business days after the Required Forms are sent.

(i) the potential winner’s Representative or any participating member does not respond to multiple emails or fails to sign and return the Required Forms by the deadline listed above, or responds and rejects the Prize;

(ii) the Prize or Prize notification is returned as undeliverable; or

(iii) the Submission or the potential winner, or any member of a potential winner’s team, is disqualified for any other reason.

In the event of a disqualification, the Poster may award the applicable Prize to an alternate potential winner.

9. PRIZE DISTRIBUTION

A. Substitutions & Changes: The Poster has the right to make a Prize substitution of equivalent or greater value. The Poster will not award a Prize if there are no eligible Submissions entered in the Hackathon, or if there are no eligible Makers or Submissions for a specific Prize.

B. Prize Delivery: A monetary Prize will be mailed to the winning Maker’s address (if an individual) or the Representative’s address (if a team) after receipt of the Required Forms. Prizes will be payable to the Maker, if an individual, or to the Maker’s Representative, if a team. It will be the responsibility of the winning Maker’s Representative to allocate the Prize among their team’s participating members, as the Representative deems appropriate.

C. Prize Delivery Timeframe: Within 45 days of the Poster’s receipt of the Required Forms

D. Fees & Taxes: Winners (and in the case of team, all participating members) are responsible for any fees associated with receiving or using a prize, including but not limited to, wiring fees. Winners (and in the case of team, 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 are required to provide a completed form W-9 and residents of other countries are required to provide a completed W-8BEN form. Winners are also responsible for complying with foreign exchange and banking regulations in their respective jurisdictions and reporting the receipt of the Prize to relevant government departments/agencies, if necessary. The Poster and/or Prize provider reserve the right to withhold a portion of the prize amount to comply with the tax laws of the United States or other Poster jurisdiction, or those of a winner’s jurisdiction.

10. ADDITIONAL TERMS THAT ARE PART OF THE OFFICIAL RULES

Please review the ChallengePost Terms of Service at http://challengepost.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. If there is a conflict between the Terms of Service and these Official Rules, the latter terms shall control with respect to this Hackathon only.

Participation in the Hackathon constitutes Maker’s full and unconditional agreement to these Official Rules. By entering, a Maker agrees that all decisions related to the Hackathon that are made pursuant to these Official Rules are final and binding, and that all such decisions are at the sole discretion of the Poster.

The Poster collects personal information from you when you enter the Hackathon. The information collected is subject to the privacy policy located here: http://ChallengePost.com/privacy.

11. CONTACT

If you have any questions or comment, or wish to send us any notice regarding this Hackathon, please email us at Support@ChallengePost.com.