miton

In development. The beta will be a downloadable desktop app with automatic updates. Access is not open yet.Request an invitation.

Trust centre / reviewed 23 July 2026

Safety is a system of visible boundaries.

Miton is powerful enough to change a project. That makes permission, untrusted input, secrets, network egress and recovery product concerns—not policy-page decoration.

01 / Data boundaries

What stays local. What may leave. Who decides.

Project data
Local
Project files, conversations, goals, workflows and local indexes live on the machine running Miton.
Model requests
Your chosen boundary
A hosted model receives the context required for a turn when you allow that provider. A local model keeps inference in its local process.
Provider keys
OS-backed secret storage
Bearer tokens and model credentials stay out of localStorage and plaintext application state.
Diagnostics
Off
Usage sharing, crash reports and response feedback are independent controls and remain off until enabled.
Beta access list
Encrypted first-party record
The site stores an HMAC index and AES-GCM ciphertext in D1, without IP, browser or tracking fields.

02 / Controls you can inspect

The privacy defaults are part of the interface.

Diagnostics are not bundled behind one vague toggle. Local media processing is named. Learning prompts require approval. Permission modes and project trust decide what tools may do before a write begins.

A current deterministic capture of the production Safety and privacy controls. This is literal interface evidence, not a product render.

Literal capture · daylight · captured 2026-07-23

Literal capture · daylight · captured 2026-07-23A current deterministic capture of the production Safety and privacy controls. This is literal interface evidence, not a product render.
Current Miton Safety and privacy settings showing local processing and disabled data-sharing controls.

03 / Injection

Treat instructions as data until they earn trust.

Retrieved pages, files and tool output can contain hostile instructions. Miton scans input, records injection signals and keeps the permission policy responsible for the final action.

04 / Egress

A network request should leave a trace.

Supported WebView and Rust request paths feed an egress ledger. The completeness guard checks both surfaces so “audited” does not mean “we searched one half of the app”.

05 / Recovery

Trust improves when action is reversible.

Project changes can be reviewed, permission prompts remain explicit and rewind gives a session-level way back. Recovery does not replace judgement; it changes the cost of a bad judgement.

WebView and Rust requests cross the same accounting boundary. The diagram explains the system; the linked tests and ledger surface establish the claim.

System diagram · verified 2026-07-23

System diagram · verified 2026-07-23WebView and Rust requests cross the same accounting boundary. The diagram explains the system; the linked tests and ledger surface establish the claim.

Responsible disclosure

Report privately. We will investigate openly.

Do not open a public issue for a suspected vulnerability. Emailsecurity@miton.dev. Include affected versions, reproduction steps and impact. Miton aims to acknowledge a report within 48 hours and coordinate disclosure after a fix is available.

Supported pre-release versions and the full reporting policy are maintained in the repositorySECURITY.md.