[2602.22699] DPSQL+: A Differentially Private SQL Library with a Minimum Frequency Rule
Summary
DPSQL+ is a new SQL library designed to enhance data privacy by enforcing differential privacy and a minimum frequency rule, ensuring sensitive information is protected during data analysis.
Why It Matters
As data privacy concerns grow, DPSQL+ addresses the need for secure data analysis tools that comply with governance requirements. By integrating differential privacy with the minimum frequency rule, it offers a robust solution for organizations handling sensitive data.
Key Takeaways
- DPSQL+ combines differential privacy with a minimum frequency rule for enhanced data protection.
- The library's modular architecture includes a Validator, Accountant, and Backend for efficient query management.
- Experiments show DPSQL+ maintains high accuracy across various analytical workloads.
Computer Science > Cryptography and Security arXiv:2602.22699 (cs) [Submitted on 26 Feb 2026] Title:DPSQL+: A Differentially Private SQL Library with a Minimum Frequency Rule Authors:Tomoya Matsumoto, Shokichi Takakura, Shun Takagi, Satoshi Hasegawa View a PDF of the paper titled DPSQL+: A Differentially Private SQL Library with a Minimum Frequency Rule, by Tomoya Matsumoto and 3 other authors View PDF HTML (experimental) Abstract:SQL is the de facto interface for exploratory data analysis; however, releasing exact query results can expose sensitive information through membership or attribute inference attacks. Differential privacy (DP) provides rigorous privacy guarantees, but in practice, DP alone may not satisfy governance requirements such as the \emph{minimum frequency rule}, which requires each released group (cell) to include contributions from at least $k$ distinct individuals. In this paper, we present \textbf{DPSQL+}, a privacy-preserving SQL library that simultaneously enforces user-level $(\varepsilon,\delta)$-DP and the minimum frequency rule. DPSQL+ adopts a modular architecture consisting of: (i) a \emph{Validator} that statically restricts queries to a DP-safe subset of SQL; (ii) an \emph{Accountant} that consistently tracks cumulative privacy loss across multiple queries; and (iii) a \emph{Backend} that interfaces with various database engines, ensuring portability and extensibility. Experiments on the TPC-H benchmark demonstrate that DPSQL+ achieves pract...