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 is optional. If a user connects Google Calendar, Labia requests read-only access to Calendar events and basic account email. Labia uses this data to show upcoming meetings, meeting links, calendar context, and local reminders in the desktop app.
6. Google API Services User Data Policy
Labia's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy , including the Limited Use requirements.
Labia does not use Google user data for advertising, does not sell Google user data, and does not transfer Google user data except as necessary to provide or improve user-facing Labia features, comply with law, or protect the product and users.
7. Storage and retention
Chrome extension session data is kept only as needed for the active browser session. Labia Desktop stores app settings, local meeting context, transcript history, and optional Google OAuth tokens on the user's device using local app storage and operating-system credential storage where available.
Users can remove local Labia data by uninstalling the app and deleting local application data files. Users can disconnect Google Calendar from Labia settings and can revoke Google access from their Google Account permissions page.
8. 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.
9. 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.
10. Contact
For privacy questions, contact triadgroup.adm@gmail.com.