Skip to content

Your first anonymization

This walkthrough takes one document from drop to safe copy.

Drag a file (or a folder) onto the Piixie window, or click the drop zone to browse. Piixie accepts .txt, .md, .pdf, and .docx files. Files land in a queue where you can review them before anything is processed.

For PDFs, Piixie counts embedded images up front so you know whether image redaction will come into play.

Each queued file gets an anonymization mode. The three everyday choices:

ModeWhat happensGood for
RedactionPII becomes [REDACTED] markersMaximum certainty, legal review
ReplacementNumbered tokens like [NAME_1], [EMAIL_2]Keeping entities distinguishable
SyntheticPlausible fake values (“Marcus Patel” → “Ethan Vance”)Documents that must read naturally

Two more modes, LLM Gen and JavaScript, are available through profiles. The full comparison is on the modes page.

You can also pick a profile instead of a bare mode. A profile carries its own mode plus prompts, field rules, and replacement dictionaries.

Hit process. A dialog follows the run:

  • A progress bar shows how far through the text the model has got, with the time left.
  • A long document is read in parts, shown as segments under the bar (“Part 3 of 8”).
  • Entries lists what the model finds as it finds it: each value with its type (NAME, ORG, ID…). Public names it keeps as they are are marked kept.
  • Model output shows the model’s raw answer as it streams, and its reasoning when the model writes one, for those who want to see it work.

You can cancel at any point; nothing is written until the run completes.

If the selected model can’t analyze images and the file contains some, Piixie asks before proceeding: continue text-only, blur all images automatically, or apply the choice to every file in the queue.

The anonymized copy is written to Piixie’s output folder inside its app data directory, unless you set a different output location (same folder as the original, or a custom directory). The history tab records the run with a full replacement table: every detected entity, its type, the original text, and what it became.

Keep the original and the safe copy side by side until you trust the result. Models are good at this, but they are not infallible. Skim for anything that slipped through, especially short name forms and dates.

Send the anonymized output wherever the original couldn’t go: an LLM prompt, a support ticket, a shared test fixture, a demo.