Acceptable Use Policy Template

A customizable Acceptable Use Policy for SaaS, apps, and online platforms, covering prohibited conduct, enforcement, and suspension. Built for clickwrap acceptance.

Updated June 2026Terms
Adjust for your territory

Sets a starting point for your main market; serving several, enable extra sections under Customize. These adjustments cover the US, UK, and EU broadly and are not a substitute for advice on your specific country's law.

Scroll for section-by-section legal context. Click any purple chip to fill in that field. Switch to Customize to enable optional clauses.

ACCEPTABLE USE POLICY

Effective Date: {Effective Date}

Last Updated: {Last Updated Date}

This Acceptable Use Policy ("AUP" or "Policy") governs your use of {Service Name} and any related websites, applications, and services we provide (the "Service"), operated by {Company Name} ("we", "us", or "our"). This Policy is part of, and is incorporated by reference into, our Terms of Service. By accessing or using the Service, you agree to this Policy.

(Customize this policy to your service. Products with user-generated content, messaging, an API, hosting, a marketplace, AI features, regulated industries, or EU users may need additional terms; enable the relevant optional clauses or add your own.)

1. Overview

This Policy sets out the rules for acceptable use of the Service. It applies in addition to our Terms of Service: where the Terms of Service describe the overall agreement, this Policy defines the specific conduct that is and is not permitted. If there is a conflict between this Policy and the Terms of Service on a question of acceptable use, this Policy controls. A violation of this Policy is a violation of our Terms of Service. We may update this Policy as described below. The version posted at the time of your use applies to that use, and material changes apply prospectively after we post or otherwise provide notice as required by law or our Terms of Service.

About this section

What's in this section

States what the Policy covers and ties it to your Terms of Service: the Terms set the overall agreement, this Policy defines the specific conduct that is and is not allowed.

Why this section is here

An AUP is enforceable because it is part of the contract the user accepted. Saying it is incorporated into the Terms, and which document controls on use questions, keeps it binding rather than advisory.

Common mistake

Publishing the AUP as a standalone page that no agreement references. If nothing the user accepted points to it, you may not be able to enforce it.

Pair this with your Terms of Service โ†’

2. Who This Policy Applies To

This Policy applies to everyone who accesses or uses the Service, including account holders, their authorized users, and anyone acting on their behalf. If you provide access to the Service to others (for example, your own employees, contractors, or end users), you are responsible for their compliance with this Policy and for any use of the Service through your account.

About this section

What's in this section

Names everyone bound by the Policy: account holders, their authorized users, and anyone acting through their account.

Why this section is here

Most abuse arrives through a customer's own users or downstream access. Making the account holder responsible for everyone they let in gives you one party to hold accountable.

Common mistake

Limiting the Policy to the signed-up account holder. Without a pass-through obligation, you have no clear claim when the abuse comes from someone they invited.

3. Prohibited Activities

You may use the Service only for lawful purposes and in accordance with this Policy and our Terms of Service. You may not use the Service, and may not assist or permit any person to use the Service, to:

  • violate any applicable law or regulation, or infringe or misappropriate any intellectual property, privacy, or other right;
  • engage in fraud, deception, or misrepresentation, or impersonate any person or entity;
  • gain or attempt to gain unauthorized access to any system, account, network, or data;
  • introduce, transmit, or distribute malware, ransomware, or other harmful code;
  • interfere with, disrupt, or place an unreasonable load on the Service or its infrastructure;
  • circumvent or attempt to circumvent any security, authentication, rate-limiting, or access control;
  • collect, scrape, or harvest data from the Service except as we expressly permit in writing;
  • collect, process, disclose, or attempt to obtain personal data without a lawful basis, required consent, or other authorization, or use the Service to dox, track, profile, or surveil individuals unlawfully;
  • use or export the Service in violation of any applicable export control, sanctions, anti-boycott, or trade compliance laws, or for the benefit of any person, entity, or jurisdiction subject to applicable sanctions or restrictions;
  • circumvent billing, usage limits, metering, seat or feature restrictions, trial limits, or other plan limitations; or
  • engage in any other conduct that is abusive, deceptive, harmful to the Service or other users, or otherwise objectionable as we reasonably determine.

This list is not exhaustive. We may treat any use that threatens the security, integrity, availability, or lawful operation of the Service as a violation of this Policy.

About this section

What's in this section

The core list of banned conduct: illegal use, fraud, IP infringement, unauthorized access, malware, interference, and circumventing security or limits.

Why this section is here

This is the list you point to when you suspend or terminate a bad actor. Enforcement is only as strong as the specific conduct you named here.

Common mistake

A single vague line like 'do not misuse the Service.' Name the conduct you actually want the right to act on, since that is the wording an enforcement decision relies on.

4. Content Standards

To the extent the Service allows you to submit, upload, post, or transmit content, you are responsible for that content and must ensure it does not:

  • infringe any intellectual property or other right;
  • contain or promote unlawful, fraudulent, or deceptive material;
  • contain malware or links to malicious resources;
  • depict, promote, or facilitate child sexual abuse material, which we act on immediately and report to the authorities;
  • harass, threaten, defame, or incite violence against any person or group; or
  • contain material that is obscene, exploitative, hateful, abusive, or otherwise objectionable as we reasonably determine.

We are not obligated to monitor content, but we may review, remove, or disable access to any content that violates this Policy or that we are required to act on by law.

About this section

What's in this section

The rules for any content users can submit or share: no infringing, unlawful, malicious, abusive, or otherwise objectionable material.

Why this section is here

If your Service carries user content, you need a stated basis to remove it and act on the account behind it. This section gives you that basis without committing you to monitor everything.

Common mistake

Promising to review all content, or omitting the illegal-content categories you are legally required to act on. Reserve the right to remove without taking on a duty to police every post.

5. System and Network Security

You may not violate or attempt to violate the security of the Service. Prohibited activities include accessing data not intended for you, probing, scanning, or testing the vulnerability of any system or network without authorization, breaching authentication or security measures, and interfering with service to any user, host, or network.

About this section

What's in this section

Security and infrastructure rules: no unauthorized access, scanning, or interference, plus optional limits for APIs, hosting, messaging, and resource use.

Why this section is here

Technical abuse threatens every other customer on shared infrastructure. Naming it here lets you cut off an attack or a runaway integration before it degrades the Service for everyone.

Common mistake

Covering only 'hacking' and ignoring automated abuse. Scraping, bot traffic, and integrations that exceed limits cause most real-world load problems.

6. Monitoring and Enforcement

We may, but are not obligated to, monitor use of the Service and investigate any suspected violation of this Policy. If we reasonably determine that you have violated this Policy, we may take any action we consider appropriate, including issuing a warning, removing or disabling content, throttling or suspending access, terminating accounts, and reporting conduct to law enforcement. We may act without prior notice where the violation is severe, involves illegal content, or poses a risk to the Service, other users, or third parties. We may also preserve and disclose information about your use where we believe in good faith that doing so is necessary to enforce this Policy, comply with applicable law or legal process, or protect the rights, safety, or property of any person. Our failure to enforce this Policy in any instance does not waive our right to enforce it later, and we are not liable for any action taken in good faith to enforce this Policy. Any action we take under this Policy is in addition to any remedy available under our Terms of Service or applicable law.

We moderate use of the Service at our discretion and are generally not liable for content provided by users under Section 230 of the US Communications Decency Act. We handle copyright complaints through the reporting process below.

About this section

What's in this section

What you can do about a violation: warn, remove content, throttle, suspend, terminate, or report to authorities, and that you may act without notice in severe cases.

Why this section is here

The right to act has to be reserved before you use it. Spelling out the range of responses, including immediate action for severe abuse, lets you respond proportionately and on record.

Common mistake

Promising notice or a cure period in every case. Keep the right to act immediately when the conduct is illegal or threatens the Service or other users.

Platform duties under the DSA โ†’

7. Reporting Abuse

If you become aware of any use of the Service that violates this Policy, report it to us at {Email Address} with enough detail for us to identify the issue, such as the account, content, or activity involved and the nature of the violation. We review reports and take the action we consider appropriate.

About this section

What's in this section

How users and third parties report a violation, and where copyright or DMCA notices go. It routes problems to a monitored channel you control.

Why this section is here

Abuse you never hear about is abuse you cannot act on. A named reporting address, and a process for legal notices, turns outside reports into enforceable action.

Common mistake

Listing no abuse contact, or an unmonitored inbox. Reports that go nowhere become the incidents and takedown demands you find out about too late.

8. Changes to This Policy

We may update this Policy from time to time to reflect new features, new types of misuse, or changes in the law. The version posted at the time of your use applies to that use, and material changes apply prospectively after we post or otherwise provide notice as required by law or our Terms of Service. We will post changes on this page and update the "Last Updated" date above.

About this section

What's in this section

Reserves the right to update the Policy and fixes which version governs: the one in effect when the user accessed the Service.

Why this section is here

Abuse rules change faster than the main contract. Tying each use to the version then in effect lets you tighten the Policy without re-papering the entire Terms of Service.

Common mistake

Editing the live Policy with no notice and assuming it binds past conduct. Keep dated versions and give notice of material changes so each one is defensible.

Re-acceptance after changes โ†’

9. Contact Us

If you have questions about this Policy or need to report a violation, contact us at:

