Google API Data Use

Limited Use

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

Ida uses Google user data only to provide prominent, user-facing features that you choose to connect. We do not use Google user data for advertising, sell it, use it to determine creditworthiness, or use it to train general-purpose AI models.

Google Data Ida Accesses

Calendar

Read-only Calendar access may include event titles, start and end times, attendee email addresses, meeting links, and event identifiers. Ida uses this information to show upcoming meetings, connect sessions with events and accounts, recognize attendee relationships, and provide direct meeting access.

Gmail

If you enable the recent-email feature, Ida requests https://www.googleapis.com/auth/gmail.readonly. This is the narrowest Gmail scope that permits Ida to search for and read the content of matching messages. The feature does not send, modify, label, or delete email.

When you open an Ida account, the feature:

1. Uses the account's saved company domain to search recent sent and received Gmail messages, including copied recipients
2. Retrieves a small candidate set and verifies sender or recipient addresses against the account domain
3. Extracts sender, recipients, subject, date, and the newest relevant body text
4. Loads pages of up to eight conversations for inline reading, with older conversations available on request
5. Shows message text without signatures or repeated history; the source message remains available in Gmail. Drafts, spam, trash, and calendar scheduling messages are excluded
6. Uses local text rules to surface questions and requests for review, and lets you explicitly save source-linked follow-ups in account Tasks
7. Matches senders to existing account People by exact email address, reuses their avatars, and offers optional name updates for blank or email-derived names. Names are changed only when you approve the suggestion
8. Lets you explicitly add a conversation as context in Ida chat; it is sent to the AI provider only when you submit your question

Storage and Retention

• Gmail content: The email reader fetches content on demand and holds it temporarily in memory. Reading email does not add message content to Ida's database or content index. If you choose to use email in chat, it becomes part of that AI request. If you save a follow-up, its selected quotes and source link are stored as ordinary workspace task content. Any resulting content you save is handled like other saved workspace content.
• Email review status: Review markers store only message and conversation identifiers on your device, scoped to your profile and account. They do not change Gmail read status.
• People name updates: If you approve a suggested sender name, that name is saved on the existing person in your workspace. This does not create new people or change your Gmail contacts.
• Linked email addresses: You can explicitly link additional addresses to an existing workspace person, choose a primary address, retire an old address, or confirm a duplicate-person merge. Saved aliases connect emails and meeting history to the same person; retired addresses remain available for historical matching. Merges preserve account and meeting links and retain an audit of the original records and your choices. Names and similar addresses are never used to merge people automatically. Gmail contacts and messages are not modified.
• Calendar data: Ida may retain the event metadata needed for calendar-linked workspace features.
• OAuth credentials: Credentials are retained only as needed to keep the Google integration connected and refresh authorized access.
• Logs and analytics: Google message content, Calendar event content, and attendee details are excluded from diagnostics and analytics.

Sharing and Transfers

Ida does not sell Google user data or share it with advertisers or data brokers. Reading email does not send its content to Ida's AI providers. If you add a conversation to Ida chat and submit a question, the selected email text and metadata are sent to the provider to answer that request. Attachment contents are not included. Data may be processed by infrastructure providers only as necessary to securely operate the feature, subject to appropriate confidentiality and security obligations, or disclosed where required by law.

Security and Human Access

Google data is encrypted in transit and access is limited to authorized requests for the user-facing integration. Ida personnel do not read Google user data unless you provide affirmative consent for support, access is needed for security or abuse investigation, access is required by law, or the data has been aggregated and anonymized for internal operations.

Revoke Access or Delete Data

You can stop future Google access at any time from your Google Account permissions . You can also sign out of Ida to clear the active local session.

Revoking access does not delete unrelated Ida workspace content. For an Ida account or server-data deletion request, follow the steps on our Data Deletion page or email hello@tryida.com.

Questions

Contact hello@tryida.com with questions about Google data or Ida's integrations.