Security and privacy
Zephr is local-first. In local mode, nothing leaves your machine: the server speaks stdio JSON-RPC to the client that launched it, and the database is a file you own.
What is local
The server stores evidence in a single SQLite file scoped by worktree. It does not scrape editor state, chat history, or project indexes — every capture is an explicit tool call the agent chose to make.
Encryption at rest
The local SQLite database is not encrypted by Zephr at rest. The file is stored as SQLite
writes it; Zephr does not apply its own encryption layer. If you require encryption at rest,
place the database file on an encrypted filesystem or disk volume. The ZEPHR_DB_PATH is simply
a filesystem path you own.
Access control
- Admission scope — tool calls outside the admitted worktree are rejected with
scope_violation. - Separated capabilities — the store, the read view, and the admin capability are separated
per ADR-Z-02; destructive operations require a minted
ZEPHR_ADMIN_TOKEN.
No network in local mode
Local mode performs no network egress as part of normal operation — the process speaks stdio to the client that launched it.