Public identity
The public Mango account is the user’s baseline identity.
Mango Private security
A separate communication space, with a clear boundary
Mango Private adds a dedicated organisation space inside the Mango app: its own server, separate connection and an independent path for private traffic.
How the spaces are separated
A user starts with a Mango public account and connects an organisation’s private space by invitation. The app keeps the two communication contexts visibly distinct.
Organisation invitation
An individual or shared code connects the user to the dedicated private space.
Private data path
Messages, media and calls for that space use the organisation’s connected server.
Not a byte becomes public traffic
Private messages, media and calls are sent only through the organisation’s dedicated server. If its connection is unavailable, not a byte of private traffic is sent through Mango Public infrastructure.
Scope of the offer.
Mango Private is developed through controlled pilots and long-term partnerships. Deployment, logs, updates, backups and support are agreed before launch; this page does not replace a customer contract, design review or threat model.
Foundation in Mango security
Mango Private follows Mango’s documented principles for supported encrypted scopes, metadata boundaries, devices, backups and notifications. It is not a claim of zero metadata, certification or absolute invulnerability.
Read the Mango security overviewDiscuss a private space for your organisation
Tell us about users, deployment environment and the communication workflow; together we can determine whether Mango Private is suitable for a pilot.
Discuss a pilot