The recurrence hold
Only recurring incidents go public
Ghostedcheck does not highlight a one-off complaint. A filing is accepted, then held, until independent first-hand accounts of the same pattern show up at the same company. The threshold is computed from the ledger itself. It is not staff approval, not a fact-check, and not proof that anyone applied.
01
Screens first
Automated filters reject names of people, contact details, threats, slurs, confidential material, and obvious spam. That happens before a filing is stored.
02
Held until it recurs
A stored filing stays off the public ledger. Ghostedcheck counts distinct connections that describe the same hiring pattern at the same company. One connection cannot corroborate itself.
03
The bar moves itself
The number required starts at three. It rises if that cluster — or the ledger, or that pattern — is being flagged or hidden. It eases once a pattern is already public. No one is scoring your prose.
04
Flags can pull it back
After a report is public, readers can flag a guideline break. Enough distinct flags hide it. If the cluster then falls below the bar, remaining reports in that cluster are held again.
What this is not
- Not a fact-check. Three matching accounts can all be wrong. The hold only asks whether a pattern recurred in the filings, not whether a story is true.
- Not a consumer report. Do not use the ledger to make employment, credit, insurance, or tenant decisions about any person.
- Not Ghostedcheck’s speech. Holding, releasing, or hiding a report is an automated integrity step. It does not make remaining reports the site’s own statements.
- Not an identity check. There are no accounts. Distinct connections are hashed for this hold and for rate limits. That is not a directory of users.
The same rule is in the community guidelines, terms, privacy policy, and legal notices. Those pages are not legal advice.