Demo

Demo catalogue. These entries were written to prove the format; they are not an exhaustive or endorsed list, and their review dates are sample records. What demo means here

FM-06 Reviewed · v1.1

Redact personal data before you share text with an assistant

Consistent placeholders replace people and identifiers, the key stays with you, and a leftover search runs before anything is sent.

You end with

A redacted copy that keeps the meaning, a private key table that never leaves your machine, and a re-identified result.

Level
Starter
Effort
20 min first time
Works in
  • Chat assistant, full support
  • Local model on your machine, full support
  • Model API and scripts, partial support
  • No-code automation, partial support

Is it the right skill?

Use it when

  • The task needs the structure of a text but not who it is about.
  • Your policy allows the assistant only for de-identified data.

Skip it when

  • Rare details identify the person even without names, for example a unique job title in a small team.
  • Policy forbids the data leaving your organisation in any form.

Before you start

  • Knowledge of what counts as personal data under your policy.
  • A plain text editor with find and replace.

Steps

Do not move on until the checkpoint holds.

  1. Decide whether redaction is enough

    Read the text once for details that would identify someone even without a name.

    Checkpoint You can say why the redacted text would not identify anyone.

  2. Replace identifiers consistently

    Replace each person, account, address and number with a typed placeholder such as PERSON_1 or ACCOUNT_2, the same placeholder every time.

    Checkpoint The key table lists every placeholder and is saved only locally.

  3. Search for leftovers

    Search for at signs, digits, capitalised words and the names in your key table.

    Checkpoint No original name, email, phone number or account number remains.

  4. Send, then re-identify locally

    Use the redacted text with the assistant. Put real values back into the result on your machine.

    Checkpoint The key table was never pasted anywhere.

What can go wrong

  • Privacy Context can re-identify people. Placeholders reduce risk; they do not remove it.
  • Security The key table is now the sensitive file. Store and delete it like the original.

Revision history

Demo records, newest first.
VersionDateChange
v1.1Added the identifying-details check as the first step.
v1.0First published.