Legal

Acceptable use policy

Short and specific on purpose. What gets a server suspended, what needs a word with us first, and what is welcome.

Last updated 16 November 2026. Part of our terms of service.

This policy applies to every service on our network, in every location. We enforce it because abuse from one server gets whole IP ranges blocklisted and draws attention to the entire network, and every honest customer pays for that. Our servers are offshore, and abuse on them still gets shut down.

Forbidden

  • Malware. Hosting, distributing or controlling malware, including ransomware, info-stealers and exploit kits.
  • Phishing. Pages or messages that impersonate a person or organisation to collect credentials, payment details or personal data.
  • Spam. Unsolicited bulk email or messages, and hosting sites advertised through spam.
  • Botnets and command-and-control. C2 servers, bot panels, or relays for compromised machines.
  • Attacks on other networks. DDoS attacks, booter and stresser services, and scanning or probing systems you do not own or have no permission to test.
  • Child sexual abuse material (CSAM). Zero tolerance. The service is terminated at once, the data is preserved, and we report it to the competent authorities.
  • Fraud. Scams, fake shops, investment fraud, carding.
  • Credential stuffing and brute force. Using stolen or guessed credentials against other people's accounts and services.
  • Copyright infringement at scale. Services built around distributing infringing material, as determined under the law of the country where the server is located.

Allowed with notice

These are legitimate, but they generate complaints by nature. Tell us before you start, by email to [email protected] with your order ID, so we recognise the complaints when they arrive and can answer them properly.

  • Tor exit nodes. Use a reduced exit policy, set a reverse DNS name that makes it obvious the IP is a Tor exit, and put contact details in your relay configuration.
  • High-volume email. Newsletters, transactional mail and mailing lists sent to people who opted in. Set reverse DNS, SPF, DKIM and DMARC, and process bounces and unsubscribes.

Allowed

  • VPN servers, for yourself or for others.
  • Tor relays (non-exit), bridges and onion services.
  • Cryptocurrency and Lightning nodes, wallets and payment servers.
  • Journalism, research, activism and whistleblowing platforms.
  • Self-hosted email, file storage, chat and websites.
  • Security testing of systems you own or have written permission to test.

If something is not on any list and you are unsure, ask before you deploy. A short answer now beats a suspension later.

How we enforce it

Complaints arrive through our abuse desk. Each one is checked against this policy and the law of the server's location. Automated notices are not acted on blindly.

Standard process

  1. Notice. We forward the complaint to you and tell you what we need.
  2. Response window. You get a fixed time, stated in the notice, to fix the problem or explain why the complaint is wrong.
  3. Suspension. If the problem continues and you have not responded, the service is suspended until it is resolved. Network access is cut; your data is kept.

Immediate suspension

For severe or ongoing abuse we suspend first and talk afterwards: CSAM, active phishing or malware distribution, an outgoing attack in progress, or a compromised server attacking others. A hacked server is not held against you. Once it is cleaned up or reinstalled, it goes back online.

Repeated abuse

Repeated or deliberate breaches lead to all of the customer's services being terminated, as set out in our terms of service.

Copyright complaints

Copyright notices are assessed under the law of the country where the server is located, not the law of the sender's country. We forward notices that are valid under that law and give you the chance to respond. Infringement at scale is handled like any other forbidden use.