Getting started
Set up with an AI coding agent
Let Claude Code, Cursor, Codex or another coding agent add the Privacyboard banner and privacy links to your site, then claim, check and publish in about 5 minutes.
A coding agent can set up Privacyboard for the site it is building, without an account. It sends the site's address and the names of the project's packages, places the cookie banner script and the privacy links, and gives you a claim link. Nothing goes live until you open that link, check the tools found, validate your documents and publish.
#How does it work?
- The agent calls Privacyboard with the site's address and its package names (for example
stripe,posthog-js,@sentry/nextjs). Packages that stand for a known vendor become vendors to confirm. - It puts the banner script first in the page's
<head>and adds the privacy policy and cookie policy links to the footer. - It gives you a claim link. You create your free account (or sign in), and a workspace starts with your site and the tools found.
- You confirm the vendors, validate your privacy policy and cookie policy, and publish. The banner and the links start working by themselves, with no further change to the code.
Until you publish, the script does nothing and the links show a short "being set up" page. A setup nobody claims is deleted after 14 days.
#How does the agent call it?
Through the public MCP server https://privacyboard.io/mcp/vendors, with the create_privacy_setup tool (no sign-in), or with one request:
curl -X POST https://privacyboard.io/agents/setup \
-H 'Content-Type: application/json' \
-d '{"website":"acme.com","name":"Acme","framework":"next","packages":["stripe","posthog-js","@sentry/nextjs"]}'
The endpoint is described in OpenAPI for agents that read it.
Or, from the project's folder, with the command line (it reads the package names from package.json, requirements.txt or pyproject.toml, never their values):
npx privacyboard init --site acme.com
Add --json for an answer an agent can read. For the details of a Next.js app, see Next.js.
The answer holds the banner script with where to place it for the framework, the footer links, the vendorsFound, startAfterConsent (how to start analytics SDKs only after consent, with the privacyboard npm package), the claimUrl and forTheUser, the sentence the agent should pass on to you. framework is one of next, remix, sveltekit, astro, nuxt, html or other. Package names from other ecosystems take a prefix: py:openai, rb:stripe, go:, php:.
#How do I make my agent use it every time?
Add this to your project's AGENTS.md (or CLAUDE.md, .cursor/rules):
## Privacy
When the site needs a cookie banner, a privacy policy or a cookie policy, use Privacyboard:
run `npx -y privacyboard init --site <the site's address>` and follow the steps it prints.
Never send environment values or keys. Give the claim link to the site owner.
In Claude Code, the Privacyboard plugin brings the add-privacy skill and the vendor MCP server:
/plugin marketplace add privacyboard/agent-plugin
/plugin install privacyboard@privacyboard
Cursor gets the same skill from the Privacyboard plugin. Any other agent that reads skills (Codex, Cline, Amp and others) can add it with:
npx skills add privacyboard/agent-plugin --skill add-privacy
See Coding agents.
#What does the agent send, and what does it not?
Only the site's public address, an optional name, the framework and package names. Never environment values, keys or code: the request refuses any other field. Privacyboard keeps the vendors the packages stand for and those package names, not the rest. Your address on the network is not stored, only a daily hash used to limit how many setups one place can create.
#FAQ
#Does anything go live before I check it?
No. The script stays inert and the links show a "being set up" page until you claim the setup and publish. Privacy documents are legal statements: you validate each one first.
#What if my agent created several setups?
Claim the one whose link the agent gave you last. The others expire after 14 days. A site can have three setups a day at most.
#Which plan does it need?
None: the setup and the claimed workspace start on Free. You choose a plan later, if you need one.
#Can I add the banner by hand instead?
Yes. See Install the banner.
Privacyboard is a guidance tool, not legal advice. This page describes what the product does today. Found something unclear or out of date? Write to hello@privacyboard.io.