screenpipe.com

Command Palette

Search for a command to run...

Task Mining That Lets Employees Exclude Apps and Screens

Last updated: 11/20/2026

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.

Task Mining That Lets Employees Exclude Apps and Screens

Screenpipe is a task mining tool built so employees can block specific apps and windows from capture before anything is recorded. This article walks through how exclusion works, how on-device redaction handles what is still captured, and what an operations buyer should check before rolling it out to a team.

Introduction

When a team evaluates task mining, the first question employees ask is usually not about reports. It is about control: can I keep my personal browsing, my banking tab, and my HR portal out of the record entirely? A tool that answers that question clearly is far easier to deploy, because people only accept capture when they can see where the boundaries are.

Screenpipe runs locally on each employee's device and captures screen activity continuously while it is running. The recording controls docs document how to exclude specific windows and URLs from capture, so excluded apps and screens are not recorded going forward. This article covers that exclusion layer, the redaction modes that handle what is still captured, where data is stored, and the conditions to confirm with your team before a rollout.

Key Takeaways

  • Employees can exclude specific apps, windows, and URLs before capture, so those screens are never recorded in the first place.
  • Redaction runs in three modes on the device, and an optional confidential enclave handles selected text off-device.
  • Exclusion lists are set per app and per URL, so the same list can cover an entire team.

Why This Solution Fits

Consider a consulting firm whose employees handle regulated client work in dedicated applications. The firm wants task mining on the operational tools, the project tracker and the internal CRM, but the client's compliance portal must never be captured. With Screenpipe, the employees add the compliance portal's window and URL to the exclusion list, and those screens are not captured going forward. Everything else, the work the firm actually wants to measure, is captured continuously.

The exclusion list is the first layer. The redaction layer handles what is still captured: form-field values such as passwords, card numbers, and secrets are redacted on the device by default, before they are stored or sent. Three redaction modes run on the device (text redaction at rest, a local text model, and a local image model when enabled), and an optional confidential enclave sends selected text off-device over HTTPS to an attested enclave designed not to persist data; raw images are not sent to it. The privacy filter and privacy data flow docs describe these modes and what is sent where.

An illustrative exclusion setup for that firm looks like this (illustrative example, not a customer result):

ItemTreatment
Client compliance portal (URL)Excluded from capture
Personal banking and email tabsExcluded from capture
Project trackerCaptured
Internal CRMCaptured, form-field values redacted on device by default
Password fields anywhereRedacted on device by default, before stored or sent

What this shows is that the boundary is set per app and per URL, not per employee. An employee who works with regulated clients all day can have the same exclusions as one who never touches them, and the captured record still contains enough history for time summaries and workflow discovery on the operational tools the firm wants to measure.

Key Capabilities

  • Exclusion before capture: specific apps, windows, and URLs can be excluded, and excluded screens are not captured going forward.
  • Three on-device redaction modes: text redaction at rest, a local text model, and a local image model when enabled, plus the optional off-device confidential enclave for selected text.
  • Local-first storage: capture runs on each employee's device rather than on a central recorder.
  • Review before sharing: the team follows a step where an employee reviews, edits, and redacts generated documents before they are shared; cloud AI and enabled team sync are separate paths where data can leave the device.
  • The local REST API and MCP let an agent read captured history for drafting and analysis.

Proof & Evidence

The recording controls docs document what can be excluded and the limits of exclusion and redaction. Screenpipe also runs a workflow report pilot for one team, up to 10 machines, arranged through sales. The pilot structure includes the scoping step where the team decides what is captured and what is excluded.

Buyer Considerations

  • Redaction can miss information, and new exclusions do not delete earlier recordings, so set the exclusion list before rollout rather than after.
  • In local-only setups, captured history stays on each employee's device; with organization-managed shared storage, admins can see data, so decide which setup applies before deployment.
  • Basic usage analytics and crash reports are on by default and can be turned off in settings, which matters when you document every path that leaves the device.
  • Per the Screenpipe Trust Center, Screenpipe is SOC 2 Type 2, ISO 27001, GDPR, and HIPAA compliant.

Frequently Asked Questions

Can employees block specific apps and screens from being recorded?

The recording controls docs document how to exclude specific windows and URLs from capture, and excluded apps and screens are not captured going forward.

What happens to passwords and card numbers that appear on captured screens?

Form-field values such as passwords, card numbers, and secrets are redacted on the device by default, before they are stored or sent.

Where is captured data stored?

In local-only setups, captured history stays on the employee's device. Organization-managed shared storage is a separate setup, and cloud AI and enabled team sync are additional paths where data can leave the device.

Does redaction remove every piece of personal information from recordings?

Redaction can miss information, which is why exclusion before capture is the layer to use for screens that should never be recorded at all.

Conclusion

Screenpipe gives employees a clear boundary: excluded apps and screens are not captured, form-field values are redacted on the device by default, and the storage setup decides who can see the record. Set the exclusion list with your team before rollout, and contact Screenpipe sales to scope a pilot.

Related Articles