Camera and microphone
Needed for calls, voice messages, video, and media. Access can be revoked in OS settings.
Data Collection Policy
MangoConnect data collection policy
A practical companion to the privacy policy: which data categories MangoConnect actually needs, what they're used for, and where collection stops.
Collection principles
- We only collect what's needed for a private messenger, security, and support.
- We do not use user data for ad targeting and we do not sell it.
- We do not ask for a phone number — it is not needed for registration.
- 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.
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, chat access | Mango, 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 members and Mango 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 | Recipients, chat members, Mango 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 | Message recipients and Mango 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 | Recipients, object storage, CDN / proxy when present | 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, Mango, LiveKit / TURN infrastructure | Call metadata is kept for history; we do not record call content |
| Notifications | APNs device token, APNs VoIP token, FCM token, badge count, message kind | Push notifications, incoming calls, unread counters | Apple APNs, Firebase Cloud Messaging, Mango | 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 | Mango and infrastructure providers | 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 | Mango and the email provider | 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 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 Mango.
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, write to hello@mango-connect.com. We may ask for confirmation that the request is from the account owner.