Rules for lawful, stable, and non-abusive use of HostingCPU services.

Prohibited Activities

You may not use HostingCPU services to engage in unlawful activity, phishing, malware distribution, botnet activity, spam, denial-of-service activity, credential theft, copyright infringement, deceptive content, fraudulent storefronts, or distribution of content that violates law or third-party rights. This includes content or conduct involving terrorism, child sexual abuse material, unlawful obscene material, hate content prohibited by law, violent or abusive unlawful content, pirated software, warez, unauthorized streaming or mass media hosting, or unlawful handling of protected confidential information.

Security and Resource Abuse

You may not attempt unauthorized access, privilege escalation, port scanning, vulnerability exploitation, interference with other customers, crypto-mining without express written approval, or excessive resource consumption that degrades platform performance.

Email and Messaging Abuse

Bulk unsolicited email, purchased mailing lists, forged headers, spam relay behavior, and messaging abuse are prohibited. HostingCPU may suspend email functionality or full services where reputation, deliverability, or anti-abuse obligations are threatened.

Customer Responsibilities

You must secure applications, maintain software updates, remove malware quickly, protect credentials, and respond promptly to abuse or security notifications. Failure to cooperate may itself be treated as a policy violation. Customers are expected to patch exposed software without unreasonable delay, maintain anti-malware and access controls appropriate to their environment, and avoid hosting material that exposes HostingCPU or its vendors to preventable legal or reputational risk.

Enforcement

HostingCPU may investigate suspected violations and may suspend, filter, block, quarantine, remove, or terminate services without prior notice where reasonably necessary to contain risk or comply with legal or vendor obligations.

HostingCPU may, where operationally necessary, access service environments, files, logs, and configurations for abuse response, security hardening, emergency maintenance, remediation, backup integrity checks, migration support, or infrastructure protection. Such access does not shift legal responsibility for customer content or customer systems away from the customer.

Last updated: April 9, 2026