Offshore No-KYC — built into every plan

KYC obligations are imposed on financial intermediaries (banks, brokers, money-services businesses), not on hosting providers. Many hosting providers nevertheless adopt KYC-style verification because their downstream payment processors push it upstream. The result is a hosting industry that asks for government ID despite no underlying legal requirement to do so — and customers who object to this on principle are funneled to a smaller and smaller set of providers.

We elect not to collect identity documents because no legal regime requires us to, and a meaningful population of legitimate customers prefer to do business with providers who don't. The election is durable: it applies at signup, at upgrade, at incident response, and at end-of-life account closure. Customers paying with cards encounter card-issuer KYC at the payment step; that verification is between the customer and the card processor, and we never see or relay it. Crypto-paid accounts pass through no KYC step at any point.

This is a positioning choice with operational consequences. We accept higher chargeback risk on card payments (mitigated by accepting only known-good processors) and we accept that crypto-paid customers may be harder to reach if an account requires manual contact. Both are worthwhile trade-offs given the customer population we want to serve.