acceptable use

• spam of any kind, including hiring someone else to send it for you.
• phishing, malware distribution, or command-and-control for botnets.
• port scanning, brute-forcing, or participating in ddos attacks, incoming or outgoing.
• child sexual abuse material. this is the one item with no warning and no conversation — the account ends and the authorities are informed.
• anything illegal where your machine sits — france, the netherlands, latvia, the united states or hong kong, depending on the location you picked.

outgoing mail ports are closed by default and opened on request after your first paid month. this annoys legitimate customers, and we do it anyway: a fresh server sending mail on day one is the single most reliable signal of an abusive signup, and one such server gets the whole ip range blacklisted.

you paid for the cpu and memory in your plan, and you may use all of it, continuously, at 100%. that is not abuse, and we will never write to you about it.

what we do act on is a machine that degrades the node for everyone else — sustained disk saturation, or traffic that triggers upstream filtering. we write first and work it out with you.

upstream abuse reports come with a deadline, usually 24 hours. our order of preference is:

• we write to you and give you the report, redacted only where the law requires.
• for something narrow — one compromised script, one open relay — we ask you to fix it and hold the deadline off.
• for an active attack coming out of your machine, we block the specific traffic first and write immediately after. an ongoing attack does not wait for office hours.
• we suspend the whole machine only if the above has not worked or the report leaves no choice.

a suspension for abuse does not wipe your disk. you get your data.

it happens, and it is not automatically your fault. a hacked server that starts scanning is treated as an incident, not a violation: we block the traffic, tell you what we saw, and help you get back up. we do not terminate accounts for being a victim.

abuse@looz.cloud. we read it, and we answer. include headers, logs and timestamps in utc — with them we act in hours instead of days.