Privacy Policy

We do not sell personal data — not now, not ever

Legal · Version 3.0

Privacy Policy — what we hold, and why.

This policy explains what personal data WenHost — an independently run hosting business registered in Viet Nam — collects when you open an account or deploy a VPS, the lawful basis for each use, who processes it alongside us, how long we keep it, and how you get it corrected, exported or deleted. It also states plainly what we never touch: your full card number, your server's private content, and your data as an advertising product.

Effective 29 October 2026 · Applies to wenhost.website and all client services

  • No card data on our servers
  • No ad trackers by default
  • Reject equals Accept
  • Answered within 30 days

The short version

If you read nothing else, these six lines are the substance of the 22 clauses that follow. Nothing below contradicts them.

We collect the minimum

Name, email, billing address, payment reference and the technical data needed to run and secure your server. We do not ask for date of birth, national ID or government documents unless a specific legal check requires it, and we say so when it does.

We never see your card

PayPal and card payments run on the processor's hosted, encrypted checkout. We store a transaction reference and the last digits your statement shows — never a full card number, never a CVV.

Your server is private

We do not monitor, screen or read customer content as routine practice. We look at a specific instance only for a credible abuse report or a valid legal order, and we tell you what we were shown.

No trackers by default

Analytics and any non-essential script stay blocked until you accept them. Declining is one click and costs you nothing on the site.

We do not sell or share for ads

No sale of personal data, no disclosure for cross-context behavioural advertising, no data brokerage. Disclosure happens only for service delivery, legal defence, or a valid order.

You stay in control

Access, correct, export or delete your data at any time through the contact form. We answer within 30 days, and deletion is bounded only by tax records we are legally required to keep.

Clause 1

Scope, and who is responsible for your data

This policy covers personal data processed by WenHost, an independently run hosting business registered in Viet Nam, when you visit wenhost.website, open a client account, order or use a VPS or related service, contact support, or pay us. In data-protection terms we act as the controller of your account and billing data, and as a processor of the content stored on your server, which is your data and your responsibility to your own users.

It does not cover third-party websites we link to, the control panels or operating systems of vendors we resell licences for, or your own use of the server to process other people's data. When you host third parties on a WenHost VPS, you become the controller and we are your processor — clause 10 explains what that means in practice.

We apply these standards to every customer worldwide, not only to those protected by the GDPR. Where your local law gives you more, the more protective rule applies to you.

Clause 2

Definitions used in this policy

TermWhat we mean by it here
Personal dataAny information relating to an identified or identifiable living person, including the definitions used in the EU GDPR and the UK GDPR.
Account dataName, email address, client-area credentials and preferences you set.
Billing dataBilling address, invoice records, payment-provider reference and the last digits of a card.
Technical dataIP addresses, server logs, resource metrics and device information tied to your account or instance.
Usage dataPages viewed, clicks and aggregated performance measurements on our website.
Content dataEverything stored or transmitted inside your VPS. Yours, not ours.
ProcessingAny action we take on data: collecting, storing, reading, correcting, sharing or deleting it.
Clause 3

Information we collect

You give us directly

  • Identity and contact: name, email address, and for business orders the organisation name and its registration details if you ask for an invoice in that name.
  • Billing: billing address, country of residence, currency of payment, invoice history, and the payment-provider reference we need to issue a refund to the original method.
  • Account settings: the theme preference, language and currency you choose, and the notification options you switch on.
  • Communications: tickets, chat transcripts, the content of emails you send us, and any attachments you upload to prove a fault.
  • Verification data where a specific check is required — for example the payer name and country returned by PayPal when a refund claim needs identity matching under clause 7.

Collected automatically

  • Server and network telemetry: CPU, memory, disk I/O, bandwidth counters, console sessions, power events and the timestamps we use to measure the 99.99% uptime commitment.
  • Security logs: source IP for logins and API calls, failed authentication attempts, firewall events and DDoS detection records.
  • Website analytics in aggregate and only after consent (clause 9), plus the record of your consent choice itself.
  • Order metadata: the IP address used at checkout, the plan ordered, the activation timestamp that starts the 72-hour and 7-day refund windows, and the promotion code if one was applied.

From third parties

  • Payment providers: confirmation that a charge succeeded or failed, the transaction reference, payer country, and fraud or chargeback notifications.
  • Abuse reporting sources: spam blacklists, upstream network complaints and law-enforcement notices relating to an IP we assigned to you.