{Company Name}

Email: {Email Address}

{Website URL}

About this section

What's in this section

Where users send questions about the Policy and where violation reports go: a named company and a monitored address.

Why this section is here

A policy with no working contact stalls every report and notice. A monitored abuse address keeps incidents from escalating into legal or platform complaints.

Common mistake

Using a generic inbox no one watches. Abuse and legal notices need a route that is actually read and acted on.

Got what you need? Copy the template now, or read on for the section-by-section guide to what each clause does and how to adapt it.

What Is an Acceptable Use Policy?

An Acceptable Use Policy (AUP) is the set of rules that defines how people may and may not use a product, service, or network. It lists prohibited conduct (such as illegal activity, abuse, unauthorized access, spam, and harmful content) and sets out what happens when someone breaks the rules.

An AUP is not a standalone contract. It works as part of a larger agreement, usually incorporated by reference into the Terms of Service, so that accepting the Terms also means accepting the AUP. That link makes the rules enforceable: you can suspend or terminate an account for conduct the user already agreed not to engage in.

Keeping the conduct rules in their own document has a practical payoff. Abuse tactics and platform risks change far faster than the core commercial terms, and a separate AUP lets you update the rulebook without reopening the entire contract.

Who Needs an Acceptable Use Policy?

Any product that other people can access, contribute to, or build on benefits from one. This acceptable use policy template fits the services that carry the highest abuse risk:

  • SaaS & Cloud

    Subscription software and cloud services that need clear limits on misuse, abuse, and resource consumption.

  • Platforms & UGC

    Sites hosting user-generated content, marketplaces, and communities that must act on illegal or abusive content.

  • Apps & APIs

    Mobile apps and API products that need to ban scraping, automated abuse, and unauthorized access.

  • Hosting & Infrastructure

    Hosting, network, and messaging providers that bind customers to anti-abuse rules and flow them down to end users.

The need grows sharpest once the Service has user-generated content, messaging, an API, or shared infrastructure, where abuse is most likely and most damaging. It is often not your choice alone: cloud, hosting, and messaging providers require their customers to maintain an AUP and flow its terms down to end users, resellers must pass it through, and app stores and platforms expect clear conduct rules as a condition of distribution.

How to Make Your Acceptable Use Policy Enforceable

An AUP only works if the user is bound by it and you can point to the specific rule they broke. Four things make the difference:

Incorporate it into an accepted agreement. Reference the AUP in your Terms of Service and capture acceptance at signup, so agreeing to the Terms means agreeing to the AUP. A policy linked in a footer, with no acceptance step, is the hardest kind to enforce.

Name specific conduct. Replace "do not misuse the Service" with the exact activities you want the right to act on. An enforcement decision is only as defensible as the rule it points back to.

Reserve a range of responses. State that you may warn, remove content, throttle, suspend, terminate, and report, and that you may act immediately when conduct is illegal or threatens the Service or other users.

Keep it versioned. Date each version and give notice of material changes, so you can show exactly which rules applied when a user acted. Because the AUP updates more often than the Terms, version history matters more here than almost anywhere else.

Handled this way, the AUP becomes a rule the user accepted, giving you a clear basis to act on abuse quickly and to stand behind the decision if it is challenged.

Frequently Asked Questions

For a small or simple product with no user-generated content, messaging, or API, an acceptable-use section inside your Terms of Service is enough. A standalone AUP earns its place once you host user content, send messages, expose an API, or run shared infrastructure, or once several agreements need to point to one set of conduct rules.
Through the agreement that incorporates it. Because the AUP is referenced by your Terms of Service and accepted at signup, breaking it is a breach of contract, which lets you warn, remove content, throttle, suspend, or terminate the account. Enforcement holds up best when you can point to the specific prohibited activity the user agreed not to engage in, so name conduct precisely rather than relying on a general 'do not misuse' line.
The Terms of Service is the full commercial contract: it grants the right to use the product, sets payment terms, allocates liability, and covers IP and termination. The Acceptable Use Policy is the narrower rulebook for conduct, usually incorporated into the Terms by reference. Keeping them separate lets the conduct rules, which change often, be updated without touching the rest of the agreement.
Usually yes, as long as your Terms of Service reserve the right to update the AUP and the version in effect governs use at that time. Post the change, update the effective date, and give notice where the change is material. For significant changes that expand what users agree to, capturing fresh acceptance is the safer course.

Not legal advice

This template is provided for informational purposes only and does not constitute legal advice. Review and adapt it to your specific situation, and consult a qualified attorney before relying on it for a real-world filing or transaction.

Make your acceptable use policy enforceable.

ClickTerm captures acceptance of your acceptable use policy with timestamps, version history, and audit-ready records, so the document holds up when it matters.