What we do protect against, and what we do not.
The boundary is written down. Read it before you trust it.
In plain words
No product protects against everything. This page states plainly which risks Provenize helps with and which it does not.
An example: if someone takes over your laptop while you are logged in, Provenize will not stop that. We do not hide that kind of thing.
Where the boundary sits
Four boundaries, and what crosses each one.
- Your machineyour files, the search index, the log and the keysnothing leaves unless you send it
- An external modelonly your question and the quoted snippetsnever your files, never the index
- The connector for your AI toolsyour own computer only, new token per startno remote client can reach it
- An auditorsigned roots and receiptsenough to verify, not to read
What we assume
What we take as given — if these fail, the guarantees fail.
- Your operating system and disk are not already compromised.
- You control who can run the application on this machine.
- The external model provider honours its own no-training terms.
- Your own key handling is sound while at-rest encryption is planned.
Deliberately not built
Absent by choice, not by backlog.
- No hosting of client corpora
- No deep Microsoft-cloud coupling
- No cloud models at the core
- No code execution
Known limits
Said out loud, because a threat model that flatters itself is useless.
- Removing personal details does not always workBuiltworks on patterns; we publish the known gaps
- Encrypted storage on diskPlannedlocal storage is not yet encrypted
- Separate checking app for othersPlannedchecking currently needs our software
- Your own keysPlannedwe do not hold your keys, but you cannot rotate them yet
- Set of compliance documentsPlanneddrafted with counsel, not written yet