Skip to content

Sensitive-app exclusions ​

The Sensitive-app exclusion card tells the tracker to censor content while specific apps, domains, or windows are in focus. Censored time still appears in the timeline — but the screen-recording clip is blacked out and the window title isn't sent for AI analysis.

Why this exists ​

Even orgs that monitor screens generally don't want to capture:

  • An employee's bank statement while they're checking their personal account on lunch.
  • The payroll dashboard while HR is processing salaries.
  • A health-portal visit during a doctor's appointment.
  • Adult content the employee may have left open by mistake.

The sensitive-app exclusion list is how you handle that without turning off recording wholesale.

Two parts ​

The card has two halves:

  1. Category packs — one-click bundles for common sensitive categories.
  2. Custom blocklist — fine-grained rules you can add by hand (process name, app path, domain, window title substring).

Category packs ​

Enable a pack by ticking it. Each pack ships with a curated list of domains and apps that match the category. Available packs:

PackExamples included
BankingChase, Wells Fargo, HSBC, and the other large retail banks.
PayrollGusto, ADP, Paychex, Rippling, Deel, …
HRWorkday, BambooHR, SuccessFactors, Lattice, …
HealthMyChart, Anthem, Cigna, Kaiser, BlueCross, NHS, …
AdultWell-known adult sites.

The exact list inside each pack is maintained by ScreenJournal and updated as new providers appear. You don't need to keep the lists up-to-date yourself.

macOS Accessibility caveat ​

The Adult pack — and any browser-domain rule generally — requires the macOS Accessibility permission so the tracker can read the URL of the focused browser tab. If accessibility isn't granted, browser-domain rules silently fail to censor on macOS. The tracker prompts the employee for accessibility on first launch.

Custom blocklist ​

Below the packs is the Custom blocklist. Each row is one rule. A rule has three parts:

  • Kind — what to match against:
    • Process name — e.g. Google Chrome. Matches any window in that process.
    • App path — e.g. Chase.app/Contents/MacOS/Chase. Useful for app-bundle precision.
    • Domain — e.g. chase.com. Matches the focused browser tab's URL.
    • Window title contains — e.g. Online Banking. Matches any window whose title contains that substring.
  • Value — the actual string to match.
  • Label (optional) — a human-readable note shown in the row so you remember why the rule exists.

Click Add entry to add a new row, set the kind / value / label, and save the policy.

Tips ​

  • Window title rules are the most portable — they don't depend on app identifiers or browser URL detection. Good for capturing workflows that span multiple apps.
  • Domain rules are the cleanest for browser-based tools, but remember the macOS Accessibility caveat above.
  • App path rules are useful when an organisation uses both the Mac App Store version and a self-distributed version of the same app — you can target one path without affecting the other.

Org vs team ​

For v1 the sensitive-app card behaves slightly differently from the boolean policy fields:

  • At org scope, packs and the custom blocklist are fully editable. This is the org-wide default.
  • At team scope, the org's effective packs and blocklist are shown read-only, so you can see what's currently in effect for the team. Team-specific overrides for sensitive-app rules are not yet supported.

If you need different sensitive-app rules per team, manage them at org scope for now and watch the changelog.

What the employee experiences ​

When a sensitive-app rule matches:

  • The screen-recording video for that segment is blacked out.
  • The window title is not sent for AI analysis. The timeline shows a generic "Sensitive content" placeholder for that segment.
  • Productivity scoring for the segment is neutral by default.

The employee sees the same neutral placeholder in their own Activity view. From their perspective the censoring is automatic — they don't have to remember to pause the tracker before opening their bank.

ScreenJournal end-user documentation. For sales or account questions visit screenjournal.ai.