Privacy Loss Distribution (PLD) is the complete probability distribution of the random variable that measures the logarithmic divergence between the output distributions of a mechanism on adjacent datasets. Unlike Rényi Differential Privacy (RDP) or moments accountant, which summarize this distribution using a single scalar moment, PLD retains the entire histogram of possible privacy loss values. This granular view captures the exact tail behavior of the loss variable, eliminating the looseness introduced by moment-based approximations and enabling precise composition of heterogeneous differentially private mechanisms.
Glossary
Privacy Loss Distribution (PLD)

What is Privacy Loss Distribution (PLD)?
Privacy Loss Distribution (PLD) is a fine-grained accounting method that tracks the full probability distribution of the privacy loss random variable across composed mechanisms, enabling significantly tighter and more accurate privacy budget calculations than moment-based approaches.
In practice, PLD accounting is implemented through privacy loss random variable (PRV) composition, where the PLDs of individual DP-SGD steps are convolved to compute the aggregate distribution. The privacy budget (epsilon) is then derived by solving for the smallest epsilon such that the tail probability of the composed PLD satisfies the desired delta bound. This numerical approach yields substantially tighter epsilon values than RDP composition, allowing practitioners to extract more utility from a fixed privacy budget while maintaining identical formal guarantees against membership inference.
Key Characteristics of PLD Accounting
Privacy Loss Distribution (PLD) accounting tracks the full histogram of privacy loss random variables, enabling significantly tighter composition bounds than moment-based methods for iterative algorithms like DP-SGD.
Full Distribution Tracking
Unlike Rényi Differential Privacy (RDP) or moments accountant which summarize privacy loss into a single scalar moment, PLD accounting maintains the complete probability distribution of the privacy loss random variable. This captures the exact tail behavior of the privacy loss, avoiding the looseness introduced by moment-based bounds. The distribution is represented as a discrete histogram over possible epsilon values, updated at each composition step through convolution operations.
Tight Composition via Convolution
PLD accountants compose mechanisms by convolving their individual privacy loss distributions rather than summing moment-generating functions. For a sequence of mechanisms M₁, M₂, ..., Mₖ, the composed PLD is computed as the convolution of their individual distributions. This exact arithmetic on distributions eliminates the compounding approximation error inherent in RDP-to-DP conversion, often yielding 20-40% tighter epsilon values for the same delta parameter in DP-SGD training runs.
Dominating Pairs and Hockey-Stick Divergence
PLD accounting is grounded in the concept of dominating pairs of distributions (P, Q) that bound the behavior of the mechanism on adjacent datasets. The privacy loss distribution is derived from the log-likelihood ratio between these dominating distributions. The final (ε, δ) guarantee is computed using the hockey-stick divergence: E_{Y∼P}[max(0, 1 - e^{ε} · (dQ/dP)(Y))] ≤ δ. This formulation provides an exact characterization of the privacy guarantee without intermediate relaxations.
Privacy Loss Random Variable
The core object in PLD accounting is the privacy loss random variable L = log(P(M(D) = o) / P(M(D') = o)), where D and D' are adjacent datasets. For DP-SGD with Gaussian noise, this variable follows a shifted and scaled non-central chi-squared distribution. PLD accountants numerically compute and track this distribution across training iterations, capturing the precise probability of large privacy losses that determine the final (ε, δ) guarantee.
Numerical Implementation in DP Libraries
Modern DP libraries implement PLD accounting through fast Fourier transform (FFT) based convolution on discretized privacy loss distributions. The open-source opacus library from Meta and Google's dp_accounting library both support PLD accountants. Key implementation details include:
- Discretization granularity: finer bins yield tighter bounds at computational cost
- Truncation bounds: clipping the distribution tails introduces negligible error
- Adaptive composition: supports variable noise multipliers and sampling rates across training
Advantage Over Moments Accountant
PLD accounting provides strictly tighter bounds than the moments accountant (RDP) for Gaussian mechanisms under Poisson subsampling. Empirical comparisons show:
- ~30% reduction in epsilon for typical DP-SGD settings (σ=1.0, q=0.01, 10⁴ iterations)
- No conversion loss: RDP must convert to (ε, δ)-DP via an inequality that introduces slack
- Handles heterogeneous compositions naturally, where noise multipliers or sampling rates vary across training steps
- Direct (ε, δ) output without intermediate RDP orders that require optimization
PLD vs. Rényi DP vs. Advanced Composition
A comparison of the three primary techniques for tracking cumulative privacy loss across composed differential privacy mechanisms.
| Feature | Privacy Loss Distribution | Rényi DP | Advanced Composition |
|---|---|---|---|
Accounting Basis | Full distribution of privacy loss random variable | Rényi divergence of order α | Moment-generating function bound |
Tightness of Bound | Tightest (exact numerical composition) | Tighter than advanced composition | Loose (worst-case analytical bound) |
Handles Heterogeneous Mechanisms | |||
Supports Poisson Subsampling | |||
Conversion to (ε, δ)-DP | Direct via tail bound on PLD | Via conversion lemma to (ε, δ)-DP | Native (ε, δ)-DP output |
Computational Cost | High (FFT-based convolution) | Low (closed-form moment computation) | Negligible (single formula) |
Typical ε Savings vs. Advanced Composition | 30-50% reduction | 15-30% reduction | Baseline |
Privacy Amplification by Iteration |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Precise answers to common questions about the mathematical foundations and practical applications of Privacy Loss Distributions in modern machine learning.
A Privacy Loss Distribution (PLD) is a precise accounting method that tracks the full probability distribution of the privacy loss random variable across composed mechanisms, enabling tighter privacy budget calculations than moment-based accountants. Rather than summarizing privacy loss with a single statistic like moments or Rényi divergence, the PLD captures the complete histogram of possible privacy loss outcomes. When a differentially private mechanism runs, the privacy loss random variable measures the log-ratio of the output probability density with versus without a specific individual's data. By convolving these distributions across iterative steps—such as in DP-SGD—the PLD accountant computes the exact trade-off curve between the privacy parameters epsilon (ε) and delta (δ). This granular accounting avoids the looseness introduced by composition theorems that rely on worst-case bounds, yielding significantly more accurate privacy guarantees for the same noise scale.
Related Terms
Core concepts that interact with Privacy Loss Distribution to enable tight, composable differential privacy guarantees.
Privacy Loss Random Variable
The fundamental building block of PLD accounting. For a mechanism M, the privacy loss random variable is defined as the log-ratio of the probability of observing an output under two neighboring datasets:
L = log( P[M(D)=o] / P[M(D')=o] )
- Support: Can take negative values (evidence for absence) and positive values (evidence for presence)
- Tail bounds on this random variable directly yield (ε, δ)-DP guarantees
- PLD tracks the full distribution of L rather than just its moments
Privacy Loss Distribution
The probability distribution of the privacy loss random variable, denoted as ω, which captures the complete privacy leakage profile of a mechanism:
- Discrete distribution for composed mechanisms, represented as a probability mass function over loss values
- Dominating pairs of distributions (P, Q) define the PLD where P models output on D and Q models output on D'
- Enables tight composition by convolving PLDs rather than summing moment bounds
- The hockey-stick divergence between P and Q at threshold ε yields the exact δ(ε) curve
Rényi Differential Privacy
A relaxation of pure DP based on Rényi divergence of order α between output distributions on neighboring datasets:
Dα(P||Q) = (1/(α-1)) log E[(P/Q)^α]
- RDP parameters (α, ε) convert to (ε, δ)-DP via tight conversion formulas
- PLD-based accounting subsumes RDP: RDP bounds the α-moment of the privacy loss, while PLD captures the full distribution
- RDP composition is additive across mechanisms but looser than PLD convolution for heterogeneous steps
- Commonly used as a lightweight alternative when full PLD tracking is computationally expensive
Privacy Loss Distribution
A precise accounting method that tracks the full distribution of privacy loss random variables across composed mechanisms, enabling tighter privacy budget calculations than moment-based accountants:
- Convolution: The PLD of composed mechanisms is the convolution of individual PLDs, computed efficiently via FFT
- Truncation: Tail probabilities below a threshold are accumulated into δ, providing the (ε, δ)-DP guarantee
- Heterogeneous composition: Unlike RDP or moments accountant, PLD handles varying noise scales and sampling rates natively
- Implemented in Google's DP libraries and the open-source
opacusandtf-privacyframeworks
Hockey-Stick Divergence
The exact operational quantity connecting PLD to (ε, δ)-DP guarantees. For distributions P and Q:
Hε(P||Q) = ∫ max(p(x) - e^ε q(x), 0) dx
- A mechanism is (ε, δ)-DP if and only if Hε(P||Q) ≤ δ for all neighboring datasets
- The trade-off curve δ(ε) is computed by evaluating Hε at each ε of interest
- PLD accountants precompute this curve once and interpolate to answer privacy budget queries
- Provides the tightest known characterization of differential privacy for composed mechanisms
Privacy Amplification by Subsampling
The property where randomly sampling a subset of data for each training step amplifies the privacy guarantee, as the uncertainty of inclusion provides an additional layer of deniability:
- Poisson subsampling: Each record is included independently with probability q, yielding a dominant pair (qP + (1-q)Q, Q)
- Shuffling: Random permutation followed by fixed-size batches provides stronger amplification than independent sampling
- PLD accountants model subsampling by transforming the PLD of the base mechanism before convolution
- The amplification effect is non-linear in the sampling rate, making PLD tracking essential for accurate accounting

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us