---
title: Public controversy check in People
description: Turn on an optional check that flags people in Venom People who also appear on CancelPeople.com, with a neutral summary and things to watch out for when engaging. Off by default; names are matched on your server and never sent to the site.
section: cloud
order: 167
audience: [user, operator]
sources: ["services/nodejs-cloud/lib/people/controversy.ts", "services/nodejs-cloud/lib/people/controversy-model.ts", "services/nodejs-cloud/lib/people/tools-controversy.ts", "services/nodejs-cloud/app/(people)/people/settings", "services/nodejs-cloud/components/people/ControversyPanel.tsx", "services/nodejs-cloud/migrations/0222_people_controversy.sql"]
features: [cloud.page-people, cloud.migrations]
---

Before you reach out to someone, it can help to know if they have been the subject of public criticism. The public
controversy check adds that as **one more signal** on whether and how to engage a person. It is never a block and never a
verdict: Venom does not decide anything about the person, and it does not stop you from adding, messaging or meeting them.

The source is [CancelPeople.com](https://cancelpeople.com), a public website that lists people who were publicly criticised
and writes up what was reported. Venom has not verified any of it, and allegations are allegations.

## It is off until an owner or admin turns it on

It is an outbound call, so it is off by default. An owner or admin turns it on under **People → Settings** (`/people/settings`, **Public controversy
check (CancelPeople.com)**) (or with the `people_controversy_set` tool). Nothing contacts the site until then.

## What is fetched, and when

While at least one organisation has the check on, the Venom Cloud server fetches, **at most once a day** for the whole install:

- the site's public index, one text file (about 350 KB) listing every entry's name and page, and
- the site's category and offense pages (about 26 pages, a few MB in all), which say which categories each entry is in.

Then, for a person who matches (below), the server fetches **that person's own page on the site once, and again once a week**.
The requests go to `cancelpeople.com` only, over https, with no redirects off that host, a timeout and a size cap. They carry
no cookies and nothing about you, your organisation or your contacts.

## Names are matched on your server

Venom compares each person's full name with the downloaded index on your own server (accents, capitals and punctuation are
ignored). **No name from your People is ever sent to the site.** A first name alone is never matched, and there is no fuzzy
matching: the full name has to be the same.

A name match is only a **possible match**, because names collide. It gets an amber outline badge, "Possible match", on the
person's row in the list and on their page, and nothing else changes. If two entries share a name, both appear.

## Confirm or dismiss

On the person's page the panel **Public controversy · CancelPeople.com** shows what was found. Compare the "same person"
hints (company, role, location the page mentions) with the profile, then press:

- **Same person**: the badge becomes the solid amber "Public controversy", with the categories as its tooltip.
- **Not this person**: the badge goes away. It does not come back unless the page's content changes later.
- **Check again**: runs the check for this person now.

Anyone who can see the person sees the badge and the panel. Confirming or dismissing is shared with everyone who can see the
person, and needs write access to People.

## The summary

For a possible or confirmed match, the page is read once and summarised by **your organisation's own model** (the same gear and
the same daily People AI limit as the context card). It writes, in neutral and attributed words ("CancelPeople.com reports…"):

- what is reported, in two to four sentences;
- the categories the site lists (never ones it does not);
- the current status as the page reports it;
- three to six **things to watch out for when engaging** (reputational association, topics to handle with care, what to verify
  independently, whether the matter appears resolved);
- facts from the page that help you confirm it is the same person.

The model is told to add no claims of its own, to treat everything as an allegation unless the page states a court finding, to
say when a page is thin or unsourced, and never to advise discriminating against the person. The source link and the date it
was last checked are always shown. If the model is unavailable or the limit is reached, the match stays and the summary is
retried later.

## Refresh

Matched pages are re-fetched weekly. The summary is rewritten only when the page's content changed (a model call costs money),
and the panel shows when it changed. If an entry leaves the site's index, the panel says "No longer listed" with the date it
was checked, and the badge goes.

## For agents

The workspace MCP server has tools for all of it (`people_controversy_get`, `people_controversy_list` (which also says whether the check is on),
`people_controversy_run`, `people_controversy_decide` and `people_controversy_set`), and the REST twins under `/api/v1/people/…/controversy`. See
[People for agents](/docs/cloud/people-mcp).

## Turning it off

Turning the check off **deletes your organisation's stored matches, page texts and summaries** straight away. When no
organisation on the install has it on, the downloaded index is deleted too. Turning it on again starts from scratch.

## Self-hosted installs

`cancelpeople.com` is the only host this feature contacts. An air-gapped install simply leaves it off: the switch is the only
thing that ever causes a request.
