Repository navigation
Protect localized private windows across capture and retained evidence - #261
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explicit private-browser markers such as Chrome's Swedish/German
(Inkognito)were not covered by the English exclusion rules. A fictionalQuarterly 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:
The companion handoff PR, #262, is stacked on this branch. Neither PR should be merged automatically.