Account ban cases, sorted by violation and level
These account ban cases each take one kind of rule-breaking account on one platform. A case file names the rule that applies, the enforcement level that violation usually draws, what would push it higher and the evidence a report has to carry. They're written from published policy, not from private client work.
Case files on the shelf
- Shelf emptyNo case files yet
The first file lands in this spot, and newer ones will stack above it. Until then, the four levels on the home page are the place to start.
Read the four enforcement levels
A case file here is a type, not a story about a client. Nobody's name, handle or screenshots end up on this site. Each file takes a situation that comes up again and again (the impersonator who copies a shop's photos, the harasser on a third account, the reseller of stolen videos) and works it through the way a moderator would.
Every file follows one order, because that's the order a platform's reviewer works in:
- The behavior. What the account did, described the way a report form would ask for it.
- The rule. The policy line it breaks, quoted from the platform's own page with the date we read it.
- The level. Where that violation usually lands on a first confirmation: a warning, a feature limit, a suspension or a permanent ban.
- The climb. What moves it higher: active strikes, an earlier removal, proof of ban evasion, a severe category.
- The evidence. Which links, dates and captures a report needs, and who has to file it.
- The dead ends. What doesn't work for that case, including the shortcuts people try first.
Files are grouped by violation, since the violation decides more than the platform does. Harassment on Instagram and harassment on X have more in common than harassment and copyright theft on one app. Inside a group you'll find the platform differences spelled out: who counts strikes, for how long and which offenses skip the count.
Two things you won't find. There are no win percentages, because the platform makes the decision and no outsider controls it. And there are no files on how to bring down an account that hasn't broken a rule. If the behavior doesn't match a written policy, the honest level is "none", and a case file would say so. The list of what we won't file covers the rest.
If you'd rather start from the rules than from a situation, the four enforcement levels and the strike counter are explained on the home page.
How to read a case file
Are these real client cases?
No. They're composite situations built from the kinds of requests that come in and from the platforms' published rules. No client's account, target or evidence is ever shown.
Why does a file give a level and not a result?
Because the level is what the written policy supports, and the result is whatever the platform's reviewer decides that day. A file can tell you a violation usually draws a feature limit. It can't tell you this one will.
My situation matches a file. Can I just file the report myself?
Yes, and for a simple first violation that's often enough. The in-app report is free. Hiring help makes sense when the evidence is scattered, the account keeps coming back or the right form isn't obvious.
Why are files grouped by violation and not by platform?
The violation decides which form you use, what evidence counts and whether strikes apply at all. The platform mostly changes the numbers.
Case files are AccountBan's own reading of public platform policies. No platform has reviewed or approved them, and the current policy page always outranks what's written here.