# Local-first & private

The Den is local-first by design. Your memory lives in a service running on your own machine, the vault keeps the most sensitive memories access-locked, and the explorer's status panel tells you exactly what's connected — and what isn't.

## Where your memory lives

The Den is a local daemon — foxmemd — that listens on 127.0.0.1:7777, a loopback address that never leaves your device. Agents read and write memory by talking to that local service, not a cloud API. Your accumulated knowledge — the Palace, every memory, every provenance node — is stored on your machine.

This is the same principle that governs the rest of your data in Foxora: the things that are yours stay local. For the full picture of what’s on-device versus in the cloud, see Where your data lives.

## The vault

Not every memory should be equally reachable. The vault root is access-locked — the explorer marks it with a lock icon, and memories placed there are held to tighter access than the open roots like work or life. Use it for the context you want remembered but guarded: credentials-adjacent notes, private preferences, anything you wouldn’t want an agent to surface casually.

> Scoped accessThe Den grants memory access by capability over a locus scope — an agent can be allowed to read work.** while the vault stays off-limits. The vault is the most restrictive end of that model.

## The service status panel

Because the Den is a service, the explorer gives you a window into its health. Select Status Info at the top of the Palace rail to open the service panel, which reports:

- Service — connected, checking, or unreachable.
- Server — the local address the Den is listening on.
- Memories stored and Loci — how much the Den holds.
- Vector index — whether semantic recall is on (otherwise recall falls back to keyword search).
- Version and Last checked — the running build and the freshness of the status.

## Local vs cloud

It’s worth being precise about the boundary:

- Local — the Den service, your Palace, every memory and its provenance, and the vault all live on your device.
- Cloud — agent execution may run in Foxora’s cloud, and embeddings used to power semantic recall are generated through the gateway. The memories those embeddings index, though, stay local.

> One source of truthBecause there’s exactly one Den per device and it’s local, you never have to reconcile two copies of what an agent “knows.” What you see in the explorer is what every agent reads.

> Memory is tied to your deviceLocal-first cuts both ways: a memory written on one machine lives on that machine. Treat the Den as device-local context, and lean on the data-location guarantees for the full story of what is and isn’t synced.