Provable, not promised
Formal ε-budgets backed by mathematical proof. "Differentially private" means something specific here: not a marketing word, but a measurable property of the algorithm.
Differential privacy for PII analytics
Philter Diffuse applies differential privacy to PII counts and aggregations, so you can answer questions like "how many SSNs flowed through this pipeline last month" with a formal bound on what the answer reveals about any one document. Early access, version 0.1.0.
Exact PII counts can reveal whether a particular document was in the data, especially when a count is small. Philter Diffuse adds calibrated noise so the aggregate stays useful while what it reveals about any one document stays bounded.
Large aggregates barely move, so they stay useful; the small, risky counts get the protection. Query the private counts, not the raw ones.
Formal ε-budgets backed by mathematical proof. "Differentially private" means something specific here: not a marketing word, but a measurable property of the algorithm.
Adding or removing one document changes the output distribution by a bounded amount, which limits what a result reveals about whether that document was in the data. The bound is per document: someone who appears in many documents is protected less, in proportion.
Counts of PII types, never raw records. The output preserves the population-level signal you need for analytics while bounding how much it reveals about any single document.
Lower ε means more noise and stronger privacy; higher ε means less noise and stronger utility. Pick the trade-off that fits your regulatory posture, per query.
Point Philter Diffuse at Philter and it reads the PII counts Philter records through Philter's API, with only an API key. Measure pipeline behavior without publishing exact counts.
Every line of the noise calibration, sensitivity analysis, and budget accounting is inspectable. The math is auditable, the implementation is auditable, the privacy bound is reproducible.
If something here isn’t covered, get in touch and we’ll answer.
Grab the open source and run it yourself, or work with our team directly. Pick the path that fits.