Integrations

Google Drive & Google Sheets integration

Cimba.ai lets you connect your Google Drive and Google Sheets so your own documents and spreadsheets can be used as a data source inside the product. You start the connection yourself from within Cimba, and Google shows you exactly which permissions you are granting before anything is shared.

What you connect, and who starts it

The connection is always initiated by you. Cimba never reaches into a Google account that has not been explicitly connected, and Google's own consent screen is the point at which this is decided — it lists the permissions in full before you agree to anything. An administrator can also restrict Cimba to specific files rather than all readable Drive content; in that mode Cimba requests only the narrowerdrive.file scope, and the restriction is enforced every time a file is fetched, not just in the interface.

What Cimba asks for, and why

Cimba has two separate Google Drive connections and they do not ask for the same thing. You grant each one separately.

Your basic profile (openid, userinfo.email, userinfo.profile) — to identify the Google account you connected and show it back to you.
Google Drive, read only (drive.readonly) — used by our original Drive connector to read the files you choose as a data source. That connector cannot write to your Drive.
Google Drive, full access (drive, drive.file) — used by our newer Drive integration, which can act on files on your behalf when you ask an agent to: moving, renaming, sharing, labelling or commenting on a file. This access can modify your Drive, and we request it only for that integration.
Google Drive file metadata (drive.metadata.readonly) — to list file and folder names so you can pick the right spreadsheet.
Google Drive labels, read only (drive.labels.readonly) — to read the labels your Workspace defines, so an administrator can nominate labels (a confidentiality label, say) whose files Cimba must never read, summarise or act on. This one exists to keep Cimba out of files, not to reach further into them.
Google Sheets, read only (spreadsheets.readonly) — to read the contents of the spreadsheets you select.

What Cimba does with it

Your documents and spreadsheets are used to do the work you ask for inside the product: answering your questions about your data, running analyses, producing reports, and powering the automations and workflows you set up. That is the whole purpose of the connection.

What Cimba does not do with it

We do not sell your data, and we do not share it for anyone else's marketing.
We do not use it for advertising or ad targeting.
We do not use it to train AI models.
We do not use it for any purpose you have not asked for.

Cimba's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Staying in control, and disconnecting

You can disconnect your Google account from Cimba at any time, from inside the product. You can also revoke Cimba's access directly from your Google Account's third-party access settings. Disconnecting stops any further access immediately.

Where the detail lives

The full account — which scopes are requested, where data is stored and how it is protected, how long it is kept, who else can see it, and how to have it deleted — is in the Privacy Policy: