Refund Policy

01 The 72-hour first-order guarantee

Your first order with VPSRento carries a 72-hour guarantee. If the service isn’t what you needed, you get the full invoiced amount back as balance credit — every plan, every location, every billing cycle, add-ons included.

Four conditions, all required:

• It must be your first order ever. Not the first on this account — the first with VPSRento. Anonymous accounts make this enforceable only one way, so we are blunt about it: creating fresh accounts to chain guarantees is one of the few patterns the abuse desk actively hunts, and it ends with termination and no credit. The guarantee runs on trust. Don’t be the reason it can’t.
• The request lands within 72 hours of activation. The activation timestamp in the client area is the reference. Hour 73 is too late, and the ticket queue timestamp is what counts.
• The request comes via ticket, from the account that placed the order. That is the only authentication that exists — no token, no guarantee claim.
• The service is not suspended or terminated for an AUP violation. The guarantee covers “this isn’t for me”. It does not cover “I got caught”.

What you get: 100% of the invoiced amount, in USD, credited to your account balance. Not a crypto refund — a credit. It never expires and it pays for anything we sell: renewals, new services, upgrades, add-ons, any location.

What it doesn’t cover: the hourly sandbox (it bills in cents and converts freely — trying it is its own guarantee), balance top-ups themselves, and anything that isn’t your first order.

02 Why there are no crypto refunds after that

Two honest reasons. Neither is “policy” — both are arithmetic.

Volatility cuts both ways

A refund “in crypto” needs a valuation moment, and every candidate is unfair to someone. Refund the coin amount and a 10% swing while the request sits in a queue shorts either you or us. Refund the USD value at refund time and the same problem mirrors. The only non-arbitrary moment is purchase time — and by the time a refund request exists, that moment is gone. A USD-denominated balance credit at the invoiced amount is the one valuation nobody can game, in either direction.

Abuse economics

Anonymous accounts plus on-demand cash-out would make us a mixing service with a hosting front-end. Anyone could cycle tainted coins through “purchases” and withdraw clean ones to a fresh address, and we would have no KYC data to even pretend to stop it. We will never operate that rail. Balance credit — spendable here, withdrawable nowhere — is the ceiling of every refund path we offer, precisely so that refund abuse is worth zero to anyone attempting it.

03 SLA credits are not refunds

Downtime compensation is a separate mechanism with its own document: the Service Level Agreement. If monthly uptime on a service drops below 99.9%, a credit posts to your balance automatically — no ticket, no claim form, no arguing with support about whether your monitoring counts.

If you ever find yourself having to ask for an SLA credit, we have failed twice: once on uptime, once on the automation. That has happened zero times since the automation shipped in 2022, and the number is on the status page for anyone to audit.

04 Chargebacks don’t exist here

There is no chargeback mechanism in this payment stack, because the stack has no card rails, no PayPal, and no banks. A confirmed crypto payment is final by protocol, not by policy. There is no issuer to call, no dispute department, no 180-day clawback window.

Understand what that buys you, because the finality cuts both ways. No frozen accounts. No rolling reserves. No “risk review” holding your balance hostage for 180 days because someone’s algorithm had a feeling. No payment processor reading your invoices. You trade the right to reverse a payment for a relationship where no third party can reach into it at all.

Make that trade with open eyes. Test with the sandbox or a monthly plan first; use the 72-hour guarantee on your first real order; scale up when you trust the service. That is what those mechanisms are for.

05 How to claim the guarantee

Three steps, no form:

• Open a ticket in the client area within 72 hours of the service activating.
• Say what you want in one line — “72-hour guarantee” as the subject is perfect. A sentence about what didn’t work helps us, but it is optional and changes nothing about the outcome.
• We verify the four conditions from §01 and credit the balance. Median first reply across all tickets is 14 minutes in 2026; guarantee credits typically land within the hour.

You can delete the service yourself first, or we delete it as part of the credit. Either way it is wiped, not hibernated — a guarantee credit and a kept server are not a combination that exists.

06 Edge cases

A situation not in the table? Open a ticket and ask. The answer will still not be an external-wallet refund — but most real situations turn out to be one of the rows above.

07 Changes

Material changes to this policy take effect no sooner than 30 days after announcement on the warrant canary page and a site-wide banner — the same mechanism as the Terms of Service. The 72-hour guarantee has existed since March 2021 and has never been narrowed; if that ever changes, it changes loudly.