Privacy on this MMY site

What this site itself does with data, kept separate from what the app does.

This site

mmyapk.org is a set of static pages. It has no account system, no forms, and no analytics script. The server sees the usual request log: an address, a browser string, the page asked for. That log is not used to build profiles and it is not sold.

The download button leaves this site. From that click onward the request goes to the install host, which has its own logging. This site does not see what happens there.

The app

The MMY package measured on 10 November 2026 declares thirteen permissions, listed on the APK file page. READ_PHONE_STATE is the one that reads device state. The manifest does not declare contacts, messages, camera or location. A channel file inside the package names an AppsFlyer source marker and a data collection host, which means the app reports install attribution somewhere. What else it sends is not visible from the manifest, and this site does not claim to know.

Contact

This site has no account data to delete, because it collects none. For data held inside the app, the request goes to the developer through the app.

The download click

The button runs to the install host with two parameters, bnp and gz, which tell that host which app and which channel file to serve. That host sees the click. This site does not add its own identifier to the link, so it cannot trace a click back to a reader afterwards.

Cookies

These pages set none. If a cookie appears while you read them, it did not come from this site.

Permissions, restated

The thirteen permissions are listed in full on the APK file page and are not repeated here. The short version: network access, audio, vibration, notifications, the phone state, an advertising id, an install-referrer lookup, message delivery through Google, and two vendor permissions that only Samsung and Huawei phones act on. No contacts, no messages, no camera, no location.