Zing Hackathon Rules and Regulations

Event name: Zing Hackathon Organizer: SkillGlider Last updated: 11 Sep 2026

1. Scope and participation

These rules describe the requirements for registering, completing assessments, submitting projects, and participating in the Zing Hackathon.

Participants must read these rules together with the published eligibility criteria, event schedule, assessment instructions, submission requirements, and judging criteria.

If any instructions appear inconsistent or unclear, participants should request clarification through the official organizer channel.

2. Eligibility and registration accuracy

Participants must satisfy the eligibility requirements published by the organizers, including any applicable institution, enrollment, age, or location requirements.

Participants must:

Provide accurate and current registration information.
Use their own identity and avoid impersonating another person.
Provide truthful institution and enrollment details where requested.
Maintain an active email address and other required contact information.
Correct inaccurate information promptly through the available registration or support process.
Provide eligibility verification when requested under the published verification process.

Submitting a registration does not confirm eligibility where organizer verification is required.

3. Team formation and responsibilities

Teams must comply with the published minimum and maximum team sizes.

Each team must appoint a primary contact or team leader responsible for official communication, coordinating submissions, and maintaining required access permissions.

Team members should agree on their respective responsibilities and ensure that every listed member has consented to being included.

Any restrictions on participating in multiple teams, changing members, replacing members, or transferring team leadership must be published by the organizers. Teams must follow the applicable process and deadlines for such changes.

4. Problem statement

Each team is responsible for selecting and explaining its own problem statement.

The submission should clearly describe:

The problem being addressed.
The people or organizations affected.
The significance of the problem.
The proposed solution and intended benefits.
Any important assumptions, dependencies, or limitations.

Where organizers publish themes, tracks, or scope restrictions, the selected problem must comply with those requirements.

Teams must accurately describe the capabilities and development status of their solution.

5. Original work and third-party materials

Teams must submit work they created or are authorized to use.

Third-party code, libraries, datasets, designs, images, audio, video, templates, and other materials must be used in accordance with their applicable licenses and permissions.

Teams must:

Credit third-party contributions appropriately.
Identify pre-existing components and explain the work completed for the hackathon.
Avoid presenting another person’s work as their own.
Retain any license notices or attribution required by the materials they use.
Accurately describe contributions made by team members and external contributors.

Any requirements concerning development during the event, reuse of previous projects, or submissions to other competitions must be published before they apply.

6. Artificial intelligence and external assistance

The organizers must publish the permitted scope of AI tools, external assistance, and collaboration for each event stage.

Assessment rules may differ from project-development rules. Participants must follow the instructions applicable to the specific activity.

Where disclosure is required, teams must identify the tools or assistance used and explain their contribution to the submitted work.

Teams remain responsible for checking the accuracy, functionality, attribution, and permitted use of all submitted content, including AI-generated content.

Organizer confirmation required: Allowed tools, prohibited uses, disclosure requirements, and stage-specific restrictions.

7. Assessment conduct

Participants must follow the published assessment instructions, including requirements relating to timing, identity verification, permitted resources, collaboration, and technical setup.

Participants must not:

Impersonate another participant or have another person complete an assessment on their behalf.
Obtain or provide assistance prohibited by the assessment instructions.
Share restricted assessment questions, answers, or access credentials.
Attempt to access another participant’s assessment or responses.
Interfere with the assessment platform or another participant’s work.

Technical problems should be reported promptly through the official support channel. Retakes, extensions, and accommodations are subject to the published organizer process.

8. Project submission requirements

Each team must place all required submission materials in its designated public Google Drive folder.

The folder must use the naming convention and access settings specified by the organizers. Teams must verify that reviewers can open the folder and access its required contents without requesting permission.

The organizers must publish the final submission checklist, which may include:

Project title and team details.
Problem statement and solution summary.
Presentation or project report.
Demonstration video.
Source-code repository or code archive.
Working prototype or deployment link.
Setup and usage instructions.
Third-party acknowledgments and required AI-use disclosures.

Teams must test all links before submitting. Passwords, API keys, private credentials, confidential information, and personal information that is not intended for public disclosure must not be placed in the public folder.

