Platform terms and rules: the four asymmetries and how to make a rule change survivable

You agreed to a contract the other party may rewrite, enforced by a system that will not explain itself, and judged by the same organization that wrote the rules. No independent appeal.

Every part of that sentence is ordinary and none of it is negotiable. Build anything of value on a platform and you are living inside it.

The useful response is not outrage and not resignation. It is to understand the shape of the relationship precisely enough to decide what you are willing to put inside it.

What to take away

Four asymmetries that define the relationship

These are not abuses. They are the standard structure of the agreements, and they are why the relationship does not behave like a commercial contract between two businesses.

Unilateral change. The service can amend the terms, and in most cases continued use is your acceptance. You are not agreeing to a fixed set of rules; you are agreeing to whatever the rules become. Standard-form agreements offered on a take-it-or-leave-it basis have a name and a body of law of their own in some systems: see an explanation of adhesion contracts, which describes one country's framework and not yours.

Discretion. Enforcement provisions are typically written to leave the decision with the service, in language broad enough to cover conduct the specific rules do not describe. A finding that you did not breach any listed rule is not necessarily a finding in your favor.

Action without prior notice. Most agreements reserve the right to act immediately where the service considers it necessary. In practice, the first notice you receive is often the action itself.

Internal review only. Appeals are decided by the same organization. Some jurisdictions have introduced requirements around notice and internal complaint handling for certain services, and those obligations vary by market and change over time, so check what applies where you are rather than assuming any of it does. The European Union's own description of its rules for online services is one example of such a regime, applying to services within its scope and saying nothing about what reaches you.

In the United States there is no general federal notice and appeal regime for platform decisions. The closest federal hooks are the FTC Act's prohibition on deceptive practices, which can reach how terms are written and changed.

Section 230 of the Communications Decency Act leaves moderation choices to the platform, and state consumer protection laws and contract law can add requirements for some businesses.

The practical consequence is that you cannot rely on the rules staying still. Anything that depends on stability has to get its stability from somewhere else.

The written rule and the enforced rule

Read the published policy and you learn what the service says it prohibits. Watch what actually happens to accounts and you learn something different, and the gap between the two is where most confusion lives.

The gap has structural causes, not dishonest ones. Rules are written in natural language for humans, then enforced by classifiers that operate on features.

A rule about context is enforced by a system with no access to context. A rule with an exception for commentary is enforced by something that cannot reliably tell commentary from endorsement. So the enforced rule ends up narrower or wider than the written one, in ways nobody documented because nobody decided them.

Enforcement also varies over time without any policy changing: thresholds get adjusted, a category gets a temporary sweep after an incident, a market gets a different setting, a system is retrained. None of this is announced, because from the service's point of view no rule changed.

Public examples show the shape of the gap. YouTube's community guidelines run a strike system in which three strikes inside 90 days removes a channel, and a strike can be appealed once. Meta's Oversight Board reviews a small number of content decisions and can overturn them, which is an appeal route but not a general one.

Apple's App Store Review Guidelines set their own rules for what an app may do and offer a separate appeal to the App Review Board after a rejection. None of the three publishes the internal thresholds that decided an individual case.

What follows for you:

The dependency inventory

Before deciding how much to worry, work out what is actually at stake. Most people have never listed it, and the list is longer than expected.

The last row causes the most disproportionate damage and is the cheapest to fix. Using a platform account as the sign-in method for other services means an enforcement action against one account can lock you out of things that have nothing to do with it.

Fill this table in for your own situation and the decision about how much to invest in a given platform becomes much less abstract. A filled row reads like this: audience, followers on one platform and no separate list; if access ends, the reach stops; recovery, none.

Enforcement is a volume operation

Almost everything that feels arbitrary follows from scale. Decisions are made in enormous numbers, quickly, mostly by automated systems, with human review reserved for a small fraction. The characteristic result is a notice that names a broad policy area rather than a specific act, a review that returns in minutes, and no route to a person.

Understanding this changes how you respond. An appeal is not a conversation or a legal argument. It is an input to a process with little attention to give it.

What travels well is short, specific, and factual: what the item was, which rule was cited, why it does not apply, and what evidence supports that, with dates. What travels badly is length, indignation, and argument about the policy in general.

Keep a template ready so you are not writing it under pressure:

It also explains the value of your own archive. If the enforcement decision references the rule as it stands today and your item was published under an earlier version, that is a concrete point an internal reviewer can act on. You can only make it if you kept a dated copy.

Design so a rule change is survivable

You cannot control the rules. You can control how much of what you have built depends on any one set of them.

Keep your own copies. Download your work and the policy that governed it, and put a date on both. A dated copy of the rules is what lets you argue that a decision applied a newer version than the one you published under.

Hold a portable audience. An audience inside a platform is a connection, not a list. A list you control, usually email addresses collected with consent, is the only audience asset that survives an account ending. Consent rules apply, including CAN-SPAM in the United States and CASL in Canada.

Separate your sign-ins. Do not use a platform account to log in to unrelated services. Use an email address you own as the identity for anything that matters, so an enforcement action cannot cascade.

Export on a schedule. Put exports on a calendar rather than reacting to a scare. Quarterly is enough for most small operations.

Read the exit terms. The clause that matters is what happens at termination: what you may take, what the platform keeps, and what happens to any balance owed to you.

Check the export tool before you need it. Formats are often partial, and message history and comments are usually the first thing missing.

None of this is expensive. All of it is much harder to arrange after something has gone wrong, which is when everybody starts.

Reading a change notice

When a change is announced, three things determine whether it matters to you, and none of them is the headline.

Scope. Which surface, which account type, and which markets. A change to advertising policy may not touch organic publishing, and a change announced in one market may not apply where you are.

Commencement. When it takes effect, and whether there is a transition period. Existing arrangements are sometimes given longer, and sometimes not.

Direction. Whether the change narrows what is permitted, widens it, or only changes how something is described. Rewrites for clarity are common and change nothing; they are easy to mistake for substantive changes, and vice versa.

Then ask the question that matters more than the text: does anything you currently do become non-compliant, and if so, by what date. Write that down with a date and an owner, because a change you noticed and did nothing about is the same as a change you missed.

Where the rules end

Platform rules and public law are different systems, and treating one as the other produces bad decisions in both directions.

A platform can ban what no law bans and often does, while allowing what the law where you are forbids, but that permission protects you from nothing.

Regulators impose some obligations on services, which then turn them into rules. So a rule that looks like a business decision may be implementing something else entirely.

The practical point: if the question is whether you may do something, the platform's rules answer only whether the platform will allow it there. Whether it is otherwise permitted is a separate question, answered by a different source, and getting a yes from one tells you nothing about the other.

What to hold on to

The relationship is asymmetric by design. You have preparation, not argument.

Keep your own copies of the rules and your own work. Hold a route to your audience that nobody can revoke. List what you would lose. Treat every appeal as a short factual submission to a busy process, not a case to argue.

Common questions

Is it worth reading the terms before signing up?

Read the parts that decide something: what license you grant over what you upload, how the terms may change, how the agreement ends, and what happens to your material and any balance when it does. Those four determine your exposure. The rest can be looked up when it becomes relevant.

Do the rules apply retroactively?

Enforcement is normally assessed against the rule in force when the act occurred, which is why keeping dated copies is worth the small effort. Whether that principle is honored in a specific case is exactly the thing you may need to demonstrate, and you can only demonstrate it with a copy you took at the time.

If a competitor is doing the same thing and nothing happens to them, is that an argument?

Not a useful one. Enforcement is inconsistent because it is automated and sampled, so the absence of action against someone else is not evidence that the rule permits it. It is evidence that they have not been caught yet.

How much notice will I get before a change?

Plan on the basis of very little. Some changes are announced in advance with a stated effective date, others appear in an updated document with a new timestamp, and some enforcement behavior changes with no document changing at all.

Should I build a business on a platform at all?

Many good businesses are built on platforms. The question is not whether but how much: fill in the dependency inventory, decide what is unacceptable to lose, and move those things off before the business grows around them.