If this sounds like your week
When Windows Search gets in the way
privacy-conscious users want local recall without sending file names, query text, or path history to an account service. Windows Search is broad and opaque compared with the repo-visible index.db, config.json, and local log files under %APPDATA%\SearchSentinel. the daily irritation is disk churn across unrelated folders when the user only wants configured watched folders.
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 index.db - config.json - release path redaction - Tauri IPC - Local-first storage - No network logger - Release path redaction