Viski

Viski Chrome extension privacy policy

Last updated 8 October 2026. This page covers the Viski extension for Chrome. The Viski privacy policy covers the Viski service itself.

What the extension is for

The extension lets Viski do browser steps for you in your own signed-in Chrome: the store-console steps of a release (Google Play Console, AdMob, App Store Connect), and, only if you switch on Web browsing for chats, websites the assistant in your Viski chats needs for a task you gave it. Every action happens in a tab marked with a Viski banner, where you can pause it at any time.

What it reads and sends to Viski

• Your Viski sign-in, to link itself. When you are signed in to viski.ai in Chrome, the extension asks Viski to link it to your account. Viski answers with a device token, kept in the extension's local storage. The extension does not read or keep your Viski password or session cookie.
• The page in a Viski tab, while Viski is working there. For each step it reports the page address and title, its visible text (up to 4,000 characters) and the buttons, links and fields on it, so the assistant can decide the next step. Screenshots are taken only when a step asks for one. Password fields are never read, and the extension refuses to type into them.
• Whether Web browsing for chats is on, and the extension's version.

It reads nothing from tabs Viski is not working in, and it does not record your browsing history.

What it does not do

• It does not type passwords or one-time codes, and it does not get past sign-ins, CAPTCHAs, payments or legal declarations by itself. It hands those to you on the tab.
• It does not sell your data, use it for advertising or credit decisions, or share it with anyone except as below.
• It does not load or run code from anywhere: everything it runs ships inside the extension.

Store sign-ins you choose to save

If a workspace owner saves an Apple ID or Google account sign-in in Viski for store releases, Viski stores it encrypted. It hands it only to an extension linked to that workspace for that console, which types it into the sign-in page. Every hand-over is logged.

Who processes the data

What the extension reports goes to Viski (viski.ai) over HTTPS. It is used to carry out the step you or your workspace started. Page content passes to the AI model that runs your chat or release, under the terms in the Viski privacy policy. It is kept with that run or chat in your workspace, and deleted with it.

Your controls

• Untick Allow Viski to work in this Chrome in the extension's menu to stop everything at once, or Web browsing for chats to take back access to websites.
• Disconnect from all workspaces in the menu, or a workspace owner in Viski, revokes the device token.
• Removing the extension deletes everything it stored in Chrome.

Contact

Questions about this policy: privacy@viski.ai.