Browser extension
Kove Connect — Privacy Policy
Kove Connect reads a signed-in session or provider page state from a site you explicitly choose to connect or drive, only after you start that action from Kove, and hands the result back to the Kove web app. It never reads your password and never works in the background.
Single purpose
Kove Connect has one purpose: to connect or drive a supported site you are already signed in to — in your own browser — so Kove can act for you on that site after your approval. It does nothing else.
Data the extension reads
- Cookies for the site you chose to connect (including httpOnly session cookies).
- localStorage for the signed-in page on that site.
- indexedDB database names and versions for that page’s origin.
- Your browser’s user-agent string.
Data the extension never collects
- Your Kove account password.
- Passwords you type into third-party sites.
- Anything from sites you did not choose to connect.
- Your browsing history or activity in other tabs.
How a capture works
- You start a capture from Kove for a supported site.
- The extension opens that site’s login page in a new tab. You sign in normally.
- Once you are signed in, the extension reads the session for that site, in that tab only.
- It returns the captured session to the Kove web app page that asked for it. The extension itself never sends anything to the Kove API.
Why the extension asks for these permissions
- cookies — to read the session cookie the site set after you signed in.
- scripting — to read the signed-in page’s localStorage and show the in-page “Finish connecting” prompt.
- storage — to keep a small local list of your recent captures, shown in the popup.
- Site access — limited to the specific sites Kove supports connecting (alo.bg, bazar.bg, estateassistant.eu, fresha.com, hippotaxi.bg, olx.bg, triumftaxi.com). The extension reads a site’s session only on a capture you explicitly start — never passively.
The Learn with Kove button on YouTube
On YouTube watch pages, Kove Connect shows a Learn with Kove button. It reads only the video id in the page address so it can offer you that video’s link. Pressing it opens your own Kove chat in a panel beside the video in the same tab, which switches YouTube to theater mode and reserves that panel’s width so the video is never covered; closing the panel puts both back. It does not read the page, the video, your YouTube account, or your watch history, and it sends nothing anywhere unless you choose to send it from that panel.
Pairing this browser with your Kove account
If you pair the extension from your signed-in Kove account, Kove issues a key for that browser and the extension stores it locally. The key exists so the Kove panel shown beside a YouTube video can sign in to your own Kove account — that panel is an embedded frame of the Kove web app, and a framed page cannot see the Kove session you are already signed in to. The key is scoped to that one browser, is replaced with a new one every time it is used, expires if it is unused for 30 days, and can be revoked from the same page, which stops it working immediately. It gives access to nothing beyond your own Kove account, is never shared with anyone, and no key exists until you pair.
Storage and transfer
The captured session is treated as a password-class secret: sent only to your Kove web app over HTTPS, encrypted at rest by Kove, and never written to logs. The extension keeps only a small local record of recent captures for the popup, which you can clear at any time.
Retention and control
You can disconnect a site from the extension popup, which clears its local record. Retention of any session you submit to Kove is controlled by Kove and described in the main Kove Privacy Policy.
Data use
Captured sessions are used only to provide the connect feature you asked for. They are never sold, never used for advertising, and never shared except as needed to operate the feature for you.
Contact
Questions about this policy: hello@wekove.com.