TreeTank Ads Ads Baby

What this policy covers

This policy covers the Ads Ads Baby plugin family published by TreeTank (Jacek Mariański): Google Ads Baby, Meta Ads Baby, Google Analytics Baby, Report Baby, and Marketing Context MCP, together with the Ads Ads Baby marketplace hub. On Google and Meta sign-in screens the app appears as TreeTank Ads Ads Baby. More about the app: treetank.net/ads-ads-baby.

Each plugin is a local MCP (Model Context Protocol) server. Your AI assistant host, such as Claude Code, Codex, or Cursor, starts it as a process on your own computer.

Google user data the app collects

When you sign in with Google, TreeTank Ads Ads Baby collects the Google user data listed below through the Google Ads API and the Google Analytics APIs. The app collects this data only on your own computer, when you or your AI assistant call one of its tools.

The app does not collect your name, email address, profile photo, contacts, or any other Google Account information, and it does not request any scopes other than the two listed above.

Google OAuth scopes the app requests

TreeTank Ads Ads Baby asks Google for two OAuth scopes and no others. It does not request your Google profile, email address, contacts, Gmail, Drive, or any other Google product.

• Google Ads (www.googleapis.com/auth/adwords), used by Google Ads Baby: the list of Google Ads accounts you can access, with their IDs and names; account structure, including campaigns, ad groups, ads, keywords, assets, budgets, bidding, targeting, and conversion goals; performance reports, including impressions, clicks, cost, conversions, and search terms. With this scope the plugin can also create, change, pause, or remove those items, but only after you confirm each change with a safe word.
• Google Analytics (www.googleapis.com/auth/analytics.readonly), used by Google Analytics Baby: the list of Analytics accounts and GA4 properties you can access; property configuration, including custom dimensions and metrics and linked Google Ads accounts; standard and realtime reports with the dimensions and metrics you ask for. This scope is read-only, so the plugin cannot change anything in Google Analytics.

How the app uses Google user data

• To answer the request you make in your AI assistant, for example “show last month’s campaign cost” or “find search terms with spend and no conversions”.
• To run the built-in analyses, such as the account hygiene report, budget scaling candidates, and search-term waste, which are calculated on your computer.
• For Google Ads only: to carry out a change you have previewed and confirmed.
• The data is not used for advertising, profiling, credit decisions, or selling, and I do not use it to train AI models. Nobody at TreeTank can read it, because it never reaches me.

Where Google user data is stored

• OAuth refresh token and client settings: in ~/.google-ads-baby/config.json and ~/.google-analytics-baby/config.json on your computer, until you revoke access or delete the file. The Google Ads developer token you enter is stored in the same place.
• API responses: kept in memory only while the tool call runs, then handed to your AI assistant. The plugins do not write them to a database or cache.
• Change log: each change you confirm in Google Ads is recorded in ~/.google-ads-baby/mutation-history.jsonl with its time, account ID, action, parameters, preview, and API result, so you can audit or undo it. It stays until you delete it.
• Files you ask for: a report rendered by Report Baby, or a note saved in Marketing Context MCP, is stored in their local folders until you delete it.
• All traffic to Google uses HTTPS. The OAuth sign-in returns to a local address on your computer (localhost), not to a TreeTank server.

Who Google user data is shared with

The app shares Google user data only with the AI assistant you run it in, and only as a result of your own request. That assistant, for example Claude Code, Codex, or Cursor, may send the data to its model provider under its own privacy policy. Google user data is not transferred to TreeTank or to anyone else, except where you direct it, for example by sending a report to a client, or where the law requires it.

Limited Use disclosure

TreeTank Ads Ads Baby’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. In particular:

• Google user data is used only to provide the user-facing features described in this policy, which you request in your own session.
• Google user data is transferred to others only when necessary to provide those features at your request, as described above, to comply with applicable law, or as part of a merger or acquisition with your consent.
• Google user data is never used or transferred for serving advertisements, including retargeting, personalized, or interest-based advertising, and is never sold.
• Google user data is never used to develop, improve, or train generalized AI or machine learning models.
• No human at TreeTank reads Google user data. The app has no server that could receive it.

How Google user data is protected

• Every request to Google APIs and Google OAuth is sent directly from your computer over HTTPS (TLS). There is no TreeTank server in between, so there is no central database of tokens or account data that could be breached.
• The OAuth sign-in redirects to a local address on your computer (localhost), so the authorization code never passes through a third-party server.
• The refresh token is stored only in the plugin’s config file in your home directory. Access to it is controlled by your operating system account; I recommend full-disk encryption and not sharing your user account.
• The Google Ads Baby safety flow requires a separate confirmation with a one-time safe word before any change is sent, so an AI assistant cannot change your account on its own.
• The source code is public, so anyone can check how the app handles data.

How long Google user data is kept and how to delete it

