What to do after a ban

An hour of reading costs nothing, and an hour of fixing can cost the rest of the group. A block is information about what a platform matched, and it reads clearest before anything moves.

Write down three things: what the screen said, which profile it was, and when that profile last opened. Everything below is built on those.

An identity check that came back refused, a suspension for what the account did, and a link to another account are three different events behind one screen.

They differ in what the platform has already decided, and so in what is left to do.

The cheapest evidence is the wording on the screen. A document request points at the first, a named rule at the second, and a mention of another account or of your network at the third.

When the wording names nothing, the timing does. A block minutes after a new sign in points at the exit, and one after a run of actions points at the pace.

Three moves turn one lost account into a lost group, and all three come to mind on the first day.

• A replacement from the same place

  A new account on the profile and the exit just flagged hands the platform the pair it was looking for.

• A message from a second account

  Writing to support from another of your accounts confirms in your own words that both are one person.

• A hurried clean up

  Cleared cookies change your side only. The platform keeps what it has read, and you lose the record of what the profile was running on.

A block travels through what the profile shares with the others. Two of those are worth breaking today: the exit it leaves through and the list it sits in.

• An exit of its own

  Assign proxy on the row ties a profile to one library entry, and a tick box hands a pool out one entry per profile.

• A group of its own

  A group is a name and a colour on the list, and the filter above it keeps the profile out of your next selection.

• A folder in a team

  Folders decide which profiles a teammate sees at all, so the one under review stops being opened out of habit.

Signed in, the workspace history lists who opened which profile, who stopped it, who signed in and from which country.

Profile edits sit there field by field, with the old value and the new one. A secret field shows only that it was edited.

The dashboard reads that history back and names three shapes. A platform can act on each one without knowing anything else about you.

• Four or more profiles on one address

  A cluster behind one exit is banned as a cluster, and it does not need them open at once.

• A run of launches inside a minute

  Openings with almost no gap between them read as one script behind every account.

• A sign in from an unusual country

  It is counted per person, so a colleague's usual country is never treated as yours.

The fingerprint card shows what a site reads through a profile: screen, graphics card, cores, fonts, time zone and language list. None of it is stored, so every launch computes the same machine.

Compare with other profiles counts how many of your own describe that machine. That number matters most after a block: two profiles with one machine are tied more tightly than by anything else here.

Delete moves a profile to the recycle bin. It stops counting against your plan, while its cookies and its whole folder stay on disk.

Erasing for good takes the browser folder, the schedules, the counters and the sealed session in your shared folder, and with them your only record of what went wrong.