Documentation · Compliance
Clear boundaries, verifiable records
Data residency
Your conversation data, run traces and telemetry live in the control plane database; your files and apps stay on your machine. LLM requests are sent to the provider you chose (or the auto-routed default) with your own API keys — the operator never sees or proxies your provider credentials.
Audit & retention
- Every run, step, token count and cost is recorded with a timestamp.
- Sensitive account actions (key management, token generation, 2FA changes, resets) are appended to the per-user audit log with IP.
- You can export your own conversation data as JSONL for fine-tuning (Settings → Deep Dive export) and wipe everything with the factory reset.
GDPR-friendly controls
- Right to erase — factory reset removes agents, conversations, tasks, tokens, keys, telemetry and audit history for your account.
- Minimal device footprint — only a revocable key on the device; no provider keys, no logs of your files.
- Right to know — the append-only audit trail shows exactly what ran, when, and at what cost.
Licensing
The client and control plane are MIT licensed and open source — MONAEXPERT/agent (client, engine, protocol) and MONAEXPERT/backend (control plane). No lock-in: the same protocol works with a self-hosted plane.
Self-hosting. Because the agent dials out over plain HTTPS and the API is documented, you can point
MONA_CLOUD at your own deployment. See Architecture.© 2026 remoteagent.onlineGitHub: docs/COMPLIANCE.md ↗