What Vantic derives
With your permission via the macOS Accessibility API, Vantic IQ derives five categories of workflow signal:
Together these describe how work moves, not what the work contains.
What Vantic never collects
- Screen content, screenshots, or any recording of your display
- Keystrokes or typed text of any kind
- File or document contents
- Email bodies or message text
- Clipboard contents
Window titles
Window titles sit at the content boundary — not raw content, but capable of carrying meaning. Vantic hashes them at the point of capture using SHA-256. The original string is discarded immediately and cannot be recovered. Hashes are used only for detecting repetition and continuity — not for reading what the title said.Why “architecture” not “policy”
Content inside applications is not on the ingestion path. That is a different posture from “we collect everything and apply access controls.” The privacy boundary is structural — enforced at capture, not downstream. See Privacy-safe by architecture for the full explanation.Auto-exclusions
The following categories are excluded by default and cannot be re-enabled:- Password managers (1Password, Bitwarden, LastPass, macOS Keychain)
- Australian banking applications
- macOS system credential prompts and dialogs
Privacy-safe by architecture
How the structural privacy boundary works.
Privacy Hub
Add your own exclusions and manage your data.
