Acceptable Usage Policy.

1. Our philosophy

We host game servers. That means a lot of customer content is loud, competitive, mildly offensive, and occasionally embarrassing — and that's fine. We're not the speech police. If it would pass muster on a regular gaming Discord or a subreddit for your game, it'll pass muster here.

What we do not tolerate is a narrow list of things that:

• Break the law in the UK, EU, US, or the country where the server is located
• Actively harm other customers on our network (DDoS origination, port scanning, noisy-neighbour exploits)
• Create liability for us as a hosting provider (CSAM, targeted harassment campaigns, malware distribution)
• Compromise the integrity of the platform (credential theft, panel exploitation, rate-limit evasion)

When in doubt, email [email protected] — we'd rather have the conversation before you deploy than shut you down after.

2. Prohibited content

You may not use the Services to host, store, transmit, or distribute:

2.1 Illegal content (hard no)

• Child sexual abuse material (CSAM) or any content that sexualises minors
• Content that incites or plans violence against specific persons or groups
• Content that facilitates terrorism or provides operational support to terrorist organisations
• Content that violates export-control laws (e.g. controlled cryptographic software, weapons designs)
• Non-consensual intimate imagery ("revenge porn")
• Content whose creation, possession, or distribution is illegal in the UK or the country where the server is located

2.2 Harmful content

• Malware, ransomware, rootkits, keyloggers, remote-access trojans — whether for "research", "educational", or active distribution
• Phishing kits, credential harvesters, or clones of legitimate login pages
• Coordinated harassment campaigns, doxxing infrastructure, stalker-ware
• Content promoting self-harm or suicide to vulnerable audiences

2.3 Content that is legal but out-of-scope

Some legal content we don't host because it's simply not what the platform is for:

• Adult / pornographic communities — our platform is not optimised for those workloads and we don't provide age-gating tooling. Use a specialist adult host.
• Unlicensed gambling operations — where you are not properly licensed in the jurisdiction you serve users.
• Pharmaceutical sales without a licence, firearms sales where prohibited, and similar regulated-commerce use cases.

3. Network abuse

You may not use your server or network allocation to:

• Originate denial-of-service (DoS / DDoS) attacks, whether directly or through amplification / reflection techniques
• Port scan, vulnerability scan, or brute-force third-party systems without documented written authorisation from the target system owner
• Run open resolvers, open mail relays, open proxies, or other infrastructure routinely abused for amplification or spam
• Spoof packets, forge source addresses, or otherwise send traffic designed to evade source attribution
• Participate in botnets, whether as command-and-control or as an infected node
• Circumvent rate limits, captchas, or other anti-abuse measures on third-party services

Legitimate security research — bug bounties, red-team engagements on systems you own or are contracted to test — is fine. Document the scope in advance and email [email protected] before you run noisy traffic so our automated monitoring doesn't flag it.

4. Platform integrity

You may not:

• Interfere with other customers' servers — through noisy-neighbour resource exhaustion, cross-VM side-channel attacks, or any action that materially degrades service for others
• Probe, scan, or attempt to exploit our customer panel, billing systems, support infrastructure, or internal APIs beyond the scope of your own account
• Reverse-engineer, disassemble, or modify our panel or platform code to evade license checks, resource limits, or security controls
• Circumvent account limits by running multiple accounts, using stolen payment methods, or creating disposable accounts to reset free trials or money-back windows
• Impersonate Fatality Servers or imply an endorsement, partnership, or authorisation we haven't granted in writing

Everything above has a responsible-disclosure path: email [email protected] if you find a vulnerability. We have a bug-bounty process and we won't sue a researcher for reporting something in good faith.

5. Copyright & DMCA

You must respect copyright, trademark, and other intellectual-property rights.

5.1 You are responsible for what you distribute

