trust, privacy, security
Trust, privacy, and security
Honest posture for self-hosted operators: what MEL assumes, what it does not promise, and where to read the full contracts.
Local-first and data ownership
MEL is designed to run on hardware you control. Base viability does not depend on a mandatory cloud control plane. What leaves the host — MQTT, backups, exports — is a configuration choice you must review.
Deep read: Privacy and data posture, Privacy posture.
Telemetry and outbound behavior
There is no “quiet phone home” narrative here — defaults and optional integrations must stay explicit in config and docs. If you enable broker backhaul or remote exposure, treat that as an operator decision with reviewable scope.
Security reporting
Report vulnerabilities responsibly: see SECURITY.md in the repository. Do not post secrets or precise location payloads in public issues.
Control-plane safeguards
Trusted control means separable lifecycle states and attributable records — not flashy buttons that blur intent and execution.
Control-plane trust (operations) · Control-plane trust model (architecture).
License
MEL is open source under GPL-3.0 — see LICENSE. Bundled dependencies (Go modules, npm) carry their own licenses.