Private means device-to-device.
Private message and attachment content is end-to-end encrypted using MLS. Your server relays encrypted content; it does not have the decryption keys.
MILO / PRIVACY OVERVIEW
You should know what stays private, what your server can see, and what this website collects.
This static website has no analytics, advertising pixels, third-party fonts, account forms, tracking cookies, or local-storage identifiers. If you choose a light or dark theme, only that appearance preference is saved in your browser; choosing System clears it. The host serving the website may process IP addresses and ordinary access logs. Its handling of those logs depends on your hosting provider.
The following overview describes the product’s current technical boundaries. It is not a claim that Milo has completed an independent security audit.
Private message and attachment content is end-to-end encrypted using MLS. Your server relays encrypted content; it does not have the decryption keys.
Standard conversations are readable by the server and can be accessed by authorized administrators. They have a separate history from private conversations.
The server can still see information such as accounts, devices, contacts, message timing, and message sizes. Reports may include material you explicitly choose to share.
A new device cannot read private history from before it joined. If all keys are lost, that private history cannot be recovered from the cloud.
Account details, device relationships, and operational metadata are processed by the server you connect to. If you submit a report, only the material you actively provide and consent to disclose is included. Your server operator is responsible for its deployment, retention, and operational policies.
Milo is in development. Public platform signing, production deployment validation, and an independent security review remain release requirements. Check the source repository’s implementation status before production use.
Self-hosting