VaultBridge · Privacy Policy · Terms of Use · Support

Privacy Policy

VaultBridge · Effective date: October 23, 2026

VaultBridge processes your documents on your Mac. The desktop app has no network access, and the developer does not receive your documents. Text you choose to share with Claude is sent by your Claude app to Anthropic.

Zero Data Collection by the Developer

We collect no data from the app. VaultBridge requires no user account, registration, or login. The developer operates no servers, receives no document contents, maintains no telemetry or analytics SDKs, and tracks no user activity. If you email support, we receive your email address and anything you include, and use it only to reply. Please do not send documents or sensitive data by email.

On-Device Processing & Zero Network Access

VaultBridge processes files entirely on your local Mac:

App Sandbox: The macOS desktop application (VaultBridge.app) is sandboxed with no network client or server entitlements (com.apple.security.network.client and com.apple.security.network.server are absent).
No Network Code: The application contains no networking code, links no network communication frameworks, and initiates no socket connections.
No Runtime Downloads: All models, lexicons, and assets used by the application are bundled locally; nothing is downloaded over the internet at runtime.

What Stays on Your Mac

All sensitive information processed by VaultBridge remains strictly local to your device:

Original Documents: Source PDFs, scanned documents, and images remain in their original locations on your Mac. The desktop app accesses only files you choose in it. The MCP connector is not sandboxed: it reads whatever local file path your Claude client passes to it.
In-Memory Vault Mappings: Token mappings connecting original text values with placeholder tokens (such as [PERSON_1] or [DATE_1]) reside exclusively in volatile process memory for the lifetime of the active application or MCP server session. They are not written to shared storage and are discarded when the process exits or when you clear the vault.
Restored Output Files: When you restore an AI answer to a file, the output is saved directly into your local ~/Downloads folder with owner-only POSIX permissions (0600).
Clipboard Restoration: When you restore text to the clipboard, the unmasked plaintext is written to the macOS pasteboard tagged with concealed, transient, and auto-generated markers (org.nspasteboard.ConcealedType, TransientType, and AutoGeneratedType) so adhering clipboard history managers ignore it.

The Claude Connection & Third-Party Privacy Policies

VaultBridge includes an embedded Model Context Protocol (MCP) server that connects to your local Claude client (such as Claude Desktop or Claude Code). When you use VaultBridge with Claude:

Only Masked Text is Sent: VaultBridge replaces detected sensitive values with placeholders before returning Markdown text to Claude. Claude sees the masked text, including any value the detector did not catch.
Direct Transmission to Anthropic: Any text that you choose to submit to Claude is sent directly from your own Claude application to Anthropic's cloud services. That data is governed exclusively by Anthropic's Terms of Service and Anthropic's Privacy Policy. The developer of VaultBridge has no access to your conversations, prompts, or model outputs.
One-Way Restoration Boundary: When Claude invokes the local restoration tool (vault_restore_text), the substitution of placeholders back to real values occurs entirely on your Mac. The MCP server returns only confirmation metadata (such as {"restored_count": 4, "destination": "clipboard"}) to Claude. The tool never returns restored values to Claude.

Important Detection Limits & User Review Requirement

Automated detection can miss values. While VaultBridge uses a multi-tier detection pipeline combining regular expressions, on-device machine learning models, and contextual rules, automated detection cannot guarantee complete or error-free identification of sensitive information.

Detection may miss identifiers in non-standard formats, unlabelled account or policy numbers, out-of-vocabulary names, or health and medical details in free-form prose.
VaultBridge is not certified under, and does not by itself make your use compliant with, HIPAA, GDPR, or other laws.
You are responsible for reviewing masked output: You must always inspect the placeholder text generated by VaultBridge before submitting it to Claude or sharing it with any third party.

Information Apple May Share

If you have enabled sharing of diagnostic and usage information with app developers in your macOS settings, Apple may provide the developer with crash reports. This information is collected and processed by Apple under Apple's Privacy Policy. VaultBridge does not add document contents to these reports.

Changes to This Policy

Any updates to this privacy policy will be published on this page with a revised effective date.

Contact

If you have questions about this privacy policy, please contact us at ohioa4@gmail.com.