Screen recordings run through the systems you care most about. Here is exactly how Knovvy handles that content, in plain terms, including the parts we have not built yet.
Open the ones you care about. Everything here describes how Knovvy behaves today, not how we intend it to behave.
Capture runs in the browser, so the extension needs access to whatever internal tool you are documenting. Here is what it does with that access.
activeTab and tabs: know which tab you are capturing, and take the screenshot.storage: hold the in-progress session so a capture survives a navigation or a worker restart.tabCapture and offscreen: record the video half of a dual-capture.When you type into a field, Knovvy decides whether it is sensitive from DOM signals only. No model call, no pixel heuristic, identical behavior every time. A field is treated as secret if any of these hold:
type="password" on the input.autocomplete of one-time-code, cc-number, or cc-csc.This detects form fields, not text. A secret already rendered as page text, say an API key shown after you generate it, is not something the DOM marks sensitive, so it is not caught automatically. Blur it yourself in the editor.
Every guide, recording, and folder belongs to a workspace. Members hold one of four roles, checked on the server for every request rather than hidden in the interface:
viewer: read what has been shared with them.editor: create and edit content.admin: plus members, invites, and billing.owner: everything, and never assignable through the API.On top of the role you can grant view, edit, or manage on one guide, recording, or folder, optionally with an expiry date. Grants are additive by design: they can open something up, but can never lock an owner out of their own workspace content.
/g/<token>.That last point is a real design tradeoff, not a footnote. If capability-URL media does not fit your threat model, tell us before you roll out rather than discovering it later.
Captions and video-to-guide transcription use whisper.cpp on infrastructure we operate. Your audio is not shipped to a third-party speech vendor, and there is no per-minute meter creating pressure to cut that corner later.
A security page that only lists strengths is useless for real diligence. As of today, these do not exist:
Where each of these sits is on the roadmap, and this page is updated when they ship, not before. If one is a hard requirement, talk to us about Enterprise and say which, because that ordering is driven by who actually asks.
Email support@knovvy.app with enough detail to reproduce it. We will confirm receipt, and we will not take action against anyone reporting a genuine issue in good faith.
Yes. Every guide and recording is private to your workspace when it is created. Nothing is reachable from outside until you explicitly publish it or grant someone access, and both of those are reversible.
Password fields, one-time-code fields, and card fields are detected from DOM signals and redacted at capture time: the typed value becomes bullets in the written step, and the field is blurred in the stored screenshot. This runs before anything is uploaded, and it is deterministic, with no AI involved.
No. The content script loads on pages you visit, but every listener is gated on an active capture session. Until you start a capture, no step is created, no screenshot is taken, and nothing is sent to our servers.
On infrastructure Knovvy operates, using whisper.cpp. Audio is not sent to a third-party transcription service, which is also why transcription is included in your plan rather than metered per minute.
The token is cleared and the URL returns a 404 on the very next request, with no grace period. If you publish the guide again later it gets a completely new token, so the revoked link stays dead permanently.
Not today, and we would rather say so than imply otherwise. We have not begun a SOC 2 audit. SAML SSO, SCIM, and a workspace audit log are also not built yet. This page is updated when they ship.
No. Billing goes through Stripe Checkout and the Stripe Customer Portal, so card numbers are entered on Stripe and never reach a Knovvy server. We hold only a Stripe customer and subscription id.