Official Rules for the 2014 Salesforce $1 Million Hackathon

THE HACKATHON IS VOID WHERE PROHIBITED BY LAW. BY PARTICIPATING, YOU AGREE TO THESE OFFICIAL RULES.

1) Overview

a) The Hackathon is designed to recognize the best mobile apps built using Force.com, Heroku, or a combination of Force.com and Heroku.
b) Hacking will take place October 10 to 12, 2014, with finalist judging taking place on October 14, 2014, and announcement of the final top winners on October 16, 2014. All times in these Official Rules are Pacific Time.
c) In these Official Rules, the term “we,” “us,” or “our” refers to salesforce.com, inc. and/or the Hackathon administrator, BeMyApp, and the term “you” refers to you, the entrant, both as an individual and as part of your team.
d) Certain Dreamforce 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 Dreamforce sponsor(s).
e) Sponsor and Administrator
- ● The Hackathon is sponsored by salesforce.com, Landmark at One Market, Suite 300 San Francisco, CA 94105, USA.
- ● The Hackathon is administered by BeMyApp Corporation, 26 O’Farrell Street, Suite 505 San Francisco, CA 94108.
f) These rules were last updated on September 16, 2014.

2) Eligibility

a) The Hackathon is open to registered participants who are at least 18 years old, or the age of majority in the jurisdiction where they reside, whichever is older.
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 salesforce.com. inc. or any of its direct or indirect wholly or majority owned subsidiaries, the Salesforce Foundation, BeMyApp Corporation, EventBrite, George P. Johnson, or ChallengePost; (b) are the immediate family (spouse, parents, siblings, and children) and household members of any of those employees or former employees in (a) above; (c) are current employees of an entity in which salesforce.com has invested and holds an ownership interest; (d) are current employees of a third-party sponsor of the Hackathon; or (e) are residents of Cuba, Iran, Myanmar, North Korea, Sudan, or Syria.
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.

3) Registration and Check-in

a) In order to participate in the Hackathon, you must register at salesforcehack.eventbrite.com by 6:30 PM on Wednesday, October 8, 2014. Registration may be closed earlier if we reach capacity.
b) You must also check-in onsite and in person at the Hackathon between 4:00 PM and 10:00 PM on Friday October 10, 2014. 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 seven eligible individuals will permitted per team. Your entire team must register as a team on ChallengePost by 12:00 PM on Saturday, October 11, 2014. 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.
d) In addition to your team’s registration at ChallengePost, your team must also designate a lead developer and send their Git repository username (either from GitHub or Bitbucket) via e-mail to salesforce1million@bemyapp.com. See the FAQ for details on how to acquire a Git repository, free of charge. BeMyApp will provide your designated lead developer access to a free private repository in order for your team to complete all Git Commit requirements under these Rules.

4) Entry

a) You must submit your team’s Entry at http://salesforcehackathon.challengepost.com by 12:00 PM on October 12, 2014, except as noted below. A team may only submit one Entry. Incomplete entries may be disqualified. Your Entry consists of:

i) Your mobile App built using Force.com, Heroku, or a combination of Force.com and Heroku;
ii) Selection of the challenge you are competing in: Force.com, Heroku, or Force.com with Heroku;
iii) If applicable, selection of Open Source challenge you are competing in: Open Source Node, Open Source Postgres, Open Source Python, or Open Source Ruby;
iv) App title;
v) App tagline;
vi) App description (should be approximately 500 words);
vii) App screenshots or image, with a maximum size of 5mb; format should be JPG, PNG or GIF with a 3:2 aspect ratio;

viii) Git Commit submissions must be submitted as described in Section 6 below.

b) By submitting an Entry, you represent and warrant that:
1. 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;
2. 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
3. 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.

5) General App Requirements

