This privacy notice applies specifically to the Kamva for Chrome extension. Use of the rest of South Assistants' products (the workspace platform at app.southassistants.com, talent-placement services, etc.) is governed by our general Privacy Policy.
1. What the extension is
The extension is a remote-control bridge between Kamva (your AI assistant running at app.southassistants.com) and the browser tabs you ask Kamva to act on. It exists for a single purpose: to let Kamva view and act in your tabs at your explicit request — read what's on a page, fill in forms, click buttons, navigate, take screenshots — using your real logged-in browser session instead of a separate cloud browser.
The extension does nothing on its own. Every action is triggered by a message you send to Kamva in the chat at app.southassistants.com.
2. What we collect, when, and where it goes
| What | When | Where it goes | How long we keep it |
|---|---|---|---|
| Page content (text, links, form fields, the URL of the page Kamva is acting on) | Only when you ask Kamva to do something that requires reading the page — e.g. "summarize this page" or "draft a reply" | Sent to the Kamva web app on app.southassistants.com → forwarded to the AI model (Moonshot Kimi K2.6) to generate Kamva's response | Saved with your chat history in your workspace, just like any other Kamva conversation. You can delete chats from the Kamva UI at any time. |
| Screenshots of the visible tab | Only when Kamva calls the browser_screenshot tool, which only fires when a tool action benefits from visual context | Same as page content | Same |
| Workspace pairing (your workspace id, your name, your user id, an opaque session token) | When you click "Pair this Chrome" in Kamva settings | Stored locally via chrome.storage.local. Never transmitted to any third party. | Until you unpair, uninstall the extension, or clear browser data |
| Activity log (a short list of recent browser actions Kamva performed) | Whenever Kamva runs a browser tool | Stored locally via chrome.storage.local. Visible only to you in the extension's side panel. | Capped at the 200 most recent entries; older entries auto-delete |
3. What we do NOT collect
- Browsing history outside of active Kamva sessions. The extension does not record what websites you visit when you're not asking Kamva to act on them.
- Passwords, credit card numbers, or autofill data. We use your already-logged-in browser sessions — we never see, ask for, or store your credentials.
- Cookies, local storage, or any persistent web identifiers of the sites Kamva visits on your behalf.
- Analytics, telemetry, or usage tracking. The extension does not ping any third-party analytics service.
- Data from tabs you haven't pinned to Kamva. Browser tools only operate on the active session tab — the one Kamva is currently working on, shown in the side panel.
4. How we use what we collect
Only to make Kamva work:
- Page content and screenshots are forwarded to the AI model so it can reason about what to do next — which button to click, what text to type into a form.
- Workspace pairing identifies which Kamva account the extension is bound to, so actions are attributed to the right user and workspace.
- Activity log is shown to you locally so you can audit what Kamva has done.
We do not sell, rent, or share your data with third parties. We do not use your data to train AI models. Page content is sent to Moonshot AI only for the purpose of generating Kamva's response to that specific request, under Moonshot's published API terms; Moonshot does not train on API-passed content per their published policy.
5. Permissions, in plain English
The extension requests these Chrome permissions:
| Permission | What it lets us do | Why we need it |
|---|---|---|
tabs | See tab titles and URLs | To find the tab you asked Kamva to act on (e.g. "the Gmail tab") and to label entries in the activity log |
activeTab + scripting | Inject code into the page Kamva is acting on | Required to actually read forms, click buttons, type into inputs |
sidePanel | Show Chrome's native side panel | Renders the live activity log next to your tabs |
storage | Save data to chrome.storage.local | Persists the workspace pairing and activity log across browser restarts |
tabGroups | Create and manage tab groups | Groups every Kamva-opened tab into a labeled "Kamva" group so you can collapse and manage them |
host_permissions: <all_urls> | Inject the content script into any website | Because you can ask Kamva to work on any site you're logged into — we can't predict which sites in advance |
6. You're in control
- Unpair anytime. Open Kamva → Settings → Connectors → Kamva for Chrome shows the current binding. Unpair to immediately revoke the extension's link to your workspace.
- Uninstall. Right-click the toolbar icon → Remove from Chrome. All locally-stored data (binding + activity log) is deleted by Chrome.
- Disable per-site. Chrome lets you restrict any extension to specific sites via
chrome://extensions→ Kamva for Chrome → "Site access". - Stop mid-task. Closing the active session tab or unpinning it immediately halts the extension's ability to act.
7. Children's privacy
The extension is not intended for users under 18. We do not knowingly collect data from minors.
8. Security
- All data sent between the extension and Kamva travels over HTTPS.
- The extension's
externally_connectablemanifest field restricts which web origins can talk to it — only thesouthassistants.comdomain and its subdomains (andlocalhostduring development) can send messages to the extension. - The session token included in pairing is opaque and tied to a single browser install. It cannot be used to log into your Kamva account or any other service.
9. Changes to this policy
If we materially change how the extension handles data, we'll publish a new version of this page and bump the extension's version. The "Updated" date at the top reflects the most recent change.
10. Contact
Questions, requests to delete data, or anything else: privacy@southassistants.com.
Or write to: South Assistants (Pty) Ltd, South Africa.