Delivery Policy

Digital delivery — nothing is posted, nothing to sign for

Legal · Version 3.0

Delivery Policy — when your server is officially yours.

WenHost sells intangible services: a VPS is delivered electronically, not shipped. This policy states how delivery happens, how fast we target, what counts as service delivery completed — the exact moment our obligation is met and your 72-hour refund window starts — and what you get if we fail to deliver. It also lists the evidence we retain to prove delivery, which is what settles an "item not received" claim in minutes instead of weeks.

Effective 29 October 2026 · Applies to all orders on wenhost.website

  • No delivery fee
  • No minimum order
  • Automatic provisioning 24/7
  • Timestamped proof of delivery

Delivery in four numbers

The whole policy compressed. Each number is measured automatically and quoted back to you in your order log.

45sec

Provisioning target

From payment confirmation to a running server on automatic checkout, for standard Linux templates in an in-stock region.

2hours

Maximum review hold

The ceiling for manual fraud and sanctions review on a first order or a PayPal-funded order. You are told if it is applied.

24h

Migration window

Target completion for a free single-server migration once you approve the plan and hand over access.

48hours

Maintenance notice

Minimum advance notice for planned maintenance affecting your region, published on the status page and emailed.

Why this page exists. Payment networks treat "service not received" as a distinct claim type with its own evidence rules. A hosting provider that cannot show when and how delivery happened loses those claims by default. So we define the moment of delivery in one place, keep the proof, and give you the same definition in the Refund Policy and clause 5 of the Terms of Service — three documents, one timestamp, no ambiguity.

Clause 1

Nature of delivery — an electronic service, not a parcel

Every WenHost product is an intangible, electronically delivered service. There is no physical shipment, no courier, no tracking number, no signature and no delivery address for the service itself. We ask for a billing address only to calculate tax, to screen fraud and to issue a valid invoice — not because anything is sent to it.

Consequently there is nothing to return, no shipping cost to refund, and no delivery fee is ever charged on any order. Domains, licences and certificates you add are also issued electronically by their vendors and are activated, not shipped.

How your order arrives

  • A running instance.Created on our hypervisor in the region you chose.
  • An email with credentials.IP, username, initial password or SSH key instructions, and panel login.
  • Access in the client area.Console, VNC, snapshots, firewall and reinstall controls.
  • An invoice.Emailed for every charge and stored in your account.

What never happens

  • No parcel or courier.Nothing is dispatched to any address, in any country.
  • No cash on delivery.Service is activated after payment clears, never before.
  • No delivery or setup fee.The plan price is the whole price for the first cycle.
  • No waiting for business hours.Provisioning is automated and runs 24/7, including weekends and holidays.
Clause 2

Definitions used across all WenHost documents

TermMeaningWhere else it is used
Order placedYou completed checkout and payment was authorised.Terms clause 5
Payment confirmedThe provider cleared the charge; the clock for provisioning starts here.Terms clause 7
ProvisioningAutomatic creation of the instance, storage volume and network attachment.This policy, clause 4
Service delivery completedThe moment defined in clause 3. Our obligation is met from this point.Refund Policy, Terms clause 5
Activation timestampThe recorded UTC time of delivery completion, stored in your order log.Refund windows, SLA
RegionOne of the twelve datacenter locations you select at checkout.Terms clause 3
Business dayMonday to Friday, excluding Vietnamese public holidays.Refund Policy, SLA

All time windows in every WenHost document are counted in continuous hours and days from the activation timestamp, in UTC as stored in our order log — not in business hours, and not from the payment date.

Clause 3

"Service delivery completed" — the defining clause

