threadVault · privacy boundary
Local-first by design
threadVault is a separate continuity product within the neuroVectoring umbrella, USA. This page explains the documented product boundary; it is not a medical claim.
What the application does not do
The application itself does not send vault contents to neuroVectoring, the developer, analytics services, or a cloud backend. It is documented not to make automatic outbound network requests, and its local interface is designed to bind only to loopback addresses.
No behavioral tracking is used. The product does not include telemetry, an account system, automatic updates, a background service, or a remote kill switch.
Email and delivery
Email is collected only to deliver a claimed copy. Optional updates require separate, affirmative consent; declining updates does not change delivery. A non-subscriber delivery address is removed after successful delivery plus the 30-day support window. Pseudonymous claim records are scheduled for deletion 90 days after the final drop, while aggregate counts may remain.
Delivery and basic setup help are available on a best-effort basis for 30 days after delivery. The public support address is support@neurovectoring.com.
Source and intake boundary
Original provider exports stay higher-authority evidence. AI-assisted intake, continuity views, and candidate categories are derived, traceable layers—not replacements for source.
If a person chooses to upload a copy of an export to an AI provider to create intake, that is a separate user-initiated provider interaction governed by that provider’s settings and terms. threadVault does not need provider passwords, cookies, tokens, or API keys.