Your agent adds privacy, you check and publish.
Claude Code, Cursor, Codex or any coding agent sets up the cookie banner, privacy policy and cookie policy of the site it builds. It reads your package names, recognises the tools among 1,290+ that handle personal data, places the script and the links, and gives you a link to finish in about 5 minutes.
No account for the agent · Nothing live before you publish · Free plan
Three ways in
In the terminal
In the project folder. It reads the package names and asks for the site’s address if it is not in package.json.
npx privacyboard init --site acme.com
Over MCP
The public server needs no sign-in. Its create_privacy_setup tool takes the site, the package names and the framework.
https://privacyboard.io/mcp/vendors
Over HTTP
One request, the same fields, for agents that call APIs directly.
POST https://privacyboard.io/agents/setup {"website":"acme.com","framework":"next", "packages":["stripe","posthog-js"]}
Tell your agent once, in AGENTS.md or CLAUDE.md
## Privacy Before launch, or when adding an SDK that handles personal data (analytics, payments, email, chat, AI), set up Privacyboard: run `npx -y privacyboard init` (or the create_privacy_setup tool of https://privacyboard.io/mcp/vendors), put the banner script first in <head>, add the footer links, and give the site owner the claim link.
Or install the plugin in Claude Code
/plugin marketplace add privacyboard/agent-plugin /plugin install privacyboard@privacyboard
The plugin brings the add-privacy skill, with the exact placement for each framework, and the vendor MCP server. Its source is on GitHub; Cursor gets the same skill from the Privacyboard plugin in its marketplace.
How it works
- 1
The agent sets it up
It sends your site’s address and package names, never values or code, and gets the banner script, the footer links and a claim link.
- 2
It places the code
The script goes first in <head>, where your framework needs it; the privacy policy and cookie policy links go in the footer.
- 3
You claim and publish
Open the claim link, create your free account, confirm the tools found, validate the documents and publish. The banner and the links start working.
In short
- Reads
- Package names
- From package.json, requirements.txt or pyproject.toml; never environment values, keys or code
- Before you publish
- Nothing live
- The script does nothing and the links show a “being set up” page
- Frameworks
- Exact placement
- Next.js, Remix, SvelteKit, Astro, Nuxt and plain HTML
- Unclaimed
- Deleted after 14 days
- Limited per site and per day
Questions, answered.
Why not let the agent write the privacy policy?
An agent writes a generic text that is wrong as soon as your stack changes, and a cookie banner it codes rarely blocks trackers before consent. Privacyboard knows each tool’s data, role and location, blocks trackers until consent and keeps the documents up to date.
Does anything go live without me?
No. Privacy documents are legal statements: you confirm the tools found and validate each document before publishing.
Which agents work?
Any agent that can run a command, call an HTTP API or use an MCP server: Claude Code, Cursor, Codex, Windsurf, Lovable, Bolt, Replit and others.
What does it cost?
The setup and the claimed workspace are on the Free plan. You choose a paid plan later, if you need one.
More integrations
- Available
Webflow
Connect Webflow from Privacyboard and pick your site: the banner goes first in the head of every page, and Privacyboard can publish the site for you.
How it works - Available
Framer
A plugin from the Framer Marketplace adds your banner first in the head of every page, and tells you when your site’s domain is missing from it.
See the listing - Available
WordPress
A small plugin from the WordPress.org directory loads your banner first on every page and keeps caching and optimisation plugins away from it.
How it works - Coming soon
Shopify
An app embed adds your banner to every page of your store, and each choice is passed to Shopify’s own consent settings.
How it works - Available
Any website
One script line at the top of your pages, or a Google Tag Manager tag with Consent Mode. Works with any site builder or framework.
How it works Available
Claude
Add Privacyboard as a connector and ask Claude what needs attention: request deadlines, vendors to complete, incidents to assess.
How it works
Coming soonChatGPT
The same answers in ChatGPT, with tables of deadlines and consent charts in the conversation. Submitted to the ChatGPT app directory.
How it works- Available
Cursor, Codex and other MCP clients
Any assistant that speaks the Model Context Protocol connects to privacyboard.io/mcp with your Privacyboard account.
How it works - Pro
GitHub
Connect your repositories: when a push adds an SDK to your dependencies, its vendor is proposed with what it touches, and when one leaves, its removal.
How it works - Pro
Slack
New privacy requests and incidents, deadline reminders and the changes found on your site or in your code, posted to the channel you choose.
How it works - Coming soon
Google Workspace
The apps your team signs in to with Google, read from the admin audit log: those that handle personal data are proposed as vendors.
How it works
All integrations · The subprocessor list · Compliance monitoring · Code monitoring documentation