PostgreSQL Anonymizer 3.1 brings local differential privacy to your database

PostgreSQL Anonymizer 3.1 shipped with local differential privacy built in. The tool sits on top of PostgreSQL and scrambles your data so people can't tell if a specific person's record is in the dataset. This version adds the "local" variant — noise is added at the row level before aggregation, not after — which means you get stronger privacy guarantees even on smaller datasets.

Differential privacy started in academia and is now showing up in government and tech. The idea is simple: add enough random noise to a dataset that a single record can't be identified, while still letting you run meaningful queries. The older "global" approach adds noise to the final output, which is fine for big data but can distort results when you're working with a few thousand rows. Local DP does the math at the source, so the noise is baked into each record from the start.

If your organization runs PostgreSQL and shares data — customer records, employee information, health data, whatever — this is a practical step forward. You get better privacy without needing a data science team or a massive dataset.

Why this matters for us: la gente who work for community organizations, clinics, and small businesses using PostgreSQL are getting a real privacy tool, not just another buzzword.