Privacy notice

1. Data the tools can access

Access is limited by the permissions of the authorised Google identity, the selected account or property, and the applicable API access level. Depending on the requested operation, returned information can include:

• Google Ads account and configuration data: account identifiers and names, manager relationships, account currency and environment, campaign and ad-group metadata, ad copy, destination URLs, keywords, campaign status, budget settings and conversion-action configuration.
• Aggregate advertising information: impressions, clicks, advertising costs and conversion counts, where available to the permitted account.
• Keyword-planning inputs and estimates: selected keywords, locations and language, together with historical search-volume, competition or cost estimates when the API returns them. A request path exists, but successful production planning access is not yet established.
• Google Analytics 4 information: property and web-stream metadata, measurement identifiers, key-event settings and aggregate event-report results used for measurement diagnostics.
• Diagnostic and audit context: timestamps, request identifiers, returned error categories, configuration snapshots, proposed actions and recorded execution outcomes.

The current connected workflows use test accounts and a dedicated test property. The website itself does not connect to Google accounts or request these records from visitors.

2. Why the operator uses this information

The current uses are account-access checks, inspection of campaign configuration, test setup, analysis of aggregate reports, diagnosis of measurement issues, and preservation of evidence about requested or performed operations. Keyword estimates, when permitted and available, support research rather than a promise of advertising results.

Selected test changes are supported. The current Google Ads test workflow blocks campaign activation and budget increases. Access to account information does not itself authorise advertising expenditure.

3. Authentication and local storage

The current API integrations use short-lived Google-issued access tokens obtained through a locally authenticated Google Cloud CLI and permitted service-account impersonation. The CLI manages its own sign-in credentials. These static information pages do not collect credentials or tokens.

Selected API outputs may be saved as local export files, campaign snapshots and diagnostic or action-history records, including a local SQLite database. Storage on the operator's device is distinct from data retained by Google or other providers. This notice does not claim that storage has received an independent security certification.

4. Google, AI assistance and website hosting

Requests to Google's APIs send the identifiers, queries or permitted configuration changes needed for the requested operation. Google's own services and retention practices continue to apply to data held by Google.

The operator may provide selected API results or diagnostic context to an authorised AI assistant for analysis, troubleshooting and development support. That involves processing outside the local device. The scope of that use must be authorised; the assistant provider's processing and retention settings are separate from local-file handling. This is not a promise that all information remains local.

Cloudflare hosts these public information pages. Website requests pass through its hosting infrastructure and may involve ordinary network and request information, such as IP addresses. Cloudflare manages its own hosting-log retention under its applicable service and privacy terms.

These pages include no analytics tags, advertising tags, contact forms or third-party scripts. They contain no Google Ads or Analytics account records and make no Google API calls.

5. Retention and deletion

The current Google integration has no automatic cleanup schedule for its local exports, snapshots or audit history. Those records remain until the operator removes them. A fixed retention period and deletion turnaround have not yet been adopted for these tools.

To request deletion of locally held records, email re458minor@gmail.com with the relevant account or property identifier and the records concerned. Do not include passwords, tokens or keys. The operator needs to identify the applicable records and confirm what has been removed; a request alone does not demonstrate completed deletion.

Deleting local files does not automatically remove records retained by Google, the AI-assistant provider, hosting infrastructure or backups. Any remaining provider or backup limitations need to be identified when handling the request.

6. Withdrawing access

An account administrator can remove the relevant identity's access through Google Ads account permissions or Google Analytics property access management. The operator can also stop using the integration and remove or revoke the applicable Google credentials or impersonation permissions.

Permission changes may prevent further API access, but do not automatically delete records already exported. Contact re458minor@gmail.com about retained copies or uncertainty over which permission to remove.

7. Data-use restrictions

Acquisition OS's use and transfer of information received from Google APIs is governed by the Google API Services User Data Policy, including its Limited Use requirements where applicable.

• Use Google account data only for the specifically authorised account-management, research and diagnostic purposes described here.
• Do not sell Google account data or use it for unrelated marketing.
• Limit any transfer to an AI assistant or another service to the data needed for an authorised task.
• Review changes in data access, purpose, sharing or retention before expanding the integration and update this notice to describe the changed practice.

Contact

App support, developer contact and data-handling questions: re458minor@gmail.com.