Paid event participation

1. 01Only teams declared eligible or shortlisted for the applicable paid event or round may participate.
2. 02Unless stated otherwise, only the team leader must make one payment on behalf of the entire team.
3. 03Teams must verify their event name, team name, members and eligibility before paying.
4. 04Multiple payments will not create additional entries, rankings or benefits.
5. 05Payment grants access only to the applicable event or round. It does not guarantee a certificate, ranking, prize, internship, qualification or any other result.
6. 06Any division or collection of the fee between team members is the team’s responsibility. We Code Coders will not resolve internal payment disputes.

Once payment has been successfully completed and participation access has been provided, the fee is final and non-refundable.

Participants must not initiate false chargebacks, provide misleading information, threaten organisers, harass volunteers or use abusive or coercive conduct to demand a refund. Genuine payment errors must be reported through the official support channel.

Fraudulent disputes or knowingly false chargebacks may lead to disqualification, exclusion from future events and submission of relevant records to the payment provider or appropriate authority.

1. 01Every team must follow the official problem statement, round instructions and submission requirements.
2. 02All required forms, files, repositories, links and demonstrations must be submitted before the announced deadline.
3. 03Inaccessible links, missing permissions, corrupted files, incomplete forms and late submissions may be rejected.
4. 04Participants are responsible for keeping proof of payment and submission.
5. 05Submitted work must be original and must comply with the announced rules concerning prior work, AI tools, open-source components and third-party resources.
6. 06Plagiarism, copied projects, fake evidence, manipulated timestamps, impersonation, fabricated information or misleading claims may result in immediate disqualification without refund.
7. 07Payment does not excuse a participant from any eligibility, conduct or submission requirement.

1. 01Round 1 and Round 2 outcomes are sent by email to every team that made a valid submission for that round, whether or not the team has been selected for the next round, at the address given at registration. Teams that qualify receive the instructions for the next round in the same email.
2. 02Results are announced in the official event group. That announcement carries the winning team names together with a link to the project each of them built. No participant’s personal details, and no further material from a team’s submission, are published or passed on unless that participant or team has given consent.
3. 03Every finalist team that takes part in Round 3 is ranked — not only the top three. The group announcement carries the top three team names only; each Round 3 finalist team is told its own position in the email that delivers its certificate, and the certificate prints it.
4. 04By entering, a team accepts that if it finishes in the top three its team name and a link to its submitted project may be published with the results — the GitHub repository for a hackathon judged on its code, or the live project URL where the event calls for a deployed product.
5. 05Individual scores, judging sheets, internal notes, comparative rankings and detailed scoring breakdowns will not be provided, and participants cannot demand personal feedback, re-evaluation, another presentation opportunity or comparison with another team.
6. 06Judges may consider the announced criteria together with originality, completion, eligibility, rule compliance and verification of claims.
7. 07The judges’ decision is final, except where the organisers identify a clear administrative error, conflict of interest, plagiarism, fraud or rule violation.
8. 08Payment does not influence judging and does not create a right to qualify or win.

1. 01Certificates are issued separately for completed rounds and are subject to all eligibility requirements.
2. 02Participants who made a valid Round 2 submission may receive a Round 2 Completion Certificate even if they later withdraw from Round 3.
3. 03Qualification for Round 3 alone does not create eligibility for a Final Round or Finalist Completion Certificate.
4. 04A Round 3 or Finalist Completion Certificate requires successful registration, payment and a valid final-round submission.
5. 05A team that pays but withdraws or fails to submit will not receive a Round 3 Completion Certificate.
6. 06Withdrawal from Round 3 does not cancel a Round 2 certificate already earned through valid participation.
7. 07Winner certificates will be issued only to the officially announced winning teams.
8. 08Certificates may be withheld for invalid submissions, false information, plagiarism, misconduct, disqualification or failure to complete mandatory requirements.

1. 01Rewards are subject to eligibility verification, sponsor approval and compliance with all event rules.
2. 02Internships, interviews, incubation, credits, subscriptions, merchandise and similar benefits are governed by the conditions announced for the event.
3. 03Non-cash rewards cannot ordinarily be exchanged for money.
4. 04Winners may be required to provide identity, project, eligibility or payment verification before receiving rewards.
5. 05Failure to provide verification within the stated period may result in forfeiture of the applicable reward.
6. 06We Code Coders will coordinate sponsored benefits but is not responsible for reasonable delays caused by sponsors, couriers, payment providers or external platforms.

1. 01We Code Coders may reasonably change schedules, round structures, submission methods, judging arrangements, communication channels or event tools when operationally necessary.
2. 02Where a communication channel, group or event tool is changed, the new link is sent by email to every registered participant at the address given during registration, and joining it is the participant’s own responsibility.
3. 03Missing an announcement because a new channel was not joined, or because the registered email address is wrong or unmonitored, is not a ground for an extension, a re-evaluation or a refund.
4. 04Reasonable changes will not automatically create a right to a refund.
5. 05Material changes will be announced through an official event channel.
6. 06The organisers may extend a deadline, reopen submissions or provide an alternative method when a widespread organiser-controlled platform failure occurs.
7. 07Participants cannot demand an extension for individual internet, device, electricity, software or availability problems.
8. 08Participants are responsible for monitoring official announcements and maintaining correct contact information.

1. 01Participants must communicate respectfully with organisers, judges, volunteers, sponsors and other participants.
2. 02A participation fee covers the cost of running the event. It does not buy the organisers, their time or their attention, and it does not entitle anyone to priority treatment, instant replies or special consideration.
3. 03Allow 24 hours for a reply to a genuine query raised through the official support channel. Repeated messages, tagging, calling or escalating inside that window will not produce a faster answer.
4. 04Threats, harassment, abusive language, discrimination, spam, impersonation, deliberate disruption or disclosure of another person’s private information may result in removal or disqualification without refund.
5. 05Participants must not ask an organiser, judge or volunteer to break a rule, waive a requirement, extend a deadline outside the published process or make an exception in their favour. A question may be asked once; a decision, once given, is not reopened by repeating the request.
6. 06Pressure, force, coercion, intimidation or threats directed at an organiser, judge, volunteer or sponsor disqualify the entire team, not only the individual responsible. Where an organiser, judge or volunteer reports feeling threatened, the team is removed from the event without refund.
7. 07Genuine questions and complaints must be submitted through the official support channel.
8. 08Messages sent to personal accounts, unrelated groups or unofficial contacts may not be treated as formal complaints.
9. 09Participants must not publish knowingly false statements or manipulated evidence concerning the event, organisers, judges or sponsors.
10. 10Nothing prevents a participant from raising an honest complaint, reporting misconduct or exercising a lawful right.

1. 01Teams retain ownership of their original projects unless separate written terms state otherwise.
2. 02Participants permit We Code Coders to display their team name, participant names, project title, project description, screenshots, demo material and results for event administration and promotion.
3. 03Private repositories or confidential source code will not be publicly shared without permission, although private access may be required for judging and verification.
4. 04Teams must possess the necessary rights to all code, designs, datasets, media, trademarks and other materials used in their submissions.

Participant information may be processed for registration, payment verification, communication, judging, certificates, rewards, fraud prevention and event administration. Relevant information may be shared with judges, sponsors, payment providers or service partners only where reasonably necessary for these purposes.

By clicking the payment or registration button and completing payment, the team leader confirms that: