Security, Abuse & Privacy

Acceptable Use Policy

Definition

An acceptable use policy, usually shortened to AUP, sits alongside the terms of service and covers content and conduct rather than billing. A typical one has three parts. First, prohibited content: malware, phishing and credential harvesting, material that infringes copyright, content that is illegal in the jurisdictions the host operates in, and content that impersonates a real organisation or person. Second, prohibited conduct: bulk automated publishing, using storage as a content delivery backend for another service, deliberately evading limits or enforcement. Third, process: how something gets reported, what actions the host can take, what notice you get and how to appeal. The policy binds the host too — it is the reason enforcement is supposed to be predictable rather than arbitrary.

Why It Matters

Most people never read the AUP until a file is held, at which point it explains both what happened and what to do. Three clauses matter more than the rest for ordinary users. Resource clauses decide whether your use counts as hosting a file or as running a service off someone else's bandwidth, which is the usual grounds for throttling a popular asset. Impersonation clauses catch things people do innocently — publishing a mockup of a real company's site, or a page with a client's logo and login styling. And the process clause tells you whether the first step is a warning or a removal, which is the difference between a delayed launch and a dead link in front of a customer.

How It Works

Enforcement moves in stages. Automated checks and inbound reports feed a queue; a reviewer compares the content against the named clause and picks a response. The scale runs from a notice with a deadline, through disabling one address while leaving the account intact, to suspending the account where the pattern is deliberate. A takedown under a legal notice follows its own track, since the host's obligations there are set by statute rather than by its own policy. Decisions are recorded in an audit log so a later appeal has something to examine. Policies change; hosts generally give notice before a clause that affects existing content takes effect, and grandfather what was published in good faith.

Real-World Example

A freelancer hosting a client's brand guidelines on 99helpers also publishes a demo page recreating the client's login screen for a design review. The demo is held under the impersonation clause, because from the outside it is a copy of a real company's sign-in page. Adding a visible banner marking it as an internal mockup, and removing the non-functional password field, satisfies the review and the page is restored the same day.

Common Mistakes

  • Only reading the terms of service — the content rules that actually cause holds usually live in a separate acceptable use document
  • Publishing a pixel-accurate copy of a real company's page as a mockup with no marking, which reads as impersonation to anyone who finds it
  • Hotlinking hosted assets into a high-traffic app and treating the resulting throttle as a fault rather than the resource clause working
  • Ignoring a notice with a deadline in the hope it lapses — an unanswered notice generally escalates on its own schedule

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →