Google Data Terms
How Intelligent uses Google data to authenticate users, read meeting context, process transcripts, and create generated documents.
Last updated: May 8, 2026
Google data we use
The app may use your Google profile email, name, and picture for sign-in. With Workspace delegation configured by an administrator, the backend can read Calendar events, read ended Google Meet conference records and transcripts, and create Google Docs/Drive files generated by the meeting pipeline.
Purpose of use
Google data is used only to provide meeting intelligence features: authenticate authorized users, locate meetings, retrieve transcript content, run analysis, and create documents that summarize or structure meeting outcomes.
Storage and retention
The app stores user records, meeting records, transcript chunks, generated documents, traces, and related metadata in the application database. Google service-account credentials are read from backend configuration and are not exposed to the browser.
Sharing
Google data is not sold. Data is processed by the application backend and configured AI services only to deliver the product workflow. Access is limited to provisioned users and administrative configuration.
Revocation and access
A Google Workspace administrator can revoke OAuth or domain-wide delegation access in Google Admin Console. Users can request deletion or correction of application records from the workspace administrator.
Relevant Google scopes
The backend currently uses Calendar readonly, Calendar events readonly, Meet conference records readonly, Drive file, and Documents scopes.
If Google scopes or data flows change, this page must be updated before those changes are used in production.