Zero-knowledge mind mapping
Private mind maps. Truly encrypted.
Zero-knowledge architecture with client-side keys. Your ideas stay yours.
Zero-knowledge mind mapping
Zero-knowledge architecture with client-side keys. Your ideas stay yours.
Why it feels different
Built for ideas that are still messy, sensitive, or early. Your maps, notes, and structure stay yours. Fully encrypted. Never readable by the server.
Learn library
Privacy and local‑first concepts explained in plain language, so you can evaluate the trust model with confidence.
Modes and plans
Three public product lanes plus an on-premise path, presented simply so the trust model stays easy to evaluate.
Cloud Free
Private cloud vaults with up to 25 MB total encrypted storage.
Cloud Pro
Increase the encrypted cloud storage limit to 250 MB without changing the trust model.
Desktop Local + Self-Hosted
Choose the fully local desktop path or run MindMapVault on your own infrastructure with PostgreSQL and S3-compatible storage.
On‑Premise Installation
Deploy MindMapVault inside your environment while preserving the zero‑knowledge model.
Email usWhat is included
Why it matters
How MindMapVault compares to other mind mapping and note apps — especially on privacy.
| Category | MindMapVault | MindMeister | XMind | DeepNotes | Standard Notes | Obsidian |
|---|---|---|---|---|---|---|
| Pricing baseline | $10/year | ~$78/year | $59/year | $60/year | $90/year | $48/year |
| Mind maps native | Yes | Yes | Yes | Partial | No | Partial |
| Client-side encryption model | Always for hosted vaults | No | Not core | Yes | Yes | Optional |
| Offline/local-first path | Yes | Mostly hosted-first | Yes | Yes | Yes | Yes |
| No admin-readable backdoor | Explicitly yes | No | No | Partial | Yes | No single strict promise |
Privacy and Mind Mapping focused alternatives guides in a static view: open a card to compare trust models in detail.
Compare privacy boundaries, hosted access, and workflow fit for visual planning.
See where local workflows, collaboration needs, and trust assumptions diverge.
Review encryption posture, note visibility, and long-term ownership tradeoffs.
Evaluate note privacy strengths versus mind mapping and structure-first workflows.
Compare local-first paths, encryption assumptions, and visual knowledge mapping.
Install MindMapVault through the platform stores for the current desktop path.
Common questions about encryption, data handling, and product limits — answered directly and published as plain HTML with structured data for search and AI retrieval.
There is no password recovery for existing encrypted vault contents. If you lose the credentials that unlock your vault keys, the content is lost by design.
The goal is downgrade, not surprise deletion. Paid storage falls back toward free-tier limits, and you can export or reduce data if over quota.
Yes. The storage model is built around versioned encrypted blobs so a vault can keep historical saves instead of only the latest state.
Stored data includes account details, encrypted vault metadata, encrypted blobs, and billing records when relevant. Logs are operational and should not contain plaintext notes or keys.
Decryption happens in the browser or desktop app after local unlock. The backend stores ciphertext and serves encrypted payloads.
Today the focus is the web UI and desktop apps. Mobile clients are not the priority yet.