Four things it will not do.
Enforced in the extension
Capture never writes a typed secret into a guide.
Password, card, email, phone, and number fields are recorded by the name of the field, never by what was typed into it. The value never leaves the browser, so there is nothing to leak later.
Enforced before publish
A screenshot never goes out before you've seen it.
Redaction is in the step editor, and nothing reaches a help center until you publish it. Draw over a region and it is blurred in the stored image, not hidden in the view — there is no original underneath to recover.
Enforced per hub
Doc never answers from another hub's docs.
It is scoped to the one hub it sits on and cannot reach anything you published elsewhere. Two clients' help centers cannot see each other's docs, and neither can their assistants.
Enforced on publish
A draft never reaches a help center.
Internal sections stay in your account, and a draft is visible to nobody until you publish it. Publishing is an action you take — nothing reaches a help center because you saved it.
Your documentation stays yours.
Never used to train a model
Your docs are never used to train a model.
Encrypted in transit and at rest
Everything is encrypted in transit and at rest.
Your docs live at real, stable URLs
Every published guide sits at an address you control, on your own domain, readable by anyone you share it with. Nothing is locked behind a viewer only we can open.
You are putting your clients' processes into somebody else's product, so here is what that means.
Ready to write it once?
Capture a process, publish it as a help center under your own name or a client's, and answer the repeat questions from what you published.