Report abuse
Updated August 13, 2026
Summary
Abuse reports go to [email protected] and are read by a person. Child sexual abuse material and active attack infrastructure are suspended immediately without notice. All other reports are forwarded to the customer with a 72-hour response window before any action is taken.
Where to send it
Reports go to [email protected] and are read by a person, usually within a few hours. There is no ticket robot in front of that address.
Include the IP address or hostname, a clear description of the conduct, timestamps with a timezone, and any logs or headers you can share. A report we can act on immediately is worth ten that require correspondence first.
What happens next
Child sexual abuse material and active attack infrastructure are suspended immediately, without notice to the customer and without waiting for a response. There is no version of this where we wait.
Everything else is forwarded to the customer with the full report text and a response window of at least 72 hours. Most reports are resolved by the customer in that window — a compromised web application sending spam is far more common than deliberate abuse, and telling the operator is usually all that is required.
Where the customer does not respond or the conduct continues, the server is suspended. Repeat breaches end the relationship.
Copyright notices
The US DMCA has no direct legal force in any of our eight jurisdictions, so we do not action it as a statutory obligation. We do read every notice.
A notice that identifies a specific work, a specific URL, and a claimant with standing under the law of the jurisdiction the server is in is forwarded to the customer with a response window like any other report. A bulk automated filing citing 17 U.S.C. §512 at a server in Chișinău receives a reply identifying the applicable jurisdiction.
Our acceptable use policy prohibits distributing content you do not have the right to distribute, and we enforce it. Jurisdiction changes which court hears a claim; it does not make infringement lawful.
For law enforcement
Requests should be sent to [email protected] with “LEGAL” in the subject, or via the PGP key at /pgp. We review every request for validity, scope and jurisdiction, and we challenge those that are improperly served or overbroad.
What a valid order can produce is an Argon2id token hash, a USD balance, a list of server identifiers and a creation timestamp. There is no name, email address, phone number or payment identity, because no such fields exist in the schema. We would rather tell you that in advance than have you spend three weeks obtaining an order for nothing.
Emergency requests involving imminent risk to life are handled out of band and quickly. Use the same address with “EMERGENCY” in the subject.
Notice statistics — 2026 Q2
- Notices received
- 4,187
- Automated, no local legal basis
- 3,946
- Actionable under local law
- 241
- Forwarded to customer
- 241
- Resolved by customer
- 228
- Resulted in suspension
- 13
Automated notices citing US statute at non-US servers receive a reply identifying the applicable jurisdiction. Notices identifying a specific work and a claimant with standing under local law are forwarded to the customer with a 72-hour response window.
55-second deploy
Pick a jurisdiction. Pay in crypto. Be running in a minute.
No account to create, no email to confirm, no card to enter.