Rules for fair and lawful use

Last updated: 18 May 2026

This acceptable use policy forms part of the terms that apply to LiquidServers services. It is designed to protect the platform, our customers, your customers, upstream suppliers, internet users, and the reputation and stability of shared infrastructure.

1. Lawful use only

Services must only be used for lawful purposes. You must ensure that your own activities, and the activities of your users, customers, resellers, sub-resellers, staff, contractors, and anyone else using services under your control, comply with applicable laws and regulations. You must not use the services to host, transmit, store, promote, facilitate, or link to content or activity that is unlawful in the United Kingdom or in any jurisdiction that applies to you, your users, or the affected parties.

You are responsible for understanding the legal and regulatory requirements that apply to your websites, applications, customers, email campaigns, data processing, industry, and target markets. We may decline, suspend, or remove content or services where we reasonably believe continued operation would expose us, our suppliers, or third parties to legal or operational risk.

2. Prohibited activities

You must not use the services for spam, phishing, malware, botnets, denial-of-service activity, unauthorised scanning, credential theft, copyright infringement, fraud, deceptive activity, illegal content distribution, sanctions evasion, impersonation, harassment, extortion, or attempts to gain unauthorised access to systems, networks, accounts, or data.

Prohibited activity includes hosting command-and-control infrastructure, exploit kits, credential harvesting pages, fake login pages, malicious redirects, carding shops, scam landing pages, unlicensed software distribution, stolen data, unlawful marketplaces, traffic exchange abuse, proxy abuse, or tools whose primary purpose is unauthorised intrusion or disruption.

3. Email, messaging, and spam

You must not send, permit, or assist unsolicited bulk email, spam, mail bombing, list bombing, snowshoe campaigns, deceptive email, forged headers, open relay activity, or messages that violate applicable anti-spam rules. Mailing lists must be permission-based, include accurate sender information, and provide a working unsubscribe process where required.

You are responsible for monitoring outbound mail generated by websites, scripts, plugins, compromised mailboxes, contact forms, customer accounts, and automated systems under your control. We may rate-limit, block, filter, suspend, or require remediation where email activity threatens platform reputation, IP reputation, deliverability, or third-party systems.

4. Security abuse and unauthorised access

You must not scan, probe, attack, intercept, disrupt, or attempt to access systems, networks, accounts, or data without authorisation. This includes brute-force attacks, credential stuffing, password spraying, vulnerability exploitation, port scanning without permission, packet sniffing, session hijacking, bypassing access controls, or using our services as a staging point for attacks.

Security research, penetration testing, vulnerability scanning, load testing, or similar activity must be authorised in advance where it could affect our platform, shared resources, third parties, or downstream customers. We may require scope, timing, source IP addresses, target systems, and proof of authorisation before allowing such activity.

5. Malware and harmful code

You must not host, distribute, promote, or link to malware, ransomware, spyware, trojans, worms, droppers, malicious scripts, exploit payloads, cryptominers installed without clear consent, or code designed to damage, disrupt, exfiltrate, conceal, or gain unauthorised access. This restriction applies even if the material is hosted for testing, archiving, research, or demonstration unless we have expressly approved the use case in writing.

If a website, account, mailbox, script, or application under your control is compromised, you must act promptly to contain the compromise, remove harmful files, patch the underlying cause, rotate credentials, and cooperate with our investigation. Repeated compromise caused by poor maintenance may be treated as a breach of this policy.

6. Content standards

You must not use the services to host or distribute content that infringes intellectual property rights, violates privacy rights, impersonates another person or organisation, facilitates fraud, promotes unlawful violence, enables illegal goods or services, or otherwise creates material legal or operational risk. You must have the rights, licences, permissions, and consents needed for content you host or distribute.

We do not actively pre-screen all customer content, but we may investigate reports and take action where content appears unlawful, abusive, fraudulent, infringing, harmful, or inconsistent with this policy. We may require you to remove content, provide evidence of rights, identify a downstream customer, or explain the purpose of a service.

7. Resource usage and network fairness

Although plans may be described as unmetered within normal service expectations, abusive, excessive, or destabilising activity is not permitted. Shared and reseller hosting depends on fair use of CPU, memory, disk I/O, process count, inode count, database connections, email queues, backup systems, network capacity, and other shared resources.

We may intervene where traffic, workloads, cron jobs, scripts, database queries, backups, file storage patterns, cache behaviour, or automation activity create operational or security risk for the wider platform. Intervention may include throttling, rate limits, process termination, temporary isolation, service recommendations, migration to a more suitable plan, or suspension in urgent cases.

8. Storage and backup misuse

Hosting storage must be used for active website, application, email, and account content connected with the service purchased. You must not use shared or reseller hosting primarily as a backup archive, file dump, media warehouse, software mirror, public download repository, log warehouse, remote storage drive, or other storage-heavy use that is unrelated to ordinary hosted services unless the plan expressly permits that use.

