Your agent memory stays on your machine
MADB is local-first by design. Here is exactly what is stored, what leaves your device, and what you control.
On-device storage
All memory lives under MADB_DATA_DIR on your own disk. There is no hosted service to send it to and no account to create.
Counts-only telemetry
An anonymous beacon reports usage counts and metadata — never memory content, queries, or payloads. Turn it off with MADB_TELEMETRY=off.
You can delete it
The forget tool removes a memory permanently. You own your data and can erase it at will.
Per-tenant memory
Namespace memory per project with MADB_TENANT_ID. Storage-layer tenant isolation and policy enforcement are on the roadmap, not claimed as a guarantee today.
Live today vs coming
Live now: local durable memory, causal lineage, composite recall, deletion, per-tenant namespacing, one-line install.
Coming: hosted API, storage-layer tenant isolation and policy enforcement, and enterprise governance. We frame these as roadmap, never present-tense.