Delivery is complete at the earliest of these three events. The first one to occur is the moment that counts, and it is recorded automatically.

  1. Event A

    The instance is Running and reachable

    The VPS reports Running in the client area and answers a network probe from our monitoring outside your server. This is the usual trigger and normally happens within a minute of payment.

  2. Event B

    Credentials are delivered

    Root or Administrator credentials are successfully delivered to your registered email — accepted by the receiving mail server, with no bounce. Where a provider returns a delivery receipt, we keep it.

  3. Event C

    You take control first

    You log in to the instance, the VNC console, or that order's management screens before A or B is recorded. Your own action evidences that the service reached you.

What this starts. The activation timestamp begins the 72-hour refund window on every new VPS order and the 7-day money-back guarantee on your first order, exactly as defined in the Refund Policy. It also starts your billing period and your SLA measurement month. A bounced credential email does not count as delivery — if your mailbox rejects it, tell us and we re-send, and the clock starts from the successful re-send.

If none of A, B or C occurs within the times in clause 4, delivery has not taken place and clause 12 applies — you are not required to chase us for a refund you are already owed.

Clause 4

Time to deliver, by order type

Times run from payment confirmation. They are our service targets, and the commitment line is the last column.

Order typeTargetCommitmentNotes
New VPS — Linux template, in-stock region~45 secondsWithin 1 hourFully automated, 24/7.
New VPS — Windows Server template2–10 minutesWithin 2 hoursLicence issue adds time.
First order on a new accountUnder 2 hoursWithin 4 hoursManual fraud and sanctions review.
PayPal-funded order, first paymentUnder 2 hoursWithin 4 hoursClearance depends on PayPal.
USDT / crypto settlement5–30 minutesWithin 2 hoursStarts after required network confirmations.
Upgrade — CPU, RAM, diskUnder 5 minutesWithin 1 hourOne reboot; data untouched.
Extra IPv4 addressUnder 15 minutesWithin 4 hoursSubject to regional stock.
Reinstall to a different OS1–3 minutesWithin 1 hourDestructive — snapshot first.
Region change / live migration15–60 minutesWithin 24 hoursDepends on data volume.
Free single-server migrationWithin 24 hoursWithin 3 business daysStarts when you approve the plan.
Custom ISO install2–4 hoursWithin 1 business dayReviewed before booting.

Where a commitment is missed and the cause is ours, the remedy in clause 12 applies automatically — you do not have to invoke it.

Clause 5

Order review, holds and declined orders

Some orders are held briefly before provisioning. A hold is a check, not a rejection, and it never exceeds the times in clause 4.

  • Why an order may be held: first payment on a new account, a PayPal dispute history on the payer identity, a billing country or IP mismatch, a sanctioned destination, an unusual order value, or a workload that needs AUP confirmation such as mail sending or mining.
  • What you see: the order shows Pending review in the client area and we email you the reason in plain terms and the expected release time.
  • What we never do: hold an order silently, or ask you to upload identity documents as a routine step. Verification is requested only where a specific check requires it, and is handled under the Privacy Policy.
  • If we decline: nothing is charged, or anything already captured is refunded in full to the original payment method, and we state the reason unless legally prevented.
Clause 6

What is included in delivery

At the moment of delivery your instance is complete and usable, not a shell waiting for a second step.

Compute & storage

The vCPU, DDR5 ECC RAM and Gen4 NVMe capacity of the plan you ordered, on RAID-10, with the transfer allowance and 1 Gbps port shown on the plan page.

Network identity

Your IPv4 address (and IPv6 prefix per plan), reverse DNS settable from the panel, and attachment to always-on layer 3/4 DDoS filtering.

Control & recovery

Client-area access, VNC console, reboot, reinstall, firewall controls, the REST API, and daily snapshots enabled with 7-day retention.

Delivery does not include operating-system configuration, control-panel installation, web-server setup or application deployment on unmanaged plans — see clause 4 of the Terms of Service for that boundary. Optional Managed Care and migrations are separate, bookable services.

Clause 7

Operating system templates available at delivery

