UGREEN Hackathon 2026 on AI NAS (the “Hackathon”) 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

Registration Period: October 22, 2026 (9:00 am Pacific Time) – November 15, 2026 (11:45 pm Pacific Time) (“Registration Period”).

Round 1 Submission Period: October 22, 2026 (9:00 am Pacific Time) – November 15, 2026 (11:45 pm Pacific Time) (“Round 1 Submission Period”).

Round 1 Judging Period: November 16, 2026 (12:00 am Pacific Time) – November 19, 2026 (5:00 pm Pacific Time) (“Round 1 Judging Period”).

Finalist Invitations: November 21, 2026 (12:00 a.m. Pacific Time).

Round 2 Submission Period: November 22, 2026 (12:00 am Pacific Time)  - November 30, 2026 (11:45 pm Pacific Time) (“Round 2 Submission Period”).

Round 2 Judging Period: December 1, 2026 (10:00 am Pacific Time) - December 5, 2026 (5:00 pm Pacific Time) (“Round 2 Judging Period”).

Winners Announced: On or around December 6, 2026 (2:00 pm Pacific Time).

Hackathon Period: October 22, 2026 (9:00 am Pacific Time) – on or around December 6, 2026 (2:00 pm Pacific Time) (“Hackathon Period”)

2. Sponsor and Administrator

Sponsor and Administrator: AMERICA UGREEN LIMITED (“Sponsor,” “Administrator,” or “UGREEN”), 865 S. Milliken Avenue, Suite B, Ontario, CA 91761.

3. Eligibility

• The Hackathon IS open to: 

• Individuals who are at least the age of majority where they reside as of the time of entry (“Eligible Individuals”);

• Teams of up to three Eligible Individuals (“Teams”); and

(the above are collectively, “Entrants”)

Each Eligible Individual may enter either individually or as a member of one Team, but not both. An Eligible Individual may not join more than one Team. 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 open to individuals residing in the following countries and territories, subject to the eligibility restrictions outlined below and the applicable geographic eligibility settings on Devpost.

North, Central & South America

United States, Canada (excluding Quebec), Mexico, Costa Rica, Honduras, El Salvador, Guatemala, Argentina, Colombia, Peru, Uruguay, Chile, and Paraguay.

Europe

Ireland, Austria, Bulgaria, Belgium, Poland, Denmark, Germany, France, Finland, Netherlands, Czech Republic, Croatia, Lithuania, Romania, Portugal, Sweden, Slovenia, Spain, Greece, Hungary, Italy, United Kingdom, Norway, Switzerland, Serbia, Albania, Moldova, Slovakia, Estonia, Latvia, Iceland, and Malta.

Asia-Pacific

Taiwan, Hong Kong SAR, Macao SAR, Indonesia, Malaysia, Thailand, Singapore, South Korea, Japan, Australia, New Zealand, Sri Lanka, Nepal, Philippines, Cambodia, Pakistan, Maldives, Laos, and Mongolia.

Middle East & Caucasus

Kuwait, Oman, Qatar, United Arab Emirates, Türkiye, Israel, Georgia, Lebanon, Jordan, Armenia, Yemen, Bahrain, and Azerbaijan.

Africa

South Africa, Egypt, Nigeria, Kenya, Morocco, Mauritius, Côte d'Ivoire, Tunisia, Algeria, Mozambique, Tanzania, and Burkina Faso

The Hackathon IS NOT open to:

• Individuals who are residents of, or Organizations domiciled in, a country, state, province or territory where the laws of the United States or local law prohibits participating or receiving a prize in the Hackathon (including, but not limited to, the province of Quebec, Afghanistan, Andorra, Angola, Antigua and Barbuda, Bahamas, Bangladesh, Barbados, Belize, Belarus, Benin, Bhutan, Bolivia, Bosnia and Herzegovina, Botswana, Brazil, Brunei, Burundi, Cabo Verde, Cameroon, Central African Republic, Chad, China, Comoros, Crimea, Cuba, Cyprus, Democratic Republic of the Congo, Djibouti, Dominica, Dominican Republic, Donetsk, and Luhansk regions, Ecuador, Equatorial Guinea, Eritrea, Eswatini, Ethiopia, Fiji, Gabon, Gambia, Ghana, Grenada, Guinea, Guinea-Bissau, Guyana, Haiti, India, Iran, Iraq, Jamaica, Kazakhstan, Kiribati, Kosovo, Kyrgyzstan, Lesotho, Liberia, Libya, Liechtenstein, Luxembourg, Madagascar, Malawi, Mali, Marshall Islands, Mauritania, Micronesia, Monaco, Montenegro, Myanmar, Namibia, Nauru, Nicaragua, Niger, North Korea, North Macedonia, Palau, Palestine, Panama, Papua New Guinea, Republic of the Congo, Russia, Rwanda, Saint Kitts and Nevis, Saint Lucia, Saint Vincent and the Grenadines, Samoa, San Marino, São Tomé and Príncipe, Saudi Arabia, Senegal, Seychelles, Sierra Leone, Solomon Islands, Somalia, South Sudan, Sudan, Suriname, Syria, Tajikistan, Timor-Leste, Togo, Tonga, Trinidad and Tobago, Turkmenistan, Tuvalu, Uganda, Ukraine, Uzbekistan, Vanuatu, Vatican City, Venezuela, Vietnam, Zambia, Zimbabwe and any other country which is comprehensively sanctioned by the U.S. Treasury’s Office of Foreign Assets Control) 
• 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 at the time of entry.
• Organizations involved with the design, production, paid promotion, execution, or distribution of the Hackathon, including the Sponsor and Administrator (“Promotion Entities”).
• Employees, representatives and agents** of such 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), 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 Administrator, 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 that 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 ugreenhackathon.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.

• Entrants will obtain access to the required developer tools/platform and complete a Project described below in Project Requirements. Use of the developer tools, the UGREEN Developer Skill Package, and any UGREEN AI NAS access is subject to the license agreement related thereto. Entry in the Hackathon constitutes consent for the Sponsor and Devpost to collect and maintain an entrant’s personal information for the purpose of operating and publicizing the Hackathon.

• Download the UGREEN Skill Developer Package at https://ai.ugreen.com/pages/hackathon-starter-kit.

• Up to thirty (30) Finalists (“Finalists”) will be invited to participate in Round 2 Submission Period. See Section 6 for details. Finalists will be invited via email with a link to a private submission URL. Submissions for Round 2 must be submitted via the private submission URL during the Round 2 Submission Period.

• At 12:00 a.m. PT on November 21, 2026 , UGREEN will email each Finalist its temporary login credentials, assigned device, testing day, connection instructions, and private submission URL. Each Finalist Project receives one set of credentials and one testing day. For Teams and Organizations, UGREEN sends the credentials only to the Representative.

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

Project Requirements

What to Create: 

Create an AI Skill for UGREEN AI NAS using the official UGOS Skill Creation Tool and the development resources provided in the Hackathon Starter Kit. Please download: ai.ugreen.com/pages/hackathon-starter-kit 

The Starter Kit provides instructions for setting up your development environment, creating Skills, and understanding supported NAS capabilities. You can also download the UGOS Skill Creation Tool directly from the Starter Kit.

All submitted Skills must comply with the supported capabilities and technical requirements specified in the official documentation. Skills must follow the official Uliya Skill Development Standard and use supported UGOS CLI capabilities through registered expert agents. Custom executable scripts, general-purpose programming runtimes, and unauthorized direct access to NAS resources are not supported.

Entrants are encouraged to use the AI NAS local AI model, but its use is not required. Properly authorized third-party models may also be used, subject to applicable rights, service terms, and the data restrictions outlined under Third Party Integrations.

Entrants are encouraged to join the UGREEN Community for technical guidance and support throughout the Hackathon.