We do not collect special category data — health, biometrics, religion, political opinion, sexual orientation or trade-union membership — and we ask you not to send it to us in a ticket. If a ticket arrives containing it, we delete it on sight.

Clause 4

How we collect it

Through the forms on our website and client area, through the checkout and payment-provider callbacks, through the monitoring agents and hypervisor telemetry on our own infrastructure, through cookies and equivalent browser storage (clause 8), and through your correspondence with support. We do not buy personal data from brokers, we do not scrape it from social networks, and we do not collect it from any third party except the payment and abuse sources named above.

Clause 5

Why we process it — purpose, data and lawful basis

PurposeData usedLawful basis
Deliver and operate your VPSAccount, technical, content dataPerformance of contract
Take payment and issue refundsBilling, payment referencePerformance of contract / legal obligation
Provide support and diagnose faultsAccount, communications, telemetryLegitimate interest (a working service)
Prevent fraud, abuse and refund misuseOrder IP, payer identity, account historyLegitimate interest / legal obligation
Secure the platform and filter DDoSNetwork and security logsLegitimate interest (service integrity)
Send service notices, invoices, maintenance alertsEmail, account dataPerformance of contract
Send marketing newslettersEmail, consent recordConsent — never required to buy
Improve the website with analyticsConsented usage dataConsent
Comply with tax, accounting and retention lawInvoices, billing dataLegal obligation
Respond to valid legal orders and defend claimsRelevant records onlyLegal obligation / legitimate interest

Where we rely on legitimate interest we have assessed it against your rights and keep the assessment on file. You may object to any processing based on legitimate interest, and clause 15 explains how.

Clause 6

What we never do with your data

Prohibited even against your consent

  • Selling or renting personal data.No data brokerage, no "advertising partners", no revenue from your information.
  • Sharing for cross-context behavioural ads.We do not feed customer lists to ad platforms.
  • Reading your server content routinely.Disks are not browsed, mailboxes are not opened, databases are not queried for our benefit.
  • Storing card numbers or CVV.Technically impossible on our systems — the processor holds them.
  • Profiling for pricing.The plan price is the same for every customer at the same moment; no dynamic pricing from your data.

What we do instead

  • Collect the minimum field set.If a form field is not needed to serve or bill you, it is not on the form.
  • Purpose limitation.Data collected for one purpose is not quietly reused for another.
  • Access on a need-to-know basis.Only the staff member handling your ticket sees your record, and their access is logged.
  • Written contracts with every processor.Confidentiality plus security obligations, per clause 10.
  • Delete on schedule.The periods in clause 12 are enforced by job, not by intention.
Clause 7

Refund verification — the identifiers we compare

Our Refund Policy limits the 7-day money-back guarantee to one refund per customer. To apply that rule honestly we compare the identifiers below against account and payment history. This is the only purpose for which these identifiers are used together, and access is restricted to the billing team.

IdentifierWeightWhy we need it
Email addressDecisivePrimary customer key across orders and tickets.
WooCommerce account IDDecisiveLinks orders placed under one login.
PayPal Payer IDDecisiveThe stable identifier PayPal returns for the funding account.
Payer name & countryStrongCatches the same person using different emails.
IP address at order timeSignal onlyNever the sole reason to decline — shared offices and family networks exist.

“Money-Back Guarantee is limited to one refund per customer. Eligibility is determined using account history and payment records. We reserve the right to deny refund requests if multiple accounts, duplicate payment identities, or abuse of the refund policy are detected.”

Refund Policy · Clause 7.2 — the rule this processing exists to apply

If a guarantee claim is declined on this basis, we tell you which identifier matched and invite you to explain. A shared office IP, a family cardholder or a company running several accounts can all be legitimate, and a human reviews every declined claim. Matching data is retained for the fraud-prevention period in clause 12 and is never used for marketing or passed to third parties for scoring.

Clause 8

Cookies and browser storage

We use a short list of cookies and two localStorage keys. Nothing is set for advertising, and nothing non-essential is set before you consent.

Name / keyTypePurposeLife
Session cookieStrictly necessaryKeeps you logged in to the client area.Browser session
CSRF tokenStrictly necessaryProtects forms against cross-site request forgery.Browser session
Consent recordStrictly necessaryRemembers your cookie choice so we never ask twice.12 months
wh-themeStrictly necessaryYour dark or light display preference.Until you change it
wh-currencyStrictly necessaryCurrency shown for display only — invoices and checkout remain USD.Until you change it
Analytics cookieOptionalAggregate, anonymised page statistics.13 months max

