Hackathon Rules


Unless otherwise defined, all capitalised terms used herein shall bear the same meanings as in the Hackathon Terms of Service.

1. The Hackathon

1.1 These Hackathon Rules apply to the Microsoft Code; Without Barriers Hackathon 2024 (the “Hackathon”).

1.2 The Hackathon is a virtual hackathon taking place from April 19, 2024 to June 28, 2024, with the closing ceremony scheduled for June 28, 2024. 

1.21 The hacking and submissions period takes place from April 19, 2024 to June 17, 2024, and submissions officially close on June 17, 2024, 11:59PM GMT+8

1.3 Eligibility

The Hackathon IS open to:

  • Women who are at least the age of majority where they reside as of the time of entry 
  • Residents of the following countries:
    • Malaysia, Singapore, Indonesia, Philippines, Thailand, Sri Lanka, Bangladesh, Laos, Cambodia, Brunei, Vietnam, Australia, New Zealand, South Korea, Japan, India, Nepal, Bhutan, China, Taiwan, Hong Kong SAR
  • Please note that this hackathon is NOT open to residents of countries outside of the countries listed above and registrants who are not at least the age of majority in their country of residence.

2. Teams

2.1 Eligibility is on an individual basis. Each Participant shall also be referred to as a Hackathon Team and each Hackathon Team will consist of only ONE (1) member.

2.2 The Participant will also act as the Team Representative for the purpose of the hackathon.

3. Participants’ Code of Conduct

3.1 The Participants consist of people from countries around the world and we expect all Participants to respect the diversity of our community. Content containing illegal or excessive obscene or foul language, excessive violence, nudity, or sexual activity will be flagged and removed. Content that is abusive or likely to be offensive to others may also be flagged and removed.

3.2 As the Hackathon is an ongoing process over a period of time, Hackathon Participants, AngelHack and the Organising Partner(s) may not be as responsive as you may hope for, due to reasons such as, amongst others, time zone differences, personal commitments outside the Hackathon, and work or education commitments. Therefore, we seek understanding from all involved parties in the Hackathon to respect each individual’s boundaries, external commitments or circumstances. Acts of disrespect to Participants, AngelHack, or the Organising Partner(s), includes, but is not limited to, constant messaging within an unreasonably short period of time, flooding the Hackathon main channel(s) without providing a reasonable amount of time for responses to be made, use of abusive and/or demanding language, etc.

3.3 We value integrity and expect you to represent who you are honestly in your submissions and in any forms that we share with you during the course of the Hackathon.

3.4 We celebrate makers, creators, developers and want to help each of you who are part of this community grow and improve your skills. When you share feedback, please keep it constructive. Any content that is abusive, threatening, expresses hatred, or is likely to offend others is unacceptable and may result in the content being removed, the suspension or termination of your account, or disqualification from the Hackathon, at the sole discretion of AngelHack and/or the Organising Partner(s).

3.5 Do not share or post any personal or private information about you or any other person. This includes any photos (unless you have explicit permission to do so), phone numbers, addresses, location details, personal email, social media profiles.

3.6 Our community and platforms help showcase software, participate in virtual challenges and hackathons, share your ideas, code, get feedback and motivation. Do not upload anything unrelated, explicit, repeatedly post the same thing or post anything that is not relevant to the event that you are participating in or send excessive, unsolicited messages to other users.

4. Project Rules

4.1 The hacking period and Submission Period for the Hackathon shall be as follows:

(a) The official hacking and Submission period takes place from April 19, 2024 to June 17, 2024, 

(b) Participants may begin hacking on April 19, 2024 after the commencement of the Opening Ceremony

(c) and the Submission Period officially closes on June 70, 2024, 11:59PM GMT+8

(d) The Participant must make the Submission to the Hackathon’s submission portal during the official Submission Period.

4.2 Participants can submit for a maximum two (2) challenge statements only during the hackathon

4.3 You are strictly not allowed to submit Submissions that are not created by you or that are not what you have worked on during the period of the Hackathon. If there are other projects that could be great resources, kindly reach out to AngelHack or the Organising Partner(s) in the community and request to add such projects to the resources.

4.4 You are not allowed to work on your project before the hacking period stipulated in Rule 4.1. Each team is required to use version control for your code throughout the course of the Hackathon. Any repositories with single commits of large files without proper history will be default assumed to be unqualified unless proven otherwise.

