Is V-DOCS for Chrome safe?
V-DOCS for Chrome sends selected or auto-triggered page documents and request details to a local WebSocket client.
When connected to the V-DOCS desktop client, the extension watches page and frame requests across permitted sites and records URLs, methods, headers, and form or raw request bodies. Toolbar, context-menu, configured auto-trigger rules, or URLs containing signing parameters cause it to send the page URL and HTML or PDF bytes to the local client over WebSocket.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itMaplewave - no other listings under this identity
Maplewave - 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 3.5.0. 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
*://*/* and 1 more
See the address and title of every tab you have open
tabs
Add items to the right-click menu
contextMenus
Run its own code inside the pages you visit
scripting
See every page you navigate to, as you navigate to it
webNavigation
Watch every request your browser makes
webRequest
Where it sends data
Destinations our analysis observed V-DOCS 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:13378
V-DOCS sends data to localhost:13378. Named as a recipient by 1 other extensions we have analysed.