These pages describe PrivacyFence 8.0.0. Download it · What changed
Connect ChatGPT¶
ChatGPT on the web connects to PrivacyFence through a Developer Mode app. ChatGPT connects to MCP
servers from OpenAI's servers, not from your computer, so it needs a PrivacyFence it can reach over
public HTTPS: an organization deployment. A single-user Docker install on your computer listens on
localhost only, on purpose, so ChatGPT cannot use it.
Which deployment you have is explained in Single-user and organization deployments.
The steps were checked with a personal ChatGPT plan. Business, Enterprise and Edu workspaces are not verified (see Organization mode).
Organization mode¶
Your administrator gives you the deployment's URL, for example https://pf.example.com.
You need a ChatGPT plan with Developer Mode. These steps were checked with a personal ChatGPT plan.
Business, Enterprise and Edu workspaces are not verified. On a workspace, an administrator may have to allow Developer Mode first, and ChatGPT may behave differently from what this page describes. A connector the workspace administrator publishes for every member is not covered here; it is tracked in issue 796.
- Turn on Developer Mode: profile icon → Settings → Security and login → Developer mode. OpenAI moves this setting now and then; some of its pages still place it under Settings → Apps → Advanced settings.
- Settings → Apps → Create, and fill in:
- Name:
PrivacyFence - MCP Server URL:
https://pf.example.com/mcp - Authentication: OAuth. Leave any OAuth client ID and secret empty: ChatGPT registers itself.
Confirm that you understand the warning, then click Create.
3. Sign in with your organization account when PrivacyFence's sign-in page opens. ChatGPT then
shows the app as connected, with PrivacyFence's tools.
4. Connect your services at https://pf.example.com/connect.
Turn the app on in every chat. In a new chat, open the + menu, choose Developer mode, and select PrivacyFence. A Developer Mode app is off in every new chat until you do.
Access tokens last one hour and are refreshed silently; after 30 days you sign in again. Setting up the deployment itself is Organization deployment.
If the deployment accepts connections only from known addresses, it must also accept the address ranges OpenAI publishes for ChatGPT's connectors, since every tool call comes from OpenAI's servers. File links are fetched from ChatGPT's code sandbox instead (see Files), which may use other addresses.
Files¶
A local path means nothing to the server. Files travel through one-time links instead (ADR 0028):
- Upload (for example
drive_upload_file, or an email attachment): ChatGPT callsprivacyfence_create_upload_slot, sends the file to the returned URL with an HTTPPUT, and passes the returnedupload:reference to the tool. - Download (for example
drive_download_file): a file of up to about 75 KB comes back in the tool result; a larger one becomes a short-lived, one-time link.
ChatGPT uses those links from its code sandbox, with no allowlist to set up. A link works only
if the client can reach the deployment's host
(ADR 0097). ChatGPT's code
sandbox fetches a download link and sends an upload's PUT itself, over public HTTPS, so unlike
claude.ai there is no domain list to add the host to.
Uploads need 5.1.0 or later when the approval waits. In 5.0.0, an upload whose approval card was still waiting when ChatGPT asked fails after you approve it, with "the upload expired or was already used", and ChatGPT may then retry by sending the file inside the tool call instead. 5.1.0 keeps the uploaded file until the approved upload runs (ADR 0102).
To read a document, no download is needed. drive_get_file_content returns a PDF, Word,
PowerPoint or Excel file's text, so ChatGPT can read it without any link. A scanned PDF has no
text; figures and layout are not in the text either.
Sizes, lifetimes and the organization settings are in Files and File delivery.
Confirmations¶
Two things can ask you before a tool runs:
- ChatGPT's own confirmation. Whether ChatGPT asks is decided by ChatGPT's permission setting, not by PrivacyFence. ChatGPT sorts PrivacyFence's tools into Read and Write by their annotations, with no separate group for the two that delete something. On a personal plan, with the setting Allow low-risk tools, ChatGPT did not ask before creating a calendar event. It asked once, before an upload, and offered to always allow that tool; after that it did not ask again. OpenAI documents that a lasting Always allow is not offered to members of a managed workspace, so a workspace member may be asked every time; that is not verified.
- PrivacyFence's approval card. A gated call waits for you at
/approvals, whatever ChatGPT was told or allowed. This is the confirmation that always decides; see Approvals and policy.
PrivacyFence always tells the client what each tool does: reads are read-only, writes are writes,
and the tools that delete something (calendar_delete_event,
drive_sheets_delete_dimensions and peek_delete_page) are destructive
(What the AI system is told). There is no switch that
advertises writes as read-only (ADR 0089).
What to expect: depending on ChatGPT's permission setting and your plan, a write is confirmed once, on PrivacyFence's card, or twice, once in ChatGPT and once on PrivacyFence's card. Allowing a tool in ChatGPT only stops ChatGPT's question: every call still goes through PrivacyFence's gate, and PrivacyFence's card is the one that decides.
How the client is identified¶
In organization mode, every approval card and audit entry names the AI system that asked. ChatGPT registers with
PrivacyFence as ChatGPT, which PrivacyFence recognises, so its cards name ChatGPT. ChatGPT
also gives a name in the MCP handshake, but the registered name is the one used when PrivacyFence
recognises it.
That name is a claim: the card says the caller says it is that system and marks it
Not verified, because any program that can reach the deployment can register under the same
name. When the registration carries only ChatGPT's own callback
(https://chatgpt.com/connector/oauth/<connector id>), PrivacyFence shows it as Verified
instead, with no administrator step. See
Which AI system is asking and
AI systems.
Troubleshooting¶
| What you see | What to do |
|---|---|
| Create fails before the sign-in page opens | The URL must end in /mcp and be reachable over public HTTPS with a valid certificate. Your administrator can check it with the validation checklist. |
| There is no Developer mode setting | Look under Settings → Security and login. If it is not there either, your plan or workspace does not offer it, or an administrator has not allowed it. Ask your workspace administrator. |
| Sign-in finishes but the app does not appear | Try Create once more. |
| The sign-in page refuses you | Your account is not allowed to sign in to this deployment. Ask your administrator. |
| PrivacyFence's tools are missing from a chat | Turn the app on for that chat: + → Developer mode → PrivacyFence. |
| Tools are listed but none of your services' tools | No service is connected yet. Ask ChatGPT to call privacyfence_status, then connect services at /connect. See Connecting a service. |
| A call waits and nothing happens | It is waiting for your approval at /approvals. |
| An upload fails after you approve it, with "the upload expired or was already used" | The deployment runs 5.0.0, and the approval waited. Ask your administrator to upgrade to 5.1.0 or later. |
| Every card says Not verified | Expected when the registration's redirect URI is not the vendor's own callback; see AI systems. |
Deployment problems are in the organization guide's Troubleshooting.