4.5 Each Submission will be judged solely on what you have worked on during the duration of the Hackathon. Participants is required to share the source code of the Submission on the Submission Portal.

4.6 If you are using an existing project, you must credit the project by disclosing all details of the same and outline the improvements made to the project during the Hackathon period in your Submission, provided always that the Intellectual Property Rights of such existing project is exclusively owned by you. Failure to comply with this Rule 4.6 may result in the disqualification of your Submission.

4.7 Make sure to check the license of any public repository before you use it for your Submission and give the appropriate credit to that repository and the creator in your Submission. You cannot utilize content that violates any third party’s rights (including privacy, personality, moral or intellectual property rights, or that constitutes copyright infringement) unless you have acquired the necessary rights to do so or the content is subject to an open source license. 

4.8 When making your Hackathon Submission, you must ensure that your Submission adheres to the Fresh Code Rule (as defined below) or that you have the right to use any existing content that forms the whole or a part of your Submission. This includes, without limitation, images, lines of code or demonstration videos in your Submission.

4.9 The use of generative AI tools, including but not limited to tools for code completion (e.g GitHub Copilot.), chatbots (e.g.ChatGPT), image generation (e.g. DALL-E), etc., are approved for the Hackathon as long as no personal, confidential, or restricted information is used with the AI tool. You who use AI technologies do so at your own risk. In the event where you expose proprietary, sensitive, confidential, or personally identifiable data to an AI tool, AngelHack reserves the right to disqualify such You from the Hackathon and any consequences arising thereof shall be solely borne by you.

4.9.1 You are responsible for ensuring any code, datasets, or similar assets generated using generative AI tools in your Submission adhere to Rules 4.6 to 4.10 above. 

4.9.2 Any usage of generative AI tools must be specifically credited and disclosed in your Submission describing the extent of the use and which parts of the Submission it was used for. For example: “GitHub Copilot was used for code completions.”

5. The Fresh Code Rule

5.1 All Participants should strictly adhere to the fresh code rule, under which the following should be adhered to (the “Fresh Code Rule”):

5.1.1 What can be done before the Hackathon

(a) Participants can create wireframes, designs and user flow.

(b) Participants can pre-train models or gather data sets prior to the event.

5.1.2 What must be done during the Hackathon

(a) All code submitted as part of the Submission must be written during the Hackathon and submitted before the expiry of the Submission Period (as per Rule 4.1).

5.2 Provided that the Fresh Code Rule is adhered to, Participants are allowed to use any coding languages or open-source libraries as part of their Submission. However, Participants are only allowed to use Azure Services exclusively, if there is any cloud-based functionality in the solution-implementation in their submissions.

5.3 Participants may also opt to subscribe for an Azure free trial, which provides $200 worth of Azure credits upon sign-up, available for use towards building their submission projects.

6. Intellectual Property Rights

6.1 Save as otherwise agreed with the relevant Hackathon Team (including under these Hackathon Rules and the AngelHack Terms of Service), all Intellectual Property Rights subsisting in a Hackathon Team’s Submission shall remain vested in such Hackathon Team. 

6.2 Submission Rights

6.2.1 By entering the Hackathon, you grant to AngelHack and/or Organising Partner(s), and any other third parties acting on the Organising Partner’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, the marketing, sale or promotion of on AngelHack and/or Organising Partner(s), products or services, posting or linking to the Submission on AngelHack and/or Organising Partner(s) websites and applications, including the Hackathon Website, and display and promotion of the Submission in any other media, worldwide.

6.2.2 By entering, you acknowledge that the AngelHack and/or Organising Partner(s) may have  developed or commissioned materials similar or identical to your Submission and you waive any claims resulting from any similarities to your entry. Further, you understand that the AngelHack and/or Organising Partner(s) will not restrict work assignments of representatives who have had access to your Submission and you agree that use of information in their representatives’ unaided memories in the development or deployment of their products or services does not create liability for us under this agreement or copyright or trade secret law.

6.2.3 Your Submission may be posted on a public website. The AngelHack and/or Organising Partner(s) are not responsible for any unauthorized use of your Submission by visitors to this website. The AngelHack and/or Organising Partner(s) and Hackathon Partner(s) are not obligated to use your Submission for any purpose, even if it has been selected as a winning Submission.

