Frequently asked questions, full version.

Seven: BTC, XMR, ETH, USDT (TRC20 and ERC20), LTC, SOL, and TRX. XMR is recommended for maximum opacity; USDT-TRC20 for reduced fees. No fiat, no bank cards, no online wallets — and that won't change: crypto-only is structural, not commercial.

Paymento generates an invoice in 15 seconds — address, exact amount, QR code — with a rate fixed at the moment of payment: it is the simplest path. Direct on-chain payment assigns a dedicated address per order, with no intermediary of any kind. Both trigger the same automatic delivery; only the path differs. Neither option asks who you are.

Provisioning starts at the first network confirmation — one for BTC, near-instant for XMR or USDT-TRC20. The median time observed in Q2 2026 is 47 seconds between confirmation and receipt of the IP and credentials. If the network is congested, it's the blockchain that slows down — not our pipeline.

Yes: each payment generates a dated, numbered invoice denominated in USD, downloadable from the console. It carries no identity — your client reference is the transaction hash. It's enough to justify an expense, without saying who you are.

Nothing is charged without action: we store no payment method, so nothing can be. A reminder appears in the console 7 days before the due date, followed by a 72 h grace period. Three formulas: monthly at the base rate, 6-month commitment at -30 %, 12-month commitment at -50 % — it is the monthly equivalent that decreases, across all VPS and RDP ranges. On top of that comes the NOREPLY code: 1 month purchased = 1 month free, applicable to any subscription and renewable — but explicitly not combinable with commitment discounts.

Yes: full refund within 72 hours of your first order, no justification required, to the original crypto address. After that period, the refund is calculated pro rata, subject to compliance with the AUP. Renewals are refundable pro rata within their first 7 days. Full details are on the Refund page.

The DMCA is an American law: its notices have no legal value in our jurisdictions. Our filters nonetheless receive thousands of them, issued by bots: they are dismissed and publicly accounted for. Only a decision handed down by a local jurisdiction and transmitted through official channels counts. In 2025: 1,847 DMCA notices received, 0 suspensions on that sole basis.

We forward it to our local counsel and comply with the decisions of the hosting country's court — that's the law, and we won't circumvent it. What we cannot hand over, however, is what we don't possess: no identity, no logs, no correspondence. A request can only yield three things: a token fingerprint, a crypto payment reference, the technical configuration of the service. Our warrant canary tracks its quarterly evolution.

Our acceptable use policy fits on one page: phishing and impersonation, malware and command infrastructure, spam, child sexual abuse material, fraud and carding. These uses result in suspension within the hour, without refund, and reporting to the relevant authorities where applicable. This restricted scope is precisely what allows us to maintain our jurisdictions over the long term.

Yes. The DMCA is an American mechanism that our jurisdictions ignore as a matter of legal competence. Local copyright, on the other hand, applies everywhere: documented commercial counterfeiting, brought by the rights holder before a local judge, is treated with the seriousness it deserves. Our position is not “anything goes” — it is “American takedown bots do not decide in your place”.

By the main threat: American copyright pressure → Romania; freedom of expression → Iceland; no data retention → Panama; maximum privacy standard → Switzerland; connectivity and peering → Netherlands; outside US/EU scope → Russia. The Locations page details each legal framework, and migration from one zone to another is free if your analysis evolves.

A server located in a country falls under that country: a local search is legally possible everywhere, including Switzerland or Iceland. What our jurisdictions reduce is the ease and scope: lengthy procedures, real protections, and with us, very little data to hand over. Disk encryption — available via custom ISO — remains your best guarantee.

Because it has been our anchor jurisdiction since 2021: Panama imposes no data retention law forcing a host to keep its customers' logs, and it sits outside American and European jurisdictions — a DMCA notice has no legal force there. Any international mutual-assistance request follows formal channels: long, documented and adversarial. An honest nuance: Panamanian law fully applies, and we comply with it — no one is above the laws of their anchor country.

No. Everything is operated from Panama City — management, support, systems and the Tier III+ datacenter. What we hold in Europe and elsewhere is exclusively a network presence: servers, peering, our own ASes. No offices, no subsidiaries, no entity incorporated in the United States or the European Union. Practical consequence: a US/EU judicial constraint reaches us only through international mutual assistance, never directly.

Median measured over July 2026: 22 minutes, all queues combined, 24/7. P1 priorities — server unreachable — are handled in under 15 minutes, with a status update every 30 minutes. Support is human: network and system profiles, not a chatbot.

On the Status page: health per site and per service, continuous public history since 2022, latency probes every 30 seconds. We don't erase past incidents — good days and bad days remain readable. Q2 2026 uptime: 99.98%.

Yes, for any incident exceeding 30 minutes of impact: timeline, root cause, actions taken, lessons learned. Most recent example — on June 14, 2026, network degradation in Bucharest (packet loss for 38 minutes): abnormal routing at a transit operator, workaround activated, postmortem published the next morning. The seven most recent are on the Status page.

Via the form on the Contact page or a ticket from any console: IP address concerned, timestamp, supporting logs. Our abuse team handles verifiable reports within the hour, 24/7. False reports are archived and counted. The policy is public: phishing, malware, spam, child exploitation content — immediate suspension, in accordance with the AUP.

That's how it normally works. Your support identity is your token or a pseudonym of your choice; we never ask for anything else. For sensitive topics, an encrypted channel is available from the Contact page. And what you tell support is not cross-referenced with anything — there is nothing to cross-reference it with.

Three steps, in order. One: check the Status page — an ongoing incident is published there within 5 minutes. Two: try the emergency console from your dashboard; if it shows a shell, the problem is network or configuration, not the machine. Three: soft reboot, then ticket with priority P1. All hardware reboots are logged and visible in the console.