Fair usage policy

Use the capacity you purchased for lawful purposes, respect others' rights and avoid harming shared infrastructure. Normal intensive use of expressly dedicated resources is not abuse simply because it exceeds another customer's average usage.

We apply this policy proportionately, based on the activity, purchased specification, measurable effects and relevant legal obligations. It is not a substitute for publishing the actual limits of a plan.

Your order must explain the resources you receive, any shared or burstable capacity, included transfer, port speed, storage, power, metered rates and measurement method. A resource described as dedicated is reserved as stated in the order. A shared or burstable resource may have a defined baseline and temporary burst capability; those conditions must be disclosed before purchase.

“Unmetered” means that usage is not billed by the transferred volume within the stated capacity. It does not mean unlimited port speed. “Unlimited” must not be used to conceal an undisclosed practical cap. If a service has a limit, we state it in the service description or order.

For percentile-based transit billing, the order must explain the sampling interval, traffic direction calculation, committed rate, burst rate and price. This policy does not supply an unpublished measurement formula or overage fee.

If activity causes a verifiable risk to a shared network, storage system or virtualisation platform, we may ask for a change, offer a more suitable plan or temporarily isolate the affected resource. We explain the relevant evidence and the scope of any restriction. We do not permanently reduce contracted dedicated capacity through an undefined “typical usage” test.

You must not use the services to:

• Conduct or facilitate unlawful activity, fraud, phishing, credential theft, extortion or intentional impersonation.
• Distribute malware, operate malicious command-and-control infrastructure, or compromise systems without permission.
• Launch denial-of-service attacks, reflection or amplification attacks, unauthorised intrusion, credential stuffing or deliberately disruptive traffic.
• Send unsolicited bulk messages, use deceptive sender identities, or continue messaging people who have opted out where that is prohibited.
• Store or distribute child sexual abuse material, facilitate sexual exploitation, or distribute intimate material without the required consent.
• Infringe intellectual property, privacy or other enforceable rights, including knowingly distributing unlawfully obtained personal data.
• Evade account restrictions, metering, licence controls or security controls, or access another customer's systems or information without permission.
• Publish open services that are being used for abuse and knowingly leave them uncorrected after a substantiated notice, such as an exploited open mail relay or an amplification service.
• Violate applicable export controls or sanctions, or misrepresent the identity, destination or use needed to determine lawful service eligibility.

We assess illegality under applicable law and lawful process. A complaint alone is not conclusive proof, and lawful controversial content is not automatically prohibited.

Hosting, streaming, content delivery, gaming, VPNs, proxies, data analysis and AI workloads are not inherently prohibited. They must remain lawful and within the agreed service specifications. You are responsible for licences, permissions and user controls appropriate to the use.

Cryptocurrency mining and other continuous compute workloads require prior written agreement only where they would exceed a shared or burstable plan's stated operating profile, agreed power or cooling limits, or another express service restriction. Lawful use of dedicated resources within their specification is not prohibited merely because it is compute-intensive.

You may test systems you own or are authorised to test, within the agreed capacity and without affecting others. Obtain our written coordination before tests that may flood shared links, simulate denial of service, access platform control systems or affect a facility. Our security reporting guidance does not authorise testing a customer's workloads or unrelated third parties.

Keep your contact details current and maintain a reachable technical contact for urgent issues. Protect credentials and promptly investigate credible compromise notices.

If you resell or allow end users to use the service, communicate applicable use restrictions and take reasonable steps to address substantiated abuse. You remain responsible for service use under your account to the extent provided by your agreement and applicable law. This does not create a general obligation to inspect every customer's private communication.

Network abuse controls, such as a port restriction, must be disclosed with the relevant product or explained when applied for a specific risk. Ask support to review a restriction that affects a legitimate use case.

Report suspected abuse to abuse@ipxon.com. Include the affected IP address, domain or service; dates and times with time zone; a concise description; and relevant evidence you can lawfully share. Avoid sending unnecessary personal data, credentials or exploit code in an initial report.

For an intellectual property complaint, identify the protected work or right, your authority to report it, the specific material or location and a reliable reply address. Any legally required declarations or counter-notice process will be requested or explained for the relevant procedure. We do not claim a statutory notice-and-takedown safe harbour simply by publishing this contact.

We review the information, may request clarification, and may share the substance of a report with the affected customer when lawful and appropriate, minimising unnecessary disclosure. We may preserve relevant evidence or disclose information where legally required, with the protections described in the Privacy Policy and DPA.

For a remediable, non-urgent issue, we normally send a notice describing the problem and allow at least 10 calendar days to resolve it. We may agree a remediation plan when the work reasonably needs longer and the continuing risk is controlled.

We may immediately filter traffic, isolate a resource, restrict access or suspend an affected service where delay would create a serious security, legal, physical or network risk. We choose the least disruptive effective measure reasonably available, explain it as soon as lawful and practicable, and review it when the risk changes.

Repeated serious violations or an unresolved material breach may lead to termination under the Terms. Suspension does not itself authorise immediate data deletion, confiscation of customer-owned equipment or automatic forfeiture of all prepayments. Applicable exit and deletion rules remain in force, subject to binding legal requirements.

If you believe a restriction is mistaken, reply to the notice or contact abuse@ipxon.com with supporting information. We will arrange a review by someone not responsible for the original decision where practicable. Restoration follows once the issue is resolved or the restriction is found unjustified; we will explain any remaining necessary condition.

We update this policy through the notice and change process in the Terms. New limits do not retroactively change capacity already purchased for a fixed term. Questions about a planned workload should be raised before ordering so its requirements can be included in the service specification.