Acceptable use policy
No-KYC is not no-rules. We never ask who you are; we do watch what leaves the network.
1. The deal
We sell anonymous compute and we intend to keep selling it. That only works while upstreams, peers and datacenters keep accepting our traffic, so this policy is the line. It is enforced identically for every account — we could not play favourites if we wanted to, because we do not know who anyone is.
2. Prohibited absolutely
The following end the contract on the first verified offence, with no notice period and no refund of bonus credit:
- Spam — unsolicited bulk email, SMS or messenger traffic, including mailer infrastructure, spam-support DNS and landing pages for spamvertised goods.
- CSAM — child sexual abuse material in any form. Zero tolerance: immediate termination, with evidence preserved and reported where the law of the hosting jurisdiction compels it.
- Malware command-and-control — C2 endpoints, malware distribution, botnet herding or pay-per-install operations.
- DDoS launching — originating denial-of-service attacks, or hosting booter/stresser services and their frontends.
- Phishing — credential-harvesting pages, lookalike portals and the kits that build them.
- Carding and payment fraud — trafficking in stolen card or account data, card-checking tools, fraud automation.
3. Network scanning
Internet-wide measurement is tolerated when it is slow, polite and non-exploitative: rate-limited probes, no authentication attempts, opt-outs honoured permanently. Credential brute-forcing, exploit spraying and vulnerability scanning of targets that did not ask for it are prohibited. If your scanner generates upstream complaints faster than we can answer them, it stops — that simple. Set reverse DNS on scanning addresses so complaints arrive with context instead of as mystery noise.
4. Grey zones, decided
- Game and IRC servers — allowed. The DDoS attacks they attract are what the included mitigation is for.
- Tor — relays and bridges are welcome everywhere. Exit nodes only on dedicated servers in Romania or the Netherlands, and tell us through the contact form first so the complaint volume gets routed properly.
- VPN endpoints and proxies — allowed. You answer for the traffic they emit, the same as for any other packet from your address.
- Crypto mining — allowed on dedicated servers; prohibited on VPS, because shared CPU is shared.
- Adult content — legal adult content is fine. Compliance with age-verification law wherever you publish is your problem, not a hosting question.
5. Takedowns — the honest version
DMCA notices are not processed. The DMCA is a United States statute with no force in any jurisdiction we operate in. Notices sent to us — single or bulk — are not answered, not forwarded and not acted on, and we do not pre-emptively police content. None of that means lawless: our operations follow the law of the country each server physically sits in.
A verified order from a court of competent jurisdiction over the hosting location is honoured — narrowly, completely, and with notice to you unless we are legally barred from giving it.
Actionable complaints — a human, with evidence, alleging a concrete violation — get human review. When we agree a complaint is actionable, you receive it with a deadline, usually 24–72 hours depending on severity, before we touch the server.
6. Enforcement ladder
- Notice — you get the complaint and a deadline; fix it or explain why it is wrong.
- Suspension — the server is stopped, data intact, while we talk.
- Termination — for section 2 offences, repeat violations, or silence past the deadline.
Under active harm — an ongoing DDoS from your address, a live phishing campaign — we act first and explain afterwards. Every neighbour on the platform depends on that.
7. Reporting abuse
Use the contact form with the Abuse topic. Include source addresses, UTC timestamps and log excerpts. Evidence gets human eyes; form letters and bulk robots do not.
Other legal documents
Questions about a clause?
Ask through the contact form — a human operator answers on the channel you leave, not an auto-responder.