IT Admin Guide: Deploying Meeting Transcription as a Browser Extension

When a team at your organization asks to use a meeting transcription tool, the IT and security evaluation typically focuses on three questions: What data does it access? Where does it go? How do we manage it at scale?

Most meeting transcription tools are SaaS platforms that operate meeting bots. These bots join calls as participants, capture the audio stream, and transmit it to external servers for processing. From an IT perspective, this means a third-party service has access to meeting audio, which triggers reviews around data classification, vendor risk assessment, and potentially SOC 2 or privacy impact assessments.

IceCubes takes a different approach. It is a browser extension (available for Chrome and Edge) that reads closed captions from the meeting platform's own captioning service. It does not capture audio, does not join meetings as a participant, and does not require API access to your meeting platform. This changes the security and deployment conversation significantly.

How IceCubes Works: Technical Overview for IT

Data Flow

1. The user joins a meeting on Google Meet, Zoom (web client), or Microsoft Teams (web client) in their browser
2. The user enables closed captions in the meeting platform (or the extension prompts them to)
3. IceCubes reads the caption text from the DOM of the meeting page
4. The caption text, along with speaker names displayed in the platform UI, is assembled into a transcript
5. The transcript is sent to IceCubes' servers for storage and AI processing
6. AI-generated summaries, action items, and insights are stored in the user's IceCubes account

What IceCubes Does NOT Do

• Does not access the user's microphone or system audio
• Does not record or capture any audio or video
• Does not join meetings as a bot or participant
• Does not require OAuth access to Google Workspace, Microsoft 365, or Zoom admin APIs
• Does not require any meeting platform admin configuration
• Does not intercept network traffic or WebRTC streams

Extension Permissions

The IceCubes browser extension requests the following permissions:

The extension does not request permissions for microphone, camera, clipboard, downloads, or access to all URLs. It activates only on meeting platform domains.

Deploying via Chrome Enterprise

For organizations using Chrome Enterprise (Chrome Browser Cloud Management), IceCubes can be deployed and managed through your existing extension management policies.

Force-Installing the Extension

To deploy IceCubes to all users or a specific organizational unit:

1. Open the Google Admin console (admin.google.com)
2. Navigate to Devices > Chrome > Apps & extensions
3. Add the IceCubes extension by ID: kjloicnkhgbhmgchjamhbldmnlgncpeo
4. Set the installation policy:
   • Force install - Extension is installed automatically, user cannot remove it
   • Force install + pin - Extension is installed and pinned to the toolbar
   • Allow install - Extension appears in the user's approved list, they install it themselves

Allowlisting the Extension

If your organization blocks all extensions by default (a common security posture), you can allowlist IceCubes specifically:

1. In the Admin console, go to Devices > Chrome > Settings > Users & browsers
2. Under Extensions, find "Extension management settings"
3. Add kjloicnkhgbhmgchjamhbldmnlgncpeo to the allowlist

Extension Version Management

Chrome Enterprise handles extension updates automatically. IceCubes follows Chrome Web Store update policies, and new versions are distributed through the standard Chrome extension update mechanism.

Deploying via Edge for Business

Microsoft Edge for Business supports similar extension management through Microsoft Intune or Group Policy.

Using Intune

1. In the Microsoft Intune admin center, navigate to Apps > Extensions
2. Add the IceCubes extension from the Edge Add-ons store (ID: ehafkkjkgebdlgfllhkgdibllgeoaecf)
3. Assign the extension to the appropriate user groups
4. Set the installation mode (force install, allowed, or blocked)

Using Group Policy

For on-premises management:

1. Open Group Policy Editor
2. Navigate to Computer Configuration > Administrative Templates > Microsoft Edge > Extensions
3. Use "Configure extension management settings" to add IceCubes to the allowed or force-installed list

Chrome Web Store Extensions in Edge

Edge can also install extensions from the Chrome Web Store. If your organization has enabled this capability, users can install IceCubes directly from the Chrome Web Store link. To manage this:

1. In Edge policies, ensure "Allow extensions from other stores" is configured appropriately
2. Add the Chrome Web Store extension ID to your management policy if using force-install

