Google Ads — API privacy notice

Last updated: July 28, 2026

This page explains how OpenPromo Social handles Google Ads–related data in line with the Google Ads API OAuth requirements and applicable Google policies. It supplements the general Privacy Policy. For the Google Ads feature, this notice takes precedence if anything conflicts.

1. Who this applies to

OpenPromo Social uses OAuth 2.0 and the Google Ads API for sign-in, listing accessible Ads customer accounts, viewing campaigns, and reading performance reports. Data processing described here applies only when you use routes such as /google-ads/login and /google-ads/manage.

2. Google services and OAuth scopes

• https://www.googleapis.com/auth/adwords — access your Google Ads accounts through the Google Ads API (list accessible customers, list campaigns, and read campaign performance metrics).
• https://www.googleapis.com/auth/userinfo.profile — read basic Google profile (display name, picture) to show which Google account is signed in.
• https://www.googleapis.com/auth/userinfo.email — read your Google account email for the same identity display purpose.

We do not use these permissions to access other users’ Ads accounts or resources you have not consented to. They are used solely to provide the Google Ads demo features described on this page.

3. Data we process

• OAuth access token, refresh token (if provided), expiry, and granted scopes.
• Accessible customer resource names / customer IDs returned by the Google Ads API for accounts you can access.
• Campaign metadata (name, status, channel type, bidding strategy, budget) and performance metrics (impressions, clicks, CTR, cost, conversions) for date ranges you select in the app.
• Basic Google account profile fields used on the consent success screen (name, email, picture).

4. Storage and security

By default, tokens are kept in this browser’s localStorage so you can use the Google Ads flows without relying on a full server-side session for token persistence. Deployments that require centralized control should use secure server-side storage and least-privilege sessions. Use HTTPS in production. API calls that need a developer token use a server-side configured token; it is not exposed to the browser.

5. Your control and revocation

• Clear local tokens from this app at any time, and revoke the app in Google Account → Third-party access.
• Google Ads account settings and campaigns remain managed in Google Ads.

6. Consistency with Google terms

We comply with and surface the Google APIs Terms of Service and Google Ads API usage policies. API call volume and features are subject to your Google Ads API access level and developer token status.

7. Contact

For questions about this channel, use Contact and mention "Google Ads API / privacy-google-ads". You may also use the same contact information as in the general Privacy Policy if it matches.