What Vantic derives
With your permission via the macOS Accessibility API, Vantic IQ derives five categories of workflow signal:| Signal | What it captures |
|---|---|
| Active application | Which app is in focus, identified by bundle ID |
| Timestamps | When focus changes |
| Session duration | How long you stay in an app before switching |
| Transition sequence | The order in which you move between apps |
| Transition timing | How quickly you switch — a proxy for context switching overhead |
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 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 by architecture
How the structural privacy boundary works.
Privacy Hub
Add your own exclusions and manage your data.