Questions, answered with links 

No Vaultr-operated server exists for matter data. In local mode, processing runs in the application process on your machine; the only outbound actions are ones you start — updates and model downloads. The distinction between this and “we promise not to look” is architecture, and the boundary test exists so you can verify it yourself rather than believe us.

In local mode nothing crosses the boundary. A firm endpoint sends prompts and retrieved passages to a host you operate, inside your perimeter. An external provider sends them to a third party you explicitly name. The mode is shown beside the run action; there is never a silent fallback. Full comparison in the mode matrix.

In the application's per-matter directory on your disk. Deleting a matter removes its index, outputs and ledger entries — there is no server-side copy to outlive the deletion. Backups are whatever your own machine backup captures. Details in the retention table.

No — and in local mode we could not, since we never receive it. This is one of the two questions vendors most often answer with reassurance instead of facts (the other is silent fallback), and our one-line answers are on the record in the procurement checklist post.

You do not trust it — you check it. Every finding carries the passage it came from, at page, line and clause. When a citation cannot be resolved, the system reports not found rather than improvising. The interactive demonstration shows the full shape on sample data.

The proposal waits at a checkpoint and counsel decides — accept, edit or reject. Wrongness is caught by review, not by hope, and the decision ledger records which human decided what. That is the honest limit of the design: the ledger proves provenance, not correctness.

There is no published benchmark to quote — when one exists, it will carry its full measurement configuration. The responsible claims policy explains why an unmeasured figure is worse than an honest pending state.

Assisted evaluation, by request. No public download, no self-service sign-up. The evaluation is shaped around your own bundle and your intended processing mode — that is the part a download cannot replicate. The commercial model page states the whole shape in writing.

Any charge is agreed in writing before installation, with no automatic renewal and nothing metered on your matter data — in local mode, metering it would require seeing it. The full terms are on the commercial page.

macOS on Apple silicon is the tested target. Windows and Linux builds are planned, not released. 16 GB unified memory minimum for small local models; 32 GB or more for long bundles. Setup is guided install on one firm-managed device, in the processing mode you want to test.

You keep your notes and exported artefacts. There is no obligation to continue.

Yes — AGPL-3.0, with the licence text, upstream attribution and history in the public repository. Your security team can read what runs before it touches a matter: github.com/sabarinath1805-loyal/Vaultr-AI.

No, and we say so in the not-done list rather than borrowing a cloud provider's certification. The one conformance statement we do publish — OpenChain licence compliance, self-certified — is scoped to exactly what it is, and the post explaining it covers what that does and does not mean.

Start with the security review packet, run the boundary test on your own machine, and bring the ten questions from the procurement checklist to every vendor — us included.