The application is not a consumer product. It is not offered to the general public, it displays no advertising, and it has no end-user accounts other than those of Resoneo staff and the account owners who explicitly authorise access.

Scope

Google user data we access

The application requests access to Google user data exclusively through Google's OAuth 2.0 consent flow or, where the account owner prefers, through a Google Cloud service account that the account owner grants access to.

Access path

OAuth 2.0

Google consent flow

Access path

Service account

Granted by the account owner

Search Console

https://www.googleapis.com/auth/webmasters.readonly

Read properties and their search-performance reports: queries, pages, countries, devices, impressions, clicks, CTR, position.

Google Analytics 4

https://www.googleapis.com/auth/analytics.readonly

Read property lists and aggregated reporting data: sessions, users, events, traffic sources, conversions.

Google Ads

https://www.googleapis.com/auth/adwords

Read account structure and performance reports: campaigns, ad groups, ads, keywords, products, impressions, clicks, cost, conversions.

Merchant Center

https://www.googleapis.com/auth/content

Read account information and product or feed reporting data. This scope has no read-only variant; the application performs read operations only.

Account identity

openid, email

Identify the Google account that granted the authorisation, so the credential can be labelled and managed in the admin interface.

Resoneo staff sign-in

Google Sign-In

Firebase Authentication authenticates Resoneo staff in the admin interface. For those users we process the email address and the Google account identifier contained in the sign-in token.

Also connected

Microsoft Advertising

Not a Google service. Data obtained from it is handled under the same terms set out in this policy.

Data we do not access

  • Gmail
  • Google Drive
  • Google Calendar
  • Google Contacts
  • Google Photos
  • Other Workspace content

The application does not access these, and does not request scopes for them. The reporting data it retrieves is business performance data about websites, advertising accounts and product feeds. It is aggregated by the Google APIs and is not intended to identify individual site visitors or end consumers.

How we use Google user data

Google user data is used solely to provide the functionality that the account owner has requested.

  1. 1

    Listing the Search Console properties, Analytics properties, Google Ads customer accounts and Merchant Center accounts that the authorising Google account can access, so that a Resoneo administrator can select which of them to include in the pipeline.

  2. 2

    Extracting the selected reporting data on a recurring schedule.

  3. 3

    Loading that data into the BigQuery dataset belonging to the corresponding client or to Resoneo, where it is used for reporting, dashboards, analysis and consulting deliverables provided to that same account owner.

  4. 4

    Refreshing and validating OAuth 2.0 access tokens so that scheduled extractions continue to run.

  5. 5

    Authenticating and authorising Resoneo staff in the admin interface, and recording which staff member created, modified or revoked a credential (audit logging).

We do not use Google user data for any other purpose.