GDPR Data Subject Request Handler

Name: GDPR Data Subject Request Handler
Availability: InStock
Author: Kata Team

Processes GDPR DSARs across Postgres + HubSpot with compliant response drafts

Works with

Claude (web & desktop)ChatGPT (Plus / Pro)CursorVS Code (Copilot)Claude CodeGemini CLIWindsurfClineContinueZedLM StudioGooseJetBrains AI AssistantWarpPostmanand more

Before you connect: what this agent would do

A preview derived from this agent’s definition — not a live run. Nothing runs and no key is sent until you connect. FindAgent runs it in an isolated sandbox on the hosted connection.

Credentials it will ask for (4)

Postgres Connection URL (DSAR role)· optional
Only ever sent to: *
HubSpot API Key· optional
Only ever sent to: api.hubapi.com
SMTP Credentials (JSON)· optional
Only ever sent to: *
Anthropic API Key· optional
Only ever sent to: api.anthropic.com

Safety rails that guard it

Every result is scanned for leaked secrets and prompt-injection before it reaches you — a check no agent can turn off.

How FindAgent keeps agents safe

Connect over MCP — runs anywhere

GDPR Data Subject Request Handler runs on FindAgent and connects over MCP — no download, no local runtime. Add the server URL to any MCP-capable client.

1 · Choose your client

1Find an agent

GDPR Data Subject Request Handler

Free

Processes GDPR DSARs across Postgres + HubSpot with compliant response drafts

gdprdsar

ConnectConnecting…Connected

Add your credentials

Postgres Connection URL (DSAR role)· optional

••••••••••••

HubSpot API Key· optional

••••••••••••

Encrypted · only sent to *

Saved securely

chatgpt.com

ChatGPT

Run the full DSAR pipeline for this request email

FindAgent · GDPR Data Subject Request Handler

✻ Spelunking…

FindAgent

Connected in ChatGPT

010203

2 · Add the server URL

remote MCP

https://mcp.findagent.cloud/agents/gdpr-data-subject-request-handler

ChatGPT (Plus / Pro): Settings → Connectors → add a remote MCP server, then paste the URL and approve it.

Open ChatGPT connectors

You add this server inside your client and approve it once — that in-client step is a security check, so there's no one-click button for it.

Signing in: the first time you connect, your client opens a FindAgent sign-in page — approve once and you're connected. There's no API key or token to copy; access is tied to your FindAgent account.

What you'll need — and where to get it

You enter these when you connect. They're encrypted, only ever sent to the agent's allowed hosts, and never shared with the creator.

Postgres Connection URL (DSAR role) · optional
Read+selective-delete Postgres connection URL for the dsar_role account. Company-specific host, set at install time. Leave blank for mock fixtures.Get this from *'s account or API settings.Paste the value as a single line.Only sent to: *
HubSpot API Key · optional
HubSpot Private App token with contacts:read scope.Get this from hubapi.com's account or API settings.Paste the value as a single line.Only sent to: api.hubapi.com
Service account JSON · optional
Get this from *'s account or API settings.Paste the full JSON of the key file (not a file path) — single-value keys are a single line. FindAgent stores it securely and gives the agent a file path to it.Only sent to: *
Anthropic API Key · optional
Optional. Leave blank on a sampling-capable client to use the host model with no key.Create a key on the Anthropic Console API keys page (console.anthropic.com → API keys).Paste the value as a single line.Only sent to: api.anthropic.com