Compliance and abuse

Send reports to abuse@nexuspartnersltd.com. A useful report includes:

• the IP address or addresses involved, and the port where relevant;
• the date and time, with the time zone;
• what happened: spam, phishing, malware, scanning, an attack, infringement or other misuse;
• evidence such as log lines or, for email, the full message headers;
• how we can reach you if we need more detail.

We act on every report within 24 hours.

We check the report against our own records and act on what we can verify. We block the abused port, protocol or destination on our network and, where a report identifies a specific account or service, we suspend it.

Our services keep no logs of user traffic, so we cannot attribute past traffic to an individual customer. We stop the activity at the network level and adjust our controls to prevent it from recurring. We tell the reporter what we did.

Everyone who uses our services agrees not to use them to:

• send spam or other unsolicited bulk messages;
• distribute malware, run phishing or commit fraud;
• attack, scan or gain unauthorised access to other networks and systems, including denial-of-service attacks;
• create, store or share material that sexually exploits children;
• infringe the intellectual-property or privacy rights of others;
• break any law that applies to them or to us.

We suspend or terminate the accounts of customers who break these rules. Each platform’s terms of service set out the full rules for its customers.

Send legal requests to legal@nexuspartnersltd.com. We review each request for its legal basis and answer within the limits of the law. We can disclose only the data we hold, and we do not hold logs of our users’ traffic.

compliance@nexuspartnersltd.com handles KYC and due-diligence requests from banks, payment providers, IP address registries and lessors, hosting providers and other counterparties. We can provide our corporate documents, a description of our services and our abuse-handling procedure.

Our contacts are also published in machine-readable form at /.well-known/security.txt.