Composition for Pufferfish Privacy
This paper establishes necessary and sufficient conditions to ensure linear composition for Pufferfish privacy by translating differentially private mechanisms via the -influence curve, thereby enabling the creation of composable algorithms for correlated data that outperform prior work.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
The Big Problem: The "Leaky Bucket" of Privacy
Imagine you have a bucket of water (your confidential data) and you want to pour some out to show people (publishing data products) without them seeing exactly how much water was in the bucket or where it came from.
Differential Privacy (DP) is the gold standard for this. It's like putting a very thick, opaque screen in front of the bucket. No matter how many times you peek through the screen, you can't tell if the bucket had 10 gallons or 11 gallons. Crucially, DP has a superpower called Composition: if you peek through the screen 10 times, you know exactly how much "blur" you've added in total. It's predictable and safe.
Pufferfish Privacy is a newer, smarter way to handle data that is correlated. Think of a family tree or a chain of friends. If you know one person's secret, you might be able to guess their brother's secret because they are related. Standard DP struggles here because it treats every person as an isolated island. Pufferfish is designed to handle these "islands connected by bridges."
The Catch: The paper argues that while Pufferfish is great for correlated data, it has a fatal flaw: it doesn't compose well.
The "Privacy Collapse" (The Magic Trick Gone Wrong)
The authors show that with Pufferfish, you can design a privacy system that looks perfect when you use it once. It reveals zero secrets. But, if you use that same system twice, it suddenly collapses, and the attacker can see the entire dataset.
The Analogy:
Imagine a magician (the data curator) who wants to hide a secret card (the data).
- Run 1: The magician shuffles the deck and shows you a card. It looks random. You learn nothing.
- Run 2: The magician does it again. Because of a hidden trick in the rules of Pufferfish, the second card reveals the first card, and suddenly you know the whole deck order.
The paper proves that without extra rules, Pufferfish is like a magic trick that works once but fails miserably the second time. This is called Privacy Collapse.
The Solution: Borrowing from the "Gold Standard"
To fix this, the authors asked: What extra rules do we need to add to Pufferfish so it stays safe even if we use it many times?
They discovered a surprising answer: You have to make Pufferfish act like Differential Privacy.
They proved that for Pufferfish to be safe over multiple uses, the mechanism must satisfy a specific type of inequality that looks exactly like the rules of Differential Privacy. It's like saying, "To make sure your family secret stays safe when you tell it to five different people, you have to follow the strict rules of telling a secret to a stranger."
The New Tool: The "Influence Curve"
How do you actually build these safe systems? The authors introduced a new concept called the -influence curve.
The Analogy:
Imagine a person, Alice, who has a contagious disease (the secret).
- (The Inner Circle): These are the people Alice is closest to (her family). If Alice is sick, they are very likely to get sick.
- (The Influence Factor): This measures how much Alice's sickness changes the odds of someone outside her inner circle getting sick.
The -influence curve is a graph that tells you: "If you protect the closest people, how much risk is left for everyone else?"
- If the curve is low, it means the secret doesn't spread far.
- If the curve is high, the secret spreads easily.
This curve acts as a translator. It allows data curators to take existing, well-tested "Differential Privacy" tools (which are already known to be safe for repeated use) and translate them into "Pufferfish" tools.
Why This Matters (The "Plug-and-Play" Benefit)
Before this paper, if you wanted to use Pufferfish for a new type of data (like a Markov chain of user locations), you had to build a brand-new privacy mechanism from scratch and prove it was safe. It was like building a new engine for every car you drove.
With this new framework:
- You calculate the Influence Curve for your specific data (how much secrets spread).
- You pick a standard, off-the-shelf Differential Privacy tool (like the Exponential Mechanism, which is great for ranking lists).
- You use the curve to translate the settings.
- Boom: You now have a Pufferfish system that is safe to use over and over again, without having to reinvent the wheel.
The Results: Better Accuracy
The authors tested this on real-world data (Foursquare check-ins and activity tracking). They compared their new method against the previous best method (called MQM).
- The Result: Their new method was significantly more accurate.
- Why? Because they weren't forced to use the same old "Laplace noise" tool that the previous method used. They could swap in better tools (like the Exponential Mechanism) that are naturally better at answering "Top 3" questions, and their new translation tool made sure those tools were still safe for Pufferfish.
Summary
- The Problem: Pufferfish privacy is great for correlated data but breaks (collapses) if you use it more than once.
- The Fix: You must add rules that look like Differential Privacy to make it safe for repeated use.
- The Tool: The -influence curve acts as a translator, letting you use existing, safe Differential Privacy tools for complex, correlated data.
- The Benefit: You get the safety of repeated use and the accuracy of specialized tools, without having to build everything from scratch.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.