1. Automate Your Workflow - Turn repetitive work into executable AI workflows. Build an AI Skill that uses authorized NAS files and data, together with the file, document, knowledge, and system capabilities provided for the Hackathon, to organize content, extract information, generate summaries, and streamline repetitive tasks.
2. Bring Memories to Life - Make family content and digital memories easier to find and enjoy. Build an AI Skill that organizes, searches, extracts text from, summarizes, or creates albums from authorized photos, videos, and documents stored on UGREEN AI NAS.
3. Unleash Your Creativity - Turn your media library into a starting point for creativity.Build an AI Skill that helps photographers, editors, designers, and other content creators search, tag, select, organize, and review media stored on UGREEN AI NAS, making creative preparation faster and more efficient.
4. Open Innovation - Combine the NAS, AI, media, file and knowledge capabilities provided for the challenge to build an original AI Skill that solves a real user need and runs on UGREEN AI NAS.

Functionality (Round 2): The Final Skill Package must install and run consistently in the assigned UGREEN AI NAS environment. It must function as shown in the video and described in the documentation. (The Skill package must follow the official Uliya Skill Development Standard and use SKILL.md as its required entry point. It may include supporting Markdown files under references/, each directly linked from SKILL.md. Separate manifests, scripts, executables, binaries, and other unsupported files must not be included.）

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: An Entrant may build on an idea conceived before the Hackathon, but the submitted Skill and its core workflow must be newly developed during the Hackathon. Previously developed Skills or submission materials may not be reused. Properly authorized third-party development tools and resources may be used, subject to the technical requirements and applicable licenses. Round 2 Submissions must build on the same Project submitted in Round 1. 

Third Party Integrations: An Entrant may use third-party SDKs, APIs, components, and data only when it has the right to do so and complies with the applicable terms and licenses. The Proposal must identify third-party components, their sources and applicable licenses, and any external services and data flows. The Entrant bears responsibility for infringement arising from its Project or use of third-party material.

Round 1 Submission Requirements 

Submissions to the Hackathon must meet the following requirements:

• Project built with the required developer tools and meets the above Project Requirements.

• Include a PDF answering the following questions. The ten substantive responses must not exceed 500 English words in total. Team consent declarations, member names, electronic signatures, and third-party license information are excluded from this word limit.

1. One sentence: What does the Skill do? 
2. Who is the target user and problem? 
3. What is your proposed solution? 
4. What is the Core User Flow? 
5. What substantive difference does your idea offer compared with existing tools or conventional AI solutions? 
6. Which UGREEN AI NAS capabilities will be used, and at which step in the workflow? 
7. What was your technical approach? Describe the planned Skill workflow, supported NAS CLI capabilities, expert agent orchestration, required inputs, permissions, AI model choices, and data handling, as applicable;
8. What is the current development status? Identify what was implemented already, not yet implemented, or is pending NAS validation if selected to be a Finalist. 
9. What is your final validation plan? Name two core test cases and one edge case to validate if selected as a Finalist. 
10. Are there any known limitations of your Project? Describe current known limitations, technical risks, and any external dependencies. 

• Include a ZIP Initial Skill Package with the following items: 

• Submit the initial version of your Skill as a ZIP file. The ZIP file must not exceed 10 MB for contest submission.
• The package must follow the official Uliya Skill Development Standard and include:
  • SKILL.md (Required): The required entry point containing the Skill name, description, user goal, required inputs, supported CLI capabilities, expert orchestration workflow, and completion and failure handling.
    • The file must include the following fortmat:
      • - name: A lowercase, hyphenated name containing 2–64 characters.
      • - description: A description of no more than 1,024 characters.Supporting References
  • Supporting References(Optional): Additional Markdown files under the references/ directory, each directly linked from SKILL.md.

• Additional Requirements
  • The Initial Skill Package does not need to be fully installable or operational on UGREEN AI NAS at this stage.
  • Local test results are optional. Executable scripts must not be included in the Skill package. Entrants are not required to submit demo videos, runtime screenshots, test reports, public repositories, Git histories, AI conversation logs, model weights, or training datasets during Round 1.
  • The package must not contain real credentials, personal data, unauthorized third-party materials, malicious code, or functionality that enables undisclosed high-risk external access. Password protection that prevents review is prohibited.
  • The submitted package will be used for preliminary evaluation. Selected finalists may continue developing and refining the same Project for the Final Round.

Round 2 Submission Requirements 

Selected finalists must submit both a Final Skill Package and a Final Demo Video for the same Project through the designated Devpost Final Round submission link. 

• Final Skill Package

Submit the final version of your Skill in the officially supported format, including SKILL.md and any required Markdown references. The final package must comply with the same file structure and technical limits specified for the Initial Skill Package. The Skill must pass the required validation checks and successfully operate in the provided UGREEN AI NAS test environment.

• Final Demo Video

Include a demonstration video of your Project. The video portion of the Submission:

• should be less than three (3) minutes. Judges are not required to watch beyond three minutes
• must include footage that shows the Project running in the UGREEN AI NAS test environment and narration explaining the Skill's core workflow, key capabilities, and actual results.
• must be uploaded to and made publicly visible on YouTube and a link to the video must be provided on the submission form on the Hackathon Website; and
• must not include third party trademarks, or copyrighted music or other material unless the Entrant has permission to use such material. Entrants may show the Sponsor’s trademarks and materials that the Sponsor provides for the Hackathon.

Multiple Submissions 

Each individual Entrant or Team may submit only one Project during the Hackathon. The Final Round submission must be the final version of the same Project submitted in Round 1 and does not count as an additional Project.

Submission ownership

Be the original work of the Entrant, be solely owned by the Entrant, and not violate the Intellectual Property rights of any other person or entity.

Testing 

Round 1: Judges will review the Round 1 PDF and ZIP Pre-test Skill Package. No website, demo link, or test build is required.

Round 2: Judges will test the Final Skill Package in the assigned UGREEN AI NAS environment. Judges may also use the video and documentation. The Entrant must keep the Project available free of charge, without restriction, for testing and evaluation by the Sponsor and Judges until the Round 2 Judging Period ends. 

Finalists are responsible for backing up any data they wish to retain, including Skill runtime logs and test data, before their assigned testing period ends. Data deleted during the reset process cannot be recovered.

Language Requirements

Registration, submitted materials, and entrant communications must be in English. Demo videos must use English narration or complete English subtitles. 

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 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.

Intellectual Property 

Your Submission must: (a) be your (or your Team, or Organization’s) original work product; (b) be solely owned by you, your Team, your Organization 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. 

Properly licensed third-party components and general technical assistance through the UGREEN Community are permitted; a person outside the team may not develop the Project or create its submission materials for the Entrant. An Entrant may submit a Submission that includes the use of open source software or hardware, provided the Entrant 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.

Financial or Preferential Support 

A Project must not have been developed, or derived from a Project developed, with financial or preferential support from the Sponsor or Administrator. 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 Administrator any time prior to the end of either 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 

Before the end of each Submission Period, you may save draft versions of your Submission. Once a Submission Period ends, you may not change the Submission for that round, but you may continue to update the Project in your Devpost portfolio. Do not delete your Round 1 Submission materials.

Modifications After a Submission Period
The Sponsor and Devpost may permit you to modify part of your Submission after a Submission Period ends 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

Sponsor and Administrator reserve the sole right to determine the eligibility and judging methodologies for all submissions. This process may utilize expert panels, peer review, automated AI-driven analysis, or any combination thereof to ensure efficient, fair, and objective evaluation. Eligible submissions will be evaluated by a panel of judges selected by the Sponsor (the “Judges”). Final eligibility and judging decisions are made by humans. 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 either Judging Period. Judging may take place in one or more rounds with one or more panels of Judges, at the discretion of the sponsor.

Round 1 Judging: 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 proposes an AI NAS solution. Eligible Projects will then be scored according to the Judging Criteria below. Because Entrants do not have NAS access during the Round 1 Submission Period, Judges will evaluate each criterion based on the Round 1 Submission materials, including the PDF and ZIP Pre-test Skill Package, and the Project’s proposed functionality, planned use of UGREEN AI NAS capabilities, and validation plan. A lack of NAS runtime evidence will not, by itself, make a Submission ineligible or lower its Round 1 score. Up to thirty (30) of the highest-scoring eligible Projects will become Finalists.

Round 2 Judging: All eligible Projects submitted during the Round 2 Submission Period will be evaluated based on their working Skill in the assigned UGREEN AI NAS environment, the video, and the documentation, including whether the ideas in the Round 1 Submission were delivered. Round 1 scores do not carry over. Winners are decided by Round 2 scores only.

Judging Criteria (Rounds 1 and 2): Entries will be judged on the following equally weighted criteria (the “Judging Criteria”), according to the sole and absolute discretion of the Judges:

• User Value: Whether the Skill addresses a clear user problem and gives users a clear workflow, useful feedback, and a meaningful result.
• Innovation & Differentiation: Whether the Skill offers a substantive new function, interaction, or workflow that differs from conventional AI tools and existing solutions.
• Technical Quality: Whether the Skill demonstrates a sound orchestration approach, appropriate use of supported CLI capabilities and expert agents, proper handling of permissions and errors, and reliable execution appropriate to its development stage.
• AI NAS Fit & Validation: Whether the Skill makes meaningful use of UGREEN AI NAS capabilities, including relevant local data, storage, computing, privacy, or other supported capabilities, rather than merely running on NAS.

If a Finalist is unable or ineligible to proceed, the Sponsor may invite the next highest-scoring eligible Project in its place.

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.

For the Most Creative Prize, if two or more Submissions are tied on the Innovation & Differentiation Judging Criterion, the tied Submission with the highest overall score will be considered the higher-scoring Submission. If any ties remain, the panel of Judges will vote on the tied Submissions.

7. Intellectual Property Rights

All Submissions remain the intellectual property of the individuals or organizations that developed them. By submitting an entry, entrants agree that the Sponsor will have a non-exclusive license to use such entry for judging the entry. Entrants agree that the sponsor and Devpost shall have the right to promote the Submission and use the name, likeness, voice and image of all individuals contributing to a Submission, in any materials promoting or publicizing the Hackathon and its results, during the Hackathon Period and for three years thereafter.  Some Submission components may be displayed to the public. Other Submission materials may be viewed by the sponsor, Devpost, and judges for screening and evaluation. By submitting an entry or accepting any prize, entrants represent and warrant 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, unless entrant is the owner of such rights or has permission from their rightful owner to post the content; and (b) the content submitted does not contain any viruses, Trojan horses, worms, spyware or other disabling devices or harmful or malicious code.

8. Prizes

IMPORTANT NOTES ON MULTIPLE PRIZE ELIGIBILITY:

• Each Project can win only one Prize. If a Project that would win Most Creative also wins the Grand Prize, Second Place, or Third Place, the Most Creative Prize goes to the next highest-scoring eligible Project for the Innovation & Differentiation Judging Criterion.

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 Entrant 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 Administrator. 
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. The deadline for returning the Required Forms to the Administrator is ten (10) business days after the Required Forms are sent. 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 of 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 and residents of other countries may be 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 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 Administrator, is not a confidential, fiduciary, or other special relationship.
   2. You will be bound by and comply with these Official Rules and the decisions of the Sponsor, Administrator, 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 Administrator’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 Administrator. 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, Administrator, and third parties acting on their behalf. Such personal information includes, but is not limited to, your name, likeness, photograph, voice, opinions, comments and hometown and country of residence. It may be used in any existing or newly created media, worldwide without further payment or consideration or right of review, unless prohibited by law. Authorized use includes but is not limited to advertising and promotional purposes. 

11. General Conditions 

• Sponsor and Administrator 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.
• Sponsor and Administrator 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.
• 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 Administrator 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.
• 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.
• 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 Administrator. The Sponsor and Administrator 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.
• 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. 
• The Sponsor or Administrator’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.
• Excluding Submissions, all intellectual property related to this Hackathon, including but not limited to copyrighted material, trademarks, trade-names, logos, designs, promotional materials, web pages, source codes, drawings, illustrations, slogans and representations are owned or used under license by the Sponsor and/or Administrator. 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 Administrator’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

• Except where prohibited by law, as a condition of participating in this Hackathon, Entrant agrees that:
  • 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 Entrant;
  • The Federal Arbitration Act shall govern the interpretation, enforcement and all proceedings at such arbitration; and
  • Judgment upon such arbitration award may be entered in any court having jurisdiction.
• 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 Entrant’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.
• 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 Devpost’s Privacy Policy, available at https://info.devpost.com/privacy, and UGREEN’s Privacy Policy, available at https://www.ugreen.com/pages/privacy-policy.

For questions, send an email to [email protected].