Google Data Use for Eazo Agent Kit
Eazo Agent Kit (EAK) is managed infrastructure for AI agents. Developers and teams use EAK to give agents identity, memory, browser execution, email workflows, and auditable tool access. This page explains why EAK connects to Google services and how Google user data is handled.
Why EAK connects to Google
Users can connect their Google Account to authorize agents to perform selected, user-approved workflows, such as email, calendar, or file-related tasks. EAK requests only the permissions needed for the feature the user enables, and the exact permissions are shown on the Google OAuth consent screen at authorization time.
Google services EAK may integrate with
Google Sign-In
Authenticate users and create or manage an EAK account.
Basic profile information, email address, and account identifier.Gmail
Support user-approved email workflows, such as drafting, sending, or working with relevant message context.
Only the Gmail data required by the scopes granted on the consent screen.Google Calendar
Support user-approved scheduling workflows and calendar-related agent actions.
Only the calendar data required by the scopes granted on the consent screen.Google Drive
Support user-approved file workflows when a user connects Drive access.
Only the file data required by the scopes granted on the consent screen.Limited Use commitments
EAK's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- Google data is used only to provide user-facing EAK features requested by the user.
- Google data is not sold and is not used for advertising.
- Google data is not used to train, fine-tune, or improve generalized AI or machine learning models.
- Human access is limited to cases such as explicit user consent, security, abuse investigation, legal compliance, or support required to provide the service.
- Users can revoke Google access at any time from EAK settings or their Google Account security settings.
User control and deletion
Users may revoke EAK's access to their Google Account from within EAK account settings, where available, or from their Google Account third-party access settings. After revocation, EAK stops accessing Google data and deletes or anonymizes previously retrieved data according to our retention and deletion procedures, except where retention is required for security, audit, or legal obligations.
Related policies
For more information, read our Privacy Policy and Terms of Service. For questions about EAK's use of Google APIs, contact official@genauth.ai.
