Skip to content

Protect localized private windows across capture and retained evidence - #261

Merged
KAVentures merged 3 commits into
mainfrom
codex/private-window-protection
Oct 21, 2026
Merged

KAVentures merged 3 commits into
mainfrom
codex/private-window-protection

Conversation

@KAVentures

@KAVentures KAVentures commented Oct 20, 2026 •

Copy link
Copy Markdown
Owner

Explicit private-browser markers such as Chrome's Swedish/German (Inkognito) were not covered by the English exclusion rules. A fictional Quarterly report - Google Chrome (Inkognito) window could retain its title and interaction metadata.

This change recognizes explicit private-window markers at capture and ingest, independently of older saved exclusion lists. Read-time guards also hide retained private-window records in local evidence, derived context, AI responses (including Full), hosted projections and exports. Structural event/session IDs, timestamps and durations remain available. Ordinary work titles and resource references retain their context.

No startup migration or historical database rewrite is introduced. Historical rows and existing screenshot files are not deleted; the existing activity-deletion controls remain available for removing stored history.

Validation:

  • 27 privacy tests passed on this standalone branch, covering focus/click/copy/paste metadata, retained hosted projections, derived-context aliases, direct Activity rendering and normal-work false positives.
  • Combined follow-up suite: 1,884 passed, 1 skipped; 31 focused privacy/Activity/export/paging checks passed after the final display adjustment.
  • Fictional fixtures only; no user work records or titles are included in this PR.

The companion handoff PR, #262, is stacked on this branch. Neither PR should be merged automatically.

@KAVentures
KAVentures merged commit 69ef791 into main Oct 21, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant