Acceptable Use Policy (AUP)
Effective Date: November 16, 2026 · Last Updated: November 16, 2026. Rules governing network conduct and resource utilization across Arizen Cloud (Parent: Arizen Tech).
Zero-Tolerance Standards
Arizen Cloud is dedicated to maintaining high-integrity compute infrastructure. Our platform operates zero-tolerance enforcement against malware distribution, network attacks, and malicious hacking. Accounts engaging in willful malicious acts will be immediately quarantined and terminated without refund.
1. Purpose and Scope
This Acceptable Use Policy (“AUP”) defines the acceptable standards of conduct for all users, bots, applications, and network traffic operating on Arizen Cloud hardware, VPS nodes, and Pterodactyl container allocations. This policy is incorporated by reference into our Terms of Service.
2. Prohibited Network & Security Activities
You may not use or permit your container to be used for any of the following activities:
Malware & Malicious Software
Hosting, executing, or distributing computer viruses, worms, trojan horses, ransomware, spyware, rootkits, or botnet command-and-control (C2) servers.
Network Attacks & Interference (DoS / DDoS)
Originating, amplifying, or relaying Denial of Service (DoS) or Distributed Denial of Service (DDoS) attacks, SYN floods, UDP amplification, or DNS reflection attacks against any target.
Unauthorized Probing & Scanning
Unauthorized port scanning, vulnerability scanning, network probing, IP spoofing, or attempts to breach or test the security of any system without explicit written authorization from the system owner.
Phishing, Fraud & Deception
Hosting deceptive web pages, fake login portals, credential harvesting campaigns, banking scams, or impersonating individuals or brands without authorization.
Cryptocurrency Mining
Executing cryptocurrency miners (e.g., XMRig, Monero miners, Bitcoin proof-of-work scripts) or blockchain verification tools designed to exhaust shared hardware compute cycles.
Unsolicited Messaging (Spam)
Operating mass automated email spammers, unauthorized scraping bots, open mail relays, or Discord user mass-DM marketing bots that violate Discord Terms of Service.
3. System & Resource Abuse
Customers must operate within allocated hardware boundaries:
- Container Jailbreaking: Any attempt to escape Docker container sandboxing, modify host cgroups, exploit Linux kernel vulnerabilities, or inspect processes belonging to other tenant containers is strictly prohibited.
- Storage Exhaustion: Filling host disks with temporary junk files, recursive disk-filling scripts, or unmanaged core dumps that endanger host operating stability.
- Network Flooding: Generating saturated continuous outbound network traffic intended to congest host node Gigabit/10G network interfaces.
4. Intellectual Property & DMCA Compliance
Arizen Cloud respects intellectual property rights and complies with copyright protection regulations.
- You may not use our hosting infrastructure to distribute copyrighted music, software, media, or proprietary source code without authentic authorization from the copyright holder.
- DMCA / Notice-and-Takedown: Valid notices of claimed copyright infringement should be submitted to
[email protected]containing the statutory notice elements (identification of copyrighted work, infringing material location, and declarant signature). - Upon receiving a verified takedown notice, we will notify the customer and may disable public access to the infringing material. Repeat infringers will face permanent termination.
5. Fair Abuse Reporting & Investigation Process
We believe in fair, transparent abuse investigations that distinguish between accidental misconfigurations and malicious intent:
Step 1: Incident Detection or Report: Abuse reports received at [email protected] or automated IDS/IPS alerts are triaged by our security operations desk within 12 hours.
Step 2: Threat Containment: If an active outbound attack (e.g., active DDoS or phishing) is detected, the container is immediately isolated/paused to prevent harm to external networks.
Step 3: Customer Notification & Remediation Window: For non-emergency or unintentional issues (e.g., compromised bot token or high memory leak), the customer is given a 24-hour remediation notice to patch their application.
Step 4: Dispute / False Positive Appeal: Customers who believe a suspension was made in error may submit an appeal ticket with log evidence to [email protected]. All appeals receive administrative human review.
6. Abuse Contact Information
To report network abuse, copyright infringement, phishing, or cybersecurity vulnerabilities originating from Arizen Cloud IP ranges (`89.106.84.0/24`):
Dedicated Abuse Desk: [email protected]
Security Operations: [email protected]
Legal & Administrative: [email protected]
Expected Triage Time: Emergency network security events are reviewed within 4 hours. General abuse inquiries within 24 hours.