Legal
Cookies and tracking on your site
Last updated: July 30, 2026
This page describes what a site built with AgentBuild places on your visitors’ devices, what changes when you add a third-party analytics or advertising provider, and where responsibility for obtaining consent sits. It describes how the product behaves. It is not legal advice, and it is not a substitute for advice from a qualified professional in your jurisdiction.
A site with no providers added sets no cookies
By default, a site AgentBuild builds for you is cookieless. Our own visitor analytics are cookieless by design: we retain no IP addresses, set no cross-site identifiers, and honor the Do Not Track and Global Privacy Control browser signals. Nothing in the default site requires a cookie banner.
Adding a third-party provider can change that
You can ask your agent to connect analytics or advertising providers. Some of them set cookies on your visitors’ devices. Where your visitors are in the European Union or the United Kingdom, the ePrivacy rules and the GDPR generally require a visitor’s prior consent before such cookies are placed, with limited exceptions. Similar rules apply in a growing number of other jurisdictions, including several US states.
| Provider | What it places on a visitor’s device | Consent |
|---|---|---|
| AgentBuild site analyticsbuilt in | No cookies. No IP addresses retained, no cross-site identifiers. | Not required |
| Plausible Analyticsplausible | No cookies. Aggregate measurement only. | Not required |
| Google Search Console verificationgsc_meta, gsc_dns | No cookies. A verification tag or DNS record only. | Not required |
| Google Analytics 4ga4 | Analytics cookies, and identifiers that can persist across visits. | Usually required in the EU and UK |
| Google Tag Managergtm | Whatever tags you load through the container, which we cannot see or bound. | Usually required in the EU and UK |
| Google Ads conversion taggoogle_ads | Advertising cookies used for conversion measurement. | Usually required in the EU and UK |
| Meta Pixelmeta_pixel | Advertising cookies used for measurement and audience building. | Usually required in the EU and UK |
| TikTok Pixeltiktok_pixel | Advertising cookies used for measurement and audience building. | Usually required in the EU and UK |
AgentBuild does not provide a consent banner
We do not currently ship a cookie consent banner, a consent management platform, or a mechanism that withholds a provider’s script until a visitor accepts. When you add a cookie-setting provider, its script loads for every visitor.
That makes the decision yours. You are the operator of your site and the controller of your visitors’ personal data. If you need consent for the audience you serve, you have three practical options: use the cookieless providers in the table above, add a consent tool of your own, or do not add the provider. Your agent will tell you which category a provider falls into at the moment you ask it to connect one.
Where each party’s responsibility sits
AgentBuild provides the platform, keeps the default site cookieless, tells you which providers set cookies, and lets you remove any provider at any time. You choose which providers to connect, decide whether consent is required for your visitors, obtain it if it is, and maintain the privacy notice your own site presents. Providers you connect process visitor data under their own terms, and you may need an agreement directly with them.
Removing a provider
Ask your agent to remove it. The provider’s script stops being included in your site at the next publish. Cookies already placed on a visitor’s device are governed by that provider’s own retention rules and are not ours to clear.
Cookies on agentbuild.it itself
This page concerns the sites you build. For the cookies our own marketing site and dashboard set, including authentication cookies, see our Privacy Policy.
Questions about this page can go to support@agentbuild.it. See also our Terms and Subprocessors.