Consent rules we hold ourselves to

  • Reject is as easy as Accept. Both buttons are the same size and prominence; closing the banner counts as reject.
  • Nothing is pre-ticked. Optional categories start off.
  • Non-essential scripts are blocked before consent — analytics code is not loaded, not merely disabled.
  • Withdraw any time from the Cookie Settings link in the footer; your choice is honoured on the next page load.
  • Declining does not degrade the site or the price you pay.

You can also block or delete cookies in your browser. Doing so will sign you out of the client area and reset your theme and currency choices.

Clause 9

Analytics and advertising

We measure traffic to understand which pages and plans are confusing, and to size capacity. Where analytics run at all, they run only after consent, with IP addresses truncated, no cross-site tracking, no ad-platform pixels and no re-marketing audiences built from your visit.

We do not place advertising cookies, we do not embed social-media trackers, and we do not share identifiers with advertising networks. If we ever add a tool that changes this, this clause is rewritten and the change is announced under clause 21 before it takes effect.

Clause 10

Who sees your data — disclosure and sub-processors

We disclose the minimum data needed, to the fewest parties possible, under written confidentiality and security obligations. We do not disclose to anyone for their own commercial use.

RecipientWhat they receiveWhy
Payment providers (PayPal, card networks)Order amount, items, billing countryTo take payment and refund it
Datacentre operators, 12 regionsFacility access records, nothing about contentRack space, power and connectivity
Upstream network carriersIP allocations and routing dataTo deliver traffic to your server
Transactional email providerYour email address and message contentInvoices, credentials, notices
Business email and ticketingCorrespondence you send usTo answer you and keep a record
Accounting and tax advisersInvoices and payment recordsStatutory accounts and tax filings
Law enforcement or regulatorsOnly what a valid order requiresLegal compliance — see below

Legal requests

We assess every request for validity and jurisdiction before releasing anything, and we narrow it where we can. We notify you if your data is requested unless legally prohibited or if doing so would endanger someone. We do not join voluntary data-sharing schemes beyond what the law requires.

If you host other people on your VPS

You are the controller and we are your processor. We will only process that content on your documented instruction or as the law requires, and we will forward any third-party or authority request that reaches us about your server to you where we are permitted to.

Clause 11

Payment data in detail

Card and PayPal payments are taken on the provider's own hosted, encrypted checkout page. Payment credentials never transit or rest on WenHost systems, which is why we cannot be the source of a card breach and why we cannot send you your full card number back.

  • What we keep: transaction reference, amount, currency, date, status, payer country and the last four digits where the provider exposes them — enough to reconcile an invoice and answer a query.
  • What we never keep: full primary account numbers, CVV/CVC codes, expiry dates, online-banking credentials or PayPal passwords.
  • Checkout currency: all charges are made in USD. The currency switcher on the site is display-only and never affects what you are billed.
  • Cryptocurrency: USDT payments are converted at receipt by our processor; we retain only the settlement reference and wallet hash needed to identify the order.
  • Refunds: returned to the original payment method only, as stated in the Refund Policy.
Clause 12

Retention schedule

We keep personal data only as long as the purpose lasts, then delete or irreversibly anonymise it. The periods below are the maximum, applied by scheduled jobs.

Data categoryKept forReason for the period
Account identity & settingsAccount life + 3 yearsTo reopen an account and honour its history
Invoices & billing recordsUp to 10 yearsTax and accounting law we are required to follow
Refund-verification identifiers5 years from the claimFraud prevention and enforcing one-per-customer
Server telemetry & metrics90 days rollingSLA measurement and capacity planning
Security & access logs90 days rollingIncident investigation
Abuse reports & evidence24 monthsDefending claims and repeat-offender detection
Support tickets & chat24 monthsContinuity of service and dispute evidence
Consent records3 yearsProving we asked properly
Marketing subscriptionUntil you unsubscribeConsent, withdrawn at any time
Instance content & snapshotsDeleted with the server; snapshots 7 days after releaseRecovery window in the Terms of Service

Backups rotate and expire, so a deleted record disappears from backup within the backup cycle even where a live-system deletion is immediate. Data in an anonymised, aggregated form — for example "88% of refund requests approved" — is kept indefinitely because it no longer identifies you.

Clause 13

How we protect your data

In transit and at rest

HTTPS with TLS on every endpoint including the API, HSTS enforced, and encryption for administrative access. Plain-protocol services are never used to move credentials.