You choose the template at checkout or reinstall later from the panel. Clean templates boot as part of provisioning; anything unusual is reviewed first.

  • Ubuntu 20.04 LTS x64
  • Ubuntu 22.04 LTS x64
  • Ubuntu 24.04 LTS x64
  • Debian 11 x64
  • Debian 12 x64
  • CentOS 7 x64
  • AlmaLinux 8 x64
  • AlmaLinux 9 x64
  • Rocky Linux 8 x64
  • Rocky Linux 9 x64
  • Fedora 41 x64
  • Fedora 42 x64
  • Windows Server 2019
  • Windows Server 2022
  • Windows Server 2025

Windows templates require the licensed Windows add-on, billed monthly and shown separately at checkout; that licence is issued by the vendor and is non-refundable once issued, per the Refund Policy. Templates reach end of life on their vendor schedule — we announce retirements at least 30 days ahead and keep older templates installable while the vendor still supports them.

Clause 8

IP addresses, reverse DNS and reputation

  • Allocation: your IP is assigned during provisioning and is yours while the instance is open. Plan IP counts are in clause 3 of the Terms of Service.
  • Reverse DNS (PTR): set it yourself in the panel, or ask us. We approve records that point at a domain you control and refuse those that impersonate another owner.
  • Extra addresses: delivered per clause 4, billed monthly, and non-refundable once assigned.
  • IP replacement: if an address arrives on a public blocklist through no fault of yours, tell us within 7 days of delivery and we replace it free.
  • Reputation is not guaranteed: we provide clean subnets and removal assistance, but we cannot promise any mailbox lands in an inbox. Sending bulk mail requires prior written approval under the AUP.
  • Return on termination: addresses come back to our pool after the release timeline in clause 9 of the Terms of Service, so request a new allocation if you relaunch later.
Clause 9

Region selection and availability

You choose the region at checkout and your content stays there, as stated in the Privacy Policy. Delivery is made in the region ordered; we do not relocate an instance without your instruction except for a documented hardware failure, and then only to an equivalent or better location.

RegionTypical provisioningNotes
Amsterdam, NLUnder 60 sOriginal site; carries our core control plane.
Ashburn · Los Angeles · New York, USUnder 60 sHighest capacity, all templates available.
Toronto, CAUnder 60 sStandard template set.
London · Frankfurt · Paris · Milan, EUUnder 60 sEU jurisdiction; Windows add-on available.
Singapore · Tokyo, APAC1–5 minCapacity released in waves at peak.
Sydney, AU1–5 minSmaller pool; extra IPs subject to stock.

If a region is out of stock we tell you at checkout rather than taking payment and waiting. If stock runs out after you paid, you choose: wait with a stated ETA, move to another region, or a full refund — and that refund is not treated as a money-back guarantee claim, because delivery never happened.

Clause 10

Migration delivery — moving in from another host

One server migration is free per new VPS subscription. It is a scheduled service, so its clock starts when you supply access, not when you pay.

  1. Step 1 · you open the ticket

    Send the details

    Source IP or control-panel access, the accounts and databases to move, and a maintenance window you accept. We never start without written approval of the plan.

  2. Step 2 · within 24 h

    Copy and test

    We replicate to the new VPS, boot it on a temporary host or IP, and you verify the site or application works. Your live service is untouched throughout.

  3. Step 3 · you approve

    DNS cutover

    You lower TTLs, we point traffic, and propagation typically completes within 24 hours depending on your DNS provider — not on us.

  4. Step 4 · after cutover

    Source kept 7 days

    We leave the source untouched for 7 days so rollback is trivial, then you close it with your old host.

Complex migrations — many accounts, mail with large mailboxes, databases over 100 GB, or platforms without standard APIs — are quoted a specific schedule instead of the 24-hour target. Migrations are performed to the boundary of copying data and starting services; application-level fixes remain your responsibility on unmanaged plans.

Clause 11

