Pseudonymizes sensitive data before it reaches cloud LLMs and restores it on the way back.
Local pseudonymisation tools for LLM workflows — replace detected PII with opaque tokens before you hand text to a cloud LLM, then restore those tokens afterward. [](#gdpr--ai-compliance) Expose MCP tools ( and ) that your client or agent can call as an explicit privacy step. The server detects PII locally, replaces it with opaque tokens, and keeps the token mapping in memory for later…
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.
Local pseudonymisation tools for LLM workflows — replace detected PII with opaque tokens before you hand text to a cloud LLM, then restore those tokens afterward. [](#gdpr--ai-compliance) Expose MCP tools ( and ) that your client or agent can call as an explicit privacy step. The server detects PII locally, replaces it with opaque tokens, and keeps the token mapping in memory for later restoration. It is a defense-in-depth measure, not a compliance silver bullet. Read the Limitations and GDPR &…