Acceptable Use Policy
Short list of bans, long list of things you may run
Legal · Version 3.0
Acceptable Use Policy — what your server may not do.
You have root, so you carry the responsibility that comes with it. This policy is the complete list of workloads we cannot host on WenHost — an independently run hosting business registered in Viet Nam — and, just as importantly, how we enforce it: what evidence we require before acting, how much notice you get, what happens at each step, and how to appeal. It is written so that a legitimate customer is never surprised by a suspension, and never left guessing about why one happened.
Effective 29 October 2026 · Incorporated into the Terms of Service
- Evidence before action
- Notice in writing
- Right to appeal
- No routine monitoring
Three principles behind every clause
If a decision is ever unclear, these three rules decide it — in this order.
1Evidence, not accusation
We act on a specific, dated, reproducible report: the offending IP, the timestamp, the payload or log, and the complainant's identity. An anonymous "your IP is spamming" with no artefact gets a request for evidence, not a suspension.
2Proportionate, always
A misconfigured newsletter gets a notice and a fix window. An active botnet getting traffic out of your server gets powered off within minutes. The response matches the harm, and clause 17 states exactly which step applies to which category.
3Declare first, run second
Most "prohibited" items become permitted with a sentence at checkout: mail sending, mining, game servers, high-fanout streaming, VPN endpoints. Tell us the workload before delivery and we will tell you honestly whether we can serve it well.
Why this document is worth reading before you order. A breach of this policy is the single largest cause of non-refundable terminations at WenHost. The Refund Policy excludes orders terminated for AUP breach from both the 72-hour window and the 7-day money-back guarantee, and clause 8 of the Terms of Service makes these obligations contractual. Reading clause 6 and clause 9 takes two minutes and prevents the most expensive mistake in budget hosting.
Scope — who and what this policy binds
This policy applies to every WenHost service: VPS instances, extra IP addresses, private VLANs, snapshots, load balancers, managed care, migrations, and the use of our network to reach any of them. It binds you, anyone you give access to your account or server, and every customer of yours whose traffic passes through a service you run on our infrastructure.
It is incorporated into the Terms of Service by clause 8 and forms part of your contract. Where this policy and the Terms differ on prohibited content and network abuse, this policy governs; on refund eligibility the Refund Policy governs; on personal data the Privacy Policy governs.
It applies equally to trial, promotional, discounted and full-price instances, and to servers that are idle. A server that does nothing still may not be used as a source of traffic to others.
Definitions used in this policy
| Term | Meaning |
|---|---|
| Your service | Your instance, its disks, its IP addresses, and anything reachable through it. |
| Third party | Anyone who is not you and not WenHost — including your own users and customers. |
| Abuse | Use of your service that harms, threatens, defrauds, or imposes unagreed cost on a third party or on shared infrastructure. |
| Outbound abuse | Harm originating from your service: spam, attacks, malware distribution, scanning, credential guessing. |
| Credible report | A dated report naming the offending IP, the time, the evidence, and a verifiable complainant. |
| Declared workload | A workload you told us about before ordering and we confirmed in writing. |
| Suspension | Instance powered off and network disabled. Data intact, restorable. |
| Termination | Instance released and disks destroyed on the schedule in clause 9 of the Terms of Service. |
What you may run — the permitted list
The list of permitted uses is deliberately far longer than the list of bans. If it is legal, does not harm third parties, and fits the resources you paid for, it is allowed.
- Websites & WooCommerce
- Web applications & APIs
- Staging & CI runners
- Databases
- Game servers (declared)
- Voice servers (declared)
- Private VPN for your own use
- Mail for your own domain (approved)
- Development & test labs
- Data processing & ETL
- Media storage you own
- Monitoring & alerting stacks
- Bots & automation you operate
- File sync for your team
- Learning & research
- Self-hosted productivity tools
Two categories need a sentence from you before delivery, because they are the two most common causes of collateral damage: outbound email (clause 6) and sustained heavy compute such as mining (clause 9). Declaring them is not an admission of guilt — it lets us assign a clean subnet, size the capacity, and tell you honestly if we are the wrong host for the job.
Illegal content and activity — zero tolerance
✕ Never permitted, in any jurisdiction we serve
- Child sexual abuse material or any exploitation of minors.Immediate termination, no notice, no refund, and an unconditional report to the relevant authority — we do not wait for a request.
- Terrorist content and recruitment, including material inciting or facilitating violence against people.
- Fraud, phishing and credential theft — including look-alike login pages, spoofed domains and infrastructure used to direct victims to them.
- Non-consensual intimate imagery and any content that stalks, harasses or threatens an identifiable person.
- Facilities for illegal goods and services — marketplaces, payment processing or logistics for controlled substances, weapons, stolen data or documents.
- Money laundering and unlicensed financial services, including schemes prohibited where you are established.
- Gambling or betting services without the licence your target market requires; we ask to see it.
- Any use that breaches export controls or sanctions of Viet Nam, the United States, the European Union or the United Kingdom.
Where content is legal but restricted in a specific market — for example adult content — it is permitted only if you hold every licence and age-verification obligation required where you serve, and you keep it off shared IP blocks on request. We are not a judge of taste; we are a judge of law and of harm to neighbours.
Malware, botnets and compromised servers
- Never: creating, distributing or serving malware, exploits, ransomware, keyloggers, crypters, botnet command-and-control panels, or infrastructure that updates a malicious client.
- Also never: hosting "cracked" software, licence-key generators, or tools whose primary purpose is unauthorised access.
- If your server is hacked: you are not in breach. Tell us, or respond when we tell you, and we will help you contain it — we power off an outbound attack source to protect the network, then hand you the logs so you can rebuild. We do not terminate a victim for being a victim.
- Repeat compromise is different: a server that is re-infected month after month because it is unpatched becomes a threat to other customers, and clause 17 escalates it.
- Scanning your own assets is allowed. Vulnerability scanning of your own IPs and domains is fine; scanning ranges you do not own is clause 7.
Email and spam — the clause that suspends the most accounts
Unsolicited bulk email is the most abused service in hosting and the fastest way to lose a subnet for every customer on it. Our rules are strict and mechanical.
✕ Prohibited
- Unsolicited bulk email.Cold outreach, purchased or scraped lists, and any send where the recipient did not ask for it.
- Open relays and open proxies.Any mail or proxy service that lets a third party send through your server.
- Forged headers and spoofing.Fake sender domains, mismatched reverse DNS, or sending as a domain you do not control.
- Mail from a non-approved instance.Port
25and submission port587are blocked outbound by default on every VPS. - List services run for third parties.Newsletter platforms, SMTP relays and sending appliances sold on to others.
- Ignoring a complaint.Failing to stop a sending problem within the notice window in clause 17.
✓ How to send mail legitimately
- Ask before you order.Tell us the volume, the list source and the domain. Approval is normal for transactional and opted-in lists.
- Use your own domain with SPF, DKIM and DMARC.We will check the records before unblocking port 25.
- Set the reverse DNS we assign.PTR must match the sending hostname; you can set it in the panel.
- Keep a suppression list and honour unsubscribes.One-touch removal, applied immediately.
- Consider a dedicated IP.For high volume we prefer a separate address so your reputation is yours alone.
Unblocking is not permanent. If an approved mailer is listed on two major blocklists within a month, or a complaint arrives with evidence, port 25 is re-blocked while we investigate. That is a protective measure, not a penalty, and it is reversed as soon as the cause is fixed.
Network abuse against other people
✕ Prohibited outbound activity
- Denial-of-service attacks of any kind, including "stress testing" or booter services, and participation in an attack as a reflector or amplifier.
- Scanning or probing networks you do not own, including port sweeps, service enumeration and subdomain brute-forcing against third-party infrastructure.
- Brute-force credential guessing against SSH, RDP, FTP, SMTP, web logins or APIs belonging to others.
- IP spoofing and source-address forgery, or any attempt to appear as traffic that is not yours.
- Exploitation attempts against other customers' instances or against our own control plane and monitoring.
- Unauthorized access to any system, and distribution of access to stolen systems.
- ARP, routing or BGP hijacking inside our network, and announcing address space you do not hold.
- Waterline abuse: deliberately saturating a shared uplink so that neighbours lose capacity.
What is not abuse: receiving an attack. Every instance sits behind always-on layer 3/4 DDoS filtering with 2 Tbps of scrubbing capacity, and being targeted is never a breach by you. If attack traffic against you saturates your region, we may null-route the target IP temporarily to protect neighbours, and we will tell you the moment we do and when it is restored. Layer 7 protection is available as an add-on for application-layer floods.
Resource use and fair use of the network
You bought a defined slice of a shared physical host. Use it hard — just do not use more than you bought in a way that degrades the neighbours.
| Resource | What you may do | What triggers a conversation |
|---|---|---|
| vCPU | Sustain 100% of your cores; that is what you paid for. | Consistent steal time affecting other instances on the node. |
| Memory | Use your full allocation, including heavy caching. | Host-level memory pressure caused by an over-committed workload. |
| NVMe I/O | Burst freely; plans are not IOPS-capped. | Sustained maximum IOPS that degrades the shared array. |
| Transfer | Inbound is never counted; outbound allowance is included in the price. | Sustained use far beyond the allowance — reviewed with 30 days' notice, never billed silently. |
| Port speed | Run at 1 Gbps whenever you have traffic to send. | Permanent line-rate saturation of a shared uplink. |
| Connections | High concurrency for applications and game servers. | Millions of half-open sockets characteristic of an attack tool. |
Where a limit is reached we contact you first with numbers and options — a larger plan, a dedicated host, or a traffic-shaped configuration. We do not throttle without notice and we do not issue surprise overage invoices.
Cryptocurrency mining and sustained heavy compute
- Mining is permitted only when declared and confirmed before delivery. It is a legitimate workload, but it runs a node at permanent maximum utilisation, so it must be planned rather than discovered.
- Undeclared mining is a breach and is the clearest case where we suspend first and discuss after, because it degrades every other customer on the node.
- Pool operators and mining-as-a-service need a separate conversation: we will ask who your miners are and what capacity you hold.
- GPU passthrough is on the roadmap and currently handled case by case — ask before you plan around it.
- Other sustained-compute workloads — video rendering farms, scientific computing, AI inference and training — are welcome under the same declare-first rule. They are usually a better fit on a dedicated host and we will say so.
Proxies, VPNs, tor and anonymisation services
✓ Allowed
- A VPN for your own traffic.WireGuard, OpenVPN or IPsec carrying only your own connections, declared at order.
- Private site-to-site links between servers you own.
- Application load balancers and CDNs serving content you own or are licensed to serve.
- Development tunnels for testing your own applications.
✕ Not allowed
- Open proxies and public resolvers.Any service relaying traffic for unidentified third parties.
- Commercial proxy, rotating-IP or "unblocker" services selling access to our address space.
- Tor exit relays, because they transfer the reputation cost of strangers onto your neighbours.
- Residential-IP resale or bot-proxy clients built on compromised hosts.
- Services whose purpose is to hide the origin of abuse.
If your legitimate VPN or proxy use causes your IP to be blocked by a third-party service, that is between you and them — we will not intervene to restore a reputation we do not control, though we will replace an address that arrived already damaged (clause 8 of the Delivery Policy).
Game, voice and community servers
Game servers are one of our largest workloads and are welcome. Declare the title and expected concurrency at order so we can place you on a region with the right capacity.
- Permitted: Minecraft, Rust, CS2, FiveM, ARK, Valheim, Garry's Mod, TeamSpeak, Mumble, Discord self-hosted alternatives, and competitive or community hosting for your own players.
- Commercial game hosting — reselling slots to the public — is allowed, but tell us: it is a clause 15 sub-user situation and usually warrants a dedicated host.
- Never: server-side cheats, aimbot distribution, account-selling tooling, or content that infringes a game publisher's rights beyond the licence you hold.
- DDoS against your server is not your breach. If a rival floods you, we filter and we tell you what we saw. Persistent targeting may make a protected IP a better fit, and we will suggest it rather than blame you.
- UDP-heavy titles need the port range open in your firewall; that is your configuration, and it is your responsibility not to leave an amplification reflector exposed.
File storage, streaming and high-fanout distribution
- Allowed: serving your own media, private object storage, podcast or video delivery for an audience you own, and game or application updates you publish.
- Not a CDN: a VPS is not built to be a global cache. If you are pushing sustained multi-hundred-TB traffic, ask us about dedicated capacity before you exceed clause 8.
- Never: distribution of copyrighted material without the rights, IPTV restreaming without licences, or file hosts that serve infringing or illegal content — including "private" locker services where the contents are known to infringe.
- Hotlink bait: a storage service open to the public that lets strangers host files is a copyright magnet and is treated as a file host under clause 13.
Intellectual property, takedown requests and repeat infringers
We comply with copyright law in the jurisdictions we operate and we handle notices in writing, with evidence, both ways.
- Receipt
Notice logged and acknowledged
A valid notice needs the work at issue, the exact URL or IP and timestamp, a good-faith statement, contact details, and a statement under penalty of perjury that the complainant is the rights owner or authorised to act.
- Same day
Forwarded to you with the evidence
We send you what we were shown, not a summary of it, and we tell you which item we are asking you to remove.
- Within 24 h
You respond or remove
Remove the material, or reply with a reason — you own the rights, it is licensed, it is fair dealing, or the notice is mistaken.
- Then
Counter-notice honoured
A valid counter-notice is passed to the complainant, and if they do not pursue it we restore the content and confirm in writing.
Repeat infringers on the same account are terminated after a documented pattern, not on a first allegation. We do not act on automated mass notices that name no evidence, and we publish a transparency summary of notices received and acted on.
Your security obligations — the minimum standard
Because one compromised server can harm thousands of strangers, these are duties, not suggestions.
- Change default credentials at first login. Every template ships with a randomised password; do not reuse it elsewhere.
- Run a host firewall. Expose only the ports you serve. The panel firewall is there for exactly this.
- Patch regularly. Unattended security upgrades are strongly recommended on internet-facing hosts.
- Do not disable SSH or key authentication. Password-only root login over the public internet is the single most common entry point we clean up.
- Keep services out of open-resolver and open-relay mode. DNS, SMTP, NTP, memcached, Redis and Elasticsearch bound to
0.0.0.0without authentication have all been used as amplifiers from rented servers. - Monitor your own egress. If traffic spikes without your doing, snapshot and ask us — we will look at the network evidence with you.
- Take your own backup. Included snapshots are our hardware safety net, not your disaster recovery (clause 11 of the Terms of Service).
Failing these is not automatically a breach. It becomes a breach when the result harms others and you do not act inside the notice window in clause 17.
Reselling, sub-users and your own customers
- Reselling is allowed and common. Agencies hosting client sites and communities running paid game servers are ordinary WenHost customers.
- You are responsible for their conduct. A client's spam is your spam to us; you must be able to identify and stop the account behind it within the notice window.
- Tell us when you resell at scale. Public resale of our capacity — selling VPS-like services to anonymous buyers — needs an agreement, because it moves the abuse surface onto our network without moving the controls.
- You are the controller for your customers' data and we are your processor; the Privacy Policy explains what that obliges us to do and what we will forward to you.
- Your terms must not promise what we cannot deliver. If you advertise unmetered bandwidth or unlimited storage on a plan that has a stated allowance, that is your exposure, not ours.
Reporting abuse — what we need from you
If you believe a WenHost server is being used to harm you, report it. We answer abuse mail around the clock, with a target of under 30 minutes for an initial human acknowledgement.
✓ Include this and we can act
- The offending IP and exact UTC timestamps."Yesterday it was bad" is not actionable; a timestamp is.
- Raw evidence.Full mail headers, packet captures, web-server access logs, or the URL and page source.
- What happened to you.Attack, fraud, infringement, harassment — it decides which clause applies.
- Your identity and contact address.We do not act on anonymous accusations against a paying customer.
- Whether you are the rights owner or authorised to act for them, for copyright claims.
✕ What we will not do
- Act on a bare IP list with no evidence attached.
- Hand over customer identity to a private complainant — that goes through a valid legal order.
- Provide legal advice or act as an investigator for a civil dispute.
- Suspend on request alone where the evidence shows legitimate traffic.
- Accept threats of public shaming or mass-reporting as a substitute for a report.
Every action we take is confirmed to the reporter with the outcome category — resolved, no breach found, customer unresponsive, terminated — without disclosing who the customer is. Reports and evidence are retained for 24 months as stated in the Privacy Policy.
The enforcement ladder — published, not improvised
Except for the immediate-action categories in clause 18, we follow these steps and we tell you which step you are on.
| Severity | Examples | First action | Your window |
|---|---|---|---|
| Informational | Blocklist entry, odd egress, misconfiguration | Notice with logs and a fix suggestion | 7 days |
| Low | Unintended relay, exposed Redis, one-off complaint | Ticket with a required reply | 72 hours |
| Medium | Spam source confirmed, scanning a third party, sustained resource harm | Fix required, port 25 or affected service blocked meanwhile | 24 hours |
| High | Repeat offence, undeclared mining, phishing page hosted | Suspension until remediated and evidenced | 24 hours to respond |
| Critical | Clause 18 categories | Immediate suspension, review for termination | Appeal only |
- Step 1
Written notice with evidence
Email and ticket, naming the IP, the timestamp, the artefact and the clause breached. Never a warning without specifics.
- Step 2
Targeted mitigation
Where a single control fixes it — blocking port 25, null-routing an attacked IP, disabling one service — we apply the narrowest measure that stops the harm, and keep your server running.
- Step 3
Suspension
Instance powered off, network disabled, data intact. You can still log in to the client area, open tickets and restore service by fixing the cause.
- Step 4
Termination
For unremedied high-severity or critical breaches. Disks are released and snapshots are kept 7 days, matching clause 9 of the Terms of Service.
Repeat pattern: three notices of the same category within 90 days escalates one level, because the third notice proves the first two did not work.
Immediate action, without the notice window
These are the only cases where we act before we ask. Each is a situation where an hour of delay harms someone who is not us.
- Active child exploitation — terminated and reported immediately, without notice to the account.
- An instance currently transmitting a DDoS attack or functioning as an amplifier against third parties.
- Command-and-control or ransomware infrastructure identified by technical evidence.
- Live phishing collecting credentials from real victims.
- An imminent threat to life or to the integrity of our shared infrastructure.
- A valid court order, regulator instruction or law-enforcement request we are legally bound to obey.
Even here we send you the evidence and the clause within 24 hours of acting, unless legally prohibited, and you keep the full appeal right in clause 19. Immediate action is not a shortcut around due process — it is due process with the order of steps changed, and we document why.
Appeals — how to get a decision reversed
Every suspension and termination is reviewed by a human, and every one is appealable. Roughly one in nine appeals succeeds, which is why we publish that number instead of hiding it.
- Within 7 days
File the appeal
Reply to the notice or use the contact form with the ticket number. State what you believe the evidence shows and what you have changed.
- Same day
Acknowledged with a reviewer named
The appeal goes to someone who did not make the original decision.
- Within 72 hours
Written outcome
Upheld with reasons, or reversed with service restored and any downtime credited under the SLA.
- Then
Second review if still wrong
If you believe the reviewer erred, ask for escalation and the business owner reviews it personally.
Where an appeal succeeds, the suspension period is credited against your next invoice and, if the instance was already released, we restore from snapshot where the 7-day window allows. We will never ask you to admit fault as a condition of restoring service that was wrongly stopped.
Consequences, changes to this policy and governing law
Money and data consequences of a breach
- Refunds: an order terminated for breach of this policy is excluded from both the 72-hour window and the 7-day money-back guarantee, as stated in the Refund Policy. A suspension that is later reversed on appeal is not a breach, and the time is credited.
- Account credit: balances on accounts terminated for critical breaches are refunded only to the original payment method and only for amounts not consumed by legitimate charges.
- Data: released instances follow the retention schedule in clause 9 of the Terms of Service and clause 12 of the Privacy Policy.
- Liability: you indemnify WenHost against claims brought by third parties arising from your breach, per clause 18 of the Terms of Service.
How this policy changes
The version and effective date at the top of this page show the text in force; superseded versions are available on request. Material changes — a new prohibition, a shorter notice window, a broader immediate-action list — are announced by email and on the status page at least 14 days before taking effect, matching the Terms of Service and Privacy Policy, and the version in force when you ordered governs that order. Clarifications that do not reduce your rights take effect immediately with the date updated.
Law, precedence and your other rights
This policy is governed by the law of Viet Nam, without regard to conflict-of-law rules, and nothing in it removes a non-waivable consumer right you hold where you live. On prohibited content and network abuse this policy governs; on refund eligibility the Refund Policy governs; on personal data the Privacy Policy governs; on everything else the Terms of Service. Where two documents still conflict, the reading most favourable to the customer applies.
Eight questions this policy gets most
Direct answers, each pointing at the clause that governs it.
Can I send newsletters from my VPS?
Yes, with prior approval. Port 25 and 587 are blocked outbound by default; we unblock them once you tell us the volume and list source and your domain has correct SPF, DKIM, DMARC and matching reverse DNS (clause 6).
Is crypto mining banned?
No — undeclared mining is. Mining is a legitimate workload that runs a node at permanent maximum utilisation, so it must be confirmed before delivery. Declared mining on appropriately sized capacity is fine (clause 9).
My server got hacked and sent spam. Will you ban me?
Not for being a victim. We power off an active outbound source to protect the network, hand you the logs, and give you the notice window to rebuild. It becomes a breach only if you do not act inside that window (clauses 5 and 17).
Do you monitor what I host?
No routine monitoring, screening or content review. We investigate a specific instance only on a credible report with evidence or a valid legal order, and we show you what we were shown (clauses 16 and 18, and the Privacy Policy).
What happens to my refund if I am terminated for a breach?
An order terminated for breach of this policy is outside both the 72-hour window and the 7-day money-back guarantee (clause 20). If the decision is reversed on appeal it was never a breach, and the downtime is credited.
Can I host my clients' websites?
Yes — agencies and community hosts are ordinary customers. You are responsible for your clients' conduct and must be able to identify and stop the account behind a complaint inside the notice window (clause 15).
Someone filed a copyright notice about my site. Now what?
We forward you the actual evidence the same day, you have 24 hours to remove or respond, and a valid counter-notice goes back to the complainant. Termination follows a documented pattern, never a first allegation (clause 13).
Am I in trouble if my server is attacked?
No. Being targeted is never a breach by you. Every instance sits behind always-on layer 3/4 filtering with 2 Tbps of scrubbing capacity, and if your region needs a temporary null-route to protect neighbours we tell you when it started and when it ends (clause 7).
Not sure your workload is allowed?
Ask before you order, or appeal after a notice. Describe what you plan to run — traffic, list source, concurrency, compute pattern — and we will tell you plainly whether it fits, what we would block by default, and which plan actually suits it. A two-minute answer now beats a suspended server later.
Version 3.0 · Effective 29 October 2026. This policy is incorporated into the WenHost Terms of Service and is not legal advice. Where these terms and the Refund Policy differ on refund eligibility, the Refund Policy applies.
