Is Open in Chrome™ safe?
Open in Chrome sends selected page or link URLs to a local native-messaging helper when you use its context menu.
When you choose the extension's context-menu action, it reads the selected page, link, or source URL and passes that URL to a local native-messaging host. The helper uses the URL as an argument when opening Chrome, and the stored evidence does not identify a remote server receiving the data.
Who publishes itAlex - no other listings under this identity
Alex - 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 0.1.4resigned1. 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 every site you visit
<all_urls>
See the address and title of every tab you have open
tabs
Store data in your browser
storage
Add items to the right-click menu
contextMenus
Show you desktop notifications
notifications
Talk to a program installed on your computer, outside the browser's sandbox
nativeMessaging
Where it sends data
Destinations our analysis observed Open in Chrome™ 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.
- com.mybrowseraddon.node
Open in Chrome™ sends data to com.mybrowseraddon.node. 2 other extensions we have analysed send data here.