Einsia/OpenChronicle

This issue exposes a critical privacy vulnerability in `OpenChronicle`: indiscriminate capture of Accessibility (AX) tree data from sensitive applications. The current `AXSecureTextField` filter is insufficient, leading to potential exposure of password manager contents, private messages, and banking data. This represents a severe trust and security liability. The proposed `exclude_bundles` denylist, with sensible defaults and early-stage filtering, is an urgent requirement. Without robust, configurable privacy controls, `OpenChronicle` cannot achieve market acceptance as a secure personal data capture tool. Prioritizing data security and user control is paramount for any system handling personal information; failure to implement this will severely limit adoption and invite significant reputational risk.