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

Towards formalizing the GDPR's notion of singling out.

Cohen, Aloni, Nissim, Kobbi · Proceedings of the National Academy of Sciences of the United States of America (2020-03-31)

Research Source

Towards formalizing the GDPR's notion of singling out.
Cohen, Aloni, Nissim, Kobbi · Proceedings of the National Academy of Sciences of the United States of America · 2020-03-31 · Source: pubmed

There is a significant conceptual gap between legal and mathematical thinking around data privacy. The effect is uncertainty as to which technical offerings meet legal standards. This uncertainty is exacerbated by a litany of successful privacy attacks demonstrating that traditional statistical disclosure limitation techniques often fall short of the privacy envisioned by regulators.

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 names, email addresses, phone numbers, social media handles, organizational affiliations. 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: removing contact identifiers from documents prevents construction of social graphs from document collections. Replace provides an alternative — substituting names and identifiers with type labels preserves document structure while breaking the social graph. 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 5(1)(c) data minimization, Article 25 data protection by design.

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 →