What the extension sends, exactly when it sends it, and what it never collects.
Last updated 15 August 2026.
The short version. Nova for Chrome is an internal KnowledgeCity tool. It sends your message — and, when you ask about a page, a picture of that page — into your own Slack direct message with Nova, inside KnowledgeCity's Slack workspace. It is not a browsing tracker: it reads nothing while you browse, records nothing in the background, and sends nothing you did not just type or point at.
KnowledgeCity employees and contractors who install the extension and sign in with their KnowledgeCity Slack account. Sign-in is refused for guest Slack accounts, bot accounts, deactivated accounts, and any account whose profile email is not a KnowledgeCity domain.
| Data | When |
|---|---|
| The message you type | When you press Send. |
| A picture of the visible page | When your message refers to what is on screen — phrases like “this page”, “this button”, “where do I…”, “what is this”, “click”, or “here”. Taken once, at that moment. |
| A picture of the area you selected, plus the whole page | When you press Annotate and drag a box. |
| Page address and title; the CSS selector and text of the element you pointed at | With the messages above, as an attached text file named page-context.txt. |
| The page's recent error log | Only when your message reports a fault — “not working”, “broken”, “blank”, “500”, “why is it…”. Never on an ordinary question. |
| Your Slack user ID, display name, profile picture and work email | Once, at sign-in, to confirm you are KnowledgeCity staff. |
To be able to tell you why a page is broken, the extension keeps a small record of that page's own error messages while you are on it. This is the most sensitive thing it handles, so it is bounded deliberately:
The extension talks to exactly two places:
slack.com) — your message and attachments are posted
into your own direct message with Nova, as you. It is an ordinary Slack conversation: it
appears in your Slack app, follows KnowledgeCity's Slack retention and compliance settings,
and is visible to whoever can already see that conversation.Nothing is sent to any other server. There is no KnowledgeCity database of your messages behind this — Slack is the record.
In the extension's own browser storage: your Slack access token, your name and work email, and the most recent few screenshots and context files it sent — kept only so the panel can show you what was sent. Choosing Sign out deletes all of it and revokes the token with Slack, so it stops working rather than merely being forgotten.
Sign out from the panel menu, or remove the extension from chrome://extensions.
Either removes everything stored locally. Messages already sent remain in your Slack
conversation, exactly as they would if you had typed them in Slack — delete them there if you
want them gone.
Use of information received from Google APIs, and all data handled by this extension, adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. The data described here is used solely to provide the feature the user requested. It is never sold, never transferred except to provide the feature, never used for advertising, and never used to build user profiles. No human reads it other than the KnowledgeCity colleagues who can already see the Slack conversation it is posted into.
Ask Nova in the panel, or email nova.b@knowledgecity.ai. Concerns about how KC handles staff data can go to the Technology Division directly.