Acceptable Use Policy
Draft, pending legal review. This text is not final and is not yet legally binding. Items in [[double brackets]] are still to be filled in.
Last updated 2026-11-13
This policy applies to everything you run on, store with or send through A-Line.cloud, and to everyone you give access. It is part of the Terms of Service.
What you must not do
- Break the law, or host, distribute or link to content that is illegal where it is served or where we operate, including child sexual abuse material, terrorist content and content that incites violence or hatred.
- Infringe intellectual property, privacy or other rights of others.
- Send spam or unsolicited bulk messages, or run open mail relays.
- Run phishing, malware, command-and-control servers, exploit kits or services that impersonate others to deceive.
- Attack, scan without permission, or try to gain unauthorised access to systems or networks, or run denial-of-service attacks (including from your workloads).
- Mine or farm cryptocurrency anywhere on the Service, meaning using compute or storage to compete for block rewards (for example proof of work or proof of space). Other blockchain workloads, such as full, archive or staking nodes, are allowed only on clusters whose provider allows them. In builds and Actions jobs they are not allowed, except local test chains that do not connect to a public network.
- Resell or share access to the Service in a way that hides who the customer is, or evade limits, quotas, billing or moderation measures (for example by creating accounts to avoid a block).
- Damage or degrade the Service or other customers, or use more shared capacity than your plan allows.
- Store or process data that you are not allowed to process, or that requires certifications we do not offer (for example payment card data in our shared services).
Your responsibilities
- Keep your software updated and your credentials secret; a compromised workload that abuses others is your breach until you fix it.
- Give us a working contact address and answer abuse reports and moderation requests in time.
- Respect the rules of any third-party service you use through the Service. Infrastructure providers are covered in the next section.
Infrastructure provider rules
Your workloads run on machines of the infrastructure provider of your cluster, and builds and Actions jobs run on machines we rent. Everything you run must follow that provider's terms and acceptable use rules, whatever its source: a catalog template, your own image, a build or an Actions job.
The catalog hides templates that a provider is known to forbid. This is an aid, not a permission: a workload the catalog offers, or one you deploy from your own image, can still breach a provider's rules. You are responsible for checking them.
When a provider reports a problem with your workload, we may share with it the information it needs to handle the report. Where the provider requires it, or our account with that provider is at risk, we may stop the workload or restrict the account at once, before we have assessed the report ourselves.
A report alone is not a confirmed breach. A breach is confirmed when we establish it ourselves, or when the provider concludes that its rules were broken, for example by charging us a penalty or ending a service because of your workload. Costs, fees and penalties a provider charges us because of your workload are costs of the breach under the Terms of Service.
Reporting abuse
Send abuse reports with the URLs or addresses involved and evidence to abuse@a-line.cloud. We assess each report, may contact the account owner and may take the measures below.
How we enforce this policy
We choose the measure by how serious the breach is, whether it is repeated, and the risk to people, other customers, our providers and the Service. Measures range from a warning or a hold on one resource to locking the whole account at once, and to termination. We may apply the same measures to other accounts and organisations that the same person owns or controls, or that are used to evade a measure.
When we suspect or are told of a breach, we open a case and may place a hold on a resource or on the account while we investigate. A hold can stop a resource, block new deployments, domains or logins, or restrict the account. We keep the reason and the evidence with the case.
We notify the account owner what was restricted and why, unless the law or an ongoing investigation prevents it. For clear and serious breaches (for example illegal content or an active attack) we may act first and tell you afterwards.
You can appeal a decision from the moderation page of your account. A person who was not involved in the first decision reviews the appeal, and we tell you the result.
The consequences of a confirmed breach (suspension, deletion, termination, the balance and costs) are in the Terms of Service. Charges continue during a suspension.
Investigations, reports to authorities and legal requests
We may investigate a suspected breach, including by reviewing account, billing and log data and the resources involved, and we preserve the evidence. We report child sexual abuse material and threats to someone's life or safety to the competent authorities, and we may report other suspected criminal activity on our own initiative, sharing the relevant data and evidence. We cooperate with lawful requests from authorities. Where we are allowed and it does not harm an investigation, we tell the affected customer.