Security Assessment Framework

For IT teams conducting a formal security review, here is a framework comparing IceCubes to bot-based transcription services:

Data Access Comparison

API Access Requirements

This reduced API footprint simplifies the procurement and security review process. There is no need to evaluate the vendor's OAuth scopes for your meeting platform, because IceCubes does not use them.

Data in Transit and at Rest

• Transcript text is transmitted over HTTPS/TLS to IceCubes servers
• AI processing (summaries, action items, insights) occurs server-side
• Data at rest is stored in encrypted databases
• Users can delete their transcripts and account data at any time

Authentication and User Management

IceCubes uses individual user accounts. There is no requirement for SSO or directory integration (though it supports Google and Microsoft sign-in). For organizations that need centralized user management:

• Users sign up individually with email/password or Google/Microsoft authentication
• Each user's transcripts are isolated to their account
• There is no shared workspace or admin console that aggregates all users' data

For organizations that require centralized administration, discuss your requirements with the IceCubes team directly.

Integration Security Considerations

IceCubes offers integrations with HubSpot, Salesforce, Slack, and Zapier. If your users plan to use these integrations, review the data flow for each:

• CRM (HubSpot/Salesforce) - Meeting summaries and structured data are pushed to CRM records. The OAuth connection is per-user. Review what data fields are synced. See CRM sync details.
• Slack - Meeting summaries can be posted to Slack channels. The connection uses Slack's OAuth flow. Review which channels receive data.
• Zapier - Connects IceCubes to 5,000+ apps via Zapier's platform. Review individual Zap configurations for data flow. See Zapier workflows.
• API/MCP Server - For custom integrations. API access is token-based and per-user. See API and MCP documentation.

Common IT Questions

"Does it work with our meeting platform's admin settings?"

IceCubes reads captions from the meeting UI. As long as your meeting platform allows captions to be enabled by participants, IceCubes works. If your Google Workspace or Microsoft 365 admin has disabled captions, IceCubes will not be able to capture transcripts.

"What happens if we need to revoke access?"

Since IceCubes is a browser extension, you can remove it through Chrome Enterprise or Edge for Business policies. This removes the extension from all managed browsers in the scope of your policy. User data remains in their IceCubes account until they delete it.

"Does it affect meeting performance?"

IceCubes reads DOM elements (caption text) from the meeting page. It does not intercept WebRTC streams, inject code into the meeting platform, or modify network traffic. The performance impact is negligible, comparable to any lightweight browser extension.

"Can we prevent specific meetings from being transcribed?"

IceCubes is controlled by the individual user. They choose when to enable it. There is no mechanism for a meeting organizer to prevent an attendee from using a browser extension on their own machine. This is the same dynamic as any note-taking tool: you cannot technically prevent someone from typing notes during a meeting.

"Do we need a BAA (Business Associate Agreement)?"

IceCubes does not capture audio and does not join meetings as a participant. However, if your users transcribe meetings that contain PHI or other regulated data, you should evaluate whether a BAA or data processing agreement is needed based on the text content of the transcripts. See our post on meeting transcription in healthcare-adjacent contexts for more detail.

Pilot Deployment Recommendation

For IT teams evaluating IceCubes, we recommend a phased approach:

1. Week 1 to 2: Allow 3 to 5 users to install the extension individually. No enterprise deployment needed. Users get 50 free AI credits with no credit card.
2. Week 2 to 4: Collect feedback on transcription quality, workflow integration, and any concerns. Review the data flow and extension permissions.
3. Week 4+: If the pilot is successful, deploy via Chrome Enterprise or Edge for Business to the broader team. Configure integration policies as needed.

This approach lets your security team evaluate the tool in a controlled setting before broader rollout, without requiring a lengthy procurement process.

Getting Started

IceCubes is available on both the Chrome Web Store and the Edge Add-ons store. Individual users can start with 50 free AI credits, no credit card required. For enterprise deployment questions, reach out to the IceCubes team.

Add to Chrome | Add to Edge