GOOGLE ADS DATA ACCESS

What EchoVerse AI does and why it requests Google Ads data.

EchoVerse AI connects to Google Ads only after a signed-in customer explicitly chooses to connect Google Ads and completes Google OAuth. The authorization is used to provide the Google advertising, video, reporting, and approved automation features the customer requests.

WHY ACCESS IS NEEDED

Google Ads data supports specific customer-facing product functions.

Authorized account discovery

Discover Google Ads client and manager accounts available to the Google user who completed OAuth, then synchronize eligible customer-serving accounts into that EchoVerse AI workspace.

Campaign management

Support eligible Search and Demand Gen workflows, campaign configuration, budgets, targeting, ad groups, ads, creative assets, scheduling, pause/resume, and related provider operations.

Video advertising assets

Support approved video workflows, including eligible YouTube video-asset upload through the Google Ads API and provider processing-state tracking.

Reporting

Retrieve campaign state and performance metrics needed for customer dashboards, monitoring, operational reporting, and optimization decisions.

Scheduled operations

Use offline authorization for customer-approved background work such as scheduled publishing, account synchronization, status checks, and reporting when the customer is not actively in the browser.

Integration reliability

Maintain provider connection status, identify reconnect requirements, prevent unsupported publication, and reconcile provider-side state with EchoVerse AI.

WHAT DATA MAY BE PROCESSED

Only data needed for the authorized Google Ads connection and requested features.

  • Authorized Google Ads customer and manager account identifiers and account hierarchy.
  • Campaign, ad group, targeting, ad, creative, and advertising-asset configuration used by supported workflows.
  • Video-asset identifiers, metadata, and provider processing state for supported video advertising workflows.
  • Campaign status and performance metrics such as impressions, clicks, spend, conversions, and related reporting fields when available.
  • OAuth authorization and connection metadata required to securely maintain or revoke the integration.
CUSTOMER CONTROL & PRIVACY

What EchoVerse AI does not do.

No Google password collection

EchoVerse AI does not request or store the customer’s Google password. Google handles authentication and consent.

No arbitrary account substitution

Provider account identifiers are synchronized from authorized Google access instead of trusting arbitrary account IDs entered in the browser.

No sale of Google user data

Google user data is used to provide requested EchoVerse AI functionality and is not sold to advertisers or unrelated third parties.

No unrelated Google access

The Google Ads connection is not permission to access unrelated Google products or accounts outside the authorization and supported product functionality.

Workspace-scoped access

Connected provider resources are associated with the customer workspace and checked against server-side permissions before use.

Revocable authorization

Customers can disconnect the Google Ads integration in EchoVerse AI and can also revoke access through their Google Account permissions.

SECURITY & RETENTION

OAuth credentials are handled by the private application layer.

Google OAuth tokens and provider credentials are not exposed in customer-facing JavaScript or public WordPress content. EchoVerse AI uses the authorization while the connection is active and applies workspace permissions and provider-readiness checks before supported operations are attempted.

YOUR AUTHORIZATION, YOUR CONTROL

Connect Google Ads only when you are ready.

Share with