Access control

Named accounts, key-based login, two-factor authentication for staff, least-privilege roles, and every administrative action logged to an account, not to a shared password.

Segmentation

Separate management and public VLANs, isolated storage networks, and no shared database between customer-facing and internal systems.

Perimeter defence

Always-on layer 3/4 DDoS filtering with 2 Tbps of scrubbing capacity, stateful edge firewalling and rate limiting on authentication endpoints.

Resilience

RAID-10 Gen4 NVMe, N+1 power and cooling at Tier III+ facilities, daily snapshots kept off the failing disk, and tested restore procedures.

Human process

Written runbooks, post-incident reviews published to the status page, staff training on data handling, and a documented breach procedure in clause 14.

No measure makes a system impenetrable. We commit to reasonable, current-practice security proportionate to the risk — not to a guarantee we could not honour.

Clause 14

Personal data breach notification

If we confirm a breach of unencrypted personal data that is likely to risk your rights, we act on this sequence.

  1. On detection

    Contain and assess

    Affected systems are isolated, evidence preserved, and the scope of data and accounts identified before any statement is made.

  2. Within 72 hours of awareness

    Notify you and the authorities

    Affected customers are emailed what happened, which data categories were involved, the likely consequences, what we have done and what you should do. Where a supervisory authority has jurisdiction, we notify it within the same window.

  3. Within 30 days

    Publish a post-incident report

    A timeline, root cause and the fixes shipped, on the status page. We name our own mistakes.

  4. Ongoing

    Support for affected customers

    Priority handling of related tickets, credential resets where useful, and no charge for any remediation work on your instance caused by our breach.

Breaches of encrypted data where the key was not compromised, and incidents affecting no personal data, are logged internally and assessed but not announced as notifications.

Clause 15

Your rights

You have the following rights over your personal data. We honour them for every customer, whatever your country, subject to the narrow legal exceptions noted.

Access

Ask what we hold about you and receive a copy, free of charge, in a machine-readable format.

Rectification

Correct a wrong name, address or billing detail — most of this you can do yourself in the client area.

Erasure

Request deletion. We must keep invoices for tax law and fraud-prevention records for the periods in clause 12; everything else goes.

Restriction

Pause processing while a dispute about accuracy or lawful basis is resolved.

Portability

Take your account and billing data with you in a structured, commonly used format.

Objection

Object to processing based on legitimate interest; we stop unless we can show compelling grounds that override your interests.

Withdraw consent

Revoke marketing or analytics consent at any time, as easily as it was given. Nothing else breaks.

No sale or sharing

There is nothing to opt out of — we do not sell personal data or share it for behavioural advertising.

Lodge a complaint

With your local data-protection authority, or with the competent authority in Viet Nam. We will not penalise you for using it.

Clause 16

Making a request, and what happens next

Submit any privacy request through the contact form, choosing the topic Legal & compliance. Use the email address on the account so we can match you instantly.

What we need from you

  • The account email and, if relevant, the order ID or server IP.
  • Which right you are exercising — "delete everything" and "give me a copy" are different jobs.
  • Proof of identity only where the request is unusual or high-risk, such as an erasure asked from an address that is not on the account.

What we will not do

  • Charge a fee for a first reasonable request.
  • Ask for documents you did not have to give us in the first place.
  • Delete records the law obliges us to keep — we will tell you exactly which ones and why.
  1. Day 0

    Acknowledgement

    You receive a ticket number and the date the 30-day clock started.

  2. Day 1–10

    Verification and gathering

    We confirm identity and collect the records across billing, support and infrastructure systems.

  3. Day 10–25

    Review of exceptions

    Legal holds, tax retention and third-party data in the same records are assessed and separated.

  4. By day 30

    Response and action

    Data exported, corrected or deleted, with written confirmation of what was removed and what was lawfully retained.

Complex requests may take up to 60 days; if so we tell you within the first 30 and explain the delay. Requests that are manifestly unfounded or excessive may be refused with reasons.

Clause 17

Where your data lives and international transfers

Your server content stays in the region you chose at checkout — one of twelve datacenters in North America, Europe, Asia-Pacific and Australia. Account and billing records are processed at our place of business in Viet Nam and replicated inside our infrastructure for availability.

