dsh-privacy-gateway
DeepSeek Harness 的本地隐私网关：在对话消息到达模型前，将个人数据替换为占位符，仅在本地界面显示原始内容，并创建 CSV/XLSX 文件的脱敏副本。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:ethanrise/dsh-privacy-gateway#d5a23dae5c85a8ffae96aac9da8e9dee4490953dPrivacy Gateway 以 dsh-privacy-gateway 发布，当前版本为 0.3.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English · 简体中文
Local privacy gateway for DeepSeek Harness (DSH).
I want AI to work with customer data, but I do not want real names, phone numbers and ID numbers to reach the model.
It does two things:
Everything is in the 🔒 Privacy Gateway tab of the right sidebar (the 🔒 button in the session header opens it). The UI follows DSH's language setting (Chinese or English).
In DSH Desktop, open Settings → Plugins → Add plugin and enter:
https://github.com/ethanrise/dsh-privacy-gateway
Reload DSH afterwards. With the CLI: dsh plugin --profile web add github:ethanrise/dsh-privacy-gateway.
You type: 给客户张三发邮件 zs@example.com，电话 13812345678
Model sees: 给客户[PERSON_7C1E0A93B2]发邮件 [EMAIL_41D0E6F8A5]，电话 [PHONE_2B9F4C07D1]
Your screen: 给客户🔒张三发邮件 🔒zs@example.com，电话 🔒13812345678
What is detected by rules:
| Type | How |
|---|---|
| PERSON | Chinese names with context: a label before them ("客户张三", "联系人：欧阳"), a title after them ("王经理", "李建国女士"), or "的" plus a contact word ("王小二的邮箱") |
| PHONE | Mainland-China mobile numbers, with or without +86, spaces or dashes |
| Email addresses | |
| ID_CARD | Mainland-China resident ID numbers, checksum-validated |
| BANK_CARD | 16–19 digit card numbers, Luhn-validated |
| IP | IPv4 addresses (off by default: frequent in technical text) |
Word list. Names the rules cannot catch (companies, people without context, project code names) go into the word list in the sidebar, one term per line, or imported from a column of a CSV/XLSX customer list. Each term is matched exactly (Latin text case-insensitively, longest term first). No short forms are derived: listing 字节跳动有限公司 does not mask 字节跳动; list that separately if you write it that way.
Placeholders are HMAC-derived from a local secret: the same value always gets the same placeholder, so the model can still tell people apart and refer back to them, and the prompt cache stays stable. You never maintain placeholders yourself.
On screen, placeholders are restored in place, prefixed with 🔒 and highlighted, including in the model's replies (with or without the brackets). Click one to see its type, the placeholder the model saw and the original, with copy buttons. Turn "show originals" off to see exactly what the model saw. Anything without a 🔒 was sent as plain text.
138****5678), TOKENIZE (stable HMAC token) or REMOVE per column.<name>.safe.csv / <name>.safe.xlsx and send that copy to AI yourself.All of it stays on this machine, under ~/.dsh-privacy-gateway/ with mode 0600:
| File | Content |
|---|---|
token-secret | HMAC key for placeholders and tokens |
vault.json | placeholder → original, so the UI can restore history after a restart |
dictionary.json | your word list |
The browser reads originals only through the plugin's own local routes. See SECURITY.md for the boundary.
maskToolResults: true, off by default because the model may then write placeholders into files it edits.In the plugin's cordis.patch.yml row:
| Key | Default | Meaning |
|---|---|---|
maskMessages | true | mask conversation messages before the model sees them (also switchable in the sidebar) |
maskToolResults | false | also mask tool results |
entities | [PERSON, PHONE, EMAIL, ID_CARD, BANK_CARD] | rule types to detect; add IP to enable it |
persistVault | true | keep vault.json on disk |
maxVaultEntries | 20000 | oldest entries are dropped past this |
npm install
npm run check # typecheck, tests, build
lib/ is committed because DSH installs from the repository without running a build: the host entry is bundled with its dependencies by esbuild, and the browser entry is a single module. Run npm run build and commit lib/ after source changes. Bumping version in package.json on main publishes a release with a prebuilt dsh-privacy-gateway.tgz.