Camera and microphone
Needed for calls, voice messages, video, and media. Access can be revoked in OS settings.
Data Collection Policy
Mango Private data collection policy
A practical companion to the privacy policy: which data categories Mango Private collects on your organization's server, what they're used for, and where collection stops.
Collection principles
Mango Private is developed by OffshoreLabs Studio LTD, a company registered in the United Kingdom under company number 17387215. Each Mango Private instance is deployed on infrastructure controlled by the purchasing organization (the "operator"). All user data resides on the operator's own server.
- We only collect what's needed for a private corporate messenger, security, and support.
- We do not use user data for ad targeting and we do not sell it.
- We do not upload the device address book in full.
- We do not collect payment data, advertising identifiers, or biometrics.
- Each permission is used only for its specific feature: camera, microphone, photos / gallery, notifications, location.
- OffshoreLabs does not have access to your organization's data unless the operator explicitly grants access for support purposes.
Data categories
| Category | Examples | Why it's needed | Who has access | Retention |
|---|---|---|---|---|
| Account | User ID, invite, name, nickname, avatar, registration date | Registration, profile, search inside Mango Private, chat access | Organization operator, members of chats where the profile is visible | While the account is active or the data is needed for security / law |
| Chats | Chat ID, type, title, avatar, members, roles, mute / read state | Chat list, access rights, notifications, history | Chat participants, organization operator, node infrastructure | While the chat exists or is needed by members |
| Messages | Text, emoji, replies, reactions, edits, deletes, forwarded metadata | Message delivery, local history, statuses, security | Chat participants, organization operator, node infrastructure | Until deleted or while history is needed by participants |
| Location in a message | Coordinates if the user actively sent a location attachment | Show the chosen point in the chat | Chat participants, organization operator, node infrastructure | As part of the message history |
| Media | Photos, videos, audio, video notes, file size, mime type, media ID, URL | Upload, delivery, download, relay-copy clean-up | Chat participants, organization operator, node infrastructure | Relay copy is deleted after recipient acks or TTL; metadata may persist in history |
| Calls | Call ID, chat ID, type, participants, statuses, times, LiveKit token | Set up voice and video calls, call history | Call participants, organization operator, node infrastructure | Call metadata is kept for history; call content is not recorded |
| Notifications | APNs device token, APNs VoIP token, FCM token, badge count, message kind | Push notifications, incoming calls, unread counters | Apple APNs, Firebase Cloud Messaging, organization operator | While the token is valid or the device uses notifications |
| Technical logs | IP, request time, route, errors, rate limits, push delivery errors | Security, diagnostics, incident investigation | Organization operator, node infrastructure; OffshoreLabs only if granted access for support | As long as needed for diagnostics, security, and law |
| Website | IP, user agent, language, referrer, font and static-asset requests | Render the site, security, basic diagnostics | Site hosting, static-asset providers | According to the hosting log retention and technical need |
| Support | Email address, message body, screenshots / logs the user attached | Respond to the request, fix the issue, security | Organization operator; OffshoreLabs if the request is escalated | While the request is open or needed to defend rights |
Notifications and previews
In the current version, push notifications may include the sender's name and a short preview of the message or media caption. The user can enable "hide notification content"; push then shows generic text without the message body.
Device permissions
Photos and gallery
Needed to pick, send, and save media. Mango Private does not scan the entire library.
Location
Used only when the user actively sends a point to a chat. Continuous background tracking is not used.
Notifications
Needed for messages, calls, and badge counters. Notification content can be hidden.
App lock
Face ID, Touch ID, or system credential are validated by the device. Biometric data is not sent to the server.
Local storage
The app keeps a local copy of profile, messages, and media for speed, history, and offline UX.
User requests
For access, correction, deletion, or clarification of data, contact your organization's Mango Private administrator or write to request@mango-private.com. We may ask for confirmation that the request is from the account owner.