Message content
In supported encrypted spaces, messages and attachments are intended for the members of that space.
Security overview
Security needs clear boundaries
This page explains how MangoConnect protects supported private use cases, which operational data helps the service work, and what users can control.
What Mango protects
End-to-end encryption applies to supported direct chats, private groups, media and calls. Public chats and channels follow a different distribution model and are not E2EE spaces.
Devices and access
New devices, recovery and backup mechanisms are sensitive events and should be reviewed carefully.
Calls
Call protection depends on the supported mode, app version and the participants’ device setup.
The important boundary
End-to-end encryption protects content; it does not eliminate all service data. Technical and operational data may be processed for delivery, synchronisation and abuse prevention.
Mango does not claim “zero metadata”.
Account and device identifiers, delivery events, connection information, security signals, traffic volume and other operational data can be needed to operate the product. The exact set depends on the feature, client version and selected mode.
What you can do
1
Protect your device
Use a screen lock and do not share active sessions.
2
Review new-device and recovery events
Treat access, recovery and device-change notices as security-relevant events.
3
Use backup and notification settings deliberately
Backups, previews and system notifications can have their own protection boundary outside the primary chat.
Need a separate organisation infrastructure?
Mango Private adds a dedicated communication space inside the same app. Private messages, media and calls use the organisation’s dedicated server; not a byte of this traffic is sent through public infrastructure.
Open Mango Private