Entering the Corrusal hackathon constitutes a legally binding agreement to these terms. Read them completely. Ignorance of these terms does not prevent disqualification.
The event operates on a strict three-week timeline from February 7, 2027, to February 28, 2027. Deadlines are absolute. Late submissions receive zero consideration. System clocks dictate time limits. Organizers reserve the right to alter the schedule, venue capacity, or evaluation metrics in response to unforeseen logistical constraints. All registered teams will receive notifications regarding any systemic changes via the official communication channel.
Registration closes on February 7 at 23:59. Teams must submit a precise problem statement and proposed solution architecture. Organizers analyze submissions for originality and technical feasibility. Duplicate concepts are filtered. Selected teams undergo a mandatory online interview. Failure to attend the interview results in immediate rejection. Round 01 concludes on February 14 at 18:00.
Shortlisted teams advance to a remote code review phase. Teams must push code to a public GitHub repository. Organizers evaluate commit history, presentations, system architecture, and code quality. Teams attend a secondary interview to defend their technical choices and outline future deployment plans. Round 02 concludes on February 21 at 18:00.
Top teams advance to the physical venue in Nagpur, Maharashtra. Teams must arrive for check-in on February 28 at 10:00. Remote participation in Round 03 is prohibited. Live project showcases and sweep-level jury reviews begin at 12:00. Teams must demonstrate functional, deployed code.
The total prize pool is divided between the top two teams. The winning team receives ₹20,000. The runner-up receives ₹8,000. Prize distribution occurs on February 28 at 16:00. Payments are processed via UPI or direct bank transfer to the designated team leader. The team leader is solely responsible for distributing funds among team members. Organizers hold no liability for internal team financial disputes. Payments are subject to verification of identity and enrollment status.
Organizers require valid university identification (only valid for enrolled students not for others and working professionals) during Round 03 check-in. Fraudulent identification results in permanent bans from all future Corrusal events. Teams consist of two to four members. Solo participation is not allowed.
Teams retain full ownership of their intellectual property and source code. By submitting a project, teams grant Corrusal organizers a perpetual, royalty-free license to use project names, descriptions, screenshots, and repository links for promotional and archival purposes. Code must not infringe on third-party patents or copyrights.
The jury evaluates projects based on four rigid metrics: execution complexity, practical utility, code efficiency, and interface compliance. Interface design must strictly adhere to the monochrome styling constraints provided. Any deviation from the raw grid system results in point deductions.
Organizers do not provide travel, accommodation, or hardware stipends. Teams are responsible for their own laptops, peripherals, and travel costs to the Nagpur venue.
The Nagpur physical node operates under strict security protocols. Access is restricted to verified participants, mentors, and jury members. Unauthorized individuals will be removed. Participants must wear their designated badges (if provided) at all times within the venue perimeter. Organizers hold no liability for external server outages, API rate limits, or deployment platform failures. Teams must design their systems to handle external API failures gracefully. Code freezes are enforced regardless of external service status.
Any form of harassment, physical altercation, or verbal abuse at the venue results in police involvement and immediate expulsion. Code plagiarism, defined as submitting copied code without attribution or relying entirely on AI-generated boilerplate without custom logic, triggers instant disqualification.
Organizers collect personal data including names, email addresses, phone numbers, and university affiliations. This data is strictly used for hackathon logistics, identity verification, and prize distribution. Data is not sold to third parties. By registering, participants consent to this data processing.
These terms are governed by the laws of Maharashtra, India. Any disputes arising from this agreement will be subject to the exclusive jurisdiction of the courts in Nagpur.