• OAuth tokens: kept until you revoke access or delete the config file.
• API responses: not retained. They exist in memory only while a tool call runs.
• Change log and files you create: kept on your computer until you delete them.
• To revoke the app’s access, go to myaccount.google.com/permissions and remove TreeTank Ads Ads Baby. Google then invalidates the tokens.
• To delete all locally stored Google user data, delete the ~/.google-ads-baby/ and ~/.google-analytics-baby/ directories, plus any reports or notes you no longer need.
• TreeTank holds no Google user data, so there is nothing to delete on my side. If you have questions about deletion, write to hello@treetank.net.

Meta user data the app accesses

Meta Ads Baby asks Facebook Login for the ads_read, ads_management, and business_management permissions. It uses them to read the ad accounts, campaigns, ad sets, ads, creatives, audiences, and insights you can access, and to make changes you confirm with a safe word. The access token is stored in ~/.meta-ads-baby/config.json on your computer. Like Google data, Meta data is kept in memory only during a tool call, is shared only with your AI assistant, and never reaches TreeTank.

Processing on your device

All data the app collects, as described in this policy, is processed by the app on your device. TreeTank does not operate servers, user accounts, telemetry, crash reporting, analytics, or advertising SDKs for the app. As a result, copies of your ad account data, analytics data, reports, notes, and OAuth tokens are not transferred to TreeTank, and TreeTank does not sell or share them.

The only personal data TreeTank itself receives is correspondence you start. If you email me or open a GitHub issue, I receive your email address or GitHub username and whatever you write. I use it only to reply and keep it as a support history for as long as it is useful, usually no longer than two years. GitHub issues are public and stay on GitHub under its own terms.

Data stored on your computer

The plugins save configuration and working files locally, in your home directory unless you change the location:

• Google Ads Baby: ~/.google-ads-baby/ holds the OAuth tokens, developer token, selected account IDs, and a local audit log of changes you confirmed (mutation-history.jsonl).
• Meta Ads Baby: ~/.meta-ads-baby/ holds the Meta access token, an optional app ID and secret of your own, safety preferences, and a local audit log of changes you confirmed.
• Google Analytics Baby: ~/.google-analytics-baby/ holds the read-only OAuth tokens and plugin settings.
• Report Baby: ~/.report-baby/ holds brandbooks and rendered PDF, PNG, and PPTX files.
• Marketing Context MCP: ~/.marketing-context/ holds client notes, decisions, reviews, and tasks that you or your assistant write, plus a local cache for search.

Network connections the plugins make

Your computer connects directly to the services below. None of these connections goes through a TreeTank server.

• Advertising and analytics platforms you authorize: the Google Ads API, the Google Analytics Data and Admin APIs, Google OAuth, the Meta Graph API, and Facebook Login. Requests carry your own tokens and fetch or change only the accounts you grant access to.
• GitHub (raw.githubusercontent.com and api.github.com): a plugin downloads its server files from its public repository the first time it starts without them, and again when you run update_plugin. Marketing Context MCP also refreshes its bundled knowledge articles on start; you can turn this off with the auto_update setting. These requests send no data about you or your accounts.
• Meta login callback: after Facebook Login, the browser opens a static page at treetank-net.github.io that passes the token on to the plugin at 127.0.0.1. The token travels in the URL fragment, which the browser never sends to GitHub’s servers.
• URLs you provide: when you ask a plugin to use an image or source document from a web address, it downloads that file directly.
• Local search model: Marketing Context MCP can install the @huggingface/transformers package from the npm registry and download a small embedding model from Hugging Face. Your notes are embedded on your computer and are never uploaded. You can turn this off with the embeddings setting or MARKETING_CONTEXT_EMBED=0.

Your AI assistant and the platforms you connect

Tool results, such as campaign data, metrics, or notes, go back to the AI assistant that called the tool. The assistant may then send them to its model provider, for example Anthropic, OpenAI, or Cursor. The privacy policy of that assistant covers this processing, not this one.

Google and Meta process API requests under their own policies: the Google Privacy Policy (policies.google.com/privacy) and the Meta Privacy Policy (www.facebook.com/privacy/policy/). GitHub, npm, and Hugging Face may log standard request details, such as IP address, when files are downloaded.

Revoking access and deleting data

• Revoke Google access at myaccount.google.com/permissions.
• Remove the Meta app at www.facebook.com/settings?tab=business_tools.
• Delete the local directories listed above to remove every token, log, note, and generated file. Uninstalling a plugin through your assistant host removes its code.

Your rights

Everything the plugins store is on your computer, so you can view, correct, export, or delete it yourself at any time. For correspondence I hold, you can ask me for access, correction, deletion, or restriction, or object to its processing, by writing to hello@treetank.net. I process it on the basis of legitimate interest in answering your message (Article 6(1)(f) GDPR) and reply within 30 days.

You can also lodge a complaint with a data protection supervisory authority. In Poland this is the President of the Personal Data Protection Office (UODO, uodo.gov.pl); elsewhere in the EU, see edpb.europa.eu/about-edpb/about-edpb/members_en.

Changes and contact

If a future version changes how data is handled, I will update this page and the date above before releasing it. The source code of every plugin is public, so you can check this policy against the code yourself.

Questions: hello@treetank.net, or open an issue in the relevant GitHub repository.