← Back to Concept Contrast

Concept Contrast Fable

Usage Policy and Acceptable Use Policy: one governs how it may be used, the other governs what is prohibited

Conclusion first:Usage policies describe the permitted ways to use a platform, including quotas, frequency, and feature scope, usually aimed at the operational level for developers or users. Acceptable use policies draw the red lines—what behavior will be prohibited or even result in account suspension. Both are posted on the same page, but their legal force is completely different: violating a usage policy may get you a rate-limit notice, while violating an acceptable use policy may get you a lawyer's letter.

Usage policies describe the permitted ways to use a platform, including quotas, frequency, and feature scope, usually aimed at the operational level for developers or users. Acceptable use policies draw the red lines—what behavior will be prohibited or even result in account suspension. Both are posted on the same page, but their legal force is completely different: violating a usage policy may get you a rate-limit notice, while violating an acceptable use policy may get you a lawyer's letter.

Fable

The inn had two signs, one reading "Guest Room Usage" and the other reading "Immediate Expulsion"

By the canal there was an inn for travelers from north and south, with two wooden signs hanging at the door. The left one described the services the inn provided: hot water was available for one shichen in the morning and one in the evening; the kitchen could be lent to guests to heat food but frying was forbidden; two cellars held ice and stored wine respectively and were for the use of first-floor residents only. This sign was called the "usage guide"—it told you what you could do at this inn, how to use it, and when to use it.

The words on the sign on the right are red and list only five rules: no gambling, no bringing in firearms, no keeping livestock in guest rooms, no robbing other guests, no unauthorized demolition of the inn's walls. Under each rule is a sentence—"Violators will be expelled immediately, with no appeal to officials." This sign is called the "expulsion order"—it tells you what will get you thrown out, with no room for negotiation.

Half a year after the inn opened, a silk merchant checked in. On the third night, he moved the ice blocks from the cellar into his room to cool and dehumidify the silk. The shopkeeper found out and told him that ice could only be used on the first floor; he could use it, but he had to complete the paperwork. The merchant completed the paperwork, and the matter was settled. In the same month, another guest set up a private gambling game in his room. When the shopkeeper found out, he said nothing and that same night had the constable take the man and the gambling equipment away together.

These two matters left the inn's staff very confused: why could the ice matter be fixed with paperwork, while the gambling matter could not even be mentioned? The innkeeper called the staff together: the sign on the left is the terms of service, and I can interpret it flexibly—bringing ice up to your room merely adds a bit of management cost and leaves one floor's residents with less ice, but it is not a safety bottom line. The sign on the right states my security commitment signed with the authorities; once someone gambles, it is not merely a breach of contract, it is illegal.

The inn later explained the difference between the two signs more clearly: the one on the left governed how the service was used, how much was used, and when it was used; the one on the right governed the bottom line, and touching it was not a matter of fixing paperwork. The former was like house rules, the latter like an eviction order. Only then did the staff understand that moving ice to the wrong floor could be fixed with a registration, but running a gambling game in a guest room could not.

The inn later faced a more complex situation: a guest writing a novel asked a staff member to check the inn's guest register three times. The innkeeper found out and said this violated the sign on the right—'No prying into other guests' information.' The guest argued that he needed material for his book, and the sign on the left said 'Guest information in public areas may be consulted.' The innkeeper said no—privately asking a staff member to check bypassed the public-area boundary; the intent was not consultation, and the key was collection. This judgment is still a qualitative AUP judgment, not a matter of usage frequency.

The shopkeeper later left the staff a rule of judgment: for the same action, the badge on the left governs quantity and method, while the badge on the right governs nature and intent. The amount of the fine is only surface; overstepping usage harms the inn's order, while overstepping an expulsion order harms the inn's reputation and legal bottom line.

Usage policy

Define the platform's acceptable normal usage range and operating parameters, including rate limits, feature availability and resource quotas. Violations usually lead to throttling or warnings, and the core concern is maintaining service quality.

Acceptable Use Policy

Legal and policy red lines defining prohibited conduct, including illegal use, abuse, safety, and ethical taboos. Violations can lead to account bans and legal action; the core purpose is to maintain platform trust and legal compliance.

Story Mapping

  • The sign on the left, "Usage Guide": usage strategy, telling you the normal operating boundaries and available features
  • The red sign on the right, "Order of Expulsion": acceptable use policy, telling you that crossing the line means expulsion
  • The silk merchant moving ice blocks was asked to complete additional procedures: usage policy violation, flexible handling
  • Guest running a private gambling ring is immediately evicted: AUP violation, zero tolerance
  • The clerk's confusion: the intuitive source of two signs with different rules and different consequences
  • Novel-writing client checks records: in gray areas, intent judgment remains a question of nature at the AUP level
  • API batch scraping example: the same operation, where policy governs volume and policy governs quality and intent

Applied to drafting platform terms and developer compliance checks

If you are a product or legal person at an API platform, split the usage policy and the AUP into two separate pages rather than cramming them into one document. The usage policy should spell out rate limits, concurrency caps, feature tiers and overage handling rules. The AUP should list prohibited behaviors separately, each with a sentence on its legal basis or consequences. When developers do a compliance self-check, they should check the AUP first: will your use case trigger a ban-level red line? Once past that, check the usage policy: does your call volume require applying for extra quota? Reversing the order will have you haggling over usage while forgetting you are standing on a red line.

京ICP备2026014272号