39 judicial requests received. 0 customer activity records produced.
Every formal request, every informal inquiry, every takedown notice — categorised, counted, and disclosed. We don't retain server-side logs of customer activity, so the "records produced" column is structurally zero. This page exists to make that fact auditable instead of just claimed.
Requests received vs records produced
39
Total requests received
Across 6 categories
8
Requests complied with
Lawful local court orders honored
0
Customer activity records produced
Zero. We don't keep logs.
0
Account closures from requests
Content takedowns ≠ account closures
Warrant canary
Active as of 2026-04-30.
As of 2026-04-30, SilentHosts LLC (Republic of Seychelles) has received zero national security letters, gag orders, secret subpoenas, or requests under any process that would prohibit it from acknowledging the existence of such a request.
SilentHosts LLC has not been compelled to install surveillance software, modify production systems for surveillance purposes, or disclose customer activity data to any government agency.
If this statement is removed without replacement, or if the next scheduled update is missed by more than 14 days, you should assume the statement's previous content is no longer accurate.
— Signed cryptographically by the operator on each update. Past canary statements and signatures are archived at /transparency. Next scheduled update: 2026-07-06.
Requests by category
Period: 2026-01-01 → 2026-04-30. Every row is a request type with its origin, count, and outcome.
| Category | Origin | Received | Complied with | Records produced |
|---|---|---|---|---|
DMCA-format takedown notices Boilerplate copyright takedowns sent under the US DMCA framework. DMCA has no legal force in any of our 8 operating jurisdictions. Notices acknowledged with the standard non-compliance reply pointing senders to local-law procedures. | USA | 21 | 0 | 0 |
Local court orders (copyright) Court-issued takedown orders from courts of competent jurisdiction in our operating countries. Properly served local court orders are honored — content removal performed where mandated. No customer records produced because we don't retain logs that could identify activity beyond billing. | EU + Switzerland | 4 | 4 | 0 |
Police inquiries (informal) Pre-litigation contact from law enforcement requesting information. Informal requests without judicial process are declined per our AUP §6.5. Every requester redirected to formal MLAT channels. | Multiple | 8 | 0 | 0 |
Subpoenas (criminal) Formal subpoenas in criminal proceedings, served via local counsel. Three subpoenas processed: the only data we hold beyond billing-tax-period records is the user's chosen pseudonym + (when provided) email. We produced what was on file. No traffic logs, no command history, no IP timestamps existed to produce. | EU member states | 3 | 3 | 0 |
Subpoenas (civil) Civil subpoenas in private-party litigation. Both quashed by our counsel — the records sought (server logs, traffic data) do not exist in our systems. | Multiple | 2 | 0 | 0 |
MLAT requests Mutual Legal Assistance Treaty requests routed via Seychelles-AG channels. One MLAT processed. The requesting authority received what was on file (pseudonym + email). No further records existed. | Multiple | 1 | 1 | 0 |
National Security Letters / equivalent Secret-process gag-ordered requests under national security statutes. None received as of the date stamped at the bottom of this page. See the warrant canary statement above. | — | 0 | 0 | 0 |
| Total | 39 | 8 | 0 | |
It's not a slogan. It's an architectural decision.
Most hosts say "we don't share logs." That promise dies the moment a court order arrives. Our promise is one layer up: we don't collect the logs in the first place.
What we never write to disk: per-customer access logs, IP timestamps for inbound traffic, command history, console session recordings, cron-job exit codes tagged to user identity, DNS query logs.
What we do keep, and why: billing records (Seychelles tax-record retention is 7 years — required by law), a bcrypt-hashed password and the user's chosen pseudonym + (optionally) email per account, and aggregate load metrics with no customer-correlation field. That's all. When a subpoena lands, we produce what we have on file — a row in the users table with an opaque ID, the pseudonym, the email if one is set, and the billing-period totals. No more, because no more exists.
What we run on the customer's VM: nothing under our control. Customer VMs are KVM virtual machines under the customer's control. We don't install monitoring agents, we don't SSH in for housekeeping, we don't run kernel-level surveillance. The hypervisor host is ours; the VM is yours.
Why the architecture matters more than the policy: an honest operator with retentive logs and a strong privacy policy can be compelled by a court to disclose. An honest operator with no logs to disclose can't produce what doesn't exist — and that's reflected on this page, row by row, with the receipts to back it up.
How this report is compiled
Every request is logged externally
Inbound legal correspondence is filed with our retained counsel in each jurisdiction. The legal log is independent of our production systems and is the canonical source for this page. Counsel signs off on every quarterly update.
Quarterly cadence
Updated the first Monday of each quarter. If an update is skipped, that's a signal. Past versions of this page are archived in our git history; each commit is signed.
The warrant canary
The canary is a positive statement ("we have NOT received X") that goes silent when X arrives. The signed canary text above is dated; if the date stops advancing, draw your own conclusions.
Limits on this report
Some jurisdictions criminalise the disclosure of certain process types. The canary mechanism is the legally-recognised way around prior-restraint orders in most jurisdictions, but it's not bulletproof — sophisticated adversaries have ways to suppress it. Verify the date and the signature on every update.
Deploy your first offshore server in 60 seconds.
Anonymous signup. Bitcoin & Monero accepted. Provisioned across 8 jurisdictions.
No credit card required · 7-day money-back guarantee