Hugging Face's logo

Spaces:
build-small-hackathon
/
PrivacyShield
Sleeping

App Files Community
PrivacyShield
File size: 5,297 Bytes
b7421ac
 
e431b8d
 
b7421ac
 
a081e8f
b7421ac
 
e431b8d
 
 
 
 
 
 
 
9f23b02
 
 
 
 
b7421ac
 
 
e431b8d
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
c2a2b46
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
---
title: PrivacyShield
emoji: 🛡️
colorFrom: red
colorTo: gray
sdk: gradio
sdk_version: 5.49.1
app_file: app.py
pinned: false
license: mit
tags:
  - build-small-hackathon
  - privacy
  - pii
  - security
  - llm-guardrails
  - ner
  - track:backyard
  - sponsor:openbmb
  - sponsor:nvidia
  - achievement:offgrid
  - achievement:welltuned
short_description: Local PII & secret firewall for LLMs
---

# 🛡️ PrivacyShield — a local firewall for LLMs

**Strip PII and leaked secrets out of text *before* it ever reaches an LLM API — then put the
real values back into the response. Nothing sensitive leaves your machine.**

Every week another company leaks customer data or an API key into an LLM prompt. The answer
isn't "stop using AI" — it's a guardrail that runs **locally**, in front of the model.

> **Demo it in two clicks:** open the app → **Try the leaked-secret example → Sanitize.** Watch the
> AWS key, JWT, emails, Aadhaar (checksum-validated), names and address get masked — **"N blocked ·
> 0 leaked."** Then hit **Simulate the LLM round-trip**: the model only ever sees placeholders, and
> the real values are restored on your machine.

## Why this matters

- **The privacy requirement makes a small local model the *correct* design, not a compromise.** You
  literally cannot send PII to a cloud API to have it redacted. PrivacyShield runs entirely on-device.
- **It catches what regex can't.** Structured data (Aadhaar, PAN, cards, AWS keys, JWTs) is caught by
  high-precision, **checksum-validated** detectors. Context-dependent data (**names, addresses,
  orgs**) is caught by a **fine-tuned model** — regex is blind to these.
- **The round-trip keeps the LLM useful.** Mask → call the LLM with safe text → restore the originals
  into the answer locally. You get a real answer; the data never left.
- **Compliance-ready.** Aligns with privacy regimes (India's DPDP Act, GDPR) that require minimizing
  exposure of personal data to third parties.

## How it works

```
your text
  → DETECT : checksum-validated regex (structured PII + secrets)  ∪  fine-tuned NER (names/addresses)
  → MASK   : each finding → reversible placeholder, e.g. [PERSON_NAME_1], [SECRET_1]; originals kept
             only in an in-memory vault (never logged, never sent)
  → CALL   : send the sanitized text to the LLM (the LLM only ever sees placeholders)
  → RESTORE: swap placeholders back to the real values in the response, locally
```

## What it detects

| Layer | Examples | How |
|---|---|---|
| **Structured PII** | email, phone, **Aadhaar** (Verhoeff checksum), **PAN**, IFSC, **card** (Luhn), UPI, IP | deterministic, high precision |
| **Secrets** | AWS keys (`AKIA…`), JWTs, GitHub tokens, private-key blocks, high-entropy strings | regex + Shannon entropy |
| **Contextual PII** | **person names, addresses, organizations** | **fine-tuned XLM-RoBERTa** |

## The model — real data, real evaluation (not vibes)

- **Base:** `FacebookAI/xlm-roberta-base` (~270M params — runs on CPU, no GPU needed at inference).
- **Fine-tuned on:** [`ai4privacy/pii-masking-200k`](https://huggingface.co/datasets/ai4privacy/pii-masking-200k)
  (real, span-labeled) **+ synthetic Indian PII** (valid-format Aadhaar/PAN/IFSC/UPI, Indian names &
  addresses) so it handles Indian documents, which generic tools miss.
- **Model:** [`perceptron01/privacyshield-ner`](https://huggingface.co/perceptron01/privacyshield-ner)
- **Param math:** 0.27B ≪ 32B cap ✅

**Evaluation (held-out mix of ai4privacy + synthetic Indian PII):**

| Method | PERSON recall | ADDRESS recall | structured PII / secrets |
|---|---|---|---|
| regex-only baseline | ~0.00 | ~0.00 | high (checksum-validated) |
| **PrivacyShield (regex + fine-tuned model)** | **~0.97** | **~0.97** | high |

**Recall is the metric we optimize** — a missed secret or PII item is a leak, so a false negative is
far worse than over-masking. Overall fine-tuned F1 ≈ **0.97** (precision 0.97 / recall 0.97).

*Honest limitations:* the synthetic portion of the test set is formulaic and inflates absolute scores;
the model occasionally labels an organization as ADDRESS (the value is still masked, so nothing leaks);
free-text address boundaries are imperfect. The structured/secret layer is the high-precision backbone.

## Privacy by design

No database, no auth, no persistence. The detected values live only in an in-memory vault for the
duration of a request; the downloadable **audit log contains placeholders only — never raw values.**

## Run locally

```bash
pip install -r requirements.txt
python app.py
```

## Tech

Gradio · Hugging Face Transformers · a fine-tuned XLM-RoBERTa token classifier · deterministic
detectors with Verhoeff (Aadhaar) and Luhn (card) checksum validation + Shannon-entropy secret detection.

## Submission

- 🤗 **Live Space:** https://huggingface.co/spaces/build-small-hackathon/PrivacyShield
- 🎥 **Demo video:** https://drive.google.com/file/d/1TERBTamfhW87jlLip9EX8Sx9KYqgMAL4/view?usp=sharing
- 📣 **Social post:** https://www.linkedin.com/posts/aman-maurya-2a394924b_privacyshield-a-hugging-face-space-by-build-small-hackathon-share-7472416023334367234-oE6J/?utm_source=share&utm_medium=member_desktop&rcm=ACoAAD3l3lsBvHlGmHXJP3WiWP5GwQFJQ2g9QZI