These answers cover security and data protection.

No. AdBuyMCP holds no ISO 27001, SOC 2 or Cyber Essentials certification, and no third-party penetration test has been commissioned. ICO registration and the exposure-ledger impact assessment are open items too. If a certification is a hard procurement requirement, AdBuyMCP does not meet it today. The security page lists every item not held, with the status of each, beside the controls that are in force.

This site's server keeps nothing from the onboarding: the homepage it reads, the page's text and the draft of your buyers are not stored there, and what you type stays in your browser tab until you close it. In the product, hashed mobile advertising ids are held for at most 90 days, after which they are persistently stripped from the exposure event, re-grading it to a coarser key rather than deleting the record. Campaign configuration, plans and delivery data are held for the life of your workspace and deleted on request. Vendor credentials are encrypted at rest with AES-256-GCM and are deleted when the connection is removed.

Your workspace is the scope boundary for every route, and a cross-tenant request returns a 404 rather than a 403, because a 403 confirms that the resource exists. Actor, source and client attribution are persisted on every action and readable in the audit log. The audit log covers what came through the API: someone with direct database access sees more, and that is AdBuyMCP. No certification attests to how that access is controlled, because none is held.

No. Agents cannot hold the exact-digest approval permission, cannot resolve human approvals, cannot revoke or replace authority and cannot close missions. Consequential calls fail closed unless the request matches an approval a human granted for those exact bytes, and enabling spend on a staged live line is a separately granted action that approval alone cannot perform.

No. It accepts only http and https on the standard ports, refuses private, loopback, link-local, multicast and reserved ranges where the connection is made, checks every redirect again, and stops after ten seconds or one megabyte of HTML. A blocked address gets the same answer as an address that does not exist, so the reply reveals nothing about this site's network.

It varies by segment, so it is recorded per segment. Every compiled plan carries a manifest naming each segment's provider and its basis: consent-chained where the provider asserts a consent chain, legitimate interest where the segment relies on one, and outside scope for out-of-home, which involves no personal data in delivery. Where a segment match is weak or a geography is unmapped, the warning stays attached to the plan.

No. The homepage text this site sends during the onboarding, and the briefs and campaign data the product sends, go to the model provider to produce your output and are not used for training. The product's AI layer also has a complete deterministic fallback, so it runs with no model provider configured at all.

The hosted API, dashboard and MCP services run on Railway in Amsterdam, and the Supabase authentication and database project is in London. A waitlist entry from this website is stored by Supabase in London too, in a separate project, and the email that carries it to the founder is sent by Resend from its EU region in Ireland. Resend stores email content and delivery logs in the United States. This is not UK-only residency. AdBuyMCP operates the service with workspace isolation. Reporting uses a Europe/London calendar and prices are in sterling; those settings do not determine where data is hosted.

For this website: Vercel for hosting, including the onboarding's homepage reading, and for the historical application records, Anthropic for the onboarding's draft of your buyers and the Ask assistant, Plausible for cookieless analytics, Kawl Now for the optional voice widget, Google for Analytics and Ads only after you allow each, Cal.com for the booking calendar, Supabase for the database in London that holds waitlist entries, and Resend for the alert email sent from Ireland, with email content and delivery logs stored in the United States. For the product: Railway for the hosted services, Supabase for identity and the database, and Resend for sign-in email. Model providers receive campaign prompts in the product only when their integration is enabled. The full list, with what each receives, is at https://adbuymcp.com/security.