Abuse
Abuse Policy
This policy explains how abuse reports, fraud investigations, network blocks, verification requirements, account restrictions, and service suspensions are handled.
Reportable abuse
Spam, malware, phishing, scanning, denial-of-service traffic, payment fraud, policy violations, resource abuse, compromised services, and illegal or harmful content may be reported for review.
Reports should include timestamps, IP addresses, URLs, logs, headers, screenshots where appropriate, transaction references where relevant, and a clear description of the harm.
Fraud department
The public fraud department email is shown on the abuse report page. If the form is unavailable, reports may be emailed directly to that address.
Do not send passwords, bank login details, card numbers, crypto private keys, seed phrases, or unrelated private files in an abuse report.
Investigation process
Admins may review abuse events, affected services, customer history, third-party notices, service usage indicators, security logs, bandwidth or scan indicators, payment risk, verification status, and previous restrictions.
IP addresses and user-agent data should be logged as hashes where practical. The platform must not log private RDP screen contents, user files, or typed desktop content while investigating.
Mitigation actions
Allowed actions include network block, service suspension, account hold, login block, purchase block, verification requirement, customer notice, support ticket, abuse case notes, fraud investigation referral, and case closure after remediation.
Admins may suspend, block, or terminate accounts according to severity, legal requirements, service requirements, payment fraud indicators, or repeated policy violations. Every action must be auditable.
Legal process and privacy
We do not sell abuse report or customer data. We only disclose customer data when needed to operate or protect the service, meet security or legal obligations, or respond to valid legal process such as a court order or subpoena.
Disclosure should be limited to the valid scope of the request, and secrets such as private operational tokens, service credentials, card data, banking passwords, private keys, and seed phrases must never be disclosed.
Appeals and restoration
Customers may contact support with remediation evidence. Admin may restore access, require verification, keep restrictions active, or terminate service according to severity and business policy.
Every abuse action should be auditable and should avoid exposing secrets or private operational credentials.