MC Together ("the app") is published by AdriMark LLC ("we", "us"). The app advertises a Minecraft: Bedrock Edition LAN world on your local Wi-Fi network. Other players on the same network see it in-game and are redirected to a remote server you choose, so nobody has to type in a server address by hand. This policy explains what data the app collects, why we collect it, and what choices you have.
Free users see an interstitial (full-screen) ad from Google AdMob when starting a server. Serving ads involves Google collecting and using device identifiers (such as your advertising ID) and other data as described in Google's Partner Policy and AdMob's own privacy documentation.
The app requests non-personalized ads only. Ads are not selected using a profile of your interests built from other apps or sites.
The app also limits the ads it will accept to Google's G ("General audiences") content rating, which is its most restrictive setting. Categories rated above G are not eligible to be shown, including gambling and real-money gaming, alcohol and tobacco, dating and sexual content, and graphic violence. Ad requests are additionally marked as coming from users who may be under the age of consent in their country, which restricts ad serving further. Ad content is served by Google, and we do not control which individual advertisers participate. If you see an ad in this app that does not meet the G rating, please report it to us at the address in the Contact section.
In the European Economic Area, the United Kingdom, and other regions where it is legally required, the app uses Google's User Messaging Platform (UMP) to show a consent form before any ad is requested. If you do not consent, no ad is requested for that session and analytics collection is disabled. Outside those regions, no form is shown and the app proceeds with non-personalized ads. On iOS, Apple's App Tracking Transparency prompt is presented as part of this flow. You can reopen Google's privacy options form at any time from the app's Settings screen where it is available in your region.
If the app crashes or encounters an unexpected error, Firebase Crashlytics collects a crash report containing a stack trace, your device model, your operating system version, and short diagnostic breadcrumbs recorded shortly before the crash. We use this data to diagnose and fix defects. It is not used for advertising, and it is never linked to an account, because the app has none.
Two details worth stating plainly. First, crash reporting starts when the app launches and is not gated on the consent form described under Advertising — it is what tells us the app is broken, including when it breaks during startup itself, so it runs on the basis of our legitimate interest in keeping the app working rather than on consent. Advertising and analytics are gated on that form. Second, a crash report describes a technical failure, so where an error came from a network operation the underlying system error message can include the address the app was trying to reach at the time — which, if you typed a server in yourself, is a value you entered. We do not use that for any purpose beyond fixing the fault, and no other text you type in the app is included in a report.
The app logs a small number of usage events through Firebase Analytics, subject to your consent where UMP requires it. We use these events to understand whether users are able to start a broadcast and whether other players find it. These are the events the app sends itself:
| Event | What it means |
|---|---|
start_tapped | User tapped "Start Server" (records whether Relay mode was on, and which server) |
broadcast_ready | The LAN advertisement started successfully |
world_discovered | A Minecraft client found the advertised world on the network |
handoff_success | A friend was successfully redirected to the target server |
connect_confirmed | Positive confirmation that a redirected friend actually connected to the target server (a stricter signal than handoff_success alone) |
start_failed | Starting the broadcast failed (records a general failure reason, e.g. network unavailable) |
catalog_opened | A server was chosen from the "Browse Servers" catalog |
relay_fallback_engaged | The app automatically switched to Relay mode after repeated failed handoffs |
game_newer_than_build | The installed game is newer than the Minecraft protocol version this app build supports |
relay_held_for_build | The app stayed in Relay mode because of the version gap above |
relay_hold_released | That hold was lifted |
paywall_shown | The Premium upsell screen was shown |
premium_purchased | A Premium purchase completed |
premium_restored | A prior Premium purchase was restored |
referral_screen_opened | The "Invite a friend" screen was opened |
referral_invite_shared | The share sheet was opened for an invite |
referral_code_redeemed | An invite code was successfully redeemed |
referral_premium_earned | Enough friends redeemed a code for the Premium reward to unlock |
The referral events carry no code and no identifier. They record only that a step happened. Your invite code and the anonymous identifier described under Invite a friend are deliberately never attached to an analytics event.
Server identity is not logged as an address. Most of the
events above record which server was involved. That value is always one
of two things: the catalog identifier of a listed server, such as
"hive", or the value "custom" if you entered
your own server. The IP address or hostname you connect to is not
included in any analytics event, and neither is any other text you enter
in the app.
Firebase Analytics also collects a standard set of events automatically, without the app asking it to. These include app installation, session start and end, screen views, app updates, and, where the advertising SDK is linked, ad impressions. Firebase associates this activity with an app-instance identifier and, on Android, with your advertising ID and Android device identifier. This data is held by Google and is described in Firebase's documentation on automatically collected events and in Google's Firebase privacy notice. We do not link any of it to a name, an email address, or an account, because the app has none.
MC Together offers one optional, non-consumable "Premium" unlock, which provides custom server images, unlimited connections, and removal of ads. It is sold through Google Play Billing on Android and Apple's In-App Purchase system on iOS. Payment processing, billing information, and receipts are handled entirely by Google or Apple under their own privacy policies. We never see or store your card details.
The only purchase information available to us is whether your account owns the Premium entitlement. That status is recorded locally on your device so that you do not have to buy it again. Restoring a purchase asks Google or Apple whether you already own it.
The app has an optional "Invite friends, get premium" feature. You share an invite code, and when enough friends install the app and enter your code, the Premium unlock is granted to you for free.
Confirming that a friend really installed the app is the one thing the app cannot work out on your device alone, so this feature — and only this feature — uses a server. It is built on Google Firebase (Authentication and Cloud Firestore).
Beyond ads/analytics/crash-reporting SDKs and the app-store billing APIs above, the app makes a few narrowly-scoped network requests on its own:
dns.google) and, as a fallback, Cloudflare
(cloudflare-dns.com). This applies to every server the app
needs to reach, which includes the servers you have favorited or entered
yourself, not only the one you are currently connecting to. Only the
hostname is sent. This is standard hostname resolution, carried over
HTTPS rather than plain DNS, and is subject to those providers' own
privacy policies.
minecraft-data project, hosted on GitHub's raw content
service or the jsDelivr mirror, to determine the current Minecraft:
Bedrock protocol version. This keeps the advertised LAN world from
claiming an outdated version. No personal or device data is sent with
this request beyond what any HTTP request necessarily includes, such as
your IP address. These files are hosted by GitHub and jsDelivr rather
than by us, and those providers may log the request under their own
privacy policies.
smt-mctogether.web.app to check for an active service notice
and an updated server list. No account or device identifier is sent.
Everything below is stored locally on your device only, using your device's standard app storage. None of it is transmitted to us or to any third party, except where noted above (e.g. the Premium flag being verified against Google/Apple's purchase records):
Uninstalling the app deletes all of this data.
ACCESS_WIFI_STATE, CHANGE_WIFI_MULTICAST_STATE). Required to advertise the LAN world so that Minecraft can discover it, and for NetherNet discovery.POST_NOTIFICATIONS). The broadcast runs as a foreground service so that Android does not stop it while you are in Minecraft. Android requires a visible notification for the duration.com.android.vending.BILLING). Required to offer the Premium purchase through Google Play.AD_ID and the related Android Ad Services permissions). Added by Google's advertising and analytics libraries so that ads can be served and measured.MC Together is a companion utility for Minecraft: Bedrock Edition, a game played by both adults and children. The app is intended for a general audience and is not directed primarily at children under 13.
We do not knowingly collect personal information from users of any age. The app never asks for a name, email address, date of birth, or any other identifying detail, and there is no sign-up, username, or profile. No user-generated content is transmitted off your device. The optional Invite a friend feature creates an anonymous, randomly generated identifier for the installation, which carries no personal information and cannot be used to contact or identify anyone.
Because the app is likely to be used by minors, we apply the additional advertising restrictions set out in the Advertising section. A parent or guardian who believes their child has provided personal information to us, or who has a concern about an ad shown in the app, should contact us using the details in the Contact section, and we will investigate.
Your settings and history exist only on your device and are removed when you clear the app's storage or uninstall it. Analytics events and crash reports are retained by Google under Firebase's own retention schedules and are not linked to any identity we hold.
The single exception is the Invite a friend feature. If you have used it, we hold an anonymous identifier for your installation, your invite code, and any redemption record, retained until you ask us to delete them. We hold no other server-side data about you, and no personal details in any case — we have no name, email address, or phone number to look you up by.
If you are in the EU/EEA/UK, California, or another jurisdiction with data protection rights (GDPR, CCPA/CPRA, or similar), you have the right to ask what data is processed about you, to object to processing, and to request deletion. For invite data, use the data deletion request page described in Deleting your data below. For everything else, requests should be directed to:
You can reset your advertising identifier or opt out of personalized ads in your device's system settings at any time. Where a consent form was shown, you can withdraw analytics and advertising consent through the privacy options entry in the app's Settings screen. For any question about this policy, or to raise a specific concern, contact us at the address below.
Everything the app stores on your device is deleted when you uninstall the app or clear its storage from your device's settings. You do not need to ask us for that, and we cannot do it for you.
The only data we hold on a server is the Invite a friend records described above. To have those deleted, use the request page:
Request deletion of your invite data
→
The same page is reachable from inside the app, under Help → About,
and from the web without the app installed. You do not need an account to
use it.
You will need your six-character invite code, because it is the only handle we have on your records — there is no name or email address attached to them. Deleting the records also releases the code, and any Premium already unlocked on your device stays unlocked.
AdriMark LLC
Email: AdriMark@Markcraft.org
If we change what the app collects or how it is used, we will update this page and the "Last updated" date shown at the top. Significant changes will also be noted in the app's release notes.