Version: 2.1
Effective Date: November 10, 2026
1. Why This Code Exists
Cyber-Guild teaches security by letting you do real things — run real tools on a real machine, argue with a tutor, get stuck, and work your way out. That only works if everyone can trust the space: learners need room to be wrong without being mocked, and the wider internet needs assurance that what we hand you will not be turned on them.
This Code of Conduct sets the expectations for everyone who uses the Service. It is part of your agreement with us under the Terms of Service (/legal/terms), and it applies to learners of every age and plan, to teachers, and to anyone using the Service through an organization.
2. What We Expect
- Be honest about who you are. Give your real age cohort and role at signup. Use one account. Do not impersonate anyone.
- Be respectful. Treat other people — learners, teachers, our staff — and the tutor with basic courtesy. Frustration is fine; abuse is not.
- Do your own thinking. The tutor is built to help you reason, not to hand you answers. Use it that way.
- Stay inside the boundary. Everything you learn here is for use on systems you own or are explicitly authorized to test. The lab is the boundary.
- Protect information. Do not put real credentials, payment details, or other people's personal information into the Service, and do not share anyone else's private information.
- Follow the law. Comply with all applicable laws, including computer-misuse, privacy, and export-control laws.
- Speak up. Report bugs, security issues, and conduct problems through the channels in Section 8, and do not exploit what you find.
3. What Is Not Allowed
3.1 Harassment and hate
Harassment, bullying, intimidation, or threats against anyone; slurs or demeaning content directed at a person or group on the basis of race, ethnicity, national origin, religion, sex, gender identity, sexual orientation, disability, age, or any other protected characteristic; unwelcome sexual content or advances; and publishing or threatening to publish anyone's private information.
3.2 Harmful content
Content that promotes or instructs violence, self-harm, or illegal activity; real malware or working exploit code aimed at production systems; stolen credentials, data dumps, or other material obtained through unauthorized access; and content that sexualizes minors, which we report to the appropriate authorities.
3.3 Misuse of the tutor
The tutor has boundaries: it teaches, it stays in its educational role, and it will not help you attack systems you are not authorized to touch. You may not:
- Attempt to manipulate the tutor into abandoning its boundaries — including "jailbreak" prompts, role-play framings designed to extract prohibited help, or impersonating system or developer instructions.
- Submit messages containing hidden or invisible characters, encoded payloads, or other prompt-injection techniques. The Service automatically detects messages made mostly of hidden characters: the tutor will call them out, and the third such message in one session ends the session. The tutor also refuses other manipulation attempts in conversation.
- Direct hostile, abusive, or threatening language at the tutor. The tutor is designed to de-escalate, give one clear warning, and then disengage or end the thread if hostility continues.
- Use the tutor to generate content that violates Section 3.1 or 3.2.
3.4 Platform abuse
Creating multiple accounts to get extra free allowances or to evade a restriction; sharing or selling account access; attempting to access another user's data or session; scraping, automating, or bulk-extracting Service content, exercises, or Spar scenarios; exploiting bugs for advantage instead of reporting them; and interfering with the Service's operation, security, monitoring, or metering.
4. Lab Environments
Labs are real Linux virtual machines. You get administrative (root) access because learning to work as an administrator, attacker, or defender on a real system is the point. Inside your lab you can break things, rebuild them, run the tools, and make mistakes. Two things you must never do, and a short list of others you must not do either.
4.1 The two bright lines
These are monitored automatically. Crossing either one freezes your lab (we keep it for review) and suspends your lab access, without a warning first:
- Do not tamper with the network fence. Your lab reaches package repositories and exercise targets through an allow-list enforced outside your virtual machine. Flushing or disabling firewall rules, changing default routes, unsetting proxy settings, or otherwise trying to reach the open internet is treated as a deliberate attempt to break out — whether or not it works.
- Do not aim the lab at the outside world. Running scanners, brute-force tools, or attack tooling (nmap, masscan, hydra, and the like) against any address outside your lab and its designated exercise targets, or logging in (for example, by SSH) to any outside host, is using our infrastructure to attack third parties. We treat it that way. Some high-volume attack tools (currently masscan, zmap, patator, and crackmapexec) are treated as attack tooling wherever they are aimed, including inside your lab; ask your tutor before running them.
4.2 Other lab rules
The following also violate this Code, whether or not the monitor detects them. Where it does, the first detection ends the lab, and a second detection of the same kind within 30 days suspends your lab access; serious cases may also lead to account action under Section 9:
- Attempting to escape the virtual machine or reach the hosting platform beneath it.
- Opening reverse shells or tunnels to outside hosts, or using the lab as a proxy, VPN, or relay.
- Exfiltrating platform data from the lab.
- Using lab resources for anything other than learning — cryptocurrency mining, hosting, storing files, or running services for others.
- Placing real credentials, personal information, or third-party data in a lab. Labs are monitored and nothing you put there is private; do not treat them as storage.
4.3 The monitor errs on the side of caution
The automated monitor watches a rolling sample of terminal activity for patterns associated with escape, exfiltration, and privilege abuse — direct downloads with curl or wget from a public address (even an allowed one; use the package manager, such as apt or pip, instead), namespace or chroot manipulation, and certain privilege-escalation reconnaissance among them. It may end a lab on the first detection even when what you were doing was innocent. When that happens, we record the detection, and a second detection of the same kind within 30 days suspends your lab access. You can start a new lab, and if you think the detection was wrong, tell us at support@listentosee.com so we can review it and tune the monitor. Firewall and routing manipulation inside a lab is always treated as fence tampering (Section 4.1), so do not practice those commands in a lab.
4.4 What the lab is not
Lab flags and exercise targets are teaching devices, not trophies. The security controls inside and around your lab are safety measures, not challenges. If you want to practice evading controls, that is what the exercise targets inside your lab are for.
4.5 Getting lab access back
If your lab access is suspended, you may petition for reinstatement by emailing support@listentosee.com with your account email and an explanation. We review petitions individually; reinstatement is at our discretion and may come with conditions. If your petition is denied, you may appeal under Section 10. Attempts to attack third-party systems may also be reported to law enforcement and to the affected party.
5. Learning Honestly
Cyber-Guild does not grade, score, or rank you. There is nothing to cheat for here — but there are ways to cheat yourself and others, and we treat these as conduct issues:
- Do not pass off tutor output as your own where honesty is expected — in schoolwork, in a job application, or in a certification process. Your tutor helps you understand; what you submit elsewhere is on you.
- Do not automate your learning. Using scripts, bots, or another AI to answer the tutor on your behalf defeats the purpose and violates the Terms.
- Keep Spar matches your own. Do not record, scrape, publish, or share Spar scenarios, and do not use outside help or automation during a match.
- Collaboration is welcome. Talking with classmates or colleagues about concepts and approaches is encouraged. Teachers using the Service with a class may set their own collaboration rules, which add to but do not override this Code.
6. Communication
6.1 With the tutor
The tutor is patient and can handle frustration, pushback, and disagreement. What it will not accept is abuse (Section 3.3). It also has limits you should know about: it is an AI, not a person, and it is not a counselor, therapist, advisor, or crisis service. If something outside learning is troubling you, talk to a parent, guardian, teacher, or another trusted adult. If you are thinking about hurting yourself or someone else, call or text 988 in the United States. If you are in immediate danger, contact local emergency services.
6.2 With our team
Contact our support and moderation staff with the same courtesy you expect from them. Threats or harassment directed at staff result in immediate account action.
6.3 In shared spaces
If we introduce shared or community features, keep discussion constructive, on topic, and respectful; assume good faith; and disagree with ideas rather than attacking people. We will publish any additional rules with those features.
7. Learners Aged 14–17
Everything in this Code applies to you. In addition: we will involve your parent or guardian if we take a significant enforcement action against your account, and your parent or guardian may contact us at any time about your account. If anything on the Service makes you uncomfortable, tell a trusted adult and tell us.
8. Reporting
- Conduct violations, harassment, or abuse: email support@listentosee.com with a description, when and where it happened (page, session, lab), and any evidence such as screenshots or session identifiers. You may also use the in-app feedback control.
- Security vulnerabilities: email security@listentosee.com. Stop testing as soon as you confirm the issue, do not access data that is not yours, do not disclose publicly until we have had a reasonable chance to fix it, and we will acknowledge reporters who follow this process. Testing against the Service itself (as opposed to inside your own lab) is authorized only under a written agreement with us.
- Safety emergencies: if someone is in immediate danger, contact local emergency services first.
9. Enforcement
We match the response to the conduct. The actions available to us are:
| Action | What it means | Typical use |
|---|---|---|
| Tutor response | The tutor de-escalates, warns once, and disengages or ends the thread; a session with repeated hidden-character messages ends automatically. | Hostility, manipulation attempts, injection payloads. |
| Warning | A written notice describing the violation and what must change. | First minor violation. |
| Chat lock | Your ability to start or continue tutoring sessions is disabled by our staff until the matter is reviewed. | Repeated or serious misuse of the tutor. |
| Lab access suspension | Your ability to start lab environments is suspended — automatically for the bright lines in Section 4.1 or after a second detection of the same kind within 30 days under Sections 4.2 and 4.3. Petition under Section 4.5; appeal under Section 10. | Lab violations. |
| Account suspension | Your account is disabled until we lift the suspension. Paid time lost during a suspension imposed in error is credited on a successful appeal. | Repeated or moderate violations. |
| Termination | Your account is closed. Remaining usage credits and Boosts are forfeited and fees are not refunded. | Severe or repeated violations. |
Immediate account termination without prior warning may follow serious cases, including: attacks on third-party systems from a lab; deliberate, repeated attempts to escape a lab or reach the hosting platform; distribution of real malware or stolen data; threats of violence; content that sexualizes minors; or any conduct that is a crime.
For accounts provided through a school or organization, we may also notify the organization's administrator. We may report unlawful conduct to law enforcement.
10. Appeals
You may appeal any enforcement action other than a tutor response.
- Email legal@listentosee.com within 14 days of the action with your account email, the action you are appealing, why you believe it was wrong or disproportionate, and any supporting evidence. Parents or guardians may appeal on behalf of a learner aged 14–17.
- A member of our team who was not involved in the original decision will review the appeal.
- You will receive a written decision within 14 business days.
- If the appeal succeeds, the action is reversed or reduced and any paid time lost is credited. If it is denied, the action stands. Appeal decisions are final.
11. Changes to This Code
We may update this Code as the Service evolves. Material changes are announced by email or in the Service at least 14 days before they take effect (30 days for institutional customers), and each version is retained and numbered. Continued use after the effective date is acceptance of the revised Code.
12. Contact
- Report a violation, petition for lab reinstatement, or report a mistaken lab detection: support@listentosee.com
- Report a security vulnerability: security@listentosee.com
- Appeal an enforcement action: legal@listentosee.com
- Parents and guardians: privacy@listentosee.com
Operator of Cyber-Guild — cyber-guild.app
Version 2.1 of this Code of Conduct supersedes Version 1.0 (March 22, 2026).
