Privacy policy
Draft for review - not legal advice. This page has not been approved yet. Text in [square brackets] must be filled in before AdOps is used by anyone other than its developers.
Draft of 23 October 2026.
Who we are
AdOps is an internal tool run by [agency legal name] ("we", "us") for its own staff. It lets staff connect their AI assistant to the Google Ads accounts they already have access to, read-only. AdOps is served at adops.dawid.digital. For any privacy question, contact [privacy contact email].
In short
- We keep as little as we can: who may use AdOps, your encrypted Google sign-in, the account notes people write, and a log of what each person did.
- We don't keep the Google Ads data your assistant reads. It passes through AdOps to your assistant. We record the question that was asked and how many rows came back, not the answers.
- We never sell your data, use it for advertising, or use it to train AI models.
What we collect, why, and for how long
| Information | What it includes | Why | How long |
|---|---|---|---|
| Your AdOps user record | Email address, Google account ID (a permanent number Google gives every account), display name, role, status, daily request limit, who added you and when. | To decide who may use AdOps and with what limits. | While you have access. If you're removed, the record is kept (marked disabled) so the audit log still makes sense. |
| Your Google sign-in | The Google access and refresh tokens created when you connect an assistant, encrypted with a key held in Google Secret Manager. | To send read-only Google Ads requests on your behalf. They are never given to your assistant. | Until they expire, you remove AdOps's access at Google, or an admin disables you (AdOps then deletes them and asks Google to revoke them). Expired entries are deleted automatically. |
| Connected assistants | For each assistant you connect: its registration (app name and sign-in return address), the AdOps tokens issued to it (encrypted), and a record linking that connection to your email address and Google account ID. | To keep your assistant signed in, and to cut off its access when needed. | AdOps access tokens last up to 1 hour. A connection stays valid while it's used at least every 90 days (7 days in total while AdOps is in Google's testing stage). Expired tokens are deleted automatically. When an admin disables you, the records linking connections to you are deleted too. |
| Account notes | Notes you or your assistant add about a Google Ads account: the text, category, source, your email address as author, dates, and every earlier version. | Shared memory of decisions and context for each account. | As long as AdOps is in use. Notes are archived rather than deleted, and earlier versions are kept as history. |
| Audit log | One record per action: the time; what happened (for example a tool call, a Google Ads query, a sign-in, a note change or an admin action); the outcome and any error message; your email address and Google account ID; the assistant you used; your IP address and browser or app details; request IDs; the tool's inputs with secrets removed; Google Ads account IDs; the text of Google Ads queries; how many rows came back; and the AdOps version. | Security, accountability, troubleshooting and daily limits. | 400 days in the dedicated audit log in Google Cloud Logging, then deleted. The copy in the AdOps database is not yet deleted automatically. |
| Cookies | A signed sign-in cookie for the My status and Admin pages (your email address, Google account ID and a security code); a sign-in cookie used only while you sign in; and, when you connect an assistant, short-lived security cookies plus one that remembers which assistants you allowed. | To keep you signed in and protect forms from forgery. They are all strictly necessary. There are no analytics or advertising cookies and no third-party scripts. | 8 hours for the website sign-in, 10 minutes while signing in, and up to 1 year for remembered assistant approvals. |
| Server logs | Google Cloud's standard request logs: time, page or endpoint requested, IP address, browser or app details and response status. | To run and troubleshoot the service. | 30 days (Google Cloud's default). |
What we don't collect
- The Google Ads results your assistant reads (campaigns, costs, conversions and so on).
- Your Google password. You only ever type it on Google's own pages.
- Your conversations with your assistant.
Signing in to the AdOps website (rather than connecting an assistant) only confirms who you are. AdOps doesn't keep the Google tokens from that sign-in.
How we use data from Google
AdOps's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- What we ask Google for: your basic profile (name, email address and Google account ID), to know who you are; and access to Google Ads, to run read-only reports when your assistant asks for them.
- How we use it: only to provide AdOps to you. Google Ads data goes only to the assistant you connected, at your request or your assistant's.
- What we never do: sell it, use it for advertising, use it to train AI models, or let people read it, except with your agreement, for security (such as investigating misuse) or where the law requires it.
- Read-only: Google's only Google Ads permission also allows changes, but AdOps only ever reads. Any other kind of Google Ads request is blocked inside AdOps before it is sent, and the attempt is logged.
Your AI assistant
When you connect Claude or Perplexity, everything AdOps returns (Google Ads results and account notes) is sent to that assistant and handled under its provider's own privacy terms: Anthropic for Claude, Perplexity for Perplexity. Use only the assistants and plans the agency has approved for client data.
Who can see your information
- AdOps admins can see the user list, the audit log, account notes and daily usage.
- Other AdOps users can see the notes for accounts they can access in Google Ads, and audit records about those accounts. That means a colleague with access to the same client account can see that you queried it, and what you asked.
- Google Cloud hosts AdOps and processes this data on our behalf.
- We don't share it with anyone else unless the law requires it.
Where it's stored and how it's protected
AdOps runs on Google Cloud. The service and its database are in the europe-west1 region (Belgium, EU). Connections use HTTPS, Google Cloud encrypts stored data, and AdOps encrypts your Google sign-in tokens a second time with its own key. Only people on the AdOps list can sign in, each person is tied to their permanent Google account ID, and removing someone takes effect on their very next request.
Your choices and rights
- You can stop AdOps using your Google account at any time at Google Account → Security → Your connections to third-party apps & services.
- You can ask us what we hold about you, and ask us to correct or delete it, at [privacy contact email]. We may keep audit records for their full retention period where we need them for security or accountability and the law allows it.
- You can complain to the data protection authority where you live or work.
Changes
We'll update this page when what AdOps stores changes, and tell staff about significant changes.