Skip to content
About
Main content

What privacy forbids

  • You cannot define privacy as a property of an output. For every such property, some prior defeats it.
  • You cannot reach privacy with any deterministic transformation, because linkability is identity (a stable pseudonym is still a stable key).
  • You cannot answer arbitrary aggregates forever without enabling reconstruction.
  • You cannot have utility on fine-grained slices and a meaningful ε on the same data.
  • You cannot compose syntactic guarantees across releases.
  • You cannot bound disclosure about correlated individuals.
  • You cannot delete from a trained model cheaply.
  • You cannot have an erasure mechanism that is itself non-disclosive, because the before-and-after difference is a signal.

Escapes and their prices

EscapeBuysPays
k-anonymity familyintuitive, no noise, keeps true valuesno composition, collapses in high dimensions, the definition never terminates
composable, independent of the , quantifiednoise ∝ sensitivity/ε, budget depletes on read, useless on small slices, ε is unprincipled
protection at zero utility cost per unitnegates the platform's collect-everything premise; no internal forcing function
Deletion vectors / rewritereal erasure of source rowstable-rewrite and compaction debt, incomplete reach, aggregates and models out of scope
Consent as a data columnactually enforced at readintersection semantics shrink usable data at every join
Consent as a metadata tagcheap, no query costconvention only; not in the narrowest waist
/ inputs never shared, no trusted partyorders-of-magnitude overhead; output disclosure not addressed at all
DP-trained one ε payment, unlimited later queriesthe tail is destroyed, which is exactly the records that matter for edge cases