1. Application and intended user
Ads Automation Manager is an internal application developed and operated by Yang Qiang, an individual developer and advertiser. It is intended only for the developer's own use and is not offered to clients, third parties, or the public.
2. Google user data accessed
After the user grants OAuth 2.0 authorization, the application may access Google Ads data for accounts owned by or explicitly authorized to the developer. Depending on the enabled workflow, this may include:
- Google Ads customer and manager-account identifiers and access status;
- campaigns, ad groups, advertisements, keywords, bids, budgets, targeting settings, and delivery status;
- aggregated advertising performance metrics such as impressions, clicks, cost, and conversions; and
- Google Ads API request results and operational error information required for audit logging.
The application does not request access to Gmail, Google Drive, Google Contacts, or unrelated Google Account data.
3. How Google user data is used
Google Ads data is used only to provide the application's internal advertising-management functions, including creating eligible customer accounts, building and managing Search campaigns, producing internal performance reports, generating optimization recommendations, validating proposed changes, applying eligible changes, and maintaining an audit trail.
4. AI-assisted processing and data sharing
Selected non-sensitive campaign metadata and aggregated performance metrics may be sent to configured AI API providers, including OpenAI, solely to generate advertising drafts or optimization recommendations for the authorized accounts. These providers process the data as service providers for the requested function.
Google OAuth credentials, developer tokens, client secrets, refresh tokens, private keys, passwords, payment information, and personally identifiable information are not sent to AI providers. Google Ads data is not sold, licensed, or shared with advertisers, data brokers, or unauthorized parties, and it is not used to train a generalized advertising model.
5. Storage, security, and retention
Data is transmitted over encrypted connections. Credentials are stored outside the public source repository and are restricted to the application owner. The application uses least-privilege access, predefined action rules, budget and bid limits, change thresholds, and audit logging.
Google Ads data and operational logs are retained only for as long as needed for the internal management, reporting, security, and troubleshooting purposes described in this policy. Data and stored authorization credentials are deleted when they are no longer required or when access is revoked, subject to any limited retention required for security or legal obligations.
6. User control and deletion
The user can revoke the application's Google Account access at any time from the Google Account third-party connections page. The user may also request deletion of application data and stored authorization credentials by contacting the developer at ysq312014834@gmail.com.
7. Google API Services User Data Policy
The application's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
8. Policy changes and contact
This policy may be updated when the application's data practices or functionality change. The effective date above will be updated when material changes are published. Questions about this policy can be sent to ysq312014834@gmail.com.