Detection
Community reports and the verdict cache
A shared, anonymous database of verdicts keyed by a hash of the content. It holds earlier rechecks, classifier results and report tallies, never who produced them.
Updated
What the cache is
Every piece of content the extension checks is identified by a one-way hash. Against that hash we keep the kind of content, the score, the label, each detector's signal and notes, any model recheck, the source URL of an image (so the same image on two sites resolves to one verdict), and a hit count. Nothing in an entry identifies a user: no account id, no session, no IP address, and never the text itself.
What the Community row shows
When your extension checks a post, our API looks the hash up. If earlier Pro users triggered a classifier or a recheck on it, those rows appear in your card as if you had run them. If people have reported the post, the row shows the tally; Agrees means the reports lean the same way as the verdict, and "No reports yet" means nobody has voted.
How reports change scores
Reports only count once three or more exist for the same content, and only for content with no provenance, classifier or recheck signal: the writing-pattern score is blended 75/25 with the report ratio. A verified signature cannot be outvoted.
Why it is shared
Paid checks are budgeted. Caching them means one Pro recheck of a viral post helps everyone who scrolls past it, and nobody pays twice for the same image.
Removal
Entries are anonymous, so deleting your account does not remove them. If an image source URL in an entry identifies you, email privacy@slopsquash.com and we will purge that entry. Copyright complaints about a URL go to dmca@slopsquash.com. See DMCA and removal requests.