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.

Legal notice

Legal notice

Last updated 3 November 2026

Application

Resoneo GCP Compliance

Developer

RESONEO

Organization

RESONEO

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.

Search Console

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

Google Analytics 4

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

Google Ads

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

Merchant Center

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

Account identity

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

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).

Data loaded into BigQuery is used only to produce the reporting and analysis requested by the account owner. It is not used to create a database for any other purpose.

How we share Google user data

We do not sell Google user data, and we do not transfer it to third parties except as follows:

Google Cloud Platform

All data is stored and processed within Google Cloud services (BigQuery, Firestore, Secret Manager, Cloud Run, Cloud Storage, Cloud Logging) operated by Google as our infrastructure provider, under Resoneo-controlled Google Cloud projects.

The account owner

Data extracted from a client's accounts is loaded into the BigQuery project designated for that client and is made available to that client and to the Resoneo staff working on their account.

Legal obligations

We may disclose data where required by applicable law, regulation, legal process or an enforceable governmental request.

Data extracted from one account owner is never combined with, or disclosed to, another account owner.

We do not transfer or disclose Google user data to third parties for targeted, personalised, retargeted, interest-based or user advertising, for sale to data brokers or information resellers, for determining creditworthiness or for lending, or to train generalised artificial intelligence or machine-learning models.

Data retention and deletion

Credentials

OAuth 2.0 tokens and service-account credentials are retained for as long as the corresponding data source remains active in the application. An administrator can revoke a credential — which calls Google's token revocation endpoint, withdrawing the grant at Google, and marks the credential unusable by the pipeline — or delete the data-source account, which additionally erases the stored token and credential payloads from Secret Manager.

Reporting data

Data loaded into BigQuery is retained for as long as the account owner's engagement with Resoneo requires it, and is deleted on the account owner's request or at the end of the engagement, in accordance with the contract between Resoneo and that account owner.

Logs

Cloud Logging entries are retained according to the retention configured on the Google Cloud project's log buckets, after which they are deleted automatically.

Your rights

Any account owner who has granted this application access may at any time:

  • revoke the application's access directly from their Google Account at myaccount.google.com/permissions, which immediately stops all further extraction;
  • request the deletion of the credentials held for their accounts and of the data extracted from them, by writing to data-team@resoneo.com.

Limited Use

This application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements, and to the Google Workspace API User Data and Developer Policy, including its Limited Use requirements.

Specifically, Resoneo does not:

use Google user data for serving targeted, personalised, retargeted, interest-based or user advertising;

sell, license or otherwise transfer Google user data to data brokers, information resellers or any other party for the purpose of resale;

use Google user data for determining creditworthiness or for lending purposes;

allow humans to read Google user data, except (a) with the account owner's affirmative agreement, (b) where necessary for security purposes such as investigating abuse, (c) to comply with applicable law, or (d) where the data has been aggregated and anonymised for internal operations;

use Google Workspace APIs to develop, improve or train generalised or non-personalised artificial intelligence and/or machine-learning models. Google user data obtained through this application is not used to train any AI or ML model.

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

Changes to this policy

We may update this policy to reflect changes to the application or to legal requirements. The date at the top of this page indicates when the policy was last revised. Material changes affecting how Google user data is handled will be communicated to the account owners concerned.

Questions about this notice: data-team@resoneo.com.