Teho

Activity Analysis trust

Privacy controls and deployment governance

This page explains how Activity Analysis is designed for team-level productivity insight, what is configurable in deployment, and how controls can be matched to your governance requirements.

What Activity Analysis captures

  • Work-pattern metadata from participating devices, grouped into workflow categories.
  • App and workflow interaction signals used to quantify time mix and friction patterns.
  • Optional screenshot capture when enabled by deployment policy, with display selection controls.

What it does not capture

  • The product is designed for aggregated team-level productivity diagnostics, not individual performance ranking.
  • Keystrokes, credentials, audio, and video content are not targeted by design.
  • Screenshot capture can be disabled entirely when policy requires it.

How privacy controls are configured

  • Configurable consent prompt and visible capture indicator.
  • Optional screenshot policy, including on/off and display capture mode.
  • Privacy guard rules to block sensitive apps and window-title keywords.
  • Optional app allowlists and denylists to keep capture focused on relevant tools.
  • Optional redaction (blur/pixelate) before upload.
  • Idle-time handling to avoid unnecessary capture.
  • Role-based access controls for operational visibility.

Data retention and deletion

  • Retention windows are configurable by deployment.
  • Screenshot purge policies can be applied to align with internal governance.
  • Data deletion can be scoped by engagement and policy requirements.

Team-level reporting approach

Output is designed to support leadership decisions about workflows, operating friction, and delivery priorities. The system is currently positioned around aggregated team-level reporting, with minimum participant thresholds used to preserve anonymity boundaries.

Deployment and governance options

  • Pilot one team, then expand by function once value and controls are validated.
  • Define policy profiles by business unit, geography, or risk class.
  • Align operating controls with HR, legal, and security stakeholders before scale.

Interactive view

Explore how privacy settings change the richness of insight.

The same Activity Analysis deployment can be tuned control by control. This interactive view shows the settings that matter most first, along with how each one changes privacy exposure and the richness of insight available to leadership. Team-level reporting remains aggregated by default.

Configuration summary

This configuration leans toward tighter control and a narrower evidence footprint.

Control 1

Screenshot capture

Usually the biggest governance decision, because it most directly affects visual evidence and perceived sensitivity.

Current setting

Off

Privacy: Lower visual exposureInsight: Less visual classification context

No screenshots are captured. Activity Analysis relies on non-visual work-pattern signals only.

Governance note

Useful for more cautious pilots or higher-sensitivity environments.

Control 2

Privacy guard rules

Controls how aggressively sensitive apps, windows, and keywords are excluded from capture.

Current setting

Stricter

Privacy: Lower sensitive-data riskInsight: Less end-to-end workflow visibility

More sensitive apps and window-title keywords are blocked, so screenshots are skipped and revealing title detail is removed more aggressively.

Governance note

Good when trust-building matters more than completeness at the start.

Control 3

On-device redaction

Changes how much readable detail is masked before evidence ever leaves the device.

Current setting

Stronger

Privacy: Lower readable detailInsight: Lower interpretability

More aggressive blur or pixelation is applied to screenshots before upload, reducing readable on-screen detail.

Governance note

Useful where screenshots are allowed but visible content still needs tighter protection.

Control 4

Display capture mode

When screenshots are enabled, this controls which screen is captured: all displays, the primary display, or the active display.

Current setting

Primary or active only

Privacy: Lower observable surfaceInsight: Less visual context

Screenshot capture is limited to the primary display or the screen currently in use, reducing visual exposure.

Governance note

A strong default when you want screenshots but need a more conservative posture.

Control 5

Application scope

Controls whether app allowlists or denylists are used to narrow which tools are included in capture.

Current setting

Focused app set

Privacy: Lower observable surfaceInsight: Less cross-tool context

App allowlists or denylists are used to keep capture limited to the tools most relevant to the workflow being studied.

Governance note

A useful way to keep pilots tightly aligned to the business question and reduce noise.

Control 6

Evidence retention

Controls how long screenshots and supporting evidence remain available for QA or review.

Current setting

Shorter

Privacy: Lower retained riskInsight: Less opportunity for QA and reruns

Evidence is purged more quickly, reducing retained visual data and shrinking the storage-risk window.

Governance note

A strong default if retention sensitivity is high.

Control 7

External context enrichment

Controls whether reports are grounded only in captured internal evidence or framed with broader market and benchmark context.

Current setting

Observed work only

Privacy: Lower additional context exposureInsight: More literal internal readout

Reports stay grounded entirely in observed deployment evidence without added contextual framing.

Governance note

Useful where teams want the cleanest possible line between captured evidence and interpretation.

Designed for team-level visibility, not individual performance ranking. These controls can be tuned together with legal, HR, and security stakeholders to match your governance posture.

Next step

Validate controls, then choose your starting path.

Book a 15 min discovery call to align scope, then use the sample report for internal review.

Get StartedView Sample Report