THE RECORD, IN THE OPEN
A private account should come with a clear account of what happens around it. Here are the requests AnoneHost received, the decisions that followed, and the data boundaries behind those decisions.
Read the request registerAcross 9,002 active accounts.
Not a name behind a number.
The two columns answer different questions. One counts what arrived; the other counts an intervention following review. A message alone does not establish a valid claim.
| Category / treatment | Received | Acted on |
|---|---|---|
| Public-authority enquiriesRequests from government bodies and law enforcement for information associated with an account. | 43 | 0 |
| Copyright correspondenceDMCA notices and other claims about material served through customer infrastructure. | 176 | 0 |
| Orders seeking recordsJudicial demands for customer information, assessed against their scope and the records held. | 5 | 0 |
| Judicial removal requestsOrders asking for a service restriction or removal of particular material. | 7 | 0 |
| Cross-border legal demandsForeign subpoenas and mutual-assistance requests requiring jurisdictional review. | 3 | 0 |
| Secret compulsory demandsNational-security or non-disclosure demands. Read the separate canary for its own declarations. | 0 | 0 |
| Child sexual abuse materialReports assessed individually; confirmed cases resulted in closure and removal. | 3 | 3 |
The reporting window is fixed above. Counts describe this period; they are not a promise about future requests or legal outcomes.
Every report of child sexual abuse material is examined. When the material is confirmed, the relevant account is terminated and the content is removed. Any further reporting follows the obligations applicable to the case.
That intervention is recorded separately, so protecting children never disappears inside a general request total.
Report harmful material through supportThe account system and a domain registration have different information requirements. Keeping those uses separate matters as much as limiting collection.
The account keeps an irreversible HMAC fingerprint of its access token. Projects, orders and support conversations remain attached to that account. Payment records can contain the transaction hash, asset, network, amount and receiving address.
No name, email address or password is required to create the token-based account. There is no advertising profile, tracking pixel or browser fingerprint. Domain registrant details are a separate requirement when registering a domain.
Account, ticket, order and payment records follow the duration needed for their function and applicable obligations. This report adds no blanket deletion deadline and makes no claim that operational records cannot exist.
Authority, scope, necessity and available records are examined separately. The result belongs in the register, without exposing the customer behind it.
Identify what is requested, who submitted it and which service is concerned. Preserve enough context to assess the request.
Check the claimed authority, jurisdiction and limits. Seek clarification or challenge a demand that extends beyond a valid scope.
Assess the actual records available. A demand cannot create information the service does not collect.
Keep the response and any service intervention distinct. Inform the affected account where permitted, through its private support space.
Each has its own purpose. Read the declarations alongside the data policy rather than asking a single number to explain everything.