Terms & Conditions

1. Eligibility

• The hackathon is open to participants aged 15 to 20 years.
• Each team must consist of exactly 2 members.
• Participants must provide accurate registration information.
• Only Pakistani phone numbers are accepted for registration.
• The Organizer may request additional information where reasonably necessary to verify eligibility.

2. Registration Fee

• The registration fee is PKR 500 per team.
• The fee is payable during registration according to the payment instructions provided by the Organizer.
• Participants must upload valid payment proof, such as a transaction image or screenshot.
• The registration fee is for the team, not for each individual member.

Registration is not considered successfully verified until the payment and registration information have been reviewed by the Organizer.

3. Registration Confirmation

The Organizer aims to review and confirm registrations within 24 hours.

A submitted registration does not automatically guarantee acceptance. The Organizer may reject or request clarification regarding registrations containing incomplete, inaccurate, invalid, or suspicious information.

4. Team Requirements

Each team must contain exactly two members.

Participants are responsible for coordinating with their teammates throughout the hackathon.

A participant may not knowingly register multiple teams unless the Organizer explicitly permits it.

5. Idea Submission

During registration, each team must provide a description of its proposed project idea.

The idea description must not exceed 1,200 characters.

Teams should provide an original and clearly described idea that can reasonably be developed as a web application within the hackathon requirements.

6. Round 1

In Round 1, teams are required to develop a complete web application based on their selected idea.

The project must contain:

• A functional frontend
• A functional backend
• Appropriate project functionality based on the selected idea
• Proper project documentation

Round 1 Submission Requirements

Teams must:

1. Host their website on Vercel.
2. Make their project repository public.
3. Provide proper project documentation.
4. Submit the live website link.
5. Submit the public repository link through the designated submission form.

The Organizer will provide further instructions regarding the submission process.

7. Round 1 Shortlisting

Following Round 1 evaluation, 5 teams will be shortlisted for Round 2.

The number of shortlisted teams may only be changed by the Organizer if circumstances require an adjustment and the participants are appropriately informed.

8. Round 2

The shortlisted teams will receive a problem statement based on a real-world problem.

Teams must develop a complete web-based solution addressing the assigned problem.

The Round 2 project must include appropriate frontend and backend functionality and must satisfy the submission requirements communicated by the Organizer.

9. Round 2 Submission Requirements

Teams must:

1. Host their website on Vercel.
2. Make their project repository public.
3. Provide proper project documentation.
4. Submit the live website link.
5. Submit the public repository link through the designated submission form.

Additional instructions may be communicated to shortlisted teams before or during Round 2.

10. Judging Criteria

Projects will be evaluated based on factors including:

UI / Design

Evaluation may consider:

• User interface quality
• Visual structure
• Usability
• Responsiveness
• Overall user experience

Codebase

Evaluation may consider:

• Code organization
• Technical implementation
• Maintainability
• Quality of development
• Proper implementation of the required functionality

Idea Selection

Evaluation may consider:

• Clarity of the problem
• Relevance of the proposed solution
• Originality and usefulness of the concept
• How effectively the idea is converted into a working application

11. Google Meet Evaluation

As an online event, no participant is required to attend in person; evaluation and meetings are conducted remotely through online tools such as Google Meet.

Teams may be onboarded to a Google Meet session to discuss the project they developed.

During the session, judges or organizers may ask questions about:

• The project idea
• Problem being addressed
• Technical implementation
• Features
• Development decisions
• Codebase
• Demonstration of the completed website

The Google Meet discussion may form part of the overall evaluation.

12. Use of AI Tools

This is an AI Web Development Hackathon, and participants may use AI-assisted development tools where permitted by the Organizer.

Participants remain responsible for:

• Understanding their submitted project
• Being able to explain their implementation
• Ensuring their project functions as submitted
• Reviewing AI-generated code before using it
• Removing confidential information from prompts, repositories, and submissions

The Organizer may ask participants to explain or demonstrate parts of their project during evaluation.

13. Originality and Intellectual Property

Participants must have the right to use the code, designs, images, content, libraries, APIs, datasets, and other materials included in their project.

Participants must not knowingly submit:

• Stolen code
• Unauthorized copyrighted material
• Another person’s private project
• Projects submitted without the necessary permission
• Malicious software or harmful code

Open-source libraries and third-party resources may be used in accordance with their applicable licenses.

Participants retain ownership of their original project work, subject to the licenses and rights applicable to third-party materials used in the project.

14. Public Repository Requirement

The public repository requirement means that submitted project repositories must be accessible for evaluation.

Participants should ensure that their repositories do not contain:

• Passwords
• API keys
• Authentication secrets
• Database credentials
• Private tokens
• Sensitive personal information

The Organizer is not responsible for confidential information that participants intentionally publish in their public repositories.

15. Prohibited Conduct

Participants must not:

• Attempt to disrupt the hackathon infrastructure
• Attack or compromise another participant’s project
• Submit malicious software
• Manipulate or interfere with judging
• Submit fraudulent payment proof
• Provide false registration information
• Impersonate another participant
• Intentionally copy another team’s project
• Use unauthorized access to obtain another team’s work
• Engage in harassment or abusive conduct toward other participants, judges, or organizers

The Organizer may disqualify a team for serious violations of these Terms.

16. Disqualification

A team may be disqualified if it:

• Does not meet the eligibility requirements
• Provides false or misleading information
• Submits invalid payment proof
• Violates the submission requirements
• Uses unauthorized or stolen work
• Attempts to manipulate the evaluation process
• Violates applicable law or these Terms
• Engages in conduct that materially disrupts the hackathon

Where reasonably practicable, the Organizer may communicate the reason for disqualification.

17. Awards

The hackathon will recognize the following cash prizes:

• 1st Prize - PKR 5,000, awarded to the winning team.
• Runner-up - PKR 3,000, awarded to the runner-up team.

All other participants who complete the hackathon automatically receive e-certificates, issued and emailed once the results are announced.

Prize disbursement and any further prize details shall be handled separately by the Organizer following the announcement of results.

18. Changes to the Hackathon

The Organizer reserves the right to modify dates, deadlines, submission procedures, problem statements, evaluation procedures, or other operational details when reasonably necessary.

Participants will be informed of significant changes through the official communication channels used for the hackathon.

19. Cancellation or Postponement

If circumstances outside the Organizer’s reasonable control affect the hackathon, the Organizer may postpone, modify, or cancel the event.

Participants will be informed of significant changes through the available official communication channels.

20. Limitation of Responsibility

Participants are responsible for maintaining backups of their project files, repositories, and other work.

The Organizer is not responsible for technical problems affecting third-party services such as hosting providers, GitHub, Vercel, Google Meet, internet service providers, payment platforms, or other external services.

21. Communication

Official hackathon instructions, deadlines, submission details, and updates will be communicated through the official channels designated by The Click Dream - Institute.

Participants are responsible for checking those channels and providing a working email address and phone number during registration.

22. Acceptance of Terms

By submitting the registration form, each participant confirms that they have read, understood, and agreed to these Terms & Conditions.

Participants who do not agree to these Terms should not register for the hackathon.

23. Contact

For questions regarding these Terms & Conditions, participants may contact The Click Dream - Institute through the official communication channel provided on the hackathon registration website.