Acceptable Use Policy

This policy is part of the Terms of Service. It applies to everything you run on Slipstream and to anyone using your account. Your instances run on shared provider infrastructure, so misuse by one customer can affect everyone — we enforce this policy strictly.

Not allowed

• Cryptocurrency mining, or any proof-of-work, proof-of-space or similar blockchain computation, including "testing" it.
• Illegal content or activity, including child sexual abuse material (which we report to the relevant authorities), and content that infringes others' intellectual property or privacy.
• Attacking or probing other systems: denial-of-service, port or vulnerability scanning, brute-forcing credentials, or accessing systems without authorization — unless it's a test you're authorized to run against systems you own or have written permission to test.
• Malware, phishing, spam or botnets, including hosting or distributing them or controlling them from an instance.
• Open proxies, VPN exit nodes or anonymizing relays offered to third parties.
• Getting around our controls: evading spending or top-up limits, creating multiple accounts, reselling access, using someone else's payment method, or interfering with metering or monitoring.
• Harming the service or providers: trying to break out of your instance, reach other customers' resources, or disrupt the platform.
• Prohibited uses under sanctions or export control law (see the Terms, section 9).

How we enforce it

We look at usage signals such as GPU utilization patterns, network traffic volume and destinations, and reports from providers and third parties — not the contents of your data. If we believe this policy has been broken we may, without notice, stop your instances, freeze or close your account, and keep any remaining credits. Where the law requires, we report activity to the authorities. If you think we got it wrong, email us.

Reporting abuse

See something coming from a Slipstream instance? Email support@slipstreamcompute.com with the IP address, time (with time zone) and what happened.