Browser Tool — Shouuut & CubeLV

Privacy policy

Updated October 7, 2026

Browser Tool — Shouuut & CubeLV connects your Chrome browser to the service you select. This policy explains the information handled by the extension and its browser automation features.

Information we handle

Account identity (name, email and member ID), access and refresh tokens, a browser device identifier and name, and connection status. During a task, information can include page URLs and titles, page text and interactive elements, screenshots, console messages, network request metadata, form inputs, uploaded files and recordings. These can contain personal or sensitive information present on the page.

When browser information is accessed

The extension runs browser tasks requested through your signed-in service. Browser actions and page inspection are limited to the tab group created for the conversation. It does not collect a general browsing-history feed or bulk-export the browser cookie store. Existing website sessions are used in Chrome. Information visible to a requested page read, screenshot or script can still be included in task results.

How information is used and shared

Task data is transmitted over HTTPS or secure WebSockets to the selected Shouuut or CubeLV service and to AI providers needed to perform your task, interpret a screenshot or locate elements. Cloud infrastructure and file storage use AWS. The selected model and service workflow determine the AI provider; the linked product privacy policies describe providers and account-data handling. We do not sell browser data, use it for advertising or use it to train generalized AI models. We use and transfer extension data only to provide and secure the user-facing features, in accordance with the Chrome Web Store User Data Policy and Limited Use requirements.

Storage and deletion

Login tokens, device information and preferences are stored in Chrome extension local storage. Sign-out removes login credentials. Browser registrations are removed when you sign out; registrations inactive for 30 days are removed when devices are listed. Temporary file uploads request a seven-day expiry. Conversation history and files saved to your workspace follow the selected product’s retention and deletion policy. Deleting the extension does not by itself delete cloud conversations or files; delete those in the app or request account deletion.

Your control

From version 0.1.6 onward, the extension performs the actions you request in the conversation directly, without separate approval prompts. You can stop an active task, sign out or uninstall the extension at any time.

Why permissions are needed

debugger enables page inspection, screenshots and browser interaction; tabs and tabGroups isolate conversation tabs; identity completes Google or Apple sign-in; storage saves local settings and credentials; notifications presents connection requests; alarms reconnects the service; downloads saves requested recording exports. Host access is limited to the selected build’s service APIs and file-storage domains.

Earlier extension versions

Versions through 0.1.5 provide action-review modes, site permissions and additional approval prompts. They also store the selected mode, allowed sites and up to 100 approval-history entries locally; sign-out clears those entries. Updating to 0.1.6 or later removes these stored settings and history. The behavior described above applies to 0.1.7 as well.

Contact and product policies

For privacy or deletion requests, email runvo.tech@gmail.com. This extension policy supplements the privacy policy of the product you connect to. Changes to this policy are published on this page with an updated date.