Privacy-Preserving Text Sanitization for Distributed Agents Collaboration via Disentangled Representations
This paper introduces DiSan, a privacy-preserving framework for distributed agent collaboration that utilizes disentangled representations to effectively remove source-identifying stylistic signatures while preserving task semantics, significantly outperforming traditional token-masking methods in reducing stylometric attribution and PII exposure.
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 Problem: The "Secret Handshake" in Text
Imagine you are an accountant at Bank A and you need to ask a colleague at Bank B for some financial data to help a client. You send a message: "Our client, Mr. Smith, has a $5M loan with Chase Bank."
If you just delete "Mr. Smith" and "Chase Bank," you might think you are safe. But the paper argues you aren't. Why? Because your writing style is like a secret handshake.
Even without names, your message might still reveal who you are because of:
- How you format things: Do you use bullet points or long paragraphs?
- Your vocabulary: Do you use words like "liquidity" or "cash flow"?
- Your sentence structure: Do you always start sentences with "Per our records..."?
These are called distributional signatures. It's like a chef who always adds a pinch of salt at the very end of cooking. Even if you hide the chef's name, the taste of the dish gives them away.
The Solution: DiSan (The "Privacy Translator")
The researchers at the Shanghai Artificial Intelligence Laboratory created a tool called DiSan (Disentangled Sanitization). Think of DiSan as a super-smart translator that doesn't just hide names; it rewrites the message so it sounds like it came from a generic, anonymous source, while keeping the important facts intact.
Here is how it works, using a Smoothie Analogy:
1. Separating the Fruit from the Juice (Disentanglement)
Imagine every text message is a smoothie made of two things:
- The Fruit (Role): The actual facts, numbers, and meaning (e.g., "Loan amount is $5M").
- The Juice (Style): The flavor, texture, and secret recipe that identifies the maker (e.g., "Bank A's specific way of writing").
Old methods (like simple masking) just try to scrape the fruit out of the glass, but they leave the juice behind, which still tastes like Bank A.
DiSan uses a special machine (a Two-Stream Encoder) that separates the smoothie into two distinct streams:
- Stream A (The Role): Contains only the pure facts. This is what gets sent to the other person.
- Stream B (The Style): Contains the "flavor" and secret recipes. This stays locked in the local computer and is never sent.
2. The Group Project (Federated Training)
Usually, to teach a computer to do this, you would have to send all the private bank documents to a central server. That's dangerous.
Instead, DiSan uses Federated Learning. Imagine 7 different banks trying to learn how to write "generic" reports.
- They don't send their secret recipes to a central teacher.
- Instead, they send tiny, abstract clay models (called Prototypes) of what a "generic fact" looks like.
- The central server mixes these clay models to create a "master mold" and sends it back.
- Each bank updates its own machine using this mold.
This way, the banks learn to speak the same "generic language" without ever seeing each other's raw, private documents.
3. The "Anti-Identity" Training (Adversarial Regularization)
To make sure the clay models don't accidentally reveal which bank made them, the system plays a game of "Hide and Seek."
- A Discriminator (a detective AI) tries to guess which bank a clay model came from.
- The Sanitizer (the translator) tries to trick the detective by making the models look as generic as possible.
- Over time, the sanitizer gets so good at hiding the source that the detective can only guess randomly.
The Results: Did it Work?
The paper tested this against other methods like simple "blanking out" (masking) or asking a large AI to rewrite the text.
- The Old Way (Masking): If you hide 19% of the words (names, dates), the "detective" can still guess who wrote it 67% of the time. The "flavor" is still there.
- The DiSan Way:
- Privacy: It reduced the ability to guess the source by 73%. It's almost impossible to tell who wrote the message now.
- Usefulness: It kept 83% of the original meaning. The facts were still accurate enough to answer questions.
- PII Exposure: It reduced the risk of accidentally leaking personal info by 20 times compared to standard methods.
The Bottom Line
DiSan is a new way for different organizations to share information safely. Instead of just crossing out names (which leaves the "voice" of the organization behind), it completely rewrites the text to strip away the unique "voice" while keeping the "story" the same. It allows agents to collaborate without revealing their secret recipes.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.