Home

Asso · Google connection

What Asso does with your Google account.

This page describes the access actually requested, what is read, what may be written, what is forbidden, and how to withdraw access in under a minute.

What Asso is
A continuity layer. Asso keeps the useful context, the decisions, the material and the next step of a case connected, so you do not rebuild the briefing every time you come back. The Asso page explains the idea in plain language.
Why a Google connection
Because the material of a real case already lives in Drive, in Gmail and in Calendar. Without access to those sources, Asso cannot retrieve a document, re-read a decision or recall a deadline: it would ask you for the whole briefing again.
Who grants access
You do, from the Google consent screen, for your own account. Access is obtained no other way. It is not purchased, not inherited from another service and not imported from an existing session.
Three scopes, no more
Drive, Gmail and Calendar. No other Google service is requested: no Contacts, no Photos, no Chat, no location data, no browsing or search history.

Google Drive

Read what is authorized, write reversibly.

The requested scope is Google Drive (auth/drive). In practice, Asso can search for a file, read its metadata and its content, and follow the folder it belongs to, within the limits of what your own account can already reach.

  • Reading the documents and folders your account has access to, so the right piece comes back at the right moment.
  • Writing only when the active authority allows it: creating a document, updating content, filing a file, moving an item to the trash.
  • Every write operation must stay reversible. Permanent deletion that bypasses the trash is forbidden.
  • Asso claims no global control of your Drive. It acts on the items involved in the current request, not on the whole space.

What a scope does not say A technical scope describes a capability, not a permission to act. In Asso, capability and authority are two separate layers: a write happens only if a current authorization covers it.

Gmail

Read, organize, prepare a draft. Not send.

The requested scope is Gmail modify (auth/gmail.modify). It covers reading and organizing your mailbox, without permanent deletion.

  • Searching threads and reading messages, to find the exchange that documents a case.
  • Organizing the mailbox: labels, read or unread, archiving, moving to the trash, all of which stay reversible.
  • Drafts: Asso can prepare and update a draft that you review and send yourself.
  • No permanent deletion bypassing the trash.

Sending email Asso does not send email through this Google connection. No send, sent-reply or forward route is open, and the mandate governing this access explicitly forbids those three actions. A message leaves only if you send it yourself from your own mailbox.

Google Calendar

Only the calendars you own.

The requested scope is events on owned calendars (auth/calendar.events.owned). It is the narrowest Calendar scope that still lets a deadline be held.

  • Searching and reading events on calendars your account owns.
  • Creating and updating those same events, to set a deadline or move an appointment.
  • Calendars you do not own, including other people’s calendars shared with you, stay outside this scope.
  • Events created are created on your own calendar. The current mandate does not allow Asso to commit a third party on your behalf.

Authorization and secrets

A revocable authorization, kept inside the system environment.

  • Asso does not know your Google password. Authentication happens at Google; what comes back is a revocable authorization, not a credential you typed.
  • Authorization material is kept inside the controlled local environment of the system, restricted to the account that operates Asso.
  • It is never displayed, never copied into a conversation, never published in a repository and never published on this public surface.
  • No local path, key or token appears here: describing the exact location of a secret is already a leak.

Use of data

What is never done with your Google data.

  • No sale, no brokerage, no transfer of your Google data to a third party.
  • No advertising, no advertising profiling, no ad network.
  • No use of Google data to train, improve or evaluate a public or generalized model.
  • No human reading of the content, except with your explicit consent, or where security or the law requires it.
  • No audience measurement, no advertising tracker and no third-party tracking script on this public surface.

Google policy Use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

The nuance worth stating To understand a request, Asso relies on artificial intelligence model providers. Content strictly necessary to the current request may therefore be processed by them, under their own business terms. That transit does not build a public product and does not feed generalized training.

Your control

Withdrawing access takes under a minute.

Asso’s Google access is withdrawn from your own Google account, on the page listing the applications with access to it. Withdrawal invalidates the existing authorization: Asso can no longer read or write anything until a new consent is given.

Withdrawal does not delete the documents, messages or events held at Google. It cuts the access, it does not touch your data.

  • Minimization: three scopes, chosen as the narrowest that still allow continuity.
  • What Asso keeps serves the continuity of the case: references, decisions, state of progress. This connection is not there to systematically copy your Drive or your mailbox.
  • Any widening of scope would require a new Google consent screen, and therefore your agreement.

Contact and references

Where to ask a question.

For any question about this connection, the contact address declared on Asso’s Google consent screen is the route. Google shows it to you at the moment you grant access. This site publishes no private contact details and hosts no form.

  • Requested scopes: auth/drive, auth/gmail.modify, auth/calendar.events.owned
  • Asso terms of service: terms
  • Publisher, hosting and legal frame of the site: Legal
  • Withdrawing access: the third-party applications page of your Google account
  • Last public verification: 30 August 2026

This page describes Asso’s Google access. It does not describe other services you may connect elsewhere.