Code of Conduct & Culture
We built InnoSprint 2.0 so student developers can collaborate, experiment, and build cool projects safely. Here is how we ensure our campus remains welcoming for everyone.
Our Pledge to Every Hacker
We pledge to make participation in InnoSprint 2.0 a harassment-free, empowering experience for everyone—regardless of age, body size, disability, ethnicity, gender identity and expression, level of programming experience, nationality, race, religion, or sexual orientation.
This policy applies to all official physical spaces at CGC University (hacking arenas, stage halls, cafeteria, resting zones) and digital channels (Discord server, Devfolio portal, WhatsApp updates, and social media mentions).
Expected vs Unacceptable Behavior
What We Love To See
- ✓Use welcoming, inclusive, and friendly language across all chats and hacking bays
- ✓Be patient and helpful with first-time hackers and cross-domain builders
- ✓Respect differing technical opinions, design choices, and personal boundaries
- ✓Accept constructive critique gracefully and keep team feedback positive
- ✓Look out for your fellow hackers—share coffee, power strips, and encouragement
Zero Tolerance Policy
- ✗Sexualized comments, jokes, imagery, or unwelcome physical or verbal advances
- ✗Discriminatory insults based on gender, identity, race, disability, or experience
- ✗Trolling, targeted harassment, deliberate intimidation, or online/offline stalking
- ✗Photographing or recording anyone who has asked not to be filmed
- ✗Publishing private personal information (doxxing) without explicit consent
- ✗Sustained disruption of workshops, sponsor talks, mentorship rounds, or pitches
Media & Photography Opt-Out
While media teams will capture event photos and stage demos, every hacker has the absolute right to opt out of being photographed or recorded.
Red Lanyard Rule
Prefer not to be on camera? Ask for a Red Lanyard at check-in. Our official media crew will automatically bypass anyone wearing a Red Lanyard during roving photography.
* Flash photography is strictly forbidden inside sleeping bays and quiet rest areas.
Code Originality
All hackathon submissions must be built during the official 24-hour sprint. Open-source libraries and APIs are completely fine, but core application logic must be written on-site. Declare any pre-existing code upfront in your GitHub README to avoid disqualification.
100% Project IP Rights
You own everything you create. Neither D4 Community nor CGC University claims any ownership, equity, or licensing rights over your code, design assets, or business ideas. Your project remains entirely yours.
What Happens When You Report?
If you experience unacceptable behavior or feel unsafe, we take action immediately. Here is our transparent 3-step incident protocol:
Reach Out Immediately
Find any organizer in a D4 Community staff hoodie, visit the Helpdesk in the main lobby, or call our direct helpline.
Private & Safe Discussion
We will listen in a quiet, private room. Your report will be kept strictly confidential among core leadership.
Decisive Action
Organizers will investigate and take immediate corrective measures, up to campus removal or law enforcement contact.
Enforcement Actions
Participants asked to stop unacceptable behavior are expected to comply immediately. Violators may face formal warnings, removal from judging, permanent expulsion from CGC University campus without reimbursement, or local law enforcement involvement.
Need Immediate Assistance?
Our organizing team and campus safety officers are stationed 24 hours in the main atrium. Feel free to reach out directly: