Community Guidelines and Copyright Complaints

    Last updated: 4 September 2026

    Part A: Community Guidelines

    The Hacker Blueprint Discord server is where students help each other, get unstuck on labs, and talk to the creator directly. These rules keep it useful and safe. They apply on Discord and anywhere else we host a community. They sit alongside Discord's own Terms and Community Guidelines and our Acceptable Use Policy.

    1. Be decent

    Treat people with respect. No harassment, hate speech, threats, discrimination, doxxing or sexual content. Disagree with ideas, not people. If someone is new and asking a basic question, remember that you were new once.

    2. Keep it legal and ethical

    • Do not ask for or offer help attacking systems you are not authorised to test. "It's my friend's network" is not authorisation.
    • Do not share, request or discuss actual certification exam content, including exam machine names, questions, or solutions. This gets people banned from their exams and gets us in trouble. Independent practice material is fine; leaked exam material is not.
    • Do not post malware, stolen credentials, leaked data, or links to them.
    • Do not post anything that would break the Acceptable Use Policy.

    3. Respect the content

    Paid content stays paid. Do not share course videos, notes, lab files, or account access, in the server or anywhere else, and do not ask others to. Sharing your own write-ups of free labs is welcome. Full solutions to paid chains should not be posted publicly; ask in the appropriate channel if unsure.

    4. No spam, scams or self-promotion without asking

    No unsolicited advertising, referral links, crypto schemes or DMs pitching services. If you have built something the community would find useful, ask a moderator before posting it.

    5. Use the right channels

    Read pinned messages. Ask lab questions in the lab channels. Do not ping the creator or moderators for things that can wait. Use spoiler tags for hints and solutions.

    6. Privacy

    Do not share other people's personal information. Do not screenshot private conversations and post them without consent. What is said in DMs stays in DMs.

    7. Enforcement

    Moderators may delete messages, mute, kick or ban at their discretion, with a warning first where that makes sense and without one for serious breaches. Bans for sharing paid content, leaking exam material, or attacking unauthorised systems are permanent and forfeit any refund. If you think a moderation decision was wrong, email hacking.academy@protonmail.com and we will review it.

    8. Reporting

    Report rule-breaking to a moderator on Discord or by email. We keep reporter identities confidential where possible.

    Part B: Copyright Complaints and Takedown Procedure

    We respect intellectual property and expect the same from our users. This procedure is modelled on the notice-and-takedown process in the US Digital Millennium Copyright Act (DMCA) and applies to content on hackerblueprint.com and in communities we run. It also applies if you believe our content is being redistributed without permission and want to tell us.

    1. Reporting infringement on our Site or community

    If you believe that material we host or that a community member posted infringes your copyright, send a notice to hacking.academy@protonmail.com with the subject "Copyright notice" containing:

    1. your name, address, phone number and email;
    2. identification of the copyrighted work you say is infringed;
    3. the exact location of the material (URL, channel and message link, or file name) so we can find it;
    4. a statement that you have a good-faith belief the use is not authorised by the copyright owner, its agent, or the law;
    5. a statement, under penalty of perjury, that the information in the notice is accurate and that you are the copyright owner or authorised to act for the owner;
    6. your physical or electronic signature.

    We will remove or disable access to the material promptly after receiving a complete notice, and notify the person who posted it where we can.

    2. Counter-notice

    If your material was removed and you believe that was a mistake or a misidentification, send a counter-notice to the same address containing your contact details, identification of the removed material and where it appeared, a statement under penalty of perjury that you have a good-faith belief it was removed by mistake or misidentification, your consent to the jurisdiction of the courts in your place of residence, and your signature. We may restore the material after 10 business days unless the complainant tells us they have filed a court action.

    3. Repeat infringers

    We end the access of users who repeatedly infringe copyright.

    4. Misuse of this process

    Knowingly making a false claim of infringement or a false counter-notice can make you liable for damages. Please be sure before you send one.

    5. Reporting piracy of Hacker Blueprint content

    If you find our videos, notes or labs being shared without permission, we would be grateful for an email with the link. Reports are confidential.

    Hacker Blueprint

    Hands-on certification prep, trusted by certified hackers around the world.

    Want new labs and discount codes first?

    We'll email you when a new lab drops or a sale goes live.

    Your email is safe with us. We don't spam.

    © 2026 Hacker Blueprint. All rights reserved.

    Built for hackers, by hackers.

    OSCP® and OSCP+™ are trademarks of OffSec. Hacker Blueprint is an independent training provider and is not affiliated with, endorsed by, or sponsored by OffSec. All content is our own original material and contains no OffSec course, lab, or exam content. Individual results vary: passing any exam depends on your own study and practice. * Lifetime access and lifetime updates run for as long as Hacker Blueprint operates, with no renewal and no extra charge.