Security

AdPilot sits between your Google accounts and the AI app you choose, Claude or ChatGPT. So we treat security as part of the product. Here is how your data and your accounts are protected, in plain language.

Your Google connection is encrypted

When you connect Google Ads, Google Analytics 4, Search Console or Merchant Center, we never see or store your Google password. Google gives us a limited access token instead. We store the long-lived Google refresh token encrypted at the application level with AES-256-GCM. Someone with a copy of our database could not read it without a separate key that we keep apart from the database.

Your AI app signs in with OAuth 2.1 and PKCE

Claude and ChatGPT connect to AdPilot through a standard OAuth 2.1 sign-in. We accept only the authorization code flow with PKCE (S256), so a stolen sign-in code is useless on its own. You sign in to AdPilot and click Allow before an app gets any access.

Access tokens expire after 1 hour. Refresh tokens expire after 60 days and are rotated: each time the app gets a new token, the old refresh token stops working. Sign-in codes expire after 10 minutes and work once.

We store hashes, not tokens

Every sign-in code, access token, refresh token and private connection link is random and stored only as a SHA-256 hash. The real value exists once, in the response that hands it to your AI app. A copy of our database could not be used to connect to your account.

You can cut the connection at any time

Each AI app you connect shows up in AdPilot under Connections. You can disconnect it there, and its tokens stop working right away. Private connection links work the same way: revoke one and it stops working.

Encrypted in transit and at rest

Every connection between you, your AI app and AdPilot is encrypted in transit over TLS (HTTPS). Our database is encrypted at rest by our provider (Neon), so your data is protected on disk as well as on the wire.

Your AI asks before every change, and every change is recorded

Claude and ChatGPT ask you before they run a change through AdPilot. You read what the app wants to do, then click Allow or Deny. AdPilot runs no AI of its own and does not change your account on its own.

Every change that goes through is written to your AdPilot history: what changed, the values before and after, and when. You can undo a change from the history.

Built-in guardrails

AdPilot checks each change against your live account before it writes it, and rejects requests that point at things that do not exist. The values from before the change are recorded every time, so there is a way back.

We only use Google data to run the service

AdPilot’s use of information from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We use your Google data only to provide AdPilot: to answer the requests your AI app sends on your behalf and to run the changes you allow. We do not sell it and do not use it for advertising of our own. You can revoke AdPilot’s access at any time from your Google account or from AdPilot.

What your AI app does with the answers it receives is governed by your agreement with that app’s provider, Anthropic or OpenAI for example.

Payments never touch our servers

Billing is handled entirely by Stripe, a PCI-DSS Level 1 payment provider. Your card details go straight to Stripe. We never see or store them.

Delete your data any time

You can ask us to delete your data at any time. On request we remove your profile, your connections and your Google access tokens, and we strip personal identifiers from the change records we are required to keep for legal reasons. See our Privacy Policy for the full detail.

Found something that looks off, or have a security question? Email junaid@heyadpilot.com. See also our Privacy Policy and Terms of Service.