These pages describe PrivacyFence 4.6.1. Download it · What changed
PrivacyFence documentation¶
How to install, use, deploy and secure PrivacyFence. These pages describe PrivacyFence 4.6.1.
Install and first steps¶
- Getting started — what you need, which install fits, your first approval, and troubleshooting shared by every platform.
- Install on macOS, Install on Windows, Install on Linux — install, connect Claude Desktop and Claude Code, troubleshoot, uninstall. One page per platform.
- Platform support — supported OS versions and architectures, where PrivacyFence keeps its data, logs, and start/stop commands.
- Connecting a service — connecting Gmail, Slack and the other services from Settings, and what each connector status means.
Using PrivacyFence¶
- How PrivacyFence works — the daemon, the companion app, how AI clients connect,
and the
privacyfence_*tools every client sees. - Approvals and policy — how requests are gated, approval cards, the PII check, "Always allow" and policy rules, the privacy filter, file previews and notifications.
- Configuration reference — every
settings.yamlkey and every organization-bundle option, with its default.
Organization deployment and security¶
- Organization deployment — deploy PrivacyFence centrally for an organization, including claude.ai as a client.
- Security and compliance — trust boundaries, step-up authentication, privilege separation, audit integrity, and what PrivacyFence does not claim.
Connector setup¶
Registering the OAuth app (or bot) each service needs, for a local install or an organization bundle:
- Google setup (Gmail, Drive, Calendar, Contacts, Tasks, Apps Script) — Gmail, Drive, Docs, Sheets, Calendar, Contacts, Tasks and Apps Script
- Slack setup
- Salesforce setup
- Atlassian setup (Jira and Confluence) — Jira and Confluence
- Telegram setup
Reference appendices¶
- Tools reference — every connector tool and how it is gated (generated).
- "Always allow" — per-tool reference — what "Always allow" proposes, tool by tool (generated).
- PII detection keywords — what the PII detector looks for.
Release history is in ../CHANGELOG.md.