a) You must create a mobile app using Force.com, Heroku, or Force.com with Heroku. 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, and may have even existed on or off of the Salesforce1 Platform as similar functionality or as an app that you are aware of or worked on previously. If so, you must declare that fact and the details associated with it to us in an affidavit that we will require in connection with your submission. This is so that the judges can take these facts into account in their judging of your Entry. Failure to declare these facts may result in the disqualification of your team’s Entry, so it is important that you openly and honestly describe these types of facts to both your team and to us in a timely manner. You owe it to your team to let them know as soon as possible, and you need to let us know in the affidavit mentioned above. 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, particularly on the Innovation criteria.
b) All materials related to the Entry must be in English.
c) Allowed Technologies:

i) Salesforce Technologies

1) Required Salesforce Technologies: You must sign up and use the Force.com development environment, the Heroku development environment, or a combination of the two environments as the starting point to build your app.

2) Other Allowed Salesforce Technologies: You may use Salesforce generally available technology, as well Salesforce technology designated by Salesforce as “beta” or “developer preview” provided it is publicly available and easily accessible at the time of the Hackathon.

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

1) Publicly discoverable and available for public use in developing applications, and provided that such code or previous versions must (a) have been publicly available on the internet before September 1, 2014, and (b) be indexed and reachable through Google’s search engine, and (c) be easily accessible (i.e., anyone can download or access if signup is required, access must be granted within 3 hours).

Our intention is that you cannot take private code and simply makand e it open source, or make a private API publicly available right before the hackathon and use it in your Entry, but that you are welcome to use open source libraries and frameworks in your Entry, for example Angular.js, jQuery, and Bootstrap.

d) 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. Each team member will be required to sign and deliver an affidavit by 12:00 PM on Sunday, October 12, 2014 attesting to his or her compliance with all of the Official Rules, and declaring whether, and if so how, any part of your Entry reflects an idea, functionality or an app you are aware of or worked on prior to this Hackathon. The failure of any team member to deliver his or her affidavit in a timely way will result in the disqualification of his or her team’s Entry.

6) Git Commit

a) Each registered team will be required to commit their code to a public or private repository on GitHub or Bitbucket between 10:00 AM and 12:00 PM on Saturday, October 11, 2014, between 6:00 PM and 8:00 PM on Saturday, October 11, 2014, and between 10:00 AM and 12:00 PM on Sunday, October 12, 2014 (“Git Commit”). If a team chooses to use a private repository, BeMyApp will provide free access to a private repository to that team on Friday evening. If your team chooses to use a public repository, you must send a URL to the repository via e-mail to salesforce1million@bemyapp.com.

b) The Git Commit must include (a) all source code of your app including CSS and supporting media; and (b) all metadata created or changed on the Force.com platform if any. (Complete instructions for obtaining Force.com metadata will be provided at the Hackathon.)

c) If, for whatever reason, your team is unable to submit via Git, then the source should be zipped up and submitted via e-mail within the deadlines in Section 6(a) to salesforce1million@bemyapp.com.

d) Failure to meet the Git Commit requirements will result in disqualification. 7) Judging

a) Category Judging (Force.com, Heroku, and a Combination of Force.com and Heroku)

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 1-25 points: (a) innovation; (b) business potential; (c) user experience; and (d) use of Salesforce1 Platform technologies. 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 viii) above.
ii) Round 1: Judging will start at approximately 1:00 PM on Sunday, October 12, 2014. 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 whenthejudgesarrive. Ifyouorateammatearenotatyourlocationwhenthe judges arrive, you will not receive a score. Judging is scheduled to conclude at approximately 5:00 PM on Sunday, October 12, 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. The top ten finalists for each category, and two alternate teams for each category, are planned to be announced at approximately 5:00 PM on Sunday, October 12, 2014. The top ten finalists for each category will then do a one-minute demonstration of their Entry on stage. Winner placement for places sixth through tenth for each category are planned to be announced at this time.
iii) Round 2: 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 of a category. Judging for this Round will start at approximately 11:00 AM on Tuesday, October 14. 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. Winner placement for places third through fifth for each category will be announced at this time. Round 2 teams will be provided with a computer and mobile device loaded with their last Git Commit

