Security & trust

Posture

Desktop app posture

Sandboxed windows

Main, Amethyst and overlay alike: page code cannot reach Node, and all capability access crosses a preload bridge. Each IPC channel validates its sender and shape; payloads are rebuilt, never passed through raw.
Default-deny input

The overlay is born click-through, non-focusable, and never accepts input. Amethyst’s mouse routing is default-deny: click-through is re-earned only while the cursor is over real character pixels.
Keystore sessions

OAuth happens in your system browser, never inside the app window; session tokens are stored encrypted via the OS keystore (DPAPI on Windows) in the main process — never in renderer localStorage, never in a URL.

AI provider keys live in Edge Function environment variables on the server. The client sends only your session token and its publishable key — both public by design.
Conversations live in a local SQLite file in your OS app-data folder, with per-user ownership checks on every query.
Screenshots are transient; mic audio is dropped after transcription; overlay geometry lives in main-process memory for the draw and is then deleted.
Database rows derive your identity from the verified session token server-side — a client cannot forge an owner id.

No published audit. No independent security audit or certification (SOC 2, penetration test) has been published. Treat any such claim elsewhere as false until it appears here.
Per-OS-user isolation. Local isolation is per-OS-user: anyone with access to your Windows account can read the same local database.
Transit, not storage. When you send an AI request, its content is processed by the gateway and the AI provider — provider-side retention windows are not contractually verified yet (see the privacy draft).

Draft item: security contact address and disclosure policy need to be confirmed before publication — see Contact & support.

Keep reading

Privacy policyDOT404’s privacy policy in draft: what stays on your device, what travels to the AI gateway when you ask, and the facts that must be confirmed before publication.
AI transparency & limitationsExactly what DOT404’s AI can see, what it never sees, and where it can be wrong: grounding misses, mock replies when signed out, and answers that are not advice.
DocumentationHow to run DOT404: the main window, the composer, Amethyst’s pill, screen questions, voice, teaching mode, settings and where your data lives.
Contact & supportHow to reach the DOT404 team for support, security reports and general questions — with an honest note on which channels are not public yet.