How your data moves

AdCopilot is a connector. When your assistant asks a question, the request goes through AdCopilot to Google's API and the answer comes back the same way.

The path a request takes

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 for 15 minutes, account settings for up to an hour. The account summary your assistant opens a conversation with is held in memory for 10 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 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.

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). 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.