Submission is complete only when the team has followed the published submission process, including registering the folder link through the designated form or dashboard where required.

9. Deadlines and submission updates

Participants must follow all published registration, assessment, submission, and presentation deadlines. The official event time zone applies to these deadlines.

Organizers must specify whether submitted materials may be changed before or after the submission deadline and how the version used for judging will be identified.

Teams must maintain the required access permissions for the published review period.

Late submissions, inaccessible files, replacement links, and requests for deadline extensions will be handled under the published policy. Participants should not assume that an extension has been granted unless the organizers confirm it through an official channel.

10. Evaluation and judging

Projects will be evaluated using the criteria published by the organizers.

The organizers must confirm the criteria, any scoring weights, assessment stages, presentation requirements, and tie-breaking process before judging begins.

Reviewers may request clarification or a demonstration of submitted work. Teams must respond accurately and must not misrepresent results, features, testing, users, or performance.

Any process for handling reviewer conflicts of interest, score corrections, or judging-related concerns must be published by the organizers.

11. Respectful participation

Participants must treat other participants, reviewers, mentors, volunteers, and organizers respectfully.

Prohibited conduct includes:

Harassment, bullying, threats, or discriminatory abuse.
Sharing another person’s private information without authorization.
Deliberately disrupting event activities or communication channels.
Tampering with another team’s work or submission.
Attempting to gain unauthorized access to accounts, systems, or files.
Attempting to improperly influence reviewers or organizers.

Concerns should be reported through the designated organizer channel with relevant supporting information.

12. Communication and support

Participants must keep their contact information current and regularly check the event dashboard, registered email account, and official announcement channels.

The organizers must identify the official channels used for deadlines, rule changes, results, and support.

Teams should include their team name or registration identifier when contacting support. Unofficial messages should be verified through an official channel when they concern event requirements or decisions.

13. Review of potential violations

Organizers may review concerns relating to eligibility, assessment conduct, submission authenticity, permissions, or participant behavior.

Reports should describe the concern clearly and include relevant evidence where available. Participants involved in a review should preserve relevant materials and cooperate with reasonable clarification requests.

The final rules must explain the review process, how affected participants can respond, who makes decisions, and how outcomes are communicated.

Organizer confirmation required: Grounds and procedures for warnings, corrective action, submission rejection, disqualification, or other consequences. This draft does not establish automatic penalties.

14. Clarifications, complaints, and appeals

Participants may request clarification or report concerns through the published organizer process.

Requests should include the team or participant identifier, the relevant event stage, a clear explanation, and supporting information where applicable.

Organizer confirmation required: Whether appeals are available, which decisions may be appealed, submission deadlines, the reviewing authority, and the expected response process.

15. Ownership, publicity, and information handling

Teams must ensure they have permission to submit their materials and make required materials publicly accessible.

Before collecting submissions, organizers must publish any terms covering project ownership, permission to display or promote submissions, event recordings, and use of participant names or images.

Organizers must also provide the applicable privacy information explaining how registration details, assessment information, and other participant data will be handled.

Organizer confirmation required: Ownership terms, organizer usage permissions, publicity terms, privacy notice, and any retention requirements.

16. Prizes and recognition

If prizes, certificates, or other benefits are offered, organizers must publish the applicable eligibility conditions, award categories, verification requirements, and distribution arrangements.

Any conditions concerning prize allocation among team members, substitutions, or unclaimed awards must be stated in the final terms.

17. Changes and organizer-configurable conditions

Organizers must publish any additional conditions before they take effect and clearly communicate material changes through official channels.

Each update should identify its publication date, effective date, and the participants or event stages affected.

Unconfirmed conditions—including AI-use restrictions, disqualification procedures, appeals, judging details, and post-submission updates—must not be presented as finalized rules until approved and published.

18. Participant acknowledgment

By completing the published acceptance process for the final rules, participants acknowledge that they have read the applicable event requirements and agree to follow them.

This draft is intended for review and completion. It must not be presented as legally approved or as the final participation agreement.