1. Who this policy is from
Mango (the “app”) is published by Mediaware, based in Slovakia (mediaware.sk). For privacy questions, write to [email protected]. For the purposes of EU data-protection law (GDPR), Mediaware is the data controller for the very limited processing described below.
2. What we collect
The honest answer for the client itself is almost nothing. Mango can be used with third-party IRC networks without a Mediaware account. Specifically:
- No analytics. We do not use Google Analytics, App Store analytics frameworks beyond what Apple itself collects (see §7), or any product-analytics SDK.
- No advertising. Mango contains no ads and no advertising identifiers. We do not access the IDFA / IDFV.
- No third-party trackers. The app makes no network requests to data brokers, attribution services, or social-network SDKs.
- No client account is required. Third-party IRC networks may require their own account or password (e.g. NickServ); those credentials are stored as described in §4. The optional Mango Account for the Mango IRC Network is covered by the separate network notice.
The limited processing Mediaware performs for diagnostics and the optional remote-content privacy service is described below.
3. Crash and error reports
When the app crashes or hits an unhandled error, Mango sends a diagnostic report to a Sentry instance that Mediaware operates itself, on Mediaware-controlled infrastructure. The data is not shared with sentry.io or any other third party.
A typical crash report contains:
- The technical stack trace and exception type from the crash.
- The app version and build number, the operating-system version, the device model identifier, and the user’s locale (e.g.
en_US). - A short trail of recent in-app navigation events (“breadcrumbs”) used to reproduce the bug.
- If you choose to submit feedback from inside the app, the name, email address, and message you typed into the feedback form.
What is not in a crash report: the contents of your IRC messages, channel names you participate in, nicknames of people you talk to, IRC server passwords, SASL passwords, or any other content you send or receive on IRC. Crash reports describe how the app failed, not what you were doing in it.
Legal basis (GDPR): legitimate interests in keeping the app stable and fixing crashes (Art. 6(1)(f) GDPR). Retention: crash reports are kept for up to 90 days and then deleted.
4. Data that stays on your device
Mango stores the following locally on the device where you installed it:
- Network profiles — server hostnames, ports, your nickname, and other connection settings you enter.
- Credentials — IRC server passwords and SASL passwords are stored in the Keychain. If you have iCloud Keychain enabled, Apple syncs these between your devices end-to-end; Mediaware never has access to them.
- UI state and preferences — selected theme, layout, recent channels, and similar settings, stored in the standard application preferences (
UserDefaults). - Cached chat history — recent messages from channels and DMs, kept locally so reopening the app is fast.
None of this is sent to Mediaware. Removing the app removes the local data; iCloud-Keychain-synced credentials follow Apple’s normal Keychain rules.
5. IRC servers you connect to
Mango is a client for IRC. When you connect to an IRC network — whether it’s Libera.Chat, OFTC, another Ergo server, or your own ZNC bouncer — that network is normally an independent third party, not operated by Mediaware. The server sees, processes, and may log everything you send to it, including your nickname, IP address, channels you join, and message contents. That is how IRC works; it’s the same on every IRC client.
Each network has its own privacy practices and operators. Please read the network’s own policy before sharing sensitive information through it.
The exception is the clearly labelled Mango IRC Network, which Mediaware operates. Creating a Mango Account or connecting to that network involves server-side processing described in its separate Network Privacy Notice.
6. Remote-content privacy service
In Mango 3.1 and later, a user who is signed in with a Mango Account can load automatic link metadata, preview images, avatars, custom emoji, themes, and Grove packages through Mango Proxy. This optional Mediaware-operated service receives a short-lived account token, the remote URL, a small allowlist of ordinary fetch headers, and the response data needed to return that resource. It does not receive IRC message history or IRC credentials.
Mango Proxy checks each destination and redirect, then asks an authenticated Cloudflare Worker to perform the remote request. The remote website therefore sees a Cloudflare network address, not the Mango user’s IP address and not Mediaware’s home-server address. Cloudflare necessarily processes the requested URL, permitted headers, response content, and connection metadata while providing this relay and abuse protection, under Cloudflare’s privacy policy.
Mango Proxy has no request-history database and does not log destination URLs, account or session identifiers, bearer tokens, request headers, or response bodies. Per-account quotas exist only in memory. A shared cache may retain eligible response bodies for up to 24 hours, but its filenames and persisted metadata use opaque digests and do not contain the URL, hostname, account, session, or token. Sanitized unexpected-error reports contain only a fixed failure code, environment, and release. Legal basis (GDPR): performance of the optional service and legitimate interests in protecting users’ network privacy, preventing abuse, and operating it reliably (Art. 6(1)(b) and Art. 6(1)(f) GDPR).
Signed-out users fetch remote resources directly. A signed-in user may also explicitly enable a less-private direct fallback in Mango’s settings; when direct fetching is used, the remote website receives that device’s public IP address as with any ordinary web request.
7. Distribution channels
App Store and TestFlight (Apple)
Mango is distributed through Apple’s App Store, TestFlight, and the Mac App Store. When you download or beta-test Mango, Apple collects information governed by Apple’s privacy practices — for example, App Store crash logs, performance metrics, and TestFlight invitation emails. Mediaware can see aggregated statistics that App Store Connect provides (for example, country-level install counts and anonymized crash counts). Mediaware does not see your Apple ID or your email address.
See Apple’s privacy policy for details on what Apple itself collects.
iCloud sync
If you enable iCloud, Apple syncs your Mango network profiles and Keychain-stored credentials between your Apple devices through your personal iCloud account. This data does not pass through any Mediaware server. Mediaware cannot read iCloud-synced data.
8. Website
The website at mangoirc.chat is a static page served behind Cloudflare. It does not set tracking cookies and does not run analytics. The homepage embeds an AppRanks badge to show Mango’s public App Store price and ranking. Loading that badge requests its script and public ranking data from appranks.app; as with an ordinary web request, AppRanks and its CDN may receive basic request metadata such as your IP address, user agent, and the referring site. No Mango app data, IRC data, or support-form data is sent to AppRanks.
Cloudflare may log basic request metadata (IP address, request path, user agent) for abuse-protection and reliability purposes, governed by Cloudflare’s privacy policy. The website does store a localStorage entry for your selected theme so the site remembers it on your next visit; that value never leaves your browser.
9. Children
Mango is not directed at children under 13 (or the equivalent minimum age in your country). We do not knowingly collect personal data from children. If you believe a child has used the in-app feedback form to send us their information, contact us and we will delete it.
10. Your rights
Because Mediaware processes so little data, most data-subject rights are easy to exercise:
- Access / portability: ask us what we have. Outside of crash reports tied to your install (which contain no name or email unless you submitted feedback), the answer is generally “nothing identifiable.”
- Erasure: we will delete crash reports or feedback messages you submitted on request.
- Objection / restriction: you can object to crash reporting at any time by deleting the app, or by disabling network access for it.
- Complaint: if you are in the EU, you have the right to lodge a complaint with your national data-protection authority. In Slovakia this is the Úrad na ochranu osobných údajov SR.
To exercise any of these rights, email [email protected].
11. International transfers
Mediaware’s Sentry instance is hosted on infrastructure located in the EU / European Economic Area. We do not transfer crash data to third countries.
Cloudflare operates a global network and may process Mango Proxy traffic outside the EEA under the transfer safeguards described in Cloudflare’s privacy documentation. Remote content itself may originate anywhere in the world, according to the location chosen by the operator of that remote website.
12. Security
Crash reports are sent over TLS. Mediaware’s self-hosted Sentry is access-controlled and only Mediaware staff can view it. Local credentials live in the operating-system Keychain, with the same protections Apple provides for any other Keychain-using app. Mango Proxy authenticates every Cloudflare egress request with a short-lived signed request; the relay refuses unsigned use and Mango Proxy refuses to start when that protection is absent.
13. Changes to this policy
If this policy changes in any way that affects what data is collected or how it is used, we will update the “Last updated” date at the top of the page and, for material changes, post a notice on the Mango website before the change takes effect.
14. Contact
Questions, concerns, or data-subject requests:
[email protected]
Mediaware, Slovakia — mediaware.sk