Privacy Policy
Last updated: 16 October 2026
1. Who is responsible
AdPilot, also called HeyAdpilot (“we”, “us”), is operated by Junaid Dar, sole proprietor, Ras Al Khaimah, United Arab Emirates, who is the controller for the processing described here. Contact for all privacy matters: junaid@heyadpilot.com. Where you are in the EU/EEA, UK, or Switzerland, the GDPR (or its UK/Swiss equivalents) applies to this processing.
2. What we process, and why
How AdPilot works. AdPilot is a connector. You connect your Google accounts (Google Ads, and optionally Google Analytics 4, Search Console and Merchant Center) to AdPilot. You then connect your own AI application to AdPilot, for example Claude by Anthropic, ChatGPT by OpenAI, or another app that supports the Model Context Protocol (MCP). When your AI app sends a request to AdPilot, AdPilot reads or changes data in your connected Google accounts and returns the result to that AI app. AdPilot itself does not run an AI model on your data. Section 3 explains what happens to the data your AI app receives.
Account & login. Your email, name, and login are handled by our authentication provider, Clerk. Our own database stores a reference to your workspace, not your password. Legal basis: performance of the contract.
Google connections. You connect each Google service through Google’s own OAuth consent screen, and you choose which permissions to grant there. We store the resulting OAuth refresh token encrypted (AES-256-GCM), together with the settings that say which Google Ads account, Analytics property, Search Console site and Merchant Center account you selected and which permissions you granted. We use these connections only to carry out requests from the AI apps you have connected (and the features described in this policy). Legal basis: performance of the contract.
Google Ads (scope adwords, which Google offers only as a combined read-and-change permission): we read campaign settings and performance data, and, when your AI app requests it, make changes such as creating or editing campaigns, ad groups, ads, keywords, budgets and bids.
Google Analytics 4 (optional) (scopes analytics.readonly for reading and analytics.edit for changes): we read your website statistics, such as visits, engagement, traffic sources and landing pages. When your AI app requests it, we can change how your property is set up, for example key events (conversions), custom dimensions and metrics, data streams, audiences, links to Google Ads and other Google products, and property settings such as data retention. We do not request the permission to change who has access to your Analytics account.
Google Search Console (optional) (scope webmasters.readonly): we read how your site does in Google search, such as clicks, impressions, the search terms people used, URL inspection results and sitemaps. Changing Search Console (submitting or deleting sitemaps, adding or removing sites) needs the broader webmastersscope. We ask for it only where that feature is enabled for your account, and Google’s consent screen shows you which one you are granting.
Google Merchant Center (optional) (scope content, the only Merchant Center permission Google offers, which covers reading and changing): we read your products, feed status, product issues and account settings. When your AI app requests it, we can change product data, data sources, inventory, shipping and return settings, programs, promotions, business information and account users.
Connections to your AI app. You can connect an AI app in two ways. With sign-in (OAuth), the app registers with AdPilot (we store the name it gives itself and its return addresses), you sign in to AdPilot and allow access, and the app receives an access token that is valid for one hour and a refresh token that is valid for 60 days and is renewed when used. With a private connection link, you create a web address that contains a secret token and paste it into your AI app. Anyone who has that link can use your connection, so keep it private. In both cases we store only a SHA-256 hash of each token, never the token itself, plus when the connection was created and last used. You can disconnect any app and revoke any link at any time in Settings. Legal basis: performance of the contract.
Requests from your AI app. Each request names a tool and its inputs, for example which campaign to read or what to change. We process the request to carry it out and send the result back to the AI app that made it. AdPilot does not change your Google accounts unless a connected AI app requests it. Your AI app decides when to call AdPilot based on your instructions to it, so please review what you ask it to do. If your AI app asks AdPilot to analyze a website, we fetch the public pages of that website and return their content. If your AI app saves facts about your business through AdPilot (for example your goal, what you sell, or your website), we store them as your business profile and return them to your AI app in later sessions. Legal basis: performance of the contract.
Change history & audit log. Every change made through AdPilot is recorded: what was changed, in which account, when, the request that was sent, and, where Google lets us read it, the state before the change and Google’s response. For Google Ads changes we also keep a pre-change snapshot. In addition, we log each tool call made by your AI app: the tool name, whether it was a change, the Google Ads account, whether it succeeded, the time, and which connection made it. This tool-call log does not store the inputs your AI app sent or the results we returned; the details of changes are kept in the change history described above. Records from earlier versions of AdPilot may also contain who approved a change, the chat message that triggered it, and your acknowledgment of our former AI risk notice (its wording, version, time, IP address, and browser identifier). Legal basis: our legitimate interest in proving what was requested and changed (establishment, exercise and defense of legal claims). This protects you as much as us.
Our own AI (internal use only). AdPilot used to offer a built-in chat assistant and AI-written report texts, powered by Claude from Anthropic, PBC acting as our processor. These now run only for our own internal accounts and our administrators. We no longer send the data of customer accounts to Anthropic as part of the service. Conversations you had with the earlier assistant remain stored with your account until you delete your account. Legal basis: performance of the contract.
Billing. Payments are processed by Stripe; card details never touch our servers. We store your plan, subscription status, and any credit balance. Legal basis: performance of the contract and legal (tax) obligations.
Server logs. Our hosting provider processes technical logs (IP address, browser type, timestamps) as required to deliver the site securely. Legal basis: legitimate interest in security and reliability.
3. Who receives data
Your own AI app (a transfer you start). You choose the AI app you connect and you have your own agreement with its provider, for example Anthropic (Claude), OpenAI (ChatGPT) or another company. Whatever AdPilot returns to your AI app, including data from your connected Google accounts, is passed to that provider because you asked for it. From then on the provider processes that data under your agreement with them and their own privacy policy. That provider is not our service provider, and we do not control how it stores, uses or shares the data, for example where it processes it, how long it keeps it, or whether it uses it to train AI models. Please check your AI provider’s terms and privacy settings. You can stop this flow at any time by disconnecting the app or revoking the link in Settings.
Our service providers (processors). We use a small set of service providers, each bound by a data processing agreement:
| Provider | Purpose | Location | Transfer safeguard |
|---|---|---|---|
| Vercel Inc. | Hosting and delivery of the website, the app and the AI connection endpoint | USA | EU-US Data Privacy Framework |
| Neon Inc. | Database (your account, connection settings, change history, audit log) | USA | Data Privacy Framework / SCCs |
| Clerk Inc. | Login and authentication | USA | EU-US Data Privacy Framework |
| Stripe, Inc. | Payments, invoices, tax | USA | EU-US Data Privacy Framework |
| Google LLC | Google Ads, Analytics, Search Console and Merchant Center APIs, and Google sign-in | USA | EU-US Data Privacy Framework |
We also use Anthropic, PBC for our own internal accounts (see Section 2). It does not receive data from customer accounts as part of the service.
We do not sell personal data, and we do not run third-party advertising on our site.
4. International transfers
We are established in the UAE and use service providers in the United States. Transfers from the EEA/UK/Switzerland to our US providers are protected by their certification under the EU-US Data Privacy Framework and/or Standard Contractual Clauses incorporated in our data processing agreements. Where data reaches us in the UAE, we apply this policy and the security measures described in it directly; the GDPR applies to that processing under Article 3(2).
Data that your own AI app receives (Section 3) goes wherever your AI provider processes it. Which safeguards apply to that transfer depends on your agreement with that provider.
5. How long we keep data
Account, business profile, earlier chat history, reports: kept while your account exists; deleted on account deletion (subject to the records below).
Google tokens: deleted when you disconnect the account or delete your account.
AI app connections: access tokens expire after one hour and refresh tokens after 60 days without use. You can revoke any connection or link at any time, and all of them are revoked when you delete your account. A revoked connection can no longer be used; we keep its record (app name, dates, token hash) together with the audit log.
Change records, audit log, acknowledgments: retained for up to 6 years after account closure to the extent necessary for the establishment, exercise or defense of legal claims (Art. 17(3)(e) GDPR). If you request erasure, we delete your profile, business profile, chat history, and Google tokens, revoke every AI app connection, and remove personal identifiers (names, message texts, IP addresses) from the retained change records, keeping only the fact, time, and content of each account change.
Billing records: kept as long as tax law requires.
Data that your AI app has already received is kept by your AI provider under its own rules; deleting your AdPilot account does not delete it there.
6. Cookies
Strictly necessary cookies keep the app working: an authentication session cookie (Clerk) and a short-lived security cookie during the Google sign-in flow. These are always on.
For visitor statistics we use two tools. Vercel Web Analytics is cookieless and does not track individuals across sites. Google Analytics 4 (provided by Google LLC) does set analytics cookies, such as _ga, which measure how visitors find and use this website so we can improve it. We use it for aggregate site statistics, not to serve you ads.
You can opt out of Google Analytics at any time with Google’s opt-out browser add-on, or by blocking cookies in your browser. Disabling these cookies does not affect your ability to use AdPilot.
7. Google user data (Limited Use)
AdPilot’s use and transfer of information received from Google APIs (Google Ads, and, if you connect them, Google Analytics, Search Console, and Merchant Center) to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.
We use Google user data only to provide the features you request through AdPilot. We pass it to your own AI app only when that app requests it through the connection you set up, so that it can give you the results you asked for. We do not sell Google user data, do not use it for advertising, and do not use it to develop, improve or train generalized AI or machine learning models. Once your AI app has received the data, its further handling is governed by your agreement with your AI provider (see Section 3).
You can revoke AdPilot’s access at any time in your Google account security settings or in AdPilot’s settings.
8. Your rights
Where the GDPR (or a similar law) applies, you have the right to access, rectify, erase, and receive a copy of your personal data, to restrict or object to certain processing, and to lodge a complaint with a supervisory authority in your country. Contact us at junaid@heyadpilot.com. We respond within one month. Deleting your account is always possible; see Section 5 for what is retained and why. For data your AI app has received, please contact your AI provider.
9. Security
All traffic is encrypted in transit (TLS); the database is encrypted at rest; Google refresh tokens are additionally encrypted at the application level (AES-256-GCM); tokens and connection links for AI apps are stored only as SHA-256 hashes, and AI app sign-in uses OAuth with PKCE; payments are handled entirely by Stripe; access to production systems is restricted. Every change made through AdPilot is recorded.
A connected AI app, and anyone who has one of your connection links, can read and change your connected Google accounts through AdPilot. Disconnect apps and revoke links you no longer use.
10. Changes
We will update this policy as the product evolves and indicate the date of the latest revision at the top. For material changes we will notify you in the app or by email.
See also our Terms of Service and Legal Notice.