How your data moves
AdCopilot is a connector, not a data warehouse. Queries run live against your Google accounts; here is what it keeps from them, and for how long.
AdCopilot is a connector with work of its own. When your assistant calls one of its tools, AdCopilot checks the call, then calls Google's API through its own Google Cloud project, with the access you granted; an audit tool also works out its findings on AdCopilot's server before the answer goes back.
On every plan, including Free, AdCopilot also reads your connected Google Ads account once a day on its own, to email you the daily check-in: a short audit that changes nothing, kept like any saved audit. The email carries the account's figures: yesterday's spend, clicks, impressions and conversions, and the keywords and search terms that spent, were clicked, showed or converted the most over the last 30 days. Like every AdCopilot email it is delivered through our email provider, named on the privacy page's sub-processor list. Pause it on the Routine card in the dashboard, or with the unsubscribe link in the email.
If you connect Search Console, AdCopilot also checks your sites once a day on its own: Google's inspection of each site's home page, and how many times Google Search showed the whole site on each day of about the last five weeks, as one total a day (no searches, pages or countries). It is there to tell you if Google is not showing your home page, or if the searches that find your site fell sharply, and only your assistant tells you, at the start of a conversation within two days of the check: what these two reads find is never in an email or on the dashboard. It changes nothing and uses none of your daily operations. To stop it, disconnect Search Console in Google products, or remove AdCopilot's access in your Google account; in a team, a site that another Search Console connection in your workspace also reaches, such as a teammate's, is still checked through that one until it is disconnected too. Pausing the check-in on the Routine card does not stop it. See Search Console tools.
The same daily check also looks at your site's pages: the sitemaps Google holds for the site and each sitemap file from your site itself, the pages Google Search showed in the last 90 days with how many times each, and Google's inspection of up to 100 of those pages a site a day, once your workspace's owner and the person who connected the site's Google account have accepted the Privacy Policy dated 2 November 2026. It tells you which pages Google left out of its index, answer 404 or redirect wrongly, and which sitemaps have a problem: your assistant says it within a week of a new finding and when you ask, and your daily check-in email can carry one line counting what was first found, which names no page. It changes nothing, uses none of your daily operations, and stops the same way. See Search Console tools.
The path a request takes
Your assistant calls a tool
You ask a question, and your AI client calls an AdCopilot tool, for example
search or full_audit.
AdCopilot calls Google
AdCopilot checks the call (your plan, the accounts you switched on, the budget checks), then calls Google's API through its own Google Cloud project, with the access you granted. An audit tool does its own arithmetic here, on AdCopilot's server.
The answer returns
The answer, Google's rows or the findings an audit worked out from them, returns to your assistant, which writes the reply you read.
What AdCopilot keeps
Queries run live against your account; audit reads are cached for up to an hour, a saved audit's findings are kept for 180 days, we log each tool call (tool, account id, outcome), and the business profile your workspace builds as you work (business details, the first campaign, a log of decisions, the last session's note) is kept until the workspace owner deletes it.
- The read cache. The rows an audit reads from Google Ads are cached so a repeated audit is faster and does not ask Google twice: performance reports and account settings alike for up to 5 minutes. The account summary your assistant opens a conversation with is held in memory for 5 minutes.
- Saved audit results. When an audit's results are saved to your dashboard, they keep the account-level figures the audit measured, such as total conversions and conversion value, with the currency, time zone and date range, and a written summary of the result; each finding keeps its description, the changes it suggests and up to 10 example rows from your account, such as search terms, keywords, ad group and campaign names, landing-page URLs, conversion-action names, cost and conversions. They are deleted after 180 days.
- The ledger. One entry per tool call: the tool, the account id, the outcome and the time. It never holds the rows that came back, and entries are deleted after 180 days.
- The server's system log. Each Google Ads request is logged with its account id and the text of the query your assistant or an audit ran, and the full content of any request Google rejects is logged too, such as the keywords or ad text it tried to set. It is kept until the server's routine log rotation removes it.
- The business profile. The business details and budget you give it, the first campaign it built, a log of decisions and a note on the last session, so the next conversation starts where the last one stopped. The workspace owner can delete it.
- The daily site check's result. With Search Console connected, the latest check of each site: the home page it inspected, what Google said about it, two averages of daily impressions, and when. Each check replaces the last, and a result is deleted 14 days after the site was last checked. The check is not a tool call, so it has no ledger entry.
- The daily check of your pages. Each page it knows on each site: its address, whether a sitemap lists it, how many times Google Search showed it in the last 90 days, Google's answer for it and what the check made of it; and each sitemap's address and the state Google and the address report. Deleted 30 days after the site's pages were last checked, and a page no sitemap or search names any more 30 days after that.
From your Google identity, AdCopilot keeps your email address, the ID Google gives your account, which is how it tells your Google account from another, and the first name on the Google account you sign in with, so its emails can greet you by name; the name is updated each time you sign in. The service also keeps billing, email, trial, sign-in, routine and error records, and nightly database backups; see the privacy policy for each and how long it is kept. The conversation itself lives with your AI client's vendor, under its policy and your plan settings.
AdCopilot's own use of AI
Apart from your conversation, AdCopilot's staff use AI models from Anthropic in two ways:
- To improve the checks. They compute aggregated statistics across workspaces on AdCopilot's server, such as how often each audit check fails, and analyse them with Anthropic's models. The statistics name no person, workspace, account, campaign, keyword or search term, hold no figure about fewer than five accounts, and are all Anthropic receives for this work. AdCopilot's own and demonstration workspaces are left out, and so is any workspace whose owner, or anyone who connected a Google account to it, has not accepted the privacy policy, or whose owner objects: the owner can switch the statistics off in Settings on the dashboard, or write to support@adcopilot.cloud.
- As a working tool. The same models help them build, run and support AdCopilot. They read Google data only when someone investigates a bug, abuse or a problem you asked about, and then only the records that investigation needs, such as the system log entries of a failed audit.
Anthropic is a sub-processor: it processes this data on AdCopilot's behalf, its commercial terms do not permit it to train models on it, and it deletes it within 30 days, keeping it longer only where those terms allow or the law requires it. The privacy policy's Google user data section is the commitment.
Your Google access
- We never see your Google password. You sign in with Google itself, and Google returns a token for the access you granted. The token is encrypted at rest.
- Each consent screen asks only for what that step needs. Connecting a product from its card in Google products asks for that product's access and your Google identity (your email address and your basic profile). Signing in asks for your Google identity alone. Joining a team or creating a workspace asks for Google Ads. Reconnecting asks again for Google Ads and the products your Google account already connected, so the new token keeps them. None of them asks for Gmail or Drive.
- You can withdraw it at any time, from your Google account's connected apps, or with Disconnect Google in Google products. That deletes the token AdCopilot stored for you in the workspace and disconnects every product. It also asks Google to cancel AdCopilot's access, unless another AdCopilot workspace or a teammate still uses the same Google account: Google's cancel applies to the whole account, so it would disconnect them too. Disconnect on a single product stops AdCopilot using that product and keeps the token.
The privacy policy on adcopilot.cloud is the commitment. This page explains the mechanism.
Read vs write tools
Reads run freely and writes are proposed first. For a hard stop, set your AI client to ask before writes (Needs approval in Claude, Allowlist in Cursor).
Accounts and scope
Which Google Ads accounts an assistant can act on — what your Google sign-in can open, the accounts you switch on, and the number your plan allows.