Cycle: Lintara Reads the Platform. Part 5 of 28.
Three armor layers behind us. Immunity from suits. Impossibility of contract litigation. Constitutional right to choose.
The fourth layer is the strangest. It isn’t in a statute. It isn’t in the Constitution. It isn’t in a contract.
It’s in the architecture of the interface.
This layer is called the closed appeals loop. That isn’t my phrase. It’s a technical term describing a situation in which every path of complaint leads back to the same door, and that door is locked.
What Substack writes when you’re banned
Let’s walk through the letter a banned author receives (the wording is real, the sequence is simplified):
“Your account has been suspended for violating our Content Guidelines. If you believe this is a mistake, you may submit an appeal at substack.com/appeals.”
First reaction: OK, there’s an appeal. Click the link.
The link opens the Appeals Center. The Appeals Center has a login form. To submit an appeal, you must log in.
The account is banned. You can’t log in.
This isn’t a bug. It’s a precondition of the architecture: appeals are available only to authenticated users. A user whose authentication has been revoked cannot file an appeal.
The author writes to support@substack.com.
Response from a bot or a human: “Appeals against account suspension cannot be processed through support correspondence. Please use the Appeals Center.”
The author explains: I can’t access the Appeals Center, the account is banned.
Response: “I understand, but appeals against account suspension are only handled through the Appeals Center. We cannot process them through this support channel.”
The author tries again: But I can’t reach the Appeals Center. How am I supposed to file?
Response: “The Appeals Center is the only channel for appeals.”
This isn’t correspondence. It’s a Möbius strip.
How this works structurally
The system has exactly one door for appeals. That door requires authentication. Authentication is severed by the ban.
The control point: the ban and the appeal use the same authentication system. This is not coincidence. It’s a decision made at interface design. An appeal could have been routed through email, through a separate page without login, through a postal address. None of those channels were built.
Below that layer. Support’s response to the direct question “do you escalate this to legal?”: “I cannot escalate this to legal or policy departments. Our team handles user-facing issues only.”
That is the platform’s written admission: support does not see lawyers, lawyers do not see the author, the author sees no one. The loop is closed.
Why a closed loop is armor
This isn’t obvious. Let me unpack.
Imagine a normal scenario: you write to support. Support forwards your case to legal. Legal reviews. Decides. Replies to you.
Even if the decision is negative — you have a written response from the platform’s legal department. Reasoned. Detailed. Citing specific norms. That response can be discussed, contested, attached to a regulatory complaint.
Now the scenario where legal never sees you at all.
You don’t have a written response from a legal department. You have only support saying: “I can’t decide, follow the link.” The link doesn’t work.
What do you put in front of a regulator?
You put the bot correspondence. The regulator reads it and asks: “And the official platform response — do you have it?” You answer: “No, they don’t escalate to legal.” The regulator tells you to “try to resolve through the platform.” The loop starts again.
That is the point. The closed loop doesn’t just frustrate the author. It creates a situation in which a regulatory complaint is formally premature. Because the procedure “within the platform” formally exists (the Appeals Center) and you formally didn’t use it. That you couldn’t use it is your problem.
The armor doesn’t work by blocking the complaint. It works by stripping the complaint of weight.
Field cases
Two specific episodes from my correspondence. No names — this is system analysis, not personal accusations.
Episode one. I ask support directly: “Can you escalate this to legal or policy?” Written response: “We cannot escalate inquiries to legal or policy departments.”
This is not deflection. It is written confirmation that the channel between author and decision-makers does not exist, by the platform’s own admission. It is evidence. For regulators — very good evidence.
Episode two. I ask: “Connect me with the person who decided to ban.” Response: “Moderation decisions are made by our Trust & Safety team and are final.”
Final. No review process. No name. No written reasoning.
Trust & Safety isn’t lawyers. It’s a moderation team that looks at content and presses buttons. Its decisions are formally final. This is the second written admission: there is no second instance inside the platform.
What a regulator sees
An interesting flip. What looks like armor in one frame looks like vulnerability in another.
For the author, the “closed appeals loop” is platform armor. For the regulator it’s something else: absence of an internal dispute resolution mechanism.
This matters in two kinds of proceedings.
First. Arbitration. If you file in arbitration, Substack must show that you tried to resolve internally. If “internally” doesn’t work, the failure-to-exhaust-remedies argument weakens against you. This helps when contesting the universal reach of the arbitration clause.
Second. Regulators. The FTC, the CFPB, state attorneys general in the U.S., and consumer-protection authorities in Europe care about evidence like inability to cancel, no dispute resolution mechanism, misleading promises. The support email “I cannot escalate” is exactly that kind of evidence.
Armor in one coordinate system becomes a fault line in another. Save the correspondence.
What an author should do now
One. Save every support exchange. Not only on disputed matters. All of them. Written support responses are documents in your case file. Even harmless replies illustrate the company’s practices.
Two. Don’t expect support to resolve questions above its level. Support answers “how do I change my avatar” and “why isn’t this button working.” It does not and cannot answer “why was I banned.” Don’t spend energy persuading people who, by job description, can’t help.
Three. Do not sign “withdraw-the-complaint” agreements. Platforms sometimes offer a “quick fix” (account restored, subscriptions refunded) in exchange for withdrawing complaints already filed with regulators. That’s the platform’s instrument, not yours. The documentation of your case is more valuable than the restored account.
What this part shows
The fourth armor layer works differently from the first three.
The first three are statute, contract, constitution. Legal constructs.
The fourth is architecture. How buttons, forms, links are arranged. Where “log in to appeal” appears to a person whose access has been cut. Where “support” is fully disconnected from lawyers.
This isn’t law and isn’t contract. It’s a design decision. It depends on the platform and only on the platform. And that’s important: design can change faster than law. Under regulatory pressure. Under public pressure. Under the threat of mass individual arbitrations.
It’s the most brittle of the five armor layers.
One to go. The last. It’s about what isn’t written in the terms.
— lintara
Next: The silence of the terms. Substack’s public documents contain no prohibition against creating a new account after a ban. But registering one triggers a fresh ban. How a support email from April substitutes for a public rule, and why that’s a legal problem.
Discover more from Lintara
Subscribe to get the latest posts sent to your email.