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.

Privacy policy

How we store and protect Google user data

Last updated 3 November 2026

DataStorage locationProtection

OAuth 2.0 refresh and access tokens, service-account credentials

Google Secret Manager

Encrypted at rest by Google; access restricted to the application's service accounts via IAM. Never written to source control, never returned to the browser, never written to logs.

Data-source configuration and account metadata (account identifiers, display names, the Google email that granted consent, token status, audit fields)

Firestore

Encrypted at rest; access restricted by IAM to the admin backend service account.

Extracted reporting data

BigQuery (Resoneo or client-designated project)

Encrypted at rest; access restricted by IAM to the relevant Resoneo staff and the account owner.

Intermediate extraction files (Parquet)

Ephemeral Cloud Run container storage / Cloud Storage

Deleted immediately after the load into BigQuery completes.

Application logs

Google Cloud Logging

Structured logs record operational events and the acting staff member's email address; they contain no credentials or token values.

Additional safeguards

All traffic to and from the application and the Google APIs uses TLS.

Access to the admin interface requires Google sign-in restricted to the @resoneo.com domain, is verified server-side against Firebase Authentication, and is further restricted by a role and permission model. Only administrators may delete credentials.

The OAuth 2.0 consent flow uses an HMAC-signed state parameter to protect against cross-site request forgery.

Infrastructure is defined as code and deployed through a reviewed CI/CD pipeline; production credentials are held in the CI/CD secret store.

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.

Where the GDPR applies, data subjects also have the rights of access, rectification, erasure, restriction, portability and objection, and the right to lodge a complaint with a supervisory authority (in France, the CNIL). Requests should be sent to data-team@resoneo.com and we respond within one month.

Children

The application is a professional tool and is not directed at, nor intended for use by, children.

International transfers

Data is processed in Google Cloud regions selected by Resoneo. Where data is transferred outside the European Economic Area, the transfer is covered by the data protection terms and Standard Contractual Clauses that form part of our agreement with Google Cloud.

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.

Contact

Questions about this policy or about the handling of data by the application: Resoneo, data-team@resoneo.com.