Privacy policy
Effective August 19, 2026
Adplane connects your ad accounts to Claude. This page describes what Adplane stores, what it never stores, and how to delete your data. Contact: support@adplane.ai.
What we store
- Your name and email address, from Google sign-in.
- For each connected ad-platform login, the name on that account, so the accounts page can show you which one is which when you connect more than one.
- Metadata about your connected ad accounts, on Google Ads and Meta Ads alike: account IDs, account names, currency codes, and manager or business structure.
- Usage counts: how many queries you run per day, for metering. Not the content of the queries or their results. We also record which tool was called and, when a request is refused, a short category code describing why, so we can fix problems and see what to build next; these records never contain your text, your account data, or anything from your reports.
- Subscription status and billing metadata: your plan, its status, billing-period dates, and Stripe reference identifiers. Payments are processed by Stripe; your card details go directly to Stripe and never touch our servers.
What we never store
Your ad report data, from Google Ads and Meta Ads alike, passes through Adplane on its way to Claude. Identical queries are cached for at most ten minutes so that repeats and pagination do not re-query the platform, then the cache expires. Report data is never written to durable storage, never sold or shared, never used for advertising, and never used to train machine learning models.
Google user data (Limited Use disclosure)
Adplane's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Adplane uses the Google Ads scope to read your reporting data at your direction and, only when you explicitly ask, to create and edit campaigns, ad groups, keywords, and ads in your account. Anything Adplane creates starts paused, and nothing can spend money without your explicit instruction. We use Google user data only to provide the user-facing features described here. We do not use it for advertising, we do not sell it, we do not use it to train machine learning models, and we do not transfer it to others except as needed to provide the service, with your consent, or as required for security or legal reasons.
Meta and other ad platforms
Adplane also connects Meta (Facebook and Instagram) ad accounts when you choose to link them, and may support further ad platforms over time. For any connected ad platform, the same rules apply. We store an access token for the connection, encrypted at rest, together with basic account metadata: account IDs, names, currency, time zone, and status. Where a platform publishes ads through a page or profile you manage, as Meta does through Facebook Pages, we also list those pages, their IDs and names only, so you can pick one when building an ad. Reporting data from any connected platform follows the same rule as above: cached for at most ten minutes, never written to durable storage, never sold or shared, never used for advertising, and never used to train machine learning models.
If you ask your assistant to build ads, the images, videos, and ad text you provide are transmitted to the platform and stored in your own ad account there; Adplane keeps no copies. Anything Adplane creates on an ad platform starts paused, and nothing can spend money without your explicit instruction. Disconnecting on the accounts page deletes the platform tokens and account metadata immediately, and we honor deletion requests initiated from the platform's own data deletion mechanism automatically.
Tokens and security
Connecting Google Ads stores a Google refresh token, and connecting Meta Ads stores a Meta access token, so Adplane can run queries, and make the changes you ask for, when you ask Claude to. Those tokens are encrypted at rest and are deleted when you disconnect on the accounts page; the Google token is also revoked with Google, and a Meta grant can additionally be revoked from your Facebook account's Business integrations settings. All traffic uses TLS. Tokens issued to Claude and other MCP clients are scoped to your user and can be revoked the same way.
Cookies, analytics, and conversion measurement
Adplane sets one session cookie to keep you signed in, plus one first-party cookie (ap_ft, kept for up to 90 days) that remembers the first page you landed on and the site that referred you, so we can tell which of our ads or links bring people here. That value is saved to your account when you sign up and is used for nothing else. The site also loads Google's advertising tag (gtag.js) so we can measure when one of our own Google ads leads to a subscription; it sets Google cookies that are governed by Google's privacy policy. It also loads the Meta Pixel so we can measure when one of our own Facebook or Instagram ads leads to a visit or a subscription; it sets Meta cookies that are governed by Meta's privacy policy. When you sign up or start a subscription, our server may also report that single event to Meta's Conversions API with your IP address, browser user agent, and the Pixel's own cookie identifiers, so the measurement still works when the Pixel is blocked; no name, email, or account data is included. For subscriptions, those same identifiers are attached to the Stripe checkout session so Stripe's payment confirmation can carry them back to our server.
The site also loads Microsoft Clarity, which records a replay of your visit: the contents of the page, your clicks, scrolling, and mouse movement, so we can see which parts of the site confuse people. It sets two first-party cookies of its own, _clck (kept for about a year) and _clsk (kept for the session), along with Microsoft cookies that are governed by Microsoft's privacy statement. Your accounts and billing pages are masked, so a recording shows the layout and where you clicked but not your ad account names, identifiers, or billing details. There are no other third-party trackers, and your Google Ads and Meta Ads report data is never used for any of this.
Service providers
Adplane runs on Fly.io (hosting and databases), routes traffic through Cloudflare, talks to the Google Ads API and Meta's Marketing API on your behalf, and uses Stripe for payments. Stripe's handling of your payment information is described in Stripe's privacy policy. These providers process data only as needed to run the service.
Retention and deletion
Disconnecting on the accounts page deletes your tokens and connected account metadata immediately, for Google Ads and Meta Ads alike. To delete your Adplane account and everything associated with it, email support@adplane.ai from your sign-in address and we will confirm within a few days.
Children
Adplane is a business tool and is not directed to anyone under 18. We do not knowingly collect data from children.
Changes
If this policy materially changes, the effective date above changes with it, and signed-in users will be notified by email.