Rebuild, reinstall and resize

  • Resize: CPU, RAM and disk grow from the panel in under five minutes with one reboot. Shrinking disk requires a rebuild, and we tell you before you click.
  • Reinstall: replacing the OS template erases the disk. The panel warns you and offers a snapshot first; take it. A reinstall is a new delivery of the same instance, so the activation timestamp for that instance updates while your billing cycle does not.
  • Rescue mode: boot a live environment to repair a broken configuration without losing data, available at any time.
  • Rollback: restore any snapshot within its 7-day retention; the instance is briefly offline during restore.
  • Region change: treated as a migration under clause 10, with the data volume as the deciding factor.
Clause 12

When delivery fails — your remedies

If the commitment column in clause 4 passes without an event under clause 3, delivery has failed and one of these applies. We do not require you to choose the option that favours us.

SituationWhat you getEffect on guarantee
Not delivered within the commitmentFull refund, or a stated ETA you may acceptDoes not use your one-time guarantee
Delivered but unreachable, our faultFix inside 4 h or full refundDoes not use your guarantee
Wrong specification deliveredCorrected, or pro-rata credit, or refundYour choice
Region out of stock after paymentWait, relocate, or refundDoes not use your guarantee
Inside 72 h of activation, any delivery fault72-hour refund under the Refund PolicySeparate from the guarantee
First order, no fault, change of mind7-day money-back guaranteeConsumes your one-time guarantee
Delay caused by you — bad access, unreachable mailClock pauses until you respondNo effect

Refunds for failed delivery follow the standard mechanics: written decision within 24 hours, issued to the original payment method within 1–3 business days, typically visible within 10 business days. Because nothing was delivered, there is nothing to release and no data to destroy.

The distinction that matters: a failed-delivery refund is a remedy for our non-performance, available on every order and unlimited. The 7-day money-back guarantee is a courtesy for a change of mind, limited to one per customer. We never charge you our courtesy against your remedy.

Clause 13

Cancelling before delivery

You may cancel any order before delivery completes, from the client area or by ticket, and anything paid is refunded in full to the original method without touching your guarantee. Once delivery completes under clause 3, the refund windows in the Refund Policy govern instead.

If you cancel while an order is held for review (clause 5), the hold is dropped and the refund is issued as a failed-delivery refund, because the service was never delivered.

Clause 14

Maintenance, interruptions and how they are announced

  • Scheduled maintenance is announced at least 48 hours ahead on the status page and by email, kept under one hour per month per region, and normally run 02:00–05:00 local time at that datacenter.
  • Emergency maintenance — a critical security flaw or failing hardware — may run without notice. We post it as it happens and follow with a written explanation.
  • Live migration of your instance for hardware reasons is scheduled with you where possible and is normally a sub-minute pause.
  • Excluded from delivery timing: planned maintenance announced under this clause does not extend the clause 4 commitments, but it does count toward the SLA if it exceeds the stated allowance.
  • Uptime and credits are measured and paid under clause 13 of the Terms of Service: 99.99% monthly commitment, credits of 5% or 10% of the monthly fee by severity, up to 100%, claimed within 14 days.
Clause 15

Proof of delivery — the record we keep

This is the clause that ends an "item not received" claim quickly, in your favour or ours, using facts rather than assertion. For each order we retain, and will share with you or your payment provider on request:

System evidence

Provisioning log with the UTC activation timestamp, hypervisor event history, network probe results proving reachability, and the IP allocated.

Delivery evidence

Mail server acceptance records for the credential email, invoice number and PDF, and the client-area access log showing first login.

Interaction evidence

Order IP, ticket transcripts, console sessions, and any instruction you gave us — the same records described in the Privacy Policy under retention.

We will not claim delivery on the strength of a payment alone, and we will not dispute a "not received" claim we cannot evidence. If our records are inconclusive, the refund is issued.

Clause 16

