Work Analysis Tools That Show Employees What They Collect
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.
Work Analysis Tools That Show Employees What They Collect
Screenpipe is the work analysis tool built to answer that question in the open: it captures work history on the employee's own device and gives employees direct controls over what is excluded, redacted, and shared. This article walks through those controls and the limits to state plainly when your team asks.
Introduction
When a team starts using a tool that records screen activity, the first questions usually come from the people being recorded, not from the buyer. What is captured? Where does it go? Can I turn parts of it off? A rollout that cannot answer these questions in concrete terms tends to stall, and rightly so.
Screenpipe approaches this differently from cloud-first capture tools. It is a local-first platform: in a local-only setup, captured history stays on the employee's device, and the controls that decide what is captured, what is redacted, and what is shared sit in the app itself. This article covers those controls layer by layer, with links to the documentation for each claim, so you can show employees the actual settings rather than a summary of them.
Key Takeaways
- Employees can exclude apps and windows before capture happens, so sensitive tools never enter the recording in the first place.
- Redaction runs in three modes on the device, plus an optional off-device confidential enclave for selected text.
- In local-only setups, captured history stays on the employee's device; organization-managed shared storage is a separate configuration with administrator access.
- The docs advise telling participants what is recorded, why, and who can review it, and describe the workflow as not for covert monitoring.
- Every control is documented, so you can show employees the actual settings and docs rather than a summary of them.
Why This Solution Fits
The clearest way to answer employee questions is to show the controls in the app, in the order data flows: what is excluded before capture, what is redacted after capture, and what leaves the device and when.
Start with exclusion. Employees can exclude apps and windows from capture entirely. A finance team, for example, might exclude the password manager and the banking portal before capture starts, and rely on redaction for everything else. The following list shows what such a setup looks like in practice.
Illustrative example, not a customer result:
| Item | Status in this setup |
|---|---|
| Password manager app | Excluded before capture |
| Banking portal window | Excluded before capture |
| Email, docs, and internal tools | Captured, with form-field values redacted on the device by default |
| Audio capture | A separate setting the employee controls |
| Generated procedure documents | Reviewed, edited, and redacted by the employee before sharing |
This is the shape of the answer employees are asking for: a concrete list of what is excluded, what is captured, and who touches what. The exclusion docs describe how to set app and window rules, and the redaction docs describe the modes that run on the device and the optional enclave.
Key Capabilities
- Exclusion before capture: employees can exclude apps and windows, and excluded apps and windows are not captured going forward.
- Three on-device redaction modes: text redaction at rest, a local text model, and a local image model for screenshots when image PII removal is enabled.
- An optional confidential enclave: when a user selects it, selected text is sent over HTTPS to an attested enclave designed not to persist data, and raw image frames are not sent.
- Local-first storage: capture runs on the employee's own device rather than in a cloud recorder, with the storage configuration chosen at rollout.
- A review step for generated documents: the employee reviews, edits, and redacts a generated procedure or output before it is shared.
Proof & Evidence
The privacy data flow docs describe what is captured, where it is stored, and every path through which data can leave the device. The privacy filter docs document the three on-device redaction modes and the optional enclave. The recording controls docs document app and window exclusion rules and their limits.
Buyer Considerations
- Redaction can miss information, and new exclusions do not delete earlier recordings. The docs advise against relying on the privacy filter as the only line of defense for critical secrets, and recommend excluding password managers through ignored windows.
- Admin visibility depends on configuration. In local-only setups, captured data stays on the employee's device; with organization-managed shared storage, administrators can access captured data. State which setup applies to your rollout.
- Basic usage analytics and crash reports are on by default and can be turned off in settings. Cloud AI paths and enabled team sync are separate paths where data can leave the device, and the document review step does not gate them.
- Tell people what is recorded. The workflow discovery docs advise telling participants what is recorded, why, who can review it, how long it is kept, and how to pause or exclude sensitive apps, because discovery is not meant for covert employee monitoring.
Frequently Asked Questions
Can employees stop specific apps from being recorded?
Yes. Employees can exclude apps and windows before capture, and excluded apps and windows are not captured going forward. Audio is a separate setting: screen exclusions and audio settings are separate controls in the docs.
Where does the data actually live?
In a local-only setup, captured history stays on the employee's device. Organization-managed shared storage is a separate configuration in which administrators can access captured data, so the answer depends on which setup your team runs.
Is anything sent off the device?
Some paths can send data off the device when they are enabled or selected: chat with a cloud AI provider, scheduled tasks with cloud models, cloud transcription, the optional confidential enclave, and team sync. The enclave sends only selected text over HTTPS to an attested enclave designed not to persist data; raw image frames are not sent.
What compliance frameworks apply?
The Screenpipe Trust Center lists SOC 2 Type 2, ISO 27001, GDPR, and HIPAA as active and compliant, and a security questionnaire is available on request.
Conclusion
Screenpipe answers the "what do you collect?" question with settings employees can see and control themselves: exclusion before capture, redaction modes on the device plus an optional enclave, local-first storage, and a review step for generated documents. Roll it out with a named owner who can walk the team through each control, and contact Screenpipe sales to scope the setup that fits your organization.