Privacy on this MMY app site

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

This site

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

The button that gets the app leaves this site. From that click the request goes to the install host, which keeps its own logs. This site does not see what happens after the click, and it adds no identifier of its own to the link, so it cannot trace a click back to a reader.

Cookies

These pages set none. A cookie that appears while you read them did not come from this site.

The app, as far as the file shows

The channel package declares thirteen permissions, listed in daily-use terms on the permissions page. READ_PHONE_STATE is the one that reads device state, and it is the line to weigh before installing. The manifest does not declare contacts, messages, camera or location, and READ_SMS is absent, so the app cannot read the login code out of your messages.

A channel file inside the package carries an AppsFlyer source marker and names a data-collection host. The app reports install attribution. What else it sends after launch is not visible from the manifest, and this site does not claim to know. POST_NOTIFICATIONS is requested at runtime on Android 13 and newer; declining it is covered on the notifications page.

Data held inside the app

This site holds no account data, because it collects none, so there is nothing here to delete on request. Data the app stores about an account lives with the operator, and a deletion request goes to the operator through the app. Clearing the app's data on the phone, from Settings, removes only the local copy.