Acceptable Use Policy

1. Intended use

The Software is a defensive tool for hosts running Pterodactyl. It is intended to protect infrastructure you own or are authorised to administer, by watching for malware, unauthorised access, abuse and resource exhaustion. Using it for anything other than protecting infrastructure you are authorised to run is not permitted.

2. Prohibited uses

You must not use the Software, or a licence obtained with it, to:

2.1 Attack or probe third-party systems

• run DDoS, flood, amplification, reflection or booter tooling of any kind;
• run scanners, port sweepers, exploit kits, credential stuffing or proxy chains against systems you do not own;
• resell or broker access to attack traffic, proxies or botnet capacity;
• use the threat-intel sharing feature to spread fabricated indicators in order to block legitimate networks.

2.2 Distribute or host malicious code

• distribute ransomware, cryptominers, botnets, rootkits, web shells or reverse shells;
• operate a phishing panel, a loader, a keylogger or a command-and-control service;
• host files whose purpose is to compromise a host, including panel-bridge bridges and disk-bomb scripts.

2.3 Break the law

• any activity that violates applicable law, including unauthorised access, data theft, extortion or interference with a service;
• the hosting of content that is unlawful in your jurisdiction, including child sexual abuse material and content that infringes intellectual property rights.

2.4 Resell or redistribute

• sell, sub-licence, rent, lease or share a voucher or an activated copy;
• publish the binary, a voucher, or activation instructions in a public repository, forum, marketplace or tutorial;
• offer the Software as part of a managed hosting or security product to your own customers without a written agreement with us.

2.5 Abuse the Portal or its API

• enumerate or brute-force voucher codes, or probe the licence API beyond the rate limits;
• automate voucher checking through the public checker at scale;
• attempt to access or enumerate operator accounts, or bypass rate limits.

2.6 Circumvent the licence mechanism

• patch, patch around, or otherwise defeat licence validation, HMAC verification, node binding, revalidation or the three-attempt lockout;
• disable or remove the self-protection features, or interfere with the file-integrity and firewall behaviour the Software applies to your host;
• forge, proxy or relay validation responses on behalf of unlicensed copies.

3. Responsible operation

The Software deletes files, suspends game servers and manipulates your firewall with root privilege. You agree to:

• test it on a non-production host before relying on it for a production panel;
• review which paths are excluded from scanning and confirm they match your own policy;
• keep current backups, because the Software is designed to delete what it considers malicious and to kill processes it considers abusive;
• tune thresholds — memory limits, flood windows, block TTLs — to your workload before enabling enforcement;
• ensure the hosting you operate complies with the law and with your upstream provider’s acceptable use policy.

4. Reporting abuse we see

We review activation records for voucher enumeration and redistribution. Where we identify activity that indicates attack tooling is being operated under a licence issued through this Portal, we may revoke that licence and preserve the relevant records for law enforcement.

Reporting suspected abuse of our service or a licence: support@wildandev.tech. Please include the voucher code, the node hostname and whatever evidence you have. We will tell you what we can within the limits of the investigation.

5. Enforcement

Depending on severity, we may: issue a warning; restrict the voucher; suspend the node binding; or revoke the licence permanently without refund. Where a warning is issued first, you will be told what to correct and given a reasonable opportunity to do so, unless the activity is ongoing or causes harm to third parties.

As noted in the Licence Agreement, revocation takes effect at a running node’s next revalidation, which can be up to 24 hours later. We may also request that the node deactivate explicitly where the situation is urgent.

We will cooperate with competent authorities where we are legally required to. We will notify you of a lawful request unless prohibited from doing so.

6. Changes to this Policy

We may update this Policy. Material changes take effect on the stated effective date and apply to licences active at that time as well as new ones. Continuing to use the Software after that date constitutes acceptance.

7. Questions

If you believe this policy is being applied to you in error, or you want clarification before buying, ask first: support@wildandev.tech or the contact form.