If this sounds like your week
When Windows Search gets in the way
corporate users search customer names, ticket IDs, and internal filenames that should not become analytics payloads. Windows Search lacks the repo-visible guarantee that Search Sentinel logs local JSON lines and avoids network output. incident response often means sensitive path names are typed while screen sharing and logs are open.
Where tooling usually breaks
Why local-first matters
index.db, config.json, and logs stay under %APPDATA%\SearchSentinel instead of a vendor-hosted workspace. Search queries are not uploaded for AI enhancement, analytics, or ad targeting. You buy the app once and keep the search index as a local workstation asset.
Technical proof points
- Local JSON-line logs - 7-day retention - Query length logging - Release path redaction - Local-first storage - No network logger