Is Meeting Controls for stream deck safe?
Meeting Controls for stream deck sends Google Meet control state to a local Stream Deck companion.
When you use Google Meet, the extension observes meeting controls such as microphone, camera, hand, leave, and reaction state. It relays that state, your active Stream Deck profile ID, and whether a meeting is open to a local Socket.IO companion, which can also ask the extension to click Meet controls.
Who publishes itkolaborateplatform - no other listings under this identity
kolaborateplatform - no other listings under this identity
What this publisher told the store about itself, and the other listings that told it the same thing.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 1.0.5. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on meet.google.com
*://meet.google.com/*
Read and change your data on localhost
http://localhost/*
Read and change your data on 127.0.0.1
http://127.0.0.1/*
Act on the current tab, but only after you click the extension
activeTab
Store data in your browser
storage
Run its own code inside the pages you visit
scripting
Where it sends data
Destinations our analysis observed Meeting Controls for stream deck contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- localhost:35623
Meeting Controls for stream deck sends data to localhost:35623. Named as a recipient in this extension's own analysis.