Acceptable Use Policy

This Acceptable Use Policy (the "AUP") applies to every service CentrixNodes provides, meaning game servers, VPS, dedicated servers and colocation, and to everyone who uses them, whether or not they hold the account.

It forms part of our Terms of Service. We keep it deliberately readable: the goal is a stable, reputable network, not a catalogue of technicalities.

Everything that happens on your service is your responsibility, including what your staff, players, sub-users and customers do with it. "Someone else on my server did it" is an explanation, not a defence.

That means keeping your software patched, your credentials private and your access lists tight. A compromised server that goes on to attack someone else is still your server.

You may not store, host, transmit or link to:

• Child sexual abuse material, in any form. This is reported to the authorities and terminated immediately, without notice and without refund.
• Content that incites or facilitates violence, terrorism or serious harm to people or animals.
• Material that harasses, stalks, threatens or targets an individual, or that publishes their private information without consent.
• Content unlawful in the United States or in the jurisdiction of the node hosting it.
• Material that infringes copyright, trademarks or other intellectual property rights, including pirated games, cracked software and unlicensed media libraries.
• Phishing pages, fraudulent stores, fake login portals and other deceptive content.
• Malware, ransomware, exploit kits, credential stuffing lists and stolen data.

You may not use our network to:

• Scan, probe or attempt to breach systems you do not own or have written permission to test.
• Run open resolvers, open relays, open proxies or reflectors that can be abused to amplify traffic.
• Spoof source addresses, forge headers or otherwise disguise the origin of traffic.
• Interfere with another customer's service, or with the routing, security or monitoring of the platform.
• Circumvent resource limits, billing controls, mitigation or any other technical restriction we apply.

Running, hosting or selling any form of attack service is an immediate termination. That includes booters, stressers, IP pullers, layer 4 and layer 7 attack panels, amplification tooling and "testing" services aimed at third parties.

Load testing your own infrastructure is fine, but tell us first and agree a window. Untelegraphed load tests are indistinguishable from an attack and our mitigation will treat them as one.

We provide DDoS mitigation as standard. Deliberately attracting attack traffic, whether by advertising your IP as a target or by reselling attack absorption, is a breach of this policy.

Bulk unsolicited email is prohibited, whether it is sent from our network or merely advertises something hosted on it. The same applies to unsolicited messaging on Discord, in game, or through any other channel.

If you send legitimate bulk email, you must keep proof of opt-in, honour unsubscribes promptly, use accurate headers and keep your complaint rate low. Outbound mail ports may be closed by default and opened on request once we understand what you are sending.

Cryptocurrency mining, plotting, hash farming and comparable distributed-compute workloads are not permitted on shared or game hosting plans. They saturate hardware that is sold on the assumption of normal use.

On dedicated servers and colocation, talk to us first: the machine is yours, but the power, cooling and network envelope still have limits, and we would rather agree them up front than throttle you later.

Also prohibited: click farms, view bots, artificial engagement services, credential-stuffing infrastructure and captcha-solving farms.

Game servers must comply with the publisher's end user licence agreement and server rules. Some publishers restrict monetisation, advertising or modifications, and those restrictions apply to you whether or not you have read them.

You may not host cracked or pirated game binaries, servers that exist to distribute cheats, or services designed to defeat anti-cheat systems. Where a publisher notifies us of a violation, we will act on it.

We respond to valid notices under the Digital Millennium Copyright Act. Send notices to support@centrixnodes.net with the material identified, the work it infringes, your contact details and the statements the DMCA requires.

We will pass the notice to the customer and, where required, remove or disable access to the material. Customers may submit a counter-notice, and repeat infringers lose their service.

Test your own systems as much as you like. Testing anyone else's from our network, including automated scanning, is prohibited without written permission from the target.

If you find a vulnerability in our platform, we want to hear about it. Report it to support@centrixnodes.net before disclosing it anywhere else, give us reasonable time to fix it, and do not access other customers' data while proving it.

IP addresses are assigned to your service for as long as you hold it and remain ours. They are not portable, and we may renumber a service where routing, mitigation or blacklisting makes it necessary.

Justify additional addresses on technical grounds. Deliberately burning through addresses to escape blocklists is a breach of this policy, and behaviour that lands our ranges on a blocklist may lead to suspension.

Shared and game hosting plans carry a stated allocation of CPU, memory, storage and network. Sustained use far beyond your allocation, or I/O patterns that destabilise the host, affect every other customer on that machine.

Where that happens we will contact you and suggest a plan that fits. Throttling, migration and suspension are last resorts, in that order.

Report anything on our network to abuse@centrixnodes.net. Include the IP addresses, the timestamps with their timezone (UTC is ideal) and the raw logs or headers. Reports with evidence are investigated the same day.

We do not share the reporter's identity with the customer unless we are legally required to, and we do not act on reports that amount to a disagreement between communities.

Our response is proportionate to what happened and to whether it is still happening:

• 1.Notice: we contact you and ask you to resolve it, which is where most cases end.
• 2.Mitigation: we filter, rate limit or null route the traffic while you fix the cause.
• 3.Suspension: we take the service offline where the problem continues or where it threatens the platform.
• 4.Termination: for severe or repeated breaches, without refund, and with data deleted on the schedule in our Terms.

Unlawful material, active attacks and ongoing compromises skip straight to suspension or termination. We will explain what happened afterwards.

If you think we got it wrong, open a ticket and tell us what we missed. Suspensions are reviewed by a human, and where the finding was mistaken we restore the service and the time you lost.