Terms of service.

1. Your order

These terms, the acceptable use policy, the privacy policy and the SLA apply to AnonVPS services. Your order identifies the resources, location, options and term you bought. Placing an order means you accept them. You must be legally able to enter a contract.

AnonVPS is the service brand. Registered-entity and postal details are not published on this site. If you need business documentation before buying, ask through support.

2. Account access

An access key identifies your account. Keep it secret and keep a safe copy: anyone with a valid key can reach the account. There is no email password reset. Contact details are optional and do not replace the key. Never send a full key, wallet seed or server password in a support message.

3. Service and responsibilities

We provide the virtual resources and options shown in your order. You manage the operating system, applications, credentials and backups. Backups are not included by default. RAM-only instances require you to plan for loss of volatile local state.

Use must follow the AUP and applicable law. Authorised security testing needs a documented scope. Reselling to your own customers under your own brand is allowed; contact us about your requirements.

4. Price and payment

Choose a prepaid term of 3, 6 or 12 months. The monthly equivalent is a comparison figure, not a one-month order. There is no automatic renewal.

No setup fee or gateway fee is added to the published configuration total. Your wallet, exchange or network may charge a transfer fee. The order total is in EUR and the payment screen gives the crypto amount, locked for 15 minutes. Paid options and the selected location affect the total.

Pay AnonVPS directly in an accepted cryptocurrency. Use the exact asset, network, address and amount shown for your order. Server preparation follows confirmation of the payment on the network; no fixed preparation time is guaranteed. The invoice is the amount charged by AnonVPS and is not a statement that no tax obligation can arise for either party.

5. Expiry and renewal

Nothing auto-renews. Arrange renewal before the prepaid term ends. When a term ends without renewal, the service is suspended for seven days and the instance is then removed. Keep an independent backup before expiry.

If you give us a contact channel, we can notify you about service matters. Without one, you are responsible for tracking your expiry date.

6. Refunds

• First payment on a new account: full refund within 72 hours, no reason required. Request it through support with the order reference. Refunds are in the cryptocurrency you sent, to an address you supply, minus network fees.
• After 72 hours: term payments are non-refundable.
• AUP violations: no refund is due if service is terminated for a violation of the acceptable use policy.
• Termination by us for other reasons: we refund the unused portion pro rata.
• SLA credits: service credits follow the SLA and are not cryptocurrency withdrawals.

7. Suspension and data

Service may be suspended for non-payment, a confirmed AUP violation, or an immediate threat to the network. Recover any permitted data promptly during an available recovery period. Keep backups outside the instance, and do not treat suspension or deletion as certified erasure.

8. Liability and protected rights

Our total liability in any 12-month period is limited to the amount you paid us in that period. Consequential losses such as lost earnings, missed deadlines and the value of lost data are excluded to the extent the law allows. This does not exclude fraud or liability that cannot lawfully be excluded, and it does not affect non-excludable consumer rights.

Service credits and refunds follow the conditions above and the SLA. Contact support about the service, an invoice or a dispute.

9. Changes to these terms

Material changes take effect 30 days after publication. If you do not accept a material change, you may end the service and receive a pro-rata refund of the unused prepaid amount, including outside the 72-hour window. Earlier versions are not published; ask support for a superseded version.

Common questions