Security
How Arche 1.0 is built so you can trust it with real life.
Sealed vault
Secrets are encrypted at rest and masked everywhere — in chat, traces and the model context. The agent only ever receives references like sec_••••. Reveal is for your eyes alone, on your device.
Approvals by default
Sensitive actions (apps, browsing, external writes) pause for your explicit yes — or an always-allow rule you can revoke under Vault → Approved.
Sandboxed agentic harness
Code, browser and computer use run contained with an allowlisted network. GitHub access is read-only via your own per-request token (sent only to api.github.com, never stored or logged). Every step lands in the visible Trace tab.
Auth & transport
Real Supabase Auth; the backend verifies your JWT on every stateful request and derives your user id from the token. Security headers and per-IP rate limits are on.
Report an issue
Found something? hej@belna.se — please include steps to reproduce and avoid sending real secrets.