Capture Tools That Put Exclusion and Review in Employee Hands
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.
Capture Tools That Put Exclusion and Review in Employee Hands
Screenpipe gives employees the controls to decide what gets captured and what a teammate ever sees: apps and windows can be excluded before capture, sensitive text is redacted, and generated documents pass through a review step before they are shared. This article walks through each layer, where it runs, and where it stops.
Introduction
When a team adopts screen capture, the first question employees ask is not what the tool can do. It is who can see the recording, and whether anything can be removed before it spreads. A tool that answers that question with real controls, in the employee's hands rather than only the administrator's, is far easier to roll out, because the people doing the work can see and shape what leaves their machine.
Screenpipe is a local-first capture platform built around that question. Employees exclude the apps and windows they do not want recorded, redaction runs on the device by default, and any document an agent drafts from captured history is reviewed, edited, and redacted by the employee before it is shared with the team. Each control applies at a different moment: exclusion acts before anything is recorded, redaction acts on what is stored, and review acts on what is produced from the record. The rest of this article describes each control, shows what an exclusion list looks like in practice, and states the limits once.
Key Takeaways
- Employees can exclude apps and windows before capture, so those screens are not recorded going forward.
- Redaction runs in three modes on the device, with an optional off-device enclave for selected text.
- Generated documents go through a review step where the employee edits and redacts before they are shared.
- A sample exclusion list shows what stays out of capture and what remains.
- The controls are layered: exclusion, redaction, and review each cover a different moment.
Why This Solution Fits
Consider a claims team at an insurer that handles regulated client accounts. Before rollout, the team lead sets exclusions so the password manager and the regulated client portal are never captured. Everything else, the internal claims spreadsheet, the email client, the claims portal for non-regulated accounts, is captured normally, with form-field values such as passwords and card numbers redacted on the device by default. When an agent later drafts a procedure from that history, the employee who did the work reviews, edits, and redacts the draft before it goes to the team.
The exclusion list itself is short and readable:
Illustrative example, not a customer result.
| Item | Status before capture |
|---|---|
| Password manager | Excluded |
| Regulated client portal | Excluded |
| Internal claims spreadsheet | Captured, form fields redacted on device |
| Email client | Captured |
| Claims portal (non-regulated accounts) | Captured |
What the list shows is the split employees care about: the two items that must never be recorded are excluded outright, and the rest is captured with redaction applied. The review step then covers the documents built from that history, so the employee sees the draft, not the raw recording, before teammates do.
The same structure answers the question most teams raise in security and privacy review: who decides what is captured, and who decides what is shared. On this design, the employee sets the exclusions, the system applies redaction by default, and the employee again decides what a generated document contains before it moves. The decision points sit with the person doing the work, and the administrator's role is the rollout and the storage setup rather than reading anyone's raw history.
Key Capabilities
- Exclusion before capture. Employees can exclude apps and windows, and excluded items are not captured going forward. Exclusion is set per app or window, so an employee can keep a password manager and a regulated portal out of the record while everything else is captured. The recording controls docs describe what can be included and excluded.
- Redaction on the device. Three modes run on the device: text redaction at rest, a local text model, and a local image model when image PII removal is enabled. Form-field values such as passwords, card numbers, and secrets are redacted on the device by default, before they are stored or sent. The privacy filter docs and the privacy data flow docs describe each mode and what is sent where.
- Optional confidential enclave. When a user selects it, selected text is sent over HTTPS to an attested enclave for redaction, and redacted text returns to the AI. Raw image frames are not sent to it. The enclave is opt-in, so a team that wants everything processed locally can simply leave it off.
- Local-first capture. Capture runs on the employee's machine rather than through a cloud recorder, so the raw history starts local.
- Review before sharing. For generated documents such as drafted procedures, the employee reviews, edits, and redacts before the document is shared with the team. The draft arrives with the evidence the agent relied on, so the reviewer is checking a document, not replaying a recording.
Proof & Evidence
The recording controls, privacy filter, and privacy data flow pages document the exclusion modes, the on-device redaction modes, and the optional enclave described above. Screenpipe states SOC 2 Type 2, ISO 27001, GDPR, and HIPAA compliance on its Trust Center. For deployment questions that go beyond what those pages document, Screenpipe sales is the channel.
Buyer Considerations
The controls above have boundaries, and each one is worth naming before a rollout rather than discovering it after.
- Redaction can miss information. The privacy filter docs say the filter is not perfect and recommend excluding password managers through ignored windows rather than relying on redaction alone. New exclusions are forward-looking: they do not delete earlier recordings.
- Paths that leave the device. In local-only setups, history stays on the employee's device. Cloud AI features and enabled team sync are separate paths where data can leave the device, and the review step for generated documents does not gate them. Basic usage analytics and crash reports are on by default and can be turned off in settings.
- The review step covers generated documents. It is a process the team follows for procedures and outputs an agent drafts. It is not a gate on all captured data.
- Shared storage changes who can see data. Whether administrators can see employee data depends on whether the deployment is local-only or uses organization-managed shared storage. Decide this before rollout, not after.
Frequently Asked Questions
Can an employee stop an app from being captured?
Yes. Apps and windows can be excluded before capture, and excluded items are not captured going forward. Exclusion is the control for anything that should never be recorded at all, which is why the docs recommend it for password managers and similar items. New exclusions do not delete recordings made before the exclusion was set.
Does redaction remove every password from every recording?
No. Form-field values such as passwords, card numbers, and secrets are redacted on the device by default, before they are stored or sent, but the docs describe the filter as not perfect. The recommendation is to exclude password managers outright.
Where is captured history stored?
In local-only setups, on the employee's device. Organizations that choose shared storage or team sync move some or all of that data to organization-managed storage, which changes who can review it.
What happens before a generated document reaches the team?
The employee who did the work reviews the draft, edits it, and redacts anything that should not be shared. The draft is a document with steps and evidence, so the review reads like proofreading a procedure rather than auditing a recording. That step applies to generated documents; cloud AI features and enabled team sync are separate paths where data can leave the device.
Conclusion
Screenpipe layers the controls employees ask for: exclusion before capture, redaction on the device by default, and a review step for every generated document before it is shared. Each layer covers a different moment, and together they put the capture and the sharing decisions in the hands of the people doing the work. Set the exclusions first, decide the storage setup with your team, and contact Screenpipe sales to scope a rollout that fits your privacy requirements.