Start free
Google API disclosure

LEADARO Google API services disclosure

Effective date: 11 July 2026

This disclosure describes how LEADARO uses information received from Google APIs. It is published separately from the general Privacy Policy and Terms of Service so that the scope-by-scope detail is easy for Google reviewers, customers and security teams to find.

LEADARO's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

We apply this commitment to every Google API surface the platform uses, regardless of whether the surface is currently in beta, public test, or general availability.

LEADARO requests the minimum set of Google OAuth scopes needed to deliver the operator-requested features. A workspace owner or admin grants the Google Ads, Analytics and Tag Manager scopes in a single Google consent when they connect Google from the Integrations settings page, and the YouTube scope in a separate consent when they connect a YouTube channel. The scopes are requested with offline access so the platform can refresh tokens without re-prompting the user. The four scopes are:

  • https://www.googleapis.com/auth/adwords — read and manage Google Ads accounts on behalf of the authorizing user, for Google Ads lead form import, campaign performance reporting, and conversion upload.
  • https://www.googleapis.com/auth/analytics.readonly — read-only access to Google Analytics 4 account summaries and data streams, used only to list the user's GA4 properties so they can pick the Measurement ID LEADARO should use for measurement.
  • https://www.googleapis.com/auth/tagmanager.readonly — read-only access to Google Tag Manager accounts and containers, used only to list the user's GTM containers so they can pick the container ID LEADARO should use.
  • https://www.googleapis.com/auth/youtube.upload — upload to the authorizing user's YouTube channel the videos they explicitly approve in the platform. Requested separately, when the operator connects a YouTube channel (not part of the Google Ads / Analytics / GTM consent).

We do not request, store or process any other Google scope. If additional scopes become necessary in the future (for example, Google Calendar for booking), they will be added to this disclosure before the corresponding feature ships, and the authorizing user will see the new scope on the Google OAuth consent screen.

Under the scopes above, LEADARO performs the following operations, always tied to the workspace that authorized the connection (each operation notes the scope it relies on):

  • Lead form submission import. Read lead_form_submission_data from connected campaigns and create or update LEADARO leads with source google_ads_lead_form. Imports are deduplicated by Google lead ID and payload hash.
  • Campaign performance read. Read campaign-level metrics (impressions, clicks, cost, conversions, conversion value) to power the operator-facing reporting views inside the workspace.
  • Conversion upload. When an operator marks a LEADARO lead as converted (e.g. booked, paid, etc.), upload a conversion event back to Google Ads so the platform can optimize bidding against real downstream outcomes.
  • Account listing + customer selection. List the Google Ads customer accounts accessible to the authorizing user, so the workspace can persist the selected customer ID for subsequent imports.
  • Campaign management at operator request. Read or update campaign state only when an operator explicitly triggers the action inside the workspace UI.
  • GA4 property listing (analytics.readonly). List the authorizing user's Google Analytics 4 account summaries and data streams solely to populate a picker so the operator can select which GA4 Measurement ID LEADARO should use. We read property and data-stream metadata only; we do not read analytics report data.
  • GTM container listing (tagmanager.readonly). List the authorizing user's Google Tag Manager accounts and containers solely to populate a picker so the operator can select which GTM container ID LEADARO should use. We read container metadata only; we do not read or modify tags, triggers, or variables.
  • YouTube video publishing (youtube.upload). Upload to the connected YouTube channel (videos.insert, resumable protocol) the videos explicitly approved in the platform, together with their title and description, and check processing state (videos.list) until publication is confirmed. Every upload requires a human approval; we do not read, modify, or delete any other content on the channel.
  • We do not transfer Google API data to third parties except as needed to provide and improve the user-facing features the operator has requested, and only to the subprocessors listed in our Privacy Policy.
  • We do not use Google API data for serving advertisements of our own.
  • We do not allow humans to read Google API data except (a) with the operator's prior explicit consent, (b) to comply with applicable law, (c) for security investigations, or (d) when the data has been aggregated and anonymized.
  • We do not use Google API data to develop, improve, or train generalized machine learning or AI models. LEADARO's AI Brain features run on third-party LLM inference services (Anthropic, OpenAI) under DPAs that prohibit using customer data for model training; Google Ads data sent into AI prompts (where applicable to operator-configured automations) is governed by the same prohibition.
  • Refresh tokens are encrypted with AES-256-GCM before being stored in the per-workspace integration record. The per-environment encryption key is held in a separate secret manager.
  • Imported lead form data is stored as part of the workspace's lead records in our EU database (Supabase, Ireland). Retention follows the workspace's own retention preferences (see Privacy Policy).
  • Campaign metrics are queried just-in-time for reporting views and cached for performance with a maximum TTL of 24 hours; the cache is invalidated on disconnect.
  • Conversion uploads are sent directly from the LEADARO server tier to the Google Ads API; conversion payloads are stored in audit logs (90-day retention) and not retained long-term.

An authorizing user can revoke LEADARO's access to their Google Ads account at any time, in two ways:

  • From within the LEADARO workspace — go to Settings → Integrations → Google Ads → Disconnect. This clears the stored refresh token and configuration metadata.
  • From the Google Account permissions page — myaccount.google.com/permissions. Removing LEADARO here invalidates the refresh token; on the next attempted refresh, the platform will mark the integration as needs_reauth and stop calling the Google Ads API for that workspace.

Questions about how LEADARO uses Google API data, or requests for additional detail for Google's review process, should be sent to office@thebrandoers.com. We acknowledge within 5 business days.