Skip to content
Orders open

PixelRackHost · Legal

Acceptable Use Policy

Rules designed to protect customers, infrastructure and third parties while using PixelRackHost services.

PixelRackHost · Current published policy

01

Responsible use

PixelRackHost services must be used lawfully and responsibly. You are responsible for activity performed through your account and services where applicable.

02

Prohibited activity

You may not use services for activity that is unlawful, abusive, harmful to infrastructure or unauthorized.

  • Malware distribution or malicious payloads
  • Spam or unsolicited bulk messaging
  • Phishing, fraud or impersonation
  • Unauthorized access, scanning or attacks
  • Denial-of-service activity
  • Distribution of unlawful content
  • Use intended to compromise systems, accounts or networks
03

Network & infrastructure abuse

Activity that intentionally disrupts, degrades or interferes with PixelRackHost systems, customers or third-party networks is prohibited.

04

Security responsibilities

Customers should maintain appropriate account and server security, including protecting credentials, applying relevant updates and restricting unauthorized access.

05

Resource & service integrity

Services must not be deliberately operated in a way intended to interfere with platform stability or bypass product restrictions. If a workload requires different infrastructure, contact us to discuss available options.

06

Abuse reports

If we receive a credible abuse or security report, we may investigate the affected service and request information or corrective action where appropriate.

07

Enforcement

Where reasonably necessary to protect infrastructure, customers or third parties, we may restrict or suspend an affected service while an abuse or security issue is investigated or addressed.

08

Reporting concerns

To report suspected abuse or ask whether a planned use is appropriate, contact PixelRackHost through the Contact page.

Questions about this policy?

Contact PixelRackHost for clarification. Never include passwords, private keys or API credentials in a general inquiry.