If you are in the EEA, UK or Switzerland, your data may therefore be processed in Viet Nam or another region where our providers operate. We rely on safeguards: contractual confidentiality and security terms with every processor, encryption in transit, access control, and standard-contract-style clauses with providers where their terms offer them. We will tell you which safeguard applies to a specific transfer if you ask.

Choosing a region is yours, and moving a live VPS between regions from the dashboard moves the content with it — old copies are destroyed on the schedule in clause 12.

Clause 18

Children

Our services are not directed to anyone under 18, and clause 2 of the Terms of Service requires you to be an adult able to contract. We do not knowingly collect personal data from children. If we learn that a minor has provided data, we delete the account and its records, refund any charge under the Refund Policy, and close the payment method from further orders.

Clause 19

Marketing communications

Marketing email is opt-in only. The checkout box for it is never pre-ticked, and declining it has no effect on your order, your price or your support queue. Every campaign carries your name, identifies us, and includes a one-click unsubscribe that works without logging in.

Transactional messages — invoices, credential delivery, maintenance notices, suspension warnings, SLA credit confirmations — are part of the service you bought and continue while your account is open. You cannot opt out of a maintenance notice any more than you can opt out of a fire alarm, and that is for your protection.

We do not buy mailing lists, do not send cold email, and do not pass your address to any third party for their own marketing.

Clause 20

Automated decision-making and profiling

Provisioning is automatic, and so are a few checks: fraud screening on first orders, DDoS detection, and resource-threshold alerts. None of these produces a legal or similarly significant decision about you based solely on automation.

Specifically: every refund decline, every AUP suspension and every account termination is made or confirmed by a human, and you may ask us to reconsider it with your own evidence. We do not build behavioural profiles of customers and do not use automated scoring to set your price.

Clause 21

Changes to this policy

The version number and effective date at the top of this page always show the text in force; superseded versions are available on request. A change never applies retroactively to reduce rights you already exercised.

If we make a material change — new categories of data, a new purpose, a new sub-processor with real consequence, or a shorter retention period — we announce it by email and on the status page at least 14 days before it takes effect, matching the notice standard in the Terms of Service. Editorial clarifications that do not change your rights take effect immediately with the date updated.

Clause 22

Governing law, complaints and this policy's place

This policy is governed by the law of Viet Nam. It works alongside the Terms of Service, the Refund Policy, the Acceptable Use Policy and the SLA; where the Terms and this policy differ about personal data, this policy governs, and where they differ about refund eligibility, the Refund Policy governs.

If you are unhappy with how we handled your data, raise it with us first through the contact form — we answer privacy complaints as priority tickets. You also have the right to complain to your local data-protection authority or to the competent authority in Viet Nam, and we will not disadvantage you for doing so.

Seven privacy questions we get most

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

Do you read what is on my server?

No, not as routine practice. Your instance is private and we do not browse disks, open mailboxes or query databases. We investigate a specific server only when we receive a credible abuse report or a valid legal order, and we tell you what we were shown (clauses 1, 6 and 10).

Why do you keep my order IP address for five years?

Only the order-time IP and the related payment identifiers, and only to apply the one-refund-per-customer rule and detect fraud (clauses 7 and 12). It is never used to profile you, never sold, and an IP alone is never the reason a claim is declined.

Can you send me everything you hold about me?

Yes. Ask through the contact form under Legal & compliance and you receive a machine-readable copy within 30 days, free (clauses 15 and 16).

If I delete my account, is everything really gone?

Everything except what the law obliges us to keep: invoices for tax purposes and the refund-verification records for the fraud-prevention period. We tell you exactly which records remain and on what legal ground (clauses 12 and 16).

Do you use Google Analytics or Facebook pixels?

No advertising pixels and no cross-site trackers. Analytics, where used, runs only after consent, with truncated IPs and no ad-platform integration (clauses 8 and 9).

Where is my data physically stored?

Server content stays in the region you chose at checkout. Account and billing records are processed from our place of business in Viet Nam, with the transfer safeguards in clause 17.

What happens if you are breached?

Containment first, then notification to affected customers within 72 hours of confirmation with the facts and what to do, and a published post-incident report within 30 days. Remediation work on your instance caused by our breach is free (clause 14).

Want a copy of your data, or want it gone?

Privacy requests are handled as priority tickets and answered within 30 days — choose the topic Legal & compliance and tell us which right you are exercising. No fee, no form to print, no retention script.

Version 3.0 · Effective 29 October 2026. This policy describes WenHost data handling and is not legal advice. Where your local law grants broader rights than those listed here, the broader rights apply to you.