Skip to main content
Legal

Acceptable Use Policy

Where the limits are. This exists so that a small number of abusive uses can be dealt with before they reach other customers and our upstream networks — not to restrict ordinary work.

Effective 2026-01-01

1. Not permitted

Port scanning, vulnerability scanning, credential stuffing, brute-forcing or denial-of-service against targets you do not have permission to test, and participation in botnets.

Sending unsolicited bulk email, or providing relay, list management or delivery support for it.

Distributing malware or ransomware, hosting phishing pages, or running anything designed to capture other people's credentials.

Storing or distributing child sexual abuse material. There is no tolerance here: we terminate immediately and report to law enforcement, with no notice period and no appeal.

Infringing copyright, trade marks or other intellectual property, including unauthorised distribution of media and software.

Circumventing someone else's technical protection measures, or scraping at scale in breach of a target site's terms.

2. Grey areas worth asking about

Proxy and VPN exits: fine for your own use, and you are responsible for everything that leaves through them. Reselling as a public or commercial proxy service needs a conversation with us first.

Cryptocurrency mining: not prohibited, but power and cooling are constrained by the facility, and sustained full load can trigger upstream limits. Check with us about the model first.

Automation and account work: the machine is an ordinary Mac and you may automate on it. Staying within the terms of the accounts and licences you use — Apple's included — is your responsibility.

Heavy distribution: relay traffic beyond your allowance needs a traffic package, or a tunnel of your own — the latter is not metered. If sustained port saturation starts affecting others in the same rack, we will contact you before doing anything else.

3. Traffic and resources

Each billing cycle includes 100 GB of relay traffic. That allowance counts only bytes forwarded through the relay we provide: a tunnel you run on the machine yourself (Tailscale, for instance), a P2P remote desktop, or anything else that leaves the machine directly is not counted against it and is not affected by the limit below.

We notify you once when 80% of the allowance is used. When it runs out we do not disconnect you, suspend the machine, or raise an invoice for the overage — we cap that machine's relay throughput at 5 Mbps. Shell access stays usable; transfers get slower.

Two ways back to full speed: buy a traffic package, which raises the allowance and lifts the cap automatically within a minute, or wait for the next cycle to reset. Traffic packages are not refundable once active.

4. How we handle reports

When an abuse report arrives we establish the facts. Except for the last item in section 1, we contact you by email and ticket first and give you a deadline, usually 24 hours. Send reports to support@fucker.sh.

Where it is urgent — an attack in progress, malware spreading — we suspend first and tell you immediately after.

You can appeal a decision. Provide evidence on the ticket and we will look again.

5. Indemnity

The legal consequences of how you use a machine are yours. If your use causes a third party to claim against us, or gets us pursued by an upstream provider or listed on a blocklist, you will cover our direct losses.

Making sure the software you run is properly licensed is your responsibility.

Questions about this document: support@fucker.sh