TRIADGROUP Labia.io
Privacy policy

How Labia handles meeting and Google Calendar data.

This policy describes Labia Desktop, the Labia Chrome extension, and the optional Google Calendar read-only integration.

1. Product overview

Labia is a local-first desktop meeting copilot by TriadGroup. The product helps users detect supported meetings, transcribe live calls, keep local meeting context, and receive in-call suggestions.

2. Data collected by the Chrome extension

The Labia Chrome extension reads the active meeting page URL, meeting code, supported meeting page title, and meeting lifecycle state on supported sites such as Google Meet, Zoom Web, and Microsoft Teams Web.

The extension may read visible meeting captions on a supported meeting page when Labia is active so the local desktop app can display a live transcript. The extension does not collect general browsing history, unrelated page contents, or browser activity outside supported meeting pages.

3. How extension data is used

Extension data is used to detect an active meeting, open or connect to the Labia desktop app, display the in-meeting Labia panel, and pass meeting captions to the local app for the active call.

The extension communicates with the locally installed Labia desktop app through Chrome Native Messaging or a local deep link fallback. The extension itself does not sell data and does not use meeting data for advertising.

4. Data handled by Labia Desktop

Labia Desktop may process microphone audio, supported meeting captions, transcript text, meeting notes, local knowledge files added by the user, app settings, license status, and setup diagnostics.

The core live meeting workflow is designed to run locally on the user's computer whenever possible. Beta builds may include setup or activation calls needed for licensing, updates, and optional integrations.

5. Google Calendar data

Google Calendar integration is optional. If you connect it, Labia requests your Google account email and read-only access to the list of calendars and their events. It stores calendar names and colors, event titles, dates, times, meeting links, organizer and attendee details needed for meeting context, and your response status in its local database.

Google Calendar events Used to display upcoming meetings, dates, times, titles, conference links, and schedule context in Labia.
Google Calendar list Used to retrieve your list of calendars so you can view and select which calendars (e.g. primary or secondary) to sync in Labia.
Google account email Used to show which Google account is connected and to help the user manage the integration.
Calendar write access Not requested. Labia does not create, edit, delete, or share Google Calendar events.

We do not request or access contacts, personal emails, Google Drive files, or any other Google Workspace service.

6. Data protection mechanisms and security for sensitive data

Labia uses HTTPS for Google API requests and operating-system secure storage to encrypt OAuth tokens before saving them locally. Calendar event data is stored in the local application database; its protection also depends on your device access controls and disk encryption. The following measures describe how the current desktop app handles Google data:

  • Encryption in Transit: All data transmitted between Labia, Google APIs, and external network endpoints is encrypted in transit using industry-standard Transport Layer Security (TLS 1.2 or TLS 1.3) and HTTPS protocols to prevent eavesdropping, tampering, or man-in-the-middle attacks.
  • Encryption at Rest: Google OAuth tokens are encrypted with the operating system's secure storage before they are saved in Labia's local database. Synced Calendar event data remains in that local database and relies on your device's access controls and disk encryption. Protect your device with an operating-system password and disk encryption.
  • Restricted Human Access: Labia does not give its staff routine access to your locally stored Google Calendar data. If you choose to export, share, or send diagnostic information, the recipients you select may receive that content.
  • Complete AI/ML Isolation & No Model Training: Google user data and information accessed through Google Workspace APIs are NOT transferred to third-party AI/ML services or models, nor are they used to develop, improve, or train generalized or non-personalized artificial intelligence (AI) and/or machine learning (ML) models.
  • Least Privilege & Minimal Scopes: Labia requests read-only scopes for Calendar events and the calendar list, plus OpenID Connect email access to identify the connected account. It does not request Calendar write access.

7. Google API Services User Data Policy & Limited Use

Labia's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy , including the Limited Use requirements.

Labia uses Google Calendar data exclusively to display upcoming meetings, meeting links, and local reminders inside the desktop application. Google Calendar data is processed locally on the user's device and is never transferred to, processed by, or shared with any third-party AI or machine learning services, nor is it used to train, develop, or improve AI/ML models. Labia does not sell Google user data or use it for advertising.

All other uses of Google user data are strictly prohibited. Specifically, Labia:

  • Does NOT use Google user data for targeted advertising, personalized advertisements, retargeted advertisements, or interest-based advertisements.
  • Does NOT sell Google user data to data brokers or information resellers.
  • Does NOT use Google user data to determine credit-worthiness or for lending purposes.
  • Does NOT create databases of Google user data for third-party access or resale.
  • Does NOT transfer Google user data to third parties except as strictly necessary to provide or improve user-facing features, comply with applicable laws, or protect user safety.

8. Data retention and deletion

Labia keeps synced Google Calendar data in its local database while the integration remains connected. Disconnecting removes that account's active calendar data and tokens from the database. Local application files, database remnants, and device backups may remain until you remove them. Chrome extension session data is kept only as needed for the active browser session.

Disconnecting a Google account removes that account's tokens, synced calendar list, and event rows from Labia's active local database. Revoking access in your Google Account stops future API access but does not itself remove Labia's local cache. Uninstalling the app may leave local application files or device backups; delete those separately if you want to remove them.

You may request for your data to be deleted by:

  • Disconnecting Google Calendar in Labia application settings.
  • Revoking permissions directly in your Google Account security page (https://myaccount.google.com/permissions).
  • Emailing suporte@labia.io for help locating and deleting local application data. We cannot remotely erase files that are stored only on your device.

9. Sharing

Labia does not sell personal data. Labia does not share Google Calendar data with advertisers. Meeting content and transcript data are not shared with third parties by the Chrome extension.

10. User choices and controls

Users can disable the Chrome extension, uninstall Labia Desktop, skip Google Calendar connection, disconnect Calendar later, or revoke Google access directly from their Google Account.

11. Contact

For privacy questions, contact suporte@labia.io.