Run anonymization and restore flows

Use this skill when you need to anonymize text/files, restore placeholders with a saved map, or tune the local detector.

Maintainer-only validation assets are excluded from ClawHub uploads.

Scope

• - Included:

• - Not included:

Working directory

Run these commands from inside the privacy-protector folder.

Requirements

• - Hard requirement: INLINECODE6
• Optional package: requests for API-backed dynamic, strict, and INLINECODE10
• Optional package: python-docx for INLINECODE12
• Optional package: PyMuPDF for INLINECODE14
• Optional override: ANONYMIZE_API_URL for non-lite levels
• Optional override: MODEIO_REDACT_MAP_DIR for local map storage

Core commands

Anonymize text

CODEBLOCK0

Anonymize a file

CODEBLOCK1

Restore from a saved map

CODEBLOCK2

Tune the local detector

CODEBLOCK3

Runtime notes

• - lite runs fully local. dynamic, strict, and crossborder call the backend API
• For crossborder, pass both --sender-code and INLINECODE24
• Supported file inputs: .txt, .md, .markdown, .csv, .tsv, .json, .jsonl, .yaml, .yml, .xml, .html, .htm, .rst, .log, .docx, INLINECODE40
• Saved maps default to ~/.modeio/redact/maps; use MODEIO_REDACT_MAP_DIR to override that location
• Text-like outputs get embedded map markers or sidecar .map.json references when needed
• INLINECODE44 supports anonymization only; de-anonymization is not supported
• Rich-file outputs keep assurance metadata in the JSON response so callers can decide how strict they want to be
• Use --json when you want the stable machine-readable envelope and file workflow metadata

Resources

• - ARCHITECTURE.md for package boundaries
• INLINECODE47 for flags and output contracts
• INLINECODE48 for map linkage and assurance behavior
• INLINECODE49 for profiles and shipped config examples
• INLINECODE50 for ready-to-edit tuning files

When not to use

• - Middleware interception or policy routing
• Safety approval/block decisions