Room to build. Clear boundaries.

These rules are a proposed launch policy, not an active hosting contract. They distinguish a lawful workload from a harmful method of operating it. Customers would remain responsible for their content, licences, credentials and the law that applies to the project and selected region.

The proposed policy excludes child sexual exploitation material, phishing, credential theft, malware distribution, fraud, denial-of-service attacks against others, unauthorised intrusion and threats of violence. It also excludes unlawful content and use that infringes third-party rights. A privacy-focused account cannot be used as permission to harm another person or system.

Messaging requires opt-in or another demonstrable lawful basis appropriate to the jurisdiction. Purchased or harvested lists, reputation evasion and misleading sender identity are outside the proposal. Configure SPF, DKIM and DMARC; bulk messages must supply a functioning List-Unsubscribe header consistent with RFC 2369 and List-Unsubscribe-Post where one-click handling under RFC 8058 is applicable. Suppress opted-out, bounced and complaining recipients promptly.

A Tor exit would require prior review, a public operational contact, a documented exit policy and a response to abuse reports within 48 hours. Bridges and non-exit relays still need compatible networking. Mining is proposed only on approved dedicated, GPU or storage hardware with exclusive resources; generic VPS, RDP, shared and cPanel products are outside that permission. Streaming and P2P require rights valid in the relevant locations.

For shared environments, sustained use above 85% CPU for more than 24 hours is a proposed review trigger. An investigation should distinguish a legitimate workload needing a better-sized plan from an attack or harmful abuse. Limits, overage handling and any migration proposal should be explained rather than hidden behind “unlimited” language.

For an ordinary, substantiated complaint, the proposal allows five business days to respond or remedy the issue. If unresolved, suspension can follow; the remediation and data-export window would then last 14 days before closure. Severe harm, an active attack or a binding urgent order may justify immediate action. An appeal may be filed within 30 days and should receive a reasoned review. The same ordinary-complaint timetable is proposed for streaming, resolving inconsistent source notice periods.

A report should identify the affected resource, the conduct, the legal or policy basis and evidence sufficient to assess it. Preserve a ticket timeline, notify the account where appropriate and use the least disruptive effective action. The policy does not guarantee that every request will be disregarded or that every allegation will result in removal.