to run their demo. Round 2 teams will be responsible for ensuring in advance of Round 2 judging that their Entry can run on these devices. We will provide support to Round 2 teams on Monday, October 13 to install any needed tools.

iv) Winner placement for places first and second in each category, in addition to the grand prize winner, will be announced on Thursday, October 16, 2014. At least one team member from each team announced on Tuesday October 14, 2014 as either a first or second place finalist must be present and ready to demonstrate their Entry onstage at 3:00 pm on Thursday October 16, 2014.

b) Open Source Judging (Node, Postgres, Python, and Ruby) - During the Round 1 judging period described above, one judge for each Open Source category will visit teams who wrote and contributed open source code in their Entry and registered to be judged in theOpenSourcejudgingcategory. Thejudgewillidentifyhimorherselfandaskyouto demonstrate your Entry. Please be ready to do your demonstration when he or she arrives. You must have a team member available at your designated location throughout the judging period to demonstrate your Entry. If you or a teammate are not at your location when the Open Source judge arrives, you will not receive a score for this category. You will be given up to three minutes to publicly demonstrate your Entry in front of the judge. 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.

i) The judges will evaluate each Entry according to the following Judging Criteria, each of which will be scored on a scale of between 1-25 points: (a) impact to other developers; and (b) ability to be reused. The judges may or may not reference the additional materials which you submit in your Entry listed Section 4(a)(ii) through viii) above. In the event of a tie, judges will deliberate to determine the winner.

c) Judges will not be salesforce.com or BeMyApp employees. If a judge or participant identifies to us a conflict of interest, 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) BeMyApp expects to send judges’ scores and feedback via e-mail to each team member who participated in the Hackathon within 24 hours after the final winner announcement.
e) 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, those of BeMyApp, and those of the judges are final.

8) Prizes
a) Category Prizes

i) Ten prizes will be awarded in each main category (Force.com, Heroku, and a combination of Force.com and Heroku). The qualifying team finalist Entry with

the highest score in each category will be awarded US $100,000; the next highest scoring qualifying team finalist Entry will be awarded US $50,000; the third highest scoring qualifying team finalist Entry will be awarded US $35,000; the fourth highest scoring qualifying team finalist Entry will be awarded US $20,000; the fifth highest qualifying team finalist Entry will be awarded US $15,000; and the sixth through tenth highest qualifying finalist teams’ Entries will each be awarded US $10,000.

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

b) Open Source Prizes
1. i) One prize will be awarded in each Open Source category (Node, Postgres, Python, and Ruby).
2. ii) The qualifying team Entry with the highest score in each Open Source category will be awarded $5,000. In addition, we will donate $5,000 to an Open Source Organization or Foundation of each winning team’s choice (one donation per team, subject to our reasonable approval).
c) The prize money will be divided evenly among all registered team members. The prize money will be sent to the winners via wire transfer, within one month from the receipt of all necessary forms from members of a winning team.
d) 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.
e) 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 salesforce.com trademarks (including any logo or brand) or rights in any salesforce.com technologies or IP. You agree to contact us prior to promoting or publicizing your participation in and, if applicable, you winning the Hackathon.

10) General Terms

a) By registering and participating in the Hackathon, you indicate your full and unconditional agreement to these Official Rules, the Dreamforce 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 http://developer.salesforce.com/milliondollarhackathon/2014rules.pdf, and may

clarify these Rules on the Discussion Forum located at http://salesforcehackathon.challengepost.com. 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 Dreamforce 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 salesforce.com, BeMyApp, 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 San Francisco, CA. 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 California, without giving effect to any choice of law or conflict of law rules (whether of California or any other jurisdiction), which would cause the application of the laws of any jurisdiction other than California.
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) You may be filmed or photographed while you are participating in the Hackathon. Except where prohibited, by participating in the Hackathon, you agree that we may use your name, likeness, photographs, audio-visual footage, comments, and any other record of your participation in the Hackathon for promotional purposes at any time and in any media.