Dashboard Structural Analysis anonym.plus SD1 LINKABILITY Case Study
← Previous Next →
anonym.plus SD1 LINKABILITY
Case Study 7 of 30

A Survey on Current Trends and Recent Advances in Text Anonymization

Tobias Deußer, Lorenz Sparrenberg, Armin Berger et al. · International Conference on Data Science and Advanced Analytics (2025-08-29)

Research Source

A Survey on Current Trends and Recent Advances in Text Anonymization
Tobias Deußer, Lorenz Sparrenberg, Armin Berger et al. · International Conference on Data Science and Advanced Analytics · 2025-08-29 · Source: semantic_scholar

The proliferation of textual data containing sensitive personal information across various domains requires robust anonymization techniques to protect privacy and comply with regulations, while preserving data usability for diverse and crucial downstream tasks. This survey provides a comprehen-sive overview of current trends and recent advances in text anonymization techniques.

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 MAC addresses, device serial numbers, CPU identifiers, TPM keys, hardware UUIDs. 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

Redact is recommended for this pain point: completely removing hardware identifiers from documents and logs eliminates persistent tracking anchors that survive OS reinstalls. Hash provides an alternative — hashing hardware identifiers enables device-level analytics without exposing actual serial numbers. For scenarios requiring reversibility, Encrypt (AES-256-GCM) enables authorized recovery of original values.

Architecture & Deployment

The local sidecar REST API (port 5002-5003) provides programmatic access to Presidio detection for local development workflow integration.

Compliance Mapping

This pain point intersects with GDPR Article 4(1) device identifiers as personal data, ePrivacy Article 5(3).

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

SpecificationValue
App Versionv8.10.5
Entity Types200+ built-in, up to 50 custom
Detection EnginePresidio 2.2.357 + spaCy 3.8.11 (23 models)
Languages48 UI, 23 NLP models
Document FormatsPDF, DOCX, XLSX, TXT, CSV, JSON, XML + Image OCR
Anonymization MethodsReplace, Redact, Mask, Hash (SHA-256/512/MD5), Encrypt (AES-256-GCM)
ArchitectureTauri 2.x (Rust + React) + FastAPI sidecar (~370 MB)
PlatformsWin/Mac/Linux
LicensingEd25519 signed, machine-fingerprinted, max 5 machines
Processing100% local — data never leaves device
ComplianceGDPR, HIPAA (data residency guaranteed by local processing)
← Previous Next →