Code of Conduct

DevLinkHub is built for people who want to Build. Connect. Grow.

We want DevLinkHub to be a place where students, developers, founders, creators, mentors, organizers, and technology enthusiasts can learn, collaborate, experiment, and build meaningful things together.

This Code of Conduct applies to everyone participating in DevLinkHub activities—including community members, event participants, organizers, volunteers, mentors, speakers, judges, partners, and guests.

The following behaviors trigger immediate disciplinary review or bans:

• Harassment: Repeated unwanted contact, intimidation, sexual harassment, unwanted romantic attention, deliberate humiliation.
• Bullying: Behavior intended to repeatedly intimidate, isolate, embarrass, or demean a community member.
• Hate & Discrimination: Hateful slurs, targeted dehumanizing language, or hostility targeting protected characteristics.
• Threats & Violence: Any threat of physical harm, violence, or stalking.
• Doxxing: Publishing or threatening to distribute private addresses, phone numbers, credentials, or private photos without authorization.
• Impersonation: Impersonating other members, staff, organizers, mentors, or sponsors.

DevLinkHub should not be used for abusive promotion or metric manipulation. Prohibited actions include repeated unsolicited advertising, mass DM broadcasting, referral spamming, fake accounts, or manipulating hackathon vote tallies.

Legitimate project showcases, sharing open-source repos, and asking for beta feedback in designated squad channels are always welcome.

As a tech community, we understand curiosity and reverse-engineering, but there is a clear distinction between security research and vandalism.

Do not launch DDoS attacks, exploit vulnerabilities maliciously, deploy malware, scrape private credentials, or interfere with event scoring servers. Responsible disclosures must be reported to hello.devlinkhub@gmail.com.

In hackathons, showcases, and challenges, builders must uphold strict academic integrity. Plagiarism, submitting pre-built closed commercial software as a 24-hour hackathon project without disclosure, fabricating dataset benchmarks, or cheating will result in immediate disqualification and revocation of certificates.

AI developer tooling (copilots, LLM APIs, code generators) is encouraged where permitted by event guidelines. However, you remain 100% accountable for the code and architecture you submit. Using AI does not excuse copyright infringement, hallucinations, or unverified claims.

Respect the copyright, patents, trademarks, and open-source licenses of other creators. Always include appropriate attribution (MIT, Apache 2.0, GPL) when incorporating external open-source libraries into your projects.

Content published in our resource vaults, tutorials, insights, and forum threads must remain constructive and technically sound. DevLinkHub moderators reserve the right to remove content that violates safety rules or presents security threats.

At physical campus hackathons and meetups, attendees must obey all campus security, fire safety codes, venue rules, and volunteer instructions. Disruptive behavior, property damage, or harassment at physical venues will result in immediate removal by venue staff.

Mentors and judges hold positions of trust. They must evaluate submissions objectively without favoritism. In turn, participants must treat judges and volunteers respectfully—disagreeing with a judging outcome is normal, but harassing judges is strictly prohibited.

Judges and mentors must recuse themselves from scoring projects built by close personal contacts, immediate family, or affiliated startups to safeguard competitive integrity.

If you experience or witness a violation, report it promptly via hello.devlinkhub@gmail.com. Please include details, timestamps, usernames, and screenshots. You do not need to investigate the matter yourself before reporting.

All reports are handled with the highest level of discretion. Information is restricted only to community safety officers required to investigate and resolve the incident.

DevLinkHub strictly prohibits retaliation against any individual who submits a good-faith report. Any retaliatory act will result in immediate and permanent removal from the community.

Our resolution process follows five structured stages:

1. Review the report and evidence immediately upon intake.
2. Contact the affected parties confidentially.
3. Gather supplemental logs, records, or witness statements.
4. Determine whether a policy violation occurred.
5. Enforce proportional, decisive corrective action.

Disciplinary actions scale with severity: informal warnings, formal written reprimands, content removal, event expulsion, hackathon disqualification, temporary squad mute, or permanent account termination.

Submitting knowingly fabricated reports to weaponize safety moderation against another member is considered a severe violation subject to disciplinary bans.

Maintainers reserve the right to take swift, proportional actions to protect participants, volunteers, digital infrastructure, and event venues from disruption.

This Code applies across DevLinkHub web portals, Discord servers, WhatsApp squads, GitHub repositories, in-person campus hackathons, workshops, and official ambassador communications.

Sanctioned members may submit an appeal containing verifiable evidence or context to hello.devlinkhub@gmail.com for review by a secondary panel.

This Code functions in full tandem with our Terms & Conditions and Privacy Policy.

Maintainers may update these standards as our global builder squads expand. Material changes will be published in official changelogs.