• Don't redistribute games, clients, or paid mods you don't have a licence for.
• Don't run piracy-focused servers or provide infrastructure whose primary use is to serve unlicensed copyrighted content.
• Where a game has a commercial-use licence required (e.g. Mojang's Commercial Usage Guidelines for Minecraft, Cfx.re license for FiveM), you are the commercial operator and you are responsible for obtaining and maintaining it.

5.2 DMCA / copyright complaints

If you believe content hosted by a Fatality Servers customer infringes your copyright, send a notice to [email protected] with:

• A physical or electronic signature of the copyright owner or authorised agent
• Identification of the copyrighted work(s) claimed to have been infringed
• Identification of the infringing material and sufficient information to locate it (URL, IP, or server identifier)
• Your contact information — name, address, phone, email
• A statement that you have a good-faith belief that the use is unauthorised
• A statement, under penalty of perjury, that the information in the notice is accurate and that you are authorised to act

We process valid DMCA notices within 48 business hours. The customer is notified, given a chance to file a counter-notice, and the content is acted on in line with applicable law. Repeat offenders are terminated per our repeat-infringer policy.

5.3 Counter-notices

If you believe a DMCA notice against your content was issued in error, submit a counter-notice to the same address following the requirements of 17 U.S.C. § 512(g) or your local equivalent. We will forward it to the complainant; if they do not pursue court action within the statutory window, we will restore the content.

6. Spam, phishing & malware

You may not use the Services to:

• Send unsolicited bulk email (spam), whether via SMTP, HTTP form-posts, or in-game message systems
• Host or link to phishing pages designed to harvest credentials for services you don't own
• Distribute malware, exploits, or RATs — including as part of "red team" tooling if not properly scoped
• Host command-and-control (C2) infrastructure for botnets or other malware families
• Run credential-stuffing infrastructure against third-party services

Outbound SMTP on managed and VPS plans is rate-limited by default. If you need to send legitimate transactional email from your game server (e.g. account verification, ticket notifications), use an authenticated relay like Postmark, SendGrid, or Amazon SES — running your own MTA at scale is not supported on our standard plans.

7. Crypto-mining & resource abuse

Our hardware is tuned for game-server workloads (high single-thread performance, modest core counts, high-clock RAM). It is not priced or cooled for 24/7 max-utilisation tasks. Therefore:

• Cryptocurrency mining is prohibited on managed game servers, shared VPS, and all plans where CPU is a shared resource. Period.
• Dedicated servers may run mining only with our prior written consent and only on hardware specifically provisioned and priced for that workload (contact sales).
• Other sustained-max-CPU workloads — distributed rendering, large-scale video encoding, continuous AI training / inference — are restricted on shared plans. Contact us before deploying anything that will peg a core at 100% indefinitely.

We monitor for anomalous sustained CPU / network / I/O patterns. Violators receive one warning; a second offence is immediate suspension.

8. Reselling

Reselling is allowed in limited, approved circumstances:

• You may run a community that uses our infrastructure and charge members for access (subscriptions, donor ranks, etc.) — that is a normal community-operator relationship and doesn't require our approval.
• You may not resell our core hosting product to unrelated third parties as if it were yours, white-label our panel, or present Fatality Servers capacity as a product line of your company — without a signed reseller agreement.
• Official reseller agreements are available — email [email protected]. They include dedicated hardware allocation, wholesale pricing, and a support SLA appropriate for resellers.

9. Game-specific rules

Some games ship with additional terms that constrain how servers can be run. It's your responsibility to comply with those. Highlights:

• Minecraft — Mojang's Commercial Usage Guidelines limit monetisation (no pay-to-win, specific rules for donation perks). Familiarise yourself with them.
• FiveM — Cfx.re Terms of Service prohibit certain monetisation models and require a valid licence key. Running unlicensed is both a violation of their ToS and our AUP.
• CS2 / CS:GO / TF2 / Rust / ARK and other SteamCMD games — Valve requires a GSLT on a VAC-clean account. Don't share GSLTs across servers; don't run with a VAC-banned account as the GSLT holder.
• Cracked / pirated clients — running a "cracked mode" (e.g. online-mode=false in Minecraft) for a community that owns the game is fine. Running one to enable unlicensed play is not.

10. Enforcement

10.1 How we investigate

Most reports come from one of four sources:

1. Automated monitoring (outbound DDoS, open-resolver detection, abnormal traffic patterns)
2. Upstream abuse reports from our datacenter partners
3. Customer reports via [email protected]
4. Third-party complaints (DMCA, law-enforcement requests, trademark holders)

Our abuse team reviews each report, pulls logs where necessary, and contacts the customer. We don't rely on a single bot report to terminate service.

10.2 Our escalation ladder

• Low severity / first offence — email notification describing the issue and asking you to correct it within 24-72 hours.
• Medium severity / repeat or unresolved — temporary suspension until the issue is resolved. You retain your data; service is paused.
• High severity / active harm — immediate suspension. Reactivation requires review and documented remediation.
• Zero-tolerance categories (CSAM, active DDoS origination, coordinated fraud) — immediate termination, evidence preservation where legally required, and in relevant cases a report to authorities.

10.3 Your rights when we enforce

Except in zero-tolerance categories or where legally compelled otherwise, we will:

• Tell you what we saw and why we're acting
• Give you a reasonable opportunity to respond or cure
• Let you export your data before termination
• Escalate internally if you dispute the finding — a second member of our team reviews before termination is finalised

10.4 No refunds for AUP termination

If your service is terminated for a material AUP violation, you forfeit the balance of prepaid fees. This is an exception to our normal Refund Policy.

11. Reporting violations

If you believe a server hosted by Fatality Servers is violating this policy, email [email protected] with:

• The server IP or domain where the content lives
• A description of the specific violation (with category from this policy)
• Timestamps, if relevant
• Evidence — screenshots, URLs, log excerpts, or headers — sufficient to let our team verify the report
• Your contact information (we keep this confidential unless legally required to disclose)

We acknowledge reports within one business day and most are fully investigated within 72 hours. Zero-tolerance categories are prioritised and usually actioned the same day.

12. Contact

• Abuse reports: [email protected]
• DMCA / copyright: [email protected]
• Security vulnerabilities: [email protected]
• Law-enforcement requests: [email protected] — please include valid legal process
• General questions about this policy: [email protected]