The Air-Gap Rule
Some networks have no internet. Not by policy — by design.
A SCIF (Sensitive Compartmented Information Facility) is a Faraday-caged room. No wireless signal goes in or out. ITAR (International Traffic in Arms Regulations) bans sending covered technical content to unapproved parties. Cloud providers are not ITAR-cleared. For these groups, "cloud SaaS" is not a risk to manage.
For these sites, cloud tools do not work. Full stop.
A tool that needs a live network link cannot run here. A tool that calls a license server is blocked. A tool that sends files to a cloud API for detection cannot function inside a SCIF. These are not edge cases. They are daily constraints for defense teams.
The ITAR Case
A data scientist at a defense firm has personnel records under ITAR. She must remove names and IDs before sharing the files. Her network is air-gapped.
There is no cloud fix. The only path is a tool that runs on the local device. It must store its models locally. It must produce clean output with no external calls.
The Tauri 2.0-based Desktop App does this. After install, no network calls happen during a run. The spaCy NER models and regex patterns all run on the local CPU. Output stays on the device until the user exports it.
Why Reversibility Matters
Classified work often needs reversible pseudonymization. Teams swap real names for codes. They keep the records useful. They protect real identities.
GDPR Article 4(5) defines pseudonymization as a formal privacy measure. It lowers risk. Pseudonymized records carry fewer legal duties — if the lookup token is stored apart from the dataset.
IAPP research (2024) found that only 23% of tools support true reversibility. Most do one-way masking or full replacement. Once a record is overwritten, it is gone.
Some government teams split their work by compartment. One team gets the pseudonymized files. They do the analysis. A second team holds the lookup token. They re-identify records only when the law requires it. This split design is the only safe approach for multi-team classified workflows.
The zero-knowledge model goes one step more. The lookup token is created on the client device. It is never sent out. If the vendor is subpoenaed, they cannot hand over the token. They never had it. This satisfies chain-of-custody rules in many classified environments.
EDPB Token Separation
EDPB Guidelines 05/2022 say the pseudonymization token must be held apart. It must not sit with the same party that holds the pseudonymized records. Or it must be locked behind controls that stop that party from reading both records and token at once.
Three things together meet this rule:
- Token created on the client device — never sent out
- All processing done locally — nothing leaves the air-gapped site
- Output and token exported separately — two separate files, two separate paths
This design meets the EDPB rule and the air-gap constraint at the same time.
For the full picture, our security overview shows how local processing cuts the third-party chain. Our compliance guide covers GDPR transfer rules. See our FAQ for setup help.
The anonym.legal Desktop App runs all PII detection on the local device. No internet is needed after install. It supports Windows, macOS, and Linux. Bundled NLP models cover all 48 supported languages.
Updated for 2026
Sources
- EDPB Guidelines 05/2022: Pseudonymization and token separation — VERIFIED-EXTERNAL
- IAPP 2024: Anonymization tool reversibility survey — FLAGGED
- LocalAI Master: Air-gapped AI for sensitive environments — VERIFIED-EXTERNAL