Toward Individual Fairness Without Centralized Data: Selective Counterfactual Consistency for Vertical Federated Learning
This paper proposes SCC-VFL, a server-centric framework for vertical federated learning that enforces individual-level counterfactual fairness by combining differentially private feature role discovery, masked counterfactual generation, and a consistency loss to significantly reduce decision flip rates while maintaining predictive accuracy and privacy.
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
Imagine you are applying for a loan. Your financial life is like a puzzle, but the pieces are scattered across different buildings. Bank A has your account history, your employer has your pay stubs, and a credit bureau has your debt records. None of them want to hand over their private files to a central boss because of privacy laws. So, they use a system called Vertical Federated Learning (VFL). Think of it like a group of chefs in separate kitchens who each have different ingredients. They send only small, cooked samples of their dishes to a head chef (the server) who mixes them to taste the final meal, without ever seeing the raw ingredients in the other kitchens.
The problem is: Is the final decision fair?
If you are 25 years old, will you get the loan? If you were 26, would you get it? If the answer changes just because of your age (a protected trait), that's unfair. But it's even trickier here because the "age" piece of the puzzle might be in one kitchen, while the "job stability" piece is in another. The system might accidentally use your age to guess your job stability and then use that to deny your loan, even if age shouldn't matter.
The authors of this paper, SCC-VFL, propose a new way to fix this. They call it Selective Counterfactual Consistency. Here is how it works, using simple analogies:
1. The "What-If" Test (Counterfactuals)
Imagine you are a time traveler. You go back and change one thing about yourself: your age. You ask, "If I were 26 instead of 25, but everything else about my life stayed exactly the same, would I still get the loan?"
- Fair: If the answer is "Yes, I still get the loan," the system is stable.
- Unfair: If the answer is "No, I get rejected," the system is unstable and potentially biased.
The goal is to make sure the answer stays the same, even if you change your age.
2. The Problem with "Blind" Fixes
Previous attempts to fix this were like trying to edit a photo by blurring the whole picture. They would try to remove all traces of age from the data. But this is too harsh. Sometimes, age does matter legally or logically (e.g., a 21-year-old can't rent a car, but a 25-year-old can). We need to be smart about what we change.
3. The SCC-VFL Solution: The "Smart Editor"
The authors built a system that acts like a Smart Editor with three specific tools:
Tool A: The "Privacy Mask" (Finding the Roles)
Before editing, the system needs to know which features are which.
- Non-Descendants (The "Fixed" Anchors): These are things that cannot change just because your age changed. For example, your loan amount or how long you've lived in your house. These must stay exactly the same in the "What-If" scenario.
- Mediators (The "Allowed" Movers): These are things that can naturally change with age. For example, your job tenure or credit history might look different for a 26-year-old than a 25-year-old. The system is allowed to update these to match the new age.
- Proxies (The "Forbidden" Leaks): These are sneaky features that secretly tell the system your age without you saying it (like a specific zip code or a demographic code). The system must block these from influencing the decision.
How do they find these without seeing the raw data? They use a Privacy Sketch. Imagine the server asks the party holding the age data to send a "blurred" version of the age list (like a foggy photo) that protects individual privacy but shows the general pattern. Using this foggy photo, the system figures out which features are "Anchors," "Movers," or "Leaks" without ever seeing the real names or ages.
Tool B: The "Masked Generator" (The Safe Edit)
Once the roles are assigned, the system creates a "What-If" version of your application.
- It locks the Anchors (Non-Descendants) so they don't budge.
- It updates the Movers (Mediators) to look realistic for the new age (e.g., slightly longer job tenure).
- It guards the Leaks (Proxies) so they don't accidentally whisper the old age to the decision-maker.
This is like a tailor who is allowed to adjust the sleeves of a suit (Mediators) to fit a new size, but is strictly forbidden from changing the fabric pattern (Anchors) or adding a hidden tag that reveals the original owner (Proxies).
Tool C: The "Stability Check" (Server-Side Enforcement)
Finally, the server looks at the original decision and the "What-If" decision.
- If the decision flips (e.g., "Approved" becomes "Rejected") just because of the allowed changes, the system gets a penalty.
- It forces the model to learn a way of deciding that is stable. It teaches the model: "If the only things that changed were the things we allowed to change, the result should stay the same."
The Results: A Fairer, Safer System
The authors tested this on three real-world scenarios: Credit (loans), Healthcare (heart disease risk), and Criminal Justice (recidivism risk).
- The Outcome: Their system (SCC-VFL) was much better at keeping decisions stable. In some cases, it reduced "decision flips" (where a person gets a different answer just because of a protected trait) by 98% compared to other methods.
- No Trade-Off: Usually, making a system fairer makes it less accurate (like a security guard who stops everyone to be safe). But SCC-VFL kept the accuracy high while making the decisions fairer.
- Privacy: It also made it harder for hackers to guess your private traits (like age or race) by looking at the data the system shared.
Summary
Think of SCC-VFL as a Fairness Filter for a team of secret chefs. It ensures that when they combine their secret ingredients to make a decision, the final taste doesn't change arbitrarily just because one secret ingredient (like your age) is slightly different. It does this by:
- Blurring the sensitive info to protect privacy.
- Sorting features into "Fixed," "Allowed to Change," and "Forbidden."
- Editing the "Allowed" parts realistically.
- Punishing the system if the final decision changes unfairly.
The result is a system that respects privacy, keeps data distributed, and ensures that your loan or medical decision depends on your actual qualifications, not on a hidden bias against your age, race, or gender.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.