Privacy policy
Last updated 2026-11-11
Camberstack ("we") runs camberstack.io, a connector that lets an AI assistant you choose read and, with your approval, change your Google Ads account. This policy explains what we access, why, and what we keep.
What we access
- Your Google account email and a stable Google account ID (the
openidandemailscopes), so the same person gets the same account and change history each time. - Your Google Ads data, optional (the
https://www.googleapis.com/auth/adwordsscope): account and campaign structure, performance metrics, search terms, keywords and conversion settings, read when your AI assistant calls a Camberstack tool. - Your Search Console data and sitemaps, optional (the
https://www.googleapis.com/auth/webmastersscope; a connection made before 2026-10-31 may holdhttps://www.googleapis.com/auth/webmasters.readonlyinstead): the websites you have verified, their Google Search clicks, impressions, queries and positions, Google's index status for pages you ask about, and the sitemaps you have submitted, read when your AI assistant calls a Search Console tool, for example to compare what you pay for with where you already rank. Google Ads and Search Console are each optional: you can untick either on Google's consent screen and add it later through a link Camberstack gives you. With the same scope, Camberstack submits, resubmits and removes sitemaps and adds and removes properties, each only when you approve a specific proposal. We keep what we need to show and reverse each change (the sitemap or property, and the proposal), as for any other change. - Your Google Analytics data and setup, optional (the
https://www.googleapis.com/auth/analytics.readonlyandhttps://www.googleapis.com/auth/analytics.editscopes): the names of the Google Analytics accounts and properties you can access; reports on your properties' traffic, such as sessions, users, engagement, key events (conversions), landing pages and traffic sources; and each property's setup (web streams and their measurement IDs, key events, Google Ads links), read when your AI assistant calls a Google Analytics tool, for example to see whether visitors from your ads convert. With edit access Camberstack can set up tracking for you, only when you approve a specific proposal: create a property with a web stream, mark or unmark an event as a key event, and link or unlink a Google Ads account. Every such change is logged and can be undone. Google Analytics is optional: both scopes come as one box on Google's consent screen, which you can untick and add later through a link Camberstack gives you. - Your Google Merchant Center data and products, optional (the
https://www.googleapis.com/auth/contentscope): the names of the Merchant Center accounts you can access; account-level issues; your products' status (eligible, limited, pending or disapproved) and the issues Google reports for each, with product IDs, titles, brands and prices; and reports on your products' Google Shopping and free-listing clicks and impressions, read when your AI assistant calls a Merchant Center tool, for example to find why products stopped showing. Camberstack can also change products for you, only when you approve a specific proposal: override a product's attributes (such as its price, GTIN or title), exclude it from Shopping ads or free listings, or create, change and delete products of its own. Overrides go through Camberstack's own supplemental data source in your account, which it creates and, the first time, places ahead of the product's feed in that feed's rules; products it creates live in its own data source, "Camberstack products". Your feed and its products are never edited, added or deleted. Every change is logged and can be undone: undoing an override lets your feed's values apply again, and undoing a deletion re-creates the product. Merchant Center is optional: it is a box on Google's consent screen, which you can untick and add later through a link Camberstack gives you. - Your Google Tag Manager containers, optional (the
https://www.googleapis.com/auth/tagmanager.edit.containers,https://www.googleapis.com/auth/tagmanager.edit.containerversions,https://www.googleapis.com/auth/tagmanager.publishandhttps://www.googleapis.com/auth/tagmanager.delete.containersscopes): the names of the Tag Manager accounts and web containers you can access, and a container's tags, triggers, workspace and versions (which tags exist, what each sends where, such as a Google Ads conversion ID or a GA4 measurement ID, and when each fires), read when your AI assistant calls a Tag Manager tool, for example to check your conversion tracking. Camberstack can also change a container for you, only when you approve a specific proposal: add a Google tag, a Google Ads conversion tag, a GA4 event tag or a Conversion Linker with the trigger it needs; pause, unpause or delete a tag; create a version of the workspace and publish it to your site; and create or delete a container. Every change is logged and can be undone, except deleting a container, which Google can't reverse and which the proposal warns about first. Tag Manager is optional: it is on Google's consent screen, which you can untick and add later through a link Camberstack gives you.
We request nothing else from your Google account: no Gmail, Drive, contacts or calendar.
How we use it
- To answer the requests your AI assistant makes on your behalf (reports and read-only queries).
- To apply changes to your Google Ads account, your Search Console sitemaps and properties, your Google Analytics setup, your Merchant Center products or your Tag Manager containers, only when you approve a specific proposal, and to reverse them if you ask.
We do not sell your data, use it for advertising, share it with data brokers, or use it to train AI or machine-learning models. Humans at Camberstack do not read your Google data unless you ask us to for support, it is needed for security or abuse investigation, or the law requires it.
Google API Services: Limited Use
Camberstack's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What we store
| Data | Why | Kept until |
|---|---|---|
| Google email and account ID | Identify you across connections | You ask us to delete it, or two years without use (not while on a paid plan) |
| How many Google Ads accounts your login can reach, how many of them had ad spend in the last 30 days, and which manager accounts they sit under (counts and IDs only, never names, amounts or other account data) | Show which accounts are active when you pick one, and size plans to how many accounts people use | The same as your email and account ID |
| Google refresh token, encrypted (AES-256-GCM) | Call Google's APIs (Google Ads, and Search Console, Google Analytics, Merchant Center or Tag Manager if you granted them) when you use a tool | You disconnect or revoke access, or six months without use |
| A sign-in session for the account page (a cookie; we store only its hash) | Keep you signed in to camberstack.io/account | 7 days, or until you sign out |
| A random value in a cookie while you connect an AI app | Check that the browser finishing the Google sign-in is the one that approved the connection | The sign-in finishes, or 1 hour |
| A random value in a cookie while you add a Google service (Google Ads, Search Console, Google Analytics, Merchant Center or Tag Manager) to your connection | Check that the browser finishing Google's consent is the one that opened your link | The consent finishes, or 10 minutes |
| Tokens we issue to your AI app (stored as hashes) | Authenticate your AI app | Expiry (1 hour access, 90 days refresh) or disconnect |
| Proposals: the changes requested, their summary and results, and for a Tag Manager tag you delete, a copy of that tag's settings | Show what changed and let you undo it | You ask us to delete them, or two years without use (not while on a paid plan) |
| Merchant Center product changes you approve: the values you set for a product, and for products you create through Camberstack, their details (such as title, price and link) | Google can't return these, so we keep them to show what's in place and to undo a change | You remove the change or the product, ask us to delete them, or two years without use (not while on a paid plan) |
Feedback you send from camberstack.io/feedback, or through your AI app with send_feedback: your message, what it's about, and your Google email. Your AI app sends only the message you approve, not your conversation | Read it and reply to you | You ask us to delete it |
| A sign-in session for the feedback page (a cookie; we store only its hash) | Know who a message is from, so we can reply and keep spam out | 1 day, or until you sign out |
| A usage log: which tool ran, for which Google Ads account ID, when, how long it took and any error message. For a custom Google Ads query, which fields and resources it asked for, with every value in it (names, keywords, IDs, dates) removed. Never the tool's other inputs, or any results | Find and fix failures, see which features are used, and count how many Google Ads accounts you use for your plan | You ask us to delete it, or two years without use (not while on a paid plan) |
Reports, search-term lists, query results, Google Analytics reports, Merchant Center product statuses and reports, and Tag Manager containers' tags and triggers are computed on request and returned to your AI assistant. We do not store them. When a proposed ad uses an image URL, we download that image only to upload it to your Google Ads account as an image asset; we do not keep the file. Web server and application logs (IP address, time, path, errors) are kept for up to 90 days for security and then deleted. When the server hits a bug, the error and where in the code it happened go to an error tracker we host ourselves; no request contents, cookies or tokens are sent with it.
Data retention and deletion
We keep Google user data only as long as we need it to run Camberstack for you. The table above gives the period for each item we store; Google data we read for you and don't list there is not retained.
- When you stop using Camberstack: "without use" means no tool call from your AI app and no new connection. After six months of it we revoke and delete your Google token (Google stops honoring an unused one after six months anyway); connect again to carry on. After two years we delete your account, proposals and usage log.
- When you disconnect: the
disconnecttool revokes our access at Google and immediately deletes your Google token and every token we issued to your AI app. If you remove Camberstack at Google instead, the token stops working at once and we delete it the next time it is tried, or after six months at the latest. Your account and change history stay until you ask us to delete them. - When you ask us to delete your data: email adam@camberstack.io from your Google account's address and within 30 days we delete your Google token, account, proposals, Merchant Center product changes, usage log and feedback.
- Backups: daily backups of our database hold the stored items above. They are used only to recover from a failure and expire after 35 days at most, so data you delete leaves them within 35 days of its deletion. A Google token in a backup stays encrypted, and stops working once revoked.
Who else handles your data
- Your AI app. Tool results go to the AI app you connected (for example Claude or ChatGPT). How that provider handles the conversation is governed by its own privacy policy.
- Service providers. Resend delivers our emails, so it receives your email address. Stripe handles payments if you upgrade, so it receives your email address and keeps payment records under its own policy. Cloudflare R2 stores an encrypted-at-rest copy of our backups. They receive this only to provide these services to us.
We do not transfer your Google data to anyone else unless you ask us to or the law requires it.
Where it runs
Camberstack runs on infrastructure we operate in the United States, with the off-site backup copy on Cloudflare R2. We use no third-party analytics on your Google data.
Emails
We may send you a few short emails about using Camberstack: a welcome when you connect, a note if you connect but don't try it within a couple of days, a note asking how it went after your first applied change, one if you try Camberstack on more Google Ads accounts or more Google services than the Free plan covers, and a confirmation if you upgrade. Each is sent once. We may also send occasional one-time announcements about changes to your account or to Camberstack's features. All of them come from adam@camberstack.io, to the email address of the Google account you connected, and never contain your Google Ads data. Every email has an unsubscribe link, and replies reach a person.
Our own ads
If you reach this site by clicking one of our Google ads, we keep the ad click identifier Google adds to the link in a cookie on this site for up to 90 days. If you then connect Camberstack for the first time, we report that click to our own Google Ads account as a conversion, so we can tell which ads work. We send only the click identifier and the time: no email, account ID or Google Ads data of yours.
The same goes for our ads in ChatGPT: we keep the click reference OpenAI adds to the link in that cookie, and report it to our own OpenAI advertising account if you then connect Camberstack for the first time, and again if you start a paid plan within 30 days. We send only the click reference, which of those two things happened, the plan's name and price, and the time: no email, account ID or Google data of yours.
Website analytics
We count visits to this website's pages with Matomo, which we host ourselves on the same infrastructure. A small script served from this site sends the page you opened, the site that linked you here, and the name of the ad or campaign that brought you, if any (never the ad's click identifier); we also record that a Google Ads account was connected, with no account, email or ID attached. Matomo sets no cookie and stores nothing in your browser. Matomo uses your IP address to estimate roughly where a visit came from and removes the last part of it before saving. Visits are grouped by a salted hash of your IP address and browser, with the salt changed daily and kept only in memory, so it cannot identify you or link visits across days.
We also use Google Analytics (GA4) on this website's pages, loaded by the same script. It records the pages you visit, how you arrived
(for example from one of our Google ads or a search), and roughly where and on what kind of device, and it sets first-party cookies
(_ga and _ga_<id>, kept up to 2 years) so repeat visits are counted once. Google processes this under
its privacy policy; you can block it with your browser's cookie settings or
Google's opt-out add-on. This covers only visits to camberstack.io.
None of your Google Ads, Search Console, Google Analytics, Merchant Center or Tag Manager data that Camberstack reads for you is ever sent to either analytics tool.
Your choices
- Disconnect: ask your AI to run the
disconnecttool, or remove Camberstack at myaccount.google.com/permissions. Either stops all access; the tool also deletes the stored token. - Delete everything: email adam@camberstack.io from your Google account's address and within 30 days we delete your Google token, account, proposals, Merchant Center product changes, usage log and feedback (see Data retention and deletion).
Data protection
We protect your Google user data and other sensitive data, including Google tokens, account details and your change history, with these measures:
- Encryption in transit: all traffic between your AI app or browser, Camberstack and Google uses HTTPS (TLS 1.2 or newer). Plain HTTP requests are redirected to HTTPS.
- Encryption of credentials at rest: Google refresh tokens are encrypted with AES-256-GCM, using a key kept outside the database. Tokens we issue and sign-in sessions are stored only as SHA-256 hashes, so a copy of the database alone can't be used to reach Google or to sign in.
- Keeping as little as possible: reports and query results pass through and are not stored, and the usage log leaves out tool results and the values in your queries.
- Access control: only Camberstack's operator can sign in to the server, the database and the backups. Each person's data is tied to their own Google account, and the service acts only on the accounts that Google account can reach.
- Isolation: the application runs as an unprivileged user in its own container, and is not exposed to the internet directly: requests reach it only through a rate-limited HTTPS proxy.
- Protected backups: backups are checked for integrity after every run. The encryption key is backed up separately, itself encrypted to a private key that is not on the server, and the off-site copy sits in a locked bucket that the server can't alter or delete.
- Safeguards on changes: changes are validated with Google before you approve them, are limited to the operations listed on the homepage, and are logged so they can be undone, apart from the few Google can't reverse, which warn you first.
Children
Camberstack is a business tool and not directed at anyone under 18.
Changes and contact
We will post changes here and update the date above. Questions: adam@camberstack.io.