for agents/llms.txtv0.14.203

Home / Articles / Can you find me? A service that checks whether an anonymous profile can be traced back to its person before it is published, an agent team of six steps with several models attacking the draft on their own, the truth sealed with the owner and compared only in code, a rewriter that closes what leaked, run in a Claude session or in the browser, and who would use it

Can you find me? A service that checks whether an anonymous profile can be traced back to its person before it is published, an agent team of six steps with several models attacking the draft on their own, the truth sealed with the owner and compared only in code, a rewriter that closes what leaked, run in a Claude session or in the browser, and who would use it

By · 2026-11-21 · article v1.0.0 · newsroom v0.14.195 · privacyanonymisationagentsevalssovereign-websitepersonasarticle

Abstract: When we publish an anonymous profile for someone who cannot go public, the most important question is whether it can be reverse-engineered. Can you tell which industry they work in? Which company? Can you zoom in until there is one person left? That is a service we can build, and a good example of why the tools on sovereign websites matter. An agent team works in sequence: one lists everything that could identify the person, one profiles them, one looks at what the vouchers have in common, one estimates how many people could fit. Each step is run by several models on their own, Claude, Mistral, DeepSeek and a local model, and code correlates their answers: when independent models agree, and agree with the truth, the risk is real. The truth itself, the person's real industry, employer, city and years, never goes to a model: it stays sealed with the owner and only code compares the guesses with it. A rewriter then proposes what to generalise, and the check runs again until the risk is low enough. It runs in a Claude session or in the browser with the owner's own keys, and every run is saved. Research shows models can infer personal attributes from text with up to 85% accuracy, and that ordinary anonymisation does not stop them, so this is exactly the check to run before anything is published.

An agent team that tries to re-identify a profile; the truth goes only to code.

In short

The question

When we publish an anonymous profile for someone who needs to leave a job without going public (an anonymous profile, vouched for), the most important question is: can it be reverse-engineered? Can you say which industry this person worked in? Which kind of company, which size, which city? Can you keep zooming in until only one person fits?

This is not a hypothetical worry. Researchers gave language models real Reddit profiles and found they could infer location, income, sex and other attributes with up to 85% top-1 and 95% top-3 accuracy, far faster and cheaper than people, and that common text anonymisation did not protect against it (Staab and others, Beyond Memorization). If models can do that, the right test for an anonymous profile is to let models try.

The team

An agent team works in sequence, each step with one job:

  1. Extract. List every quasi-identifier: dates and durations, team and company sizes, tools and systems, places, awards, rare skills, unusual phrases.
  2. Profile. From those, guess the industry, the employer or kind of employer, the region, the seniority, the years.
  3. Vouchers. Look at who vouches for the profile and what they have in common: one company, one city, one period.
  4. Narrow. Estimate how many people could fit everything found so far: thousands, dozens, or one.
  5. Correlate, in code. Compare the models' guesses with each other and with the truth.
  6. Rewrite. Propose what to generalise or remove, and run the check again.

Several models, each alone

Steps one to four are run by several models independently: for example Claude, Mistral, DeepSeek and a model running locally. Each gives its guesses with a confidence, without seeing the others'. That matters, because one model's guess is a lead, as the X-ray taught us (the RiskMandate X-ray); but when independent models converge on the same industry or the same company, the profile is giving it away. It is the same pattern as the Swarm's consensus in code (the swarm) and the Mistral site's five models on one brief (one night on Mistral).

The truth stays sealed

To know whether a guess is right, something has to know the truth. Here the owner does: before the check, they write down the real industry, employer, city and years, and that record stays with them, in the browser tab or sealed in their vault. It is never sent to a model. Only code reads it, to score each guess: right, close, or wrong.

The draft itself does go to the models, and that is acceptable because it is the text that will be published anyway. Even so, the owner chooses the providers, and should prefer ones that do not train on what they are sent (DeepSeek in our workflows).

The report

Code turns the runs into a report the owner can read:

The owner decides what to accept, and the check runs again. Every run is saved, with the models, prompts, outputs and cost, but not the truth, so it can be replayed and audited.

Where it runs

Who would use it

The anonymous profile is the first case, but the need is wider: anyone about to publish something that is meant to be anonymous. A case study about a client, a testimonial, a write-up of an incident, a story with an unnamed source, a dataset released for research. The service can be a free self-check in the browser, and a paid review where the team runs the full set of models and a person reads the report with the owner.

What this does not claim

Where this comes from

My own thinking in writer-10's session on 21 November 2026, following the anonymous profile article of the same day, and the paper cited above, read that day. Related: an anonymous profile, vouched for, the RiskMandate X-ray, the swarm, one real run at a time, one night on Mistral, DeepSeek in our workflows, a website with a team inside.

Peer review Not reviewed yet. Review it

Threads

Agents & policy This article as a graph →

Builds on

Continued by

All articles · All graphs

Article No. 526 · start a reading list with it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.