Privacy Policy

Last updated: 23 October 2026

AdData is a private service operated by Pavlo Shum (private individual, Kyiv, Ukraine). This policy explains what data the service receives when you sign in with Google, what happens to it, and how to delete it.

What data we receive

• Your Google email address and sign-in confirmation (the openid and userinfo.email scopes) — to identify who is making a request and to check whether you are allowed to use the service.
• Google access and refresh tokens — to call the Google Ads API, the Google Analytics Data API and the Search Console API on your behalf. The service never sees your Google password.
• Data from your advertising and analytics accounts — campaign statistics, reports, search terms. The service requests them from Google only in response to your specific request in a conversation, and cannot reach accounts your own Google account has no access to.

The service does not collect your conversation history, does not use tracking cookies, and this website carries no third-party advertising or analytics scripts.

How we use the data

Solely to fulfil your request and return the answer to Claude. We do not sell data, do not pass it to third parties for their own purposes, and do not use it for ad targeting, profiling or training artificial-intelligence models.

Who can see the data

• You — in your conversation in Claude. The data you requested is, by your own command, passed to Claude (a service of Anthropic), where Anthropic's privacy policy applies.
• Google Cloud — as the hosting provider: the service runs on Google Cloud Run (region europe-west1, Belgium) and encrypted tokens are stored in Google Cloud Firestore (region europe-central2, Warsaw). The data does not leave the European Union.
• The service owner — technical logs show the email address that made a request, the name of the tool and the fact that an account was changed. Reports themselves are not written to logs.

Where and how long data is stored

• Google tokens — encrypted (Fernet / AES-128-CBC with HMAC) in Firestore, until you disconnect the connector or revoke access.
• Meta token — encrypted in Firestore the same way, if you connected Facebook. Removed with the meta_disconnect tool.
• Your AUTO.RIA account number — in Firestore, unencrypted: it is not a secret, just the number that tells the service whose listings to show. Removed with the ria_forget_account tool.
• Reports and statistics — not stored. They pass through the server in memory and go to your conversation; the list of available Google Ads accounts is kept in memory for no longer than 15 minutes, and AUTO.RIA reference data for up to a day, to avoid asking the same question twice and running out of request quota.
• Technical logs — in Google Cloud Logging, 30 days by default.

How to revoke access and delete your data

1. Disconnect the AdData connector in your Claude settings, or revoke access at myaccount.google.com/permissions. After that the service can no longer reach your accounts.
2. To have the stored tokens and records about you deleted, write to iampavelshum@gmail.com. We action such requests within 30 days.

Security

All data travels over HTTPS. Secrets are kept in Google Secret Manager and tokens are encrypted with a separate key. Only email addresses on an allowlist may use the service; any other address is refused even if the Google sign-in itself succeeds.

Your rights

You may request access to your data, its correction or deletion, and you may withdraw your consent at any time — write to iampavelshum@gmail.com. The service is not intended for people under 18.

Changes to this policy

If this policy changes, we will update the date at the top of the page and notify material changes to the address you sign in with.

Contact

Pavlo Shum (private individual, Kyiv, Ukraine), iampavelshum@gmail.com.