Security and privacy

Your agent signs in with OAuth 2.1, in your browser. AdsGPT never sees your agent’s credentials, and you never copy an API key.
An authorization works on one AdsGPT organization, the one you choose when you sign in, with your role’s permissions.
It has two scopes: ads:read, to read, and ads:write, which your agent asks for the first time it needs to change something.
AdsGPT’s server talks to each ad platform with the access your organization granted when it connected it. Your agent’s token never reaches an ad platform.

What AdsGPT receives

The calls your agent makes to AdsGPT’s tools, with their inputs: account IDs, queries, campaign plans, ad texts, image URLs, YouTube links and landing page URLs. It never receives your conversation.

What AdsGPT stores

In your AdsGPT organization, available to its members as their roles allow:

the campaign plans, their ads, images and videos, and the campaigns they launched;
a log of every change made to your ad accounts: what changed, what it had before, and the member and the agent it came from.

Who else receives data

The ad platforms you connected, such as Google Ads: the queries, reports and changes your agent asks for, and the images a plan uploads.
The sites of the images you give by URL, which AdsGPT downloads to check and upload them.

Your agent’s provider, such as Anthropic or OpenAI, handles what the tools return under its own privacy policy.

On your machine

The AdsGPT plugin contains only text: the skills, a manifest for each client and the server’s address. It has no scripts, hooks or binaries.

Revoke access

Remove an agent’s access from AdsGPT at any time, or disconnect an ad platform from the Plugins screen. In your agent, you can also remove the AdsGPT server or plugin.