Acceptable use

What you may run, what you may not, and what happens if a line is crossed.

Short, and meant to be read once rather than referred to by lawyers.

The principle

Run what you like, as long as it does not harm other people, other customers, or the platform's ability to serve them. Everything below is that sentence applied to specific cases.

What you may not run

Anything illegal under Algerian law, or under the law where your users are.

Attacks on others. Scanning, flooding, credential stuffing, or sending traffic designed to exhaust somebody else's capacity. This includes testing your own systems hosted elsewhere without the written permission of whoever runs them.

Unsolicited bulk messaging, of any kind, by any channel.

Deliberate misrepresentation. Impersonating a person, a company or a public body; collecting credentials or payment details under a false identity; hosting content designed to be mistaken for someone else's service.

Material that exploits children, or that exists to incite violence against people.

Deliberate abuse of the platform itself. Attempts to reach another customer's resources, to escape the boundaries of your own, or to consume shared capacity in ways the pricing does not account for.

What you may run, that people sometimes ask about

Security tools, and research. Scanners, proxies, analysis tooling and exploit development are legitimate work. What matters is the target: your own systems, or systems whose owners have authorised you in writing.

Anything resource-intensive, as long as you are paying for the capacity. Heavy computation is a bill, not a violation.

Content others may disagree with. Journalism, criticism, satire and political speech are not violations, and we do not remove them because somebody complained. Illegality is judged by law, not by volume of objection.

Resource use

Shared capacity is shared. An application that consumes far beyond what it is paying for — filling a region's network, exhausting a shared service — will be throttled and you will be told why.

This is about honesty of accounting rather than a hidden quota: if you need more capacity, buy it, and it is yours to use hard.

How this is enforced

In proportion, and with notice wherever notice is safe.

For most issues the first step is a message describing what we have seen and asking you to deal with it, with a deadline that reflects how serious it is. Most matters end here, and many turn out to be a compromised deployment rather than a deliberate act.

Without notice only where notice would cause harm: an active attack coming from your application, material that must come down immediately by law, or a compromise being actively exploited. In those cases the narrowest possible action is taken — suspending one application rather than an organization — and you are told immediately afterwards.

Suspension of the organization is the last step, not the first, and requires a person to decide it.

If you think we got it wrong

Reply to the notice. A human will read it, and actions taken in error are reversed rather than defended. If your service was suspended incorrectly, say so plainly and ask for it to be restored; you do not need to be polite about it.

Reporting abuse

If something hosted here is harming you, report it with the address and what you observed. Reports about content are assessed against this page and against the law, not against how strongly they are expressed.