Acceptable Use Policy

These rules define what can and cannot be done with Proxynade servers, proxies, tickets, and related infrastructure. The goal is simple: lawful use, low abuse, and safe service operations.

Last updated: 2026-04-23 Applies to: servers, proxies, dashboard tools Abuse contact: abuse@proxynade.net

Plain-English summary

Do not use Proxynade for malware, spam, fraud, or credential attacks.
Do not attack third parties or bypass Proxynade safeguards.
Warnings can be skipped for severe abuse or legal risk.
Report abuse to abuse@proxynade.net with evidence and timestamps.

1. Baseline rule

Use the service lawfully, honestly, and in a way that does not damage Proxynade, platform systems, third-party services, or other users. If a use case creates abuse complaints, high legal risk, or operational instability, it can be restricted or removed.

2. Common violation examples

Sending phishing pages, credential traps, or account takeover traffic.
Running brute-force logins, credential stuffing, or unauthorized scanners.
Hosting malware, loaders, botnets, or remote access trojans.
Using servers or proxies for bulk spam, DDoS traffic, or payment fraud.
Using tickets, email, or support channels to harass staff or third parties.

3. Strictly prohibited activity

Malware, loaders, botnets, or remote access trojans.
DDoS activity, stress attacks, or unauthorized scanning.
Spam, unsolicited bulk messaging, or mail abuse.
Phishing, credential theft, or social engineering.
Credential stuffing, brute force, or account takeover activity.
Carding, payment fraud, or money laundering.
Harassment, stalking, doxxing, or targeted abuse.
Any illegal content or unlawful operation.

4. Proxy and server specific restrictions

Do not use the service to break another platform's account security.
Do not resell access if that use would increase abuse or complaint volume.
Do not run abusive automation against public or private targets.
Do not bypass monitoring, rate limits, or other service safeguards.
Do not deliberately overload protected targets or the Proxynade dashboard.

5. Resource and network protection

Proxynade may apply stock limits, concurrency limits, protocol restrictions, token quarantine, temporary holds, or service pauses to protect the platform. Those controls are part of the service and may change without notice when abuse or instability requires it.

6. Enforcement ladder

Warning or support contact.
Feature restriction or rate limit.
Order cancellation, token unassignment, or manual review.
Account suspension or deletion.
Registration ban and external abuse escalation.

Severe cases: malware, fraud, active credential attacks, and infrastructure abuse can trigger immediate suspension without a warning.

7. Reporting abuse

Send abuse reports to abuse@proxynade.net. Include timestamps, target hosts, order references, and evidence where possible. Reports without useful detail may be impossible to investigate. Service issues should go through the dashboard ticket flow instead.

8. Policy updates

This policy may change when abuse trends, operational requirements, or service features change. The current version is the version published on this page.