Knowby Capture Browser Extension Security and Privacy Overview
This article breaks down exactly what data we collect, what we don't, and why we request certain permissions, so you can confidently deploy Knowby Capture across your organisation.
At Knowby, we understand that enterprise security teams need complete transparency before deploying new tools.
The Knowby Capture Chrome extension is designed to help your team instantly create step-by-step instructional guides by capturing screen activity and clicks.
To do this effectively, the extension requires specific browser permissions.
What Data We Collect (and What We Don't)
Our data collection is strictly limited to the information necessary to generate your instructional guides.
What we DO collect during an active recording session:
-
User Activity: We monitor clicks, mouse positions, scrolling, and keystrokes exclusively to generate the steps of your guide.
-
Website Content: We capture text, images, and visual elements on the specific page you are recording to create screenshots and video fragments for your instructions.
What we DO NOT collect: We adhere to strict data minimisation principles. Knowby Capture does not collect:
-
Personally identifiable information (PII)
-
Authentication information (passwords, credentials, PINs)
-
Financial or payment information
-
Health information
-
Personal communications (emails, chats)
-
Location data (GPS, IP addresses)
-
General web history (we do not track your browsing outside of active recording sessions)
Important Note on User-Captured PII and Redaction:
While the Knowby extension does not systematically collect or harvest PII, it captures exactly what is visible on the user's screen during an active session. If a user intentionally or accidentally records a screen that displays sensitive information (such as customer data or internal credentials), that information will be visible in the captured screenshots or video fragments.
It is the user's responsibility to use the built-in media tools within the Knowby editor to obscure any sensitive information before publishing and sharing.
Why We Request Specific Browser Permissions
When you install the extension, Chrome will display a list of required permissions. Here is the enterprise justification for each:
-
Host Permissions &
activeTab: We only access and capture content on the specific tab you explicitly trigger for recording. We do not constantly monitor your browser. -
scripting: This is necessary to inject our capture tools into the webpage you are recording. It allows us to visually highlight elements on the screen and track your clicks to automatically generate the steps in your knowby. -
storage: We use local storage to temporarily save screenshots and recording fragments directly on your machine. This prevents data loss if a tab is accidentally closed. Once your capture session is complete, this temporarily stored data is securely uploaded to your selected Knowby organisation to generate the final knowby. We also store session identifiers here to keep you logged in, but we never store passwords. -
tabs&webNavigation: These permissions allow the extension to smoothly follow your workflow. If your process requires switching tabs, loading new pages, or logging into a new service during a recording, the extension can accurately map your steps to the correct locations. -
sidePanel&contextMenus: These are purely for user experience, allowing us to provide a persistent sidebar to manage your capture progress and a right-click menu option to quickly "Capture Screenshot."
Enterprise Security Highlights
-
No Remote Code: Knowby Capture does not use remote code (JS or Wasm). All code required to run the extension is bundled within the package itself. This means no unverified external scripts are being evaluated on your users' machines.
-
Strict Data Handling Guarantees: We officially certify that we:
-
Do not sell or transfer user data to third parties outside of approved use cases.
-
Do not use or transfer user data for purposes unrelated to the extension's single purpose (creating instructional guides).
-
Do not use or transfer user data to determine creditworthiness.
-
Further Reading For full legal details regarding our data handling and privacy practices, please review our complete privacy policy at: https://www.knowby.co/privacypolicy