Acceptable Use Policy
What you may not run on Aspian Cloud, and what happens if a workload breaks these rules.
Last updated 7 November 2026 · Draft
Not allowed
- Anything unlawful where it is hosted, where it is used, or in Nigeria or the United Kingdom.
- Malware, phishing, credential harvesting, or sites that pretend to be another organisation.
- Attacks on any system, including scanning, denial of service and attempts to get past another tenant’s isolation. Testing your own applications is fine; testing ours needs the responsible disclosure policy.
- Unsolicited bulk messages. Alert and approval messages must go to people who have agreed to receive them, and opt-outs must be honoured.
- Cryptocurrency mining, or using resources in a way designed to avoid metering.
- Content that sexually exploits children, promotes terrorism, or incites violence.
- Trying to read a stored secret value, or to get an AI agent to do so. Secrets are write-only by design.
Regulated data is welcome, with the right edition
Health, insurance, finance, education and government records are what Regulated and Sovereign are for. If you host such data on a sovereign cell, choose the region your obligations require.
What we do about a breach
- We contact the workspace owner, say what we found and ask for it to be fixed.
- If there is urgent harm to people or to other customers, we may pause the workload first and tell you straight away.
- Every pause is recorded in your audit trail with who did it and why.
- Repeated or serious breaches can end the agreement. Your data stays available to export unless a court or regulator orders otherwise.
Reporting abuse
Report abuse of an Aspian Cloud workload to hello@aspianalliance.com.