PubPilots

Privacy policy

How PubPilots uses Google data

16 October 2026

PubPilots is a dashboard for a publishing company. It shows whether Google Ads spend is paid back by Google Ad Manager revenue on that company's websites. This policy explains what we access from Google, what we do with it, and how you can take the access away.

PubPilots' use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

Google Ads

When a company admin clicks Connect Google Ads, Google asks that person to allow PubPilots to see, edit, create, and delete their Google Ads accounts and data. That is the permission Google shows for the Ads API. We use it only for the work below.

  • We store the Google account email and an encrypted refresh token so later syncs can run without another sign-in.
  • We list the Ads accounts that login can see: name, account id, currency, and whether the account is active or suspended.
  • We read campaign cost, clicks, conversions, budget, and target CPA for the accounts a website uses.
  • If a user saves a budget or a target CPA in PubPilots, we send that update to the matching Google Ads campaign.

We do not create campaigns, edit ads, change keywords, or change targeting.

Google Ad Manager

Ad Manager does not use that Google sign-in. The company adds PubPilots' service account as a user on a network and gives us the network code. We read revenue reports for websites on that network. We can also list and create the named ad units a website asks for.

Google Analytics

A website can store an optional GA4 property id. The scheduled cost and revenue sync does not pull Analytics reports. A property is kept so the company can see which property belongs to the site.

Account data we store ourselves

PubPilots accounts have a name, email, and password for this product. Passwords are stored as a hash. A password reset email is sent only when someone asks for one.

How the data is used

Figures are stored for the company that connected them and shown to people in that company, and to PubPilots operators who run the service. We use them to show cost, revenue, profit, and ROAS, and to keep a history of sync runs so a failed pull can be fixed.

We do not sell Google user data. We do not use it to show ads. We do not share one company's Ads or Ad Manager data with another company. We do not use it to decide creditworthiness or for employment decisions.

How long we keep it

We keep the connection and the stored reports while the company uses PubPilots. Removing a Google Ads login in PubPilots deletes that saved token. You can also revoke PubPilots from your Google Account permissions. After a revoke, the next sync cannot read Ads until someone connects again.

Contact

Questions about this policy: adesh@thebesads.com. The same address is the user support email on the Google consent screen. See also the terms of service.