PRIVACY BY ARCHITECTURE

Nothing leaves
your Mac. Ever.

VAULT runs entirely on your machine. No telemetry, no accounts, no cloud round-trips. The pages below explain exactly where your data lives and how it's processed — plain enough to read in five minutes, precise enough to verify in thirty seconds.

The details
01 · Storage

Your memories live in a single file.

That file is a SQLite database. It's on your disk, inside your user folder, protected by macOS like every other app's data.

Finder — VAULT
$ open ~/Library/Application\ Support/VAULT
VAULT/
├─memories.dbSQLite database
├─embeddings/vector cache
└─config.jsonyour preferences

01

You own the file

Back it up, move it to a new Mac, inspect it with any SQLite viewer, delete it. The database is yours.

02

No server, no sync

VAULT never opens a socket to a remote host. No account, no upload, no background sync.

03

Sandboxed by macOS

The app only has access to folders you explicitly grant. Full-disk access is opt-in.

02 · AI Processing

The AI runs on your CPU.

Every embedding, every semantic search, every summary — computed on your Apple Silicon chip by a local Ollama server. Zero network calls.

A file, from import to search result
Your file
PDF · MD · IMG · MP3
Parser
on-device
Ollama
Apple Silicon
Vector
float[768]
SQLite
~/Library/...
All five steps happen on your Mac
Cloud AI · Typical stack

Your file leaves your machine.

  • Upload to OpenAI / Anthropic / Google
  • Stored on vendor servers (even if transiently)
  • Processed on GPU clusters you don't control
  • Subject to the vendor's retention policy
  • One API outage = search broken
VAULT · Local-first

Your file never moves.

  • Processed by Ollama on your Apple Silicon
  • Embeddings written to local SQLite
  • Runs without network entirely (verify in Airplane Mode)
  • Retention policy: you delete when you want to
  • Works the same on a plane, in a tunnel, offline
03 · The models

You can see them. You can delete them.

VAULT downloads its models through Ollama once, then keeps them on disk. Nothing is hidden — open Terminal and list them yourself.

Terminal — ollama list
$ ollama list
NAMESIZEMODIFIEDnomic-embed-text274 MB2 days agollama3.2:3b2.0 GB2 days agogemma3:4b3.3 GB5 days ago
Stored at: ~/.ollama/models · Remove any time with ollama rm <name>
04 · Verify

Don't take our word for it.

Three thirty-second tests that prove VAULT doesn't talk to the network. Run any of them, any time.

01

Activity Monitor

  1. Open Activity Monitor → Network tab
  2. Search for “vault” or “ollama”
  3. Watch the Sent Bytes column while you use the app
  4. It will stay at 0 kB.
02

Airplane Mode

  1. Turn on Airplane Mode (or disconnect Wi-Fi + Ethernet)
  2. Open VAULT, add a file, search semantically
  3. Everything still works.
  4. A cloud-dependent app would error out here.
03

Little Snitch / Lulu

  1. Install any outgoing-connection firewall
  2. Launch VAULT
  3. No rule is ever requested — the app makes no outbound calls
  4. (Ollama only binds to 127.0.0.1)

Ready when you are.

Install VAULT and verify everything above on your own machine in under a minute.