1. Check where “no KYC” stops
KYC — “know your customer” — means proving who you are: an ID document, a selfie, a proof of address, sometimes a phone number checked by SMS. Many hosts advertise “no KYC” at sign-up and still ask for ID later: when an order is flagged for review, at a renewal, or after a complaint. Ask the question directly, in writing: is there any situation in which you would ask for my identity?
At DediCrypto the answer is no: an email address is the whole account, at sign-up and afterwards, and complaints are handled on what a server does — not by asking who runs it.
2. Check who processes the payment
A host can collect no personal data and still send you to a third-party crypto payment processor that runs its own identity checks, or that stores your IP address and wallet next to your order. Cards and PayPal are identity by definition.
Look for invoices issued by the host’s own gateway, with a one-time address per invoice. Ours are: no payment processor sees your order.
3. Check the coins, the fees and the rate lock
Three questions. Is Monero accepted, at the same price as every other coin? Is the price set in a stable currency, with the rate locked long enough to pay calmly? And for stablecoins, which networks are accepted — USDT sent on the wrong chain can be hard to recover.
DediCrypto prices every server in US dollars, locks the rate for 30 minutes per invoice and accepts 14 cryptocurrencies with no surcharge, Monero included. USDT works on TRC-20 or ERC-20, and the invoice shows which network to use.
4. Check the hardware, not just the price
Privacy-friendly hosts too often run old machines. Ask for the exact CPU model and generation, whether the memory is ECC, whether the disks are datacenter NVMe or consumer SSDs, and whether you get IPMI/KVM access to repair a server that no longer boots. A test report for the machine you receive beats a spec sheet.
Every DediCrypto server has ECC memory and passes a 24-hour burn-in and a 12-hour memory test before delivery; the report is yours. Older generations stay in the range only where they are still the best value, and they are labelled as such.
5. Read the abuse policy
“Bulletproof”, “DMCA ignored” and “anything goes” are red flags, not features. A host that ignores every complaint attracts spam, phishing and malware to the servers next to yours; its IP ranges end up on blocklists, and sometimes the whole provider is taken down with your server inside.
What protects a legitimate project is a published procedure: complaints forwarded to you, time to answer, proportionate action. That is how our acceptable use policy works.
6. Choose the jurisdiction after the latency
Where a server sits decides which laws apply to it — but a server far from its users is a slow server. Shortlist the locations close enough to your audience, then compare their legal frameworks: data retention, access by authorities, data-protection law.
Our latency planner estimates round-trip times from major cities, and the jurisdiction guide compares the EU, the UK, the US and Singapore.
7. Look for proof, not promises
Anyone can write “we never share your data”. Signals you can verify are harder to fake: a warrant canary signed with a published PGP key and dated by a recent Bitcoin block, a transparency report that counts legal requests, and the PGP key to check both.
DediCrypto publishes a signed canary every month and a transparency report every quarter; the key is on the PGP page.
8. Check how you would get back into your account
Without identity data, a host cannot verify you the usual way when you lose access. Ask how recovery works before you need it — email reset, two-factor authentication, recovery codes — and check that you can sign in over Tor or a VPN.
Here, your email address and your password are the only proof of ownership: keep them safe. Tor and VPN users are welcome, and the site works in Tor Browser’s Safest mode.
9. Ask what is logged
“No logs” rarely means nothing at all. Ask what the website records, how long sign-in IP addresses are kept, and whether customer traffic is inspected.
Our website’s access logs contain no IP addresses; sign-in IPs are kept 30 days to detect account takeovers; customer traffic is neither inspected nor recorded. The complete list is in the privacy policy.
The checklist
| Check | Good sign | Red flag |
|---|---|---|
| Identity | No ID at any stage, in writing | “No KYC” at sign-up only |
| Payment | The host’s own gateway, one address per invoice | A processor with its own checks |
| Coins | Monero at the same price, USD rate locked | A surcharge on private coins |
| Hardware | Exact CPU, ECC, NVMe, IPMI, a test report | Vague “enterprise-grade” specs |
| Abuse | A published procedure with due process | “Bulletproof”, “DMCA ignored” |
| Jurisdiction | Chosen after the latency | Chosen for its reputation alone |
| Proof | Signed canary, transparency report | Promises nobody can check |
| Recovery | 2FA, Tor welcome | ID required to regain access |
| Logs | A precise, published list | “No logs”, with no details |
