Privacy Policy
This Privacy Policy describes how ManagementGA (the "Application", "we", "us") accesses, uses, stores, and shares information, including Google user data obtained through the Google Ads API. ManagementGA is an internal tool operated by our in-house marketing team at management-ga.com. It is not offered to the public and has no external users or clients.
- What ManagementGA does
- Google user data we access
- How we use the data
- How we store the data
- How we share the data
- Data retention and deletion
- Revoking access
- Google API Services User Data Policy
- Security
- Other information we collect
- Changes to this policy
- Contact
1. What ManagementGA does
ManagementGA runs once each morning. It reads the previous day's campaign performance from the Google Ads accounts under our manager account (MCC), writes those figures to an internal shared spreadsheet, and emails a digest to our account managers. It flags campaigns that have spent more than 90% of their daily budget. If a campaign has already reached its cap, a member of our team can pause that campaign from the tool after explicitly confirming the action. The Application does not pause, edit, or create anything automatically.
2. Google user data we access
The Application authenticates to Google using OAuth 2.0 and requests a single scope,
https://www.googleapis.com/auth/adwords, which allows it to manage Google Ads campaigns on
behalf of the Google account that authorized it. That account belongs to a member of our team and has
access to our Google Ads manager account.
Using that authorization, the Application accesses only the following data through the Google Ads API:
| Data | API service used |
|---|---|
| The list of Google Ads customer accounts our manager account can access (customer IDs and descriptive names). | CustomerService.ListAccessibleCustomers |
| Campaign settings: campaign ID, name, status, advertising channel type, and daily budget. | GoogleAdsService.Search |
| Campaign performance metrics for the previous day: impressions, clicks, cost, and conversions. | GoogleAdsService.Search |
| Campaign status changes (set to Paused) for a specific campaign, only after a team member confirms the action. | CampaignService.MutateCampaigns |
The Application does not access:
- Audience lists, customer match data, or any personal information about people who see or click our ads.
- Billing, payment, or invoice information.
- Ad creatives, keywords, or search terms beyond the campaign-level fields listed above.
- Gmail, Google Drive, Google Contacts, Calendar, or any other Google service. The Application requests no scope other than the Google Ads scope.
The Application uses the official Google Ads API client library for Python. It does not use browser automation, scraping, or any unofficial method of reading Google Ads data.
3. How we use the data
We use the Google Ads data described above solely to:
- Produce a daily record of the previous day's impressions, clicks, cost, conversions, and remaining daily budget for each campaign.
- Write that record to an internal shared spreadsheet used by our marketing team.
- Send a daily digest email summarizing that record to our account managers.
- Identify campaigns that have spent more than 90% of their daily budget so a team member can review them.
- Pause a campaign that has reached its daily budget cap, when and only when a team member confirms that action in the tool.
We do not use this data for any other purpose. In particular, we do not use it to:
- Serve advertisements or build advertising profiles.
- Train or improve machine-learning or artificial-intelligence models.
- Sell, license, or otherwise monetize the data.
- Determine creditworthiness or for lending purposes.
4. How we store the data
OAuth credentials
The OAuth refresh token issued by Google is stored on infrastructure controlled by our team, in a configuration store with restricted access. It is used only to obtain short-lived access tokens for the Google Ads API calls described in this policy. It is never included in the spreadsheet, digest emails, logs, or any other output.
Campaign data
The daily campaign metrics and settings pulled by the Application are written to an internal shared spreadsheet accessible only to members of our marketing team, and are included in the daily digest email sent to our account managers. The Application may also keep short-lived operational logs (for example, whether the daily run succeeded) on our infrastructure; these logs do not contain OAuth tokens.
We do not maintain a separate database of Google Ads data, and no data is stored on servers operated by third parties other than the spreadsheet and email providers our team already uses for internal work.
6. Data retention and deletion
- OAuth refresh token: retained until access is revoked (see section 7) or the team member who authorized the Application leaves the team, at which point it is deleted from our configuration store.
- Campaign metrics in the spreadsheet: retained as part of our team's internal historical performance record for as long as the team needs it for reporting. Rows can be deleted by any team member with edit access to the spreadsheet.
- Digest emails: subject to our organization's normal email retention practices.
- Operational logs: retained for a short period for troubleshooting and then discarded.
Requests to delete data held by the Application can be sent to [email protected].
7. Revoking access
The Google account holder who authorized the Application can revoke its access at any time from the Third-party apps & services page of their Google Account. Once access is revoked, the Application can no longer call the Google Ads API on that account's behalf, and we delete the stored refresh token.
8. Google API Services User Data Policy
ManagementGA's use and transfer of information received from Google APIs to any other application adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, we only use Google user data to provide the internal reporting and budget-monitoring functions described in this policy, we do not transfer it to third parties except as described in section 5, we do not use it for advertising, and we do not allow humans to read it except as needed for the functions described here, for security purposes, to comply with law, or with the account holder's consent.
Our use of the Google Ads API is also subject to the Google Ads API Terms and Conditions and the Google Ads API Policies.
9. Security
We take reasonable technical and organizational measures to protect the data the Application handles. OAuth credentials are stored with restricted access and are never exposed in output. API calls are made over HTTPS. Access to the spreadsheet, digest emails, and the infrastructure that runs the Application is limited to members of our marketing team. No method of storage or transmission is completely secure, and we cannot guarantee absolute security.
10. Other information we collect
This website (management-ga.com) is a static informational site. It does not use cookies, analytics, or tracking scripts, and it does not collect personal information from visitors. If you email us, we will receive the information you choose to include and will use it only to respond to you.
11. Changes to this policy
If we change how the Application accesses, uses, stores, or shares Google user data, we will update this policy and revise the "Last updated" date above before the change takes effect, and we will notify the team members who use the Application.
12. Contact
Questions about this Privacy Policy or our handling of Google Ads data can be sent to [email protected].