6.3 Submission Display

6.3.1 The following Submission components may be displayed to the public: Name, Description, Images, Video URL, GitHub link, Demo Website, the Submission Category and Platform, and Submitter Type. Other Submission materials may be viewed by the AngelHack and/or Organising Partner(s), and Judges for screening and evaluation.

6.4. Participants represent and warrant that the AngelHack and/or Organising Partner(s), and Hackathon Partner(s) are free to use Participant(s)’ Submission in the manner described above, as provided or as modified by the Administrator, without obtaining permission or license from any third party and without any compensation to Participants.

7. Judging

7.1 Judges

Eligible Submissions will be evaluated by a panel of judges selected by the AngelHack and/or Organising Partner(s) (the “Judges”). Judges may be employees of the AngelHack and/or Organising Partner(s) or external, which 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 AngelHack and/or Organising Partner(s). 

7.2 Criteria

The Judges will score eligible Submissions using the Judging Criteria (the “Judging Criteria”):

I. Technical Merit
II. Feasibility
III. Innovation & Creativity
IV. Potential impact
V. Pitch quality
VI. Submission check-in

The Judging Criteria above may not apply to every Prize. The Participant(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.

7.3 Submission Review 

Judges are not required to test the Application and may choose to judge Applications based solely on the text description, images and video provided in the Submission.

7.4 Tie Breaker

For each Prize, 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.

8. Prizes

8.1 Participants are only eligible to win up to one (1) Challenge Prize.

8.2 The prizes for the Hackathon comprise of either cash, in-kind, or internship and job opportunities. In the event that the prize is awarded as cash, it is denominated in USD, and includes all applicable taxes and fees associated with prize receipt and/or use by the prize recipients.

8.2.1 Prize recipients are responsible for any fees associated with receiving or using a prize, including but not limited to, wiring fees. Prize recipients are responsible for reporting and paying all applicable taxes in their jurisdiction of residence (federal, state/provincial/territorial and local). Prize recipients 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. Prize recipients 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 prize provider reserves the right to withhold a portion of the prize amount to comply with the tax laws of the United States or those of a winner’s jurisdiction. 

8.2.2 All prize recipients will be contacted within thirty (30) working days after the announcement of the Winner(s) and prize administration will take place within the next sixty (60) working days after the Hackathon has concluded.

8.2.3 Prizes for the Hackathon shall be distributed and administered in the manner determined by Microsoft in its sole discretion.


(a) Disqualification: AngelHack may deem a potential winner ineligible to win if:

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

(ii) failure to provide correct information required for the delivery of a Prize or to provide the verification necessary to meet the eligibility requirements;

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

(iv) the Submission or the potential winner, is disqualified for any other reason

(v) In the event of a disqualification, the Poster and/or Administrator may award the applicable Prize to an alternate potential winner.

8.3 Prize distribution may be delayed due to processing time or where there are any issues with the information provided by a recipient of a prize. For example, distribution of a prize in fiat currency may be delayed by an additional fourteen (14) days to account for further processing time for the following cases:

(a) Winning team is based in a country where Paypal does not operate, or has issues receiving funds through Paypal.

(b) Correction of bank information

(c) Requests to facilitate local bank’s funds verification process and processing timeline.

8.4 You agree that AngelHack and/or the Organising Partner(s) shall be deemed to have discharged its obligations in relation to the administration and distribution of prizes under this Rule 8 upon effecting the administration and distribution of such prizes in accordance with the relevant details provided by the relevant Winners under Rule 8.2. Save in the case of fraud, gross negligence or misconduct, AngelHack and/or the Organising Partner(s) shall not be responsible for any delay and/or failure to receive the prizes.

9. Removal of Content and Terms 

AngelHack and/or Organising Partner(s) reserves the right to remove your content and/or block or remove your account from the platform if we believe that you have violated any of the guidelines mentioned above. 

10. Incorporation of General Terms

In addition to these Hackathon Rules, please read our terms of service, privacy policy, code of conduct for terms which also apply to your participation in the Hackathon.

AngelHack and/or the Organising Partner(s) reserve the right to modify these Hackathon Rules without prior notice.

Sponsored by:

Powered by:

Stay connected: