From t-closeness to differential privacy and vice versa in data anonymization
Research Source
k-Anonymity and ε-differential privacy are two mainstream privacy models, the former introduced to anonymize data sets and the latter to limit the knowledge gain that results from including one individual in the data set. Whereas basic k-anonymity only protects against identity disclosure, t-closeness was presented as an extension of k-anonymity that also protects against attribute disclosure.
Executive Summary
This research paper examines a critical privacy challenge related to LINKABILITY — the ability to connect two pieces of information to the same person.
anonym.plus addresses this through 200+ entity types processed 100% locally via Presidio 2.2.357 sidecar — detection and anonymization that never leaves the device.
Root Cause: SD1 — LINKABILITY
The ability to connect two pieces of information to the same person. This is the foundational operation that makes PII dangerous. Nearly every pain point is an expression of linkability being created, exploited, or failing to be broken.
Irreducible truth: You cannot have useful data that is completely unlinkable AND completely useful. The very features that make data informative make it linkable. This is not a bug — it is information theory. The information content of a dataset and its linkability are the same property measured differently.
The Solution: How anonym.plus Addresses This
Detection Capabilities
anonym.plus identifies 200+ entity types including text content, writing patterns, timestamps, posting metadata, timezone indicators. The local Presidio 2.2.357 + spaCy 3.8.11 architecture uses Presidio 2.2.357 deterministic recognizers with 121 built-in presets for structured identifiers and spaCy 3.8.11 with 23 language models, all running locally via FastAPI sidecar for contextual references.
Anonymization Methods
Replace is recommended for this pain point: replacing original text content with anonymized alternatives disrupts the stylometric fingerprint that writing analysis algorithms depend on. Redact provides an alternative — removing text content entirely prevents any stylometric analysis though it reduces document utility. For scenarios requiring reversibility, Encrypt (AES-256-GCM) enables authorized recovery of original values.
Architecture & Deployment
The Tauri 2.x desktop application (Rust + React) processes 7 document formats (PDF, DOCX, XLSX, TXT, CSV, JSON, XML) plus images (Tesseract OCR). AES-256-GCM vault with Argon2id protects all stored data.
Compliance Mapping
This pain point intersects with GDPR Article 4(1) personal data extends to indirectly identifying information including writing style.
anonym.plus’s GDPR (data never leaves device), HIPAA (local processing) compliance coverage, combined with 100% local — data never leaves device hosting, provides documented technical measures organizations can reference in their compliance documentation and regulatory submissions.
Product Specifications
| Specification | Value |
|---|---|
| App Version | v8.10.5 |
| Entity Types | 200+ built-in, up to 50 custom |
| Detection Engine | Presidio 2.2.357 + spaCy 3.8.11 (23 models) |
| Languages | 48 UI, 23 NLP models |
| Document Formats | PDF, DOCX, XLSX, TXT, CSV, JSON, XML + Image OCR |
| Anonymization Methods | Replace, Redact, Mask, Hash (SHA-256/512/MD5), Encrypt (AES-256-GCM) |
| Architecture | Tauri 2.x (Rust + React) + FastAPI sidecar (~370 MB) |
| Platforms | Win/Mac/Linux |
| Licensing | Ed25519 signed, machine-fingerprinted, max 5 machines |
| Processing | 100% local — data never leaves device |
| Compliance | GDPR, HIPAA (data residency guaranteed by local processing) |
Research Limitations
Academic Scope: This summary reflects findings from the original academic research paper. Implementation contexts, regulatory landscapes, and technical capabilities may have evolved since publication. Readers should verify current best practices and compliance requirements in their jurisdiction.
Generalizability: Research findings may be specific to the studied populations, geographic regions, or technical environments described in the original paper. Organizations should evaluate applicability to their specific use case before adopting recommendations.
Not a Substitute for Legal/Compliance Advice: This research summary is provided for informational and educational purposes only. It does not constitute legal, compliance, or professional consulting advice. Consult qualified privacy counsel for GDPR, HIPAA, CCPA, or other regulatory compliance guidance.