Privacy

In short

YAAPI Agent acts on your Google Analytics, Tag Manager, BigQuery, Google Sheets and Google Ads accounts from instructions you write in plain language. To do that, the content of your conversations — including the configuration the agent reads from your accounts — is sent to Anthropic, which produces the replies.

If you work on your own clients' accounts, you remain responsible for what you put into the tool. Do not enter data your agreements do not allow you to share with a subprocessor.

What is collected

  • Account — email, name and picture from your Google profile, used to identify you in the app.
  • Conversations — your messages, the agent's replies, and the files you upload.
  • Technical log — the tool and API calls made on your behalf, their status, duration and token usage.
  • Action log — for every write to your Google accounts, what was changed and where, so you can retrace it. Clone and bulk-patch operations also record the previous values, which lets those be rolled back by hand.
  • Credentials — the OAuth client secret or service account key of your Google Cloud project, the Google tokens you grant through it, and your Anthropic key, all encrypted at rest.

Secrets, tokens and private keys detected in logged content are masked before being written to the database.

Your own Google Cloud project

Signing in uses this application's own Google sign-in and asks for your name, email and picture only. Every call to a Google product is then made with a credential from your own Google Cloud project — an OAuth client or a service account you create there and register in Settings.

The practical consequences: Google counts those calls against your project's API quotas, not against a pool shared with other users; BigQuery work is billed to your project; the calls appear in your project's own API dashboards and audit logs; and removing the credential, here or in the Cloud Console, cuts the agent off entirely. Google Ads is the one exception: its API additionally requires a developer token that belongs to this deployment, and the daily operation budget attached to that token is shared by everyone who uses Google Ads here.

Your client secret or key is used only to send you to Google's consent screen, to renew the tokens you grant there, or to mint tokens for the service account. It is never sent anywhere but to Google, and never shown again once saved.

Google permissions requested

You choose between two grants when you connect each product, and you can switch later from Settings. These permissions are requested through your own project's OAuth client.

Read-only — the default

The agent can audit, report and export, and cannot change anything. For every product except Google Ads this is enforced by Google itself, not by this application: the token carries no write permission, so no instruction hidden in a file you import and no defect in this code can produce a write. Google Ads publishes no read-only permission, so there the same refusal is enforced by this application before anything is sent.

PermissionWhy
Analytics — readAudit your GA4 configuration and pull reports
Tag Manager — readInventory your containers, workspaces and tags
Google Cloud — read-onlyRun SELECT queries on BigQuery. Google publishes no BigQuery-specific read scope, so this is the narrowest one that still allows querying
Sheets — read onlyImport your spreadsheets as a data source
Google AdsReport on campaigns and audit account structure. Google publishes a single Ads permission covering read and write, so on a read-only connection this application refuses every change before it is sent

Read and write

Needed for configuration work. Every write is recorded in the action log with the previous values.

PermissionWhy
Analytics — read, edit, manage usersAudit and configure your GA4 properties
Tag Manager — edit containers and versionsCreate and modify tags, triggers and variables
Tag Manager — publishPublish a version, only when you explicitly ask for it
BigQueryQuery and load your datasets
Sheets — read onlyImport your spreadsheets as a data source
Google AdsAudit and change campaigns, budgets and account structure, each change requiring your explicit approval

You can revoke this access at any time from your Google account, independently of this application.

Retention

  • Messages and conversations: 30 days
  • Tool calls: 14 days
  • API calls: 30 days
  • Errors: 14 days
  • Token usage: 90 days
  • Action log: 180 days

Credentials are kept until you revoke them. Generated files expire on their own.

Security

  • Credentials encrypted at rest with AES-256-GCM, with key rotation supported.
  • Message content is stored in clear text, so incidents stay diagnosable.
  • Session held in an encrypted cookie, sent over HTTPS only.
  • Every record is tied to its account: no cross-account access.
  • The agent's outbound calls cannot reach internal addresses.

Subprocessors

RecipientRoleData involved
AnthropicLanguage modelConversation content and the results of calls made for you
GoogleAnalytics, Tag Manager, BigQuery, Sheets and Google Ads APIsRequests issued on your behalf under the permissions you granted
VercelHostingTechnical logs, cookieless audience measurement
NeonDatabaseAll of the above, hosted in the European Union

Cookies

One cookie is set: your session, which is strictly necessary for the app to work. There is no advertising cookie and no third-party tracker — the audience measurement in use sets nothing. No consent banner is therefore required.

Your rights

  • Access and portability — the “Export my data” button in Settings produces a JSON file of everything held about you.
  • Erasure — “Delete my account” in Settings immediately and permanently removes all of your data.
  • Withdrawing consent — remove your project credential from Settings, revoke the grant from your Google account, or delete the OAuth client or key in your Google Cloud project; or remove your Anthropic key from Settings.

Questions: antoine.hervillard@yaapi.net