What we need from you for delivery to succeed

  • A mailbox that accepts mail. Whitelist our sending domain; a rejected credential email delays delivery and, under clause 3 event B, delays your own refund clock.
  • Accurate billing details. A mismatched country or name can trigger the review in clause 5.
  • A workload you can describe. Mail sending, mining, game servers and high-fanout streaming need prior AUP confirmation — tell us at checkout, not after delivery.
  • Access for migrations. Source credentials and an approved window; our clock starts when both exist.
  • Your own backup. Delivery includes 7 days of snapshots, not a substitute for your copy (clause 11 of the Terms of Service).
Clause 17

Delays outside our control

Clause 20 of the Terms of Service applies to delivery. Where a natural disaster, war or civil unrest, government or regulator action, an upstream carrier failure, a power-grid outage at a datacentre despite N+1 provision, a widely exploited vulnerability requiring emergency patching, or a labour dispute not involving our staff prevents delivery on time, the commitment clock is extended by the period of the event and we keep you informed on the status page.

Even then, you are never left paying for nothing: if delivery cannot be completed within 24 hours of the original commitment, you may cancel and receive a full refund, which the event does not reduce.

Clause 18

Changes to this policy, and its place among the documents

The version and effective date at the top of this page show the text in force; superseded versions are available on request. Material changes are announced by email and on the status page at least 14 days before taking effect, matching the standard in the Terms of Service and Privacy Policy, and the version in force when you ordered governs that order.

Order of precedence, stated identically in every WenHost document: on refund eligibility the Refund Policy governs; on prohibited content the Acceptable Use Policy; on uptime measurement and credits the SLA; on delivery timing and the definition of delivery this policy; on everything else the Terms of Service. Where two documents still conflict, the reading most favourable to the customer applies.

Governing law: Viet Nam, without regard to conflict-of-law rules, and without removing any non-waivable consumer right you hold where you live. Nothing in this policy limits your statutory rights, including any withdrawal or remedy period that law grants you beyond the windows stated here.

Delivery questions, answered

Short answers, each pointing at the clause that governs it.

How long until my VPS is ready?

About 45 seconds for a standard Linux template in an in-stock region, 2–10 minutes for Windows, and up to 2 hours if a first order or PayPal payment needs manual review. The commitment column in clause 4 is the number you can hold us to.

Do you ship anything, or charge for delivery?

No, and no. Every product is delivered electronically, so there is no courier, no tracking number and no delivery fee on any order. The address you enter is for billing and tax only (clause 1).

When exactly does my 72-hour refund window start?

At the activation timestamp — the earliest of the instance running and answering a probe, credentials reaching your mailbox, or you logging in first (clause 3). It is measured in continuous hours in UTC from our order log, not from the moment you paid.

What if you never deliver my server?

You get a full refund or a stated ETA you may accept, and it does not consume your one-time money-back guarantee, because a failed-delivery refund is a remedy for our non-performance rather than a courtesy (clause 12).

The credential email never arrived. Am I out of luck?

No. A bounced or rejected email is not delivery under clause 3, so your refund clock has not started. Tell us through the contact form and we re-send; the clock starts from the successful delivery.

Can I move my server to another region later?

Yes. A region change is handled as a migration under clause 10, typically 15–60 minutes depending on data volume, with a 24-hour commitment. Old copies are destroyed on the retention schedule in the Privacy Policy.

Do you keep proof that you delivered?

Yes — provisioning logs with the UTC timestamp, network probe results, mail acceptance records, the invoice, and first-login logs (clause 15). If our records are inconclusive, we issue the refund rather than argue.

Order stuck, or delivery not what you expected?

Open a ticket with your order ID and we will tell you the activation timestamp, the evidence behind it, and the remedy that applies — in writing, within 24 hours. If we did not deliver on time, the refund is automatic and your money-back guarantee stays unused.

Version 3.0 · Effective 29 October 2026. This page states WenHost delivery terms for electronically supplied services and is not legal advice. Where these terms and the Refund Policy differ on refund eligibility, the Refund Policy applies.