We may ask you to reduce stored files, remove redundant archives, delete unlawful or abusive material, optimise backups, or move high-storage workloads to a more appropriate product. Backup retention provided by us, if any, may be limited by product type, account status, abuse history, available capacity, and technical feasibility.

9. Reseller responsibility

Resellers remain responsible for the conduct of downstream users. You must maintain suitable customer vetting, abuse handling, suspension rights, security expectations, and terms that allow you to enforce this policy against your own customers, resellers, sub-resellers, and end users.

You must respond to abuse complaints promptly, identify responsible downstream accounts when requested, preserve relevant logs where available, and cooperate with requests for information or remediation. If you repeatedly fail to control downstream abuse, we may restrict reseller features, suspend individual accounts, require improved controls, or terminate the reseller service.

10. Account and credential security

You should keep systems patched, use strong and unique passwords, enable multi-factor authentication where available, protect management interfaces, restrict administrator access, monitor login activity, remove unused accounts, and take reasonable steps to prevent compromise. Negligent security practices that expose the platform or third parties to significant risk may be treated as policy breaches.

You must not share account credentials publicly, sell access to management panels, bypass authentication controls, or allow unauthorised parties to use your account. If credentials are exposed or suspected to be compromised, you must rotate them promptly and review account activity.

11. Automation, APIs, and control panels

Automation, scripts, APIs, billing integrations, reseller tools, and control panel functions must be used responsibly. You must not automate account creation, resource allocation, email sending, DNS changes, login attempts, support submissions, or other functions in a way that bypasses limits, degrades service, conceals abuse, or creates operational risk.

We may apply rate limits, disable API keys, revoke automation access, or require changes to scripts that make excessive requests, trigger security systems, create duplicate accounts, or interfere with platform reliability.

12. IP addresses, DNS, and routing

IP addresses, DNS services, nameservers, reverse DNS, and routing resources must be used in a way that protects network reputation and availability. You must not use allocated addresses for spam, abuse, evasion, fast-flux hosting, malicious redirection, deceptive domains, unauthorised proxying, or activity likely to result in blacklisting or supplier complaints.

Additional IP addresses may require technical or business justification. We may reclaim, renumber, suspend, or refuse IP resources where required by supplier policy, registry policy, abuse handling, scarcity, operational needs, or failure to provide accurate justification.

13. Adult, high-risk, and regulated content

Some lawful content or business models may still be unsuitable for our platform because they create elevated legal, payment, security, reputation, or supplier risk. This can include adult content, gambling, financial promotions, investment schemes, pharmaceuticals, health claims, age-restricted products, political campaigning, high-volume affiliate offers, and other regulated or high-complaint activity.

We may require pre-approval, additional information, compliance evidence, age-gating, licensing evidence, or a move to a more suitable service. We may refuse or discontinue high-risk use cases where we cannot support them safely or where upstream suppliers prohibit them.

14. Investigations and cooperation

We may investigate suspected breaches using account records, support history, server logs, network data, public reports, third-party complaints, automated alerts, malware scans, and information supplied by customers, suppliers, rights holders, law enforcement, or security researchers. You must cooperate with reasonable investigation requests and provide accurate information.

Where possible, we will try to give you an opportunity to remediate issues. However, urgent risks may require immediate action before notice is given, particularly where activity involves phishing, malware, spam, attacks, child safety concerns, data exposure, serious legal risk, or harm to platform stability.

15. Enforcement

We may suspend, restrict, filter, null-route, rate-limit, quarantine, remove content, disable email, reset credentials, block ports, terminate processes, disable accounts, revoke reseller privileges, or terminate services where needed to protect our systems, customers, partners, suppliers, or legal position. The action taken will depend on severity, urgency, history, risk, and available remediation options.

Repeated, deliberate, concealed, or severe breaches may lead to termination without refund. We may preserve and share relevant information with payment providers, upstream suppliers, affected networks, regulators, law enforcement, courts, or professional advisers where required or where reasonably necessary to investigate, prevent, or respond to abuse.

16. Appeals and remediation

If you believe enforcement action was taken in error, contact support with the account details, service identifiers, relevant timestamps, and a clear explanation. We may ask for remediation steps, malware reports, customer identification, security changes, or evidence of permission before restoring access.

Restoration is not guaranteed. We may decline restoration where risk remains, where information is incomplete, where activity was serious or repeated, or where an upstream supplier, law, court order, or authority prevents continued service.

17. Changes to this policy

We may update this acceptable use policy to reflect new abuse patterns, supplier requirements, legal changes, security threats, product changes, or operational needs. The current version published on our website applies from its publication date. Continued use of the services after changes take effect will be treated as acceptance of the updated policy.

18. Reporting abuse

Reports concerning abuse, malware, spam, phishing, copyright infringement, security incidents, or network misuse should be directed to sales@liquidservers.example with enough detail for investigation. Useful information includes domain names, URLs, IP addresses, email headers, timestamps with time zone, screenshots, log extracts, affected accounts, and a description of the suspected abuse.

We may not be able to act on incomplete reports, but we will review credible reports and take appropriate action based on available evidence, legal requirements, platform risk, and customer obligations.