8.5 Account Management and Surviving Bans

The ban signal travels with the device and the network, not with the content. [UNVERIFIED] A restriction applied to one account on a device or network is reported to correlate with restrictions on other accounts created or operated from the same device or network — including accounts whose content never violated anything.

One operator's reported case: seven accounts, each with 200,000 to 500,000 followers, all restricted, with appeals succeeding in two cases.

What this means practically. Content compliance is necessary and not sufficient. Two accounts on one phone are not two independent accounts; they are one account with two profiles, from the platform's enforcement perspective. Every isolation decision in this chapter follows from that single observation.

The honest caveat. [UNVERIFIED] This is a pattern reported by operators, not a published mechanism. Platforms do not disclose their signals, and the correlation could have other causes — the same operator running the same risky practices across all seven accounts, for instance. The isolation practices below are cheap enough that they are worth adopting regardless of whether the mechanism is exactly as described.

Isolation by layer

Five layers, each independently separating accounts.

What this costs. A second device is the real expense. Everything else is configuration: a second browser profile, a second email, a second phone number for verification. The device is where operators economize, and it is the layer most associated with the reported correlation.

What to do if you only have one device. Accept the risk explicitly and prioritize accordingly: one primary account that you protect obsessively, rather than three accounts that share a failure. This is a legitimate strategy, and it is the one most solo operators should choose.

Link hygiene

A specific and underappreciated flag: the direct link from a social platform to a monetization platform.

Why it is a flag. The pattern is recognizable — a new account whose bio links directly to a subscription platform reads as promotional infrastructure rather than as a content account. It is also the pattern that platform classification systems are built to detect.

The mitigation, which is also better funnel design. Route through an intermediate step: a landing page, a link-in-bio service, an intermediate channel, or a code. Chapter 10.1 covers the routing architecture; this chapter's point is that the intermediate step makes the routing less legible to the platform as well as more measurable for you.

Two further link practices:

• Do not use the same shortened link across accounts. A shared redirect destination joins accounts.
• Do not put a monetization link in the bio of a brand-new account. This is what the silence phase in 8.2 prevents.

The appeal procedure

When an account is restricted, the appeal is the only remedy, and most appeals fail because they are written badly.

What to include:

• A plain statement of what the account is. Including, for a synthetic persona, an explicit statement that the account is an AI persona and is disclosed as such. Hiding this turns a labeling issue into deception.
• Which policy you believe was misapplied, by name if you can find it.
• The evidence that your disclosure practice is consistent — the specific posts, the date the disclosure was added, the templates used (11.3).
• A request for the specific reason, which is the one question an appeal can usefully ask.
• One appeal, then a follow-up. Repeated appeals do not help and can be read as abuse.

What not to write: anger, accusations of bias, threats, a claim that the platform is wrong about the facts without evidence, or a long narrative of how much the account means to you. None of these affect the outcome and some worsen it.

How long it takes. [UNVERIFIED] Operators report days to several weeks, with no reliable pattern, and a substantial share of appeals failing. Plan on failure being the likely outcome, which is why the Plan B below matters more than the appeal.

What to do first, before appealing: download or export anything the platform allows, including your follower list if the platform provides it, your post archive, and your analytics. Do this on the day the restriction appears, because access can disappear.

Plan B, built in advance

The practices that turn an account loss from a catastrophe into a setback.

Own your audience elsewhere. A mailing list or a channel is the only audience asset a platform cannot take. Chapter 10.1's funnel includes an intermediate channel for exactly this reason: it is both a conversion step and an insurance policy. A persona with 50,000 followers and 2,000 email subscribers survives losing the account; a persona with 50,000 followers and no list does not.

Keep the canonical assets outside the platforms. References, adapters, prompt lists, and masters live in your own storage (7.4). This is already the architecture, and this chapter is the reason.

Maintain a real presence on the secondary platform. Chapter 8.1's secondary is not decoration. If the primary is lost, an existing secondary with a real audience is where the announcement happens.

Register with whichever platforms allow advance protection. Some platforms offer additional verification or account protection measures for creators. Where they exist, they are worth the effort.

Document what you published and when. Chapter 7.4's metadata and 11.3's disclosure records are also the evidence you need in an appeal and the material you need for a migration announcement.

Account hygiene as a routine

Four habits that reduce the chance of losing an account, all cheap.

One account per environment. The isolation table above, applied consistently rather than when convenient.

No automation of platform actions. Chapter 7.3's table: engagement automation is the enforceable violation and the one that most often ends accounts.

Disclosure kept current. Every post labeled, consistently, from the first one. A lapse is an enforcement opportunity.

Keep the credentials recoverable. Recovery email and phone kept current, two-factor enabled, backup codes stored somewhere you will find them. Losing access to your own account for an administrative reason is a common and entirely preventable loss.

A migration plan, on one page

If the primary account is lost, the first week decides whether the audience follows you or disperses. The plan is short because it has to be executable under stress.

Day 1. Export whatever is still accessible. Post a short, factual note on the secondary platform and on the ownership channel, stating where you will publish going forward. No grievance narrative; the audience needs the destination, not the complaint.

Day 2–3. File the appeal using the template above. Simultaneously, verify that the ownership channel and the secondary platform are both live and reachable from your site or link-in-bio.

Day 4–7. Resume the posting cadence on the secondary platform at the normal frequency, with the same format mix. The consistency matters more than the content quality this week, because the signal being sent is that the account still exists.

What the plan assumes, and why each assumption is a prerequisite rather than a hope: canonical assets are already local (7.4), the ownership channel already has members (10.1), the secondary platform already has a real audience (8.1), and the disclosure records are already exportable (7.4, 11.3). Every one of those is built before the incident, which is the whole argument of this chapter.

Where this goes wrong

Two accounts on one device. One failure, two casualties, on the reported mechanism.

A direct monetization link in the bio of a new account. The recognizable pattern.

No mailing list or channel. The audience is rented and the landlord can evict you.

Appealing without exporting first. You lose access to what you needed for the appeal.

An angry appeal. No effect on the outcome, some risk of making it worse.

Repeated appeals. Read as abuse.

Canonical assets kept only on the platform. The ban takes the work as well as the audience.

No second platform presence. Nowhere to announce, nowhere to recover.

The gate

1. Do you operate one account per device and network, or have you accepted a single-account strategy deliberately?
2. Is there an intermediate step between the social platform and the monetization platform?
3. Do you own an audience channel that no platform can remove?
4. Are your canonical assets stored outside the platforms?
5. Do you have a written appeal template that states the account's nature and its disclosure practice?
6. Are the credentials recoverable, with two-factor and backup codes stored?

What you leave with

The reported finding that the ban signal follows device and network rather than content, with an honest caveat and the practical conclusion that content compliance is necessary and not sufficient, a five-layer isolation table with the cost of each and a legitimate single-account strategy, link hygiene including the direct-link flag and why the funnel fix is also the safety fix, an appeal procedure with what to include and what to avoid plus the export step that comes first, a four-part Plan B built before it is needed, and four account hygiene habits.