App analysis · 04.10.2026
PayMe
com.payme.app · version 1.1.0
In short
SDKs found: 2. Companies: 1, of which outside the EEA — 1. Sensitive permissions: 4 — all code inside the app, including embedded SDKs, can use them.
What is inside — embedded SDKs
- Firebase Cloud Messaging — Google LLC, United States outside EEA push notifications
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
Sensitive permissions (4)
- contacts —
android.permission.READ_CONTACTS - files on the device —
android.permission.READ_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - phone data (carrier, call state) —
android.permission.READ_PHONE_STATE
All manifest permissions (10)
android.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.INTERNETandroid.permission.READ_CONTACTSandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.READ_PHONE_STATEandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGEcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE
Limits of the analysis
The analysis shows code inside the app file, not data transfers: an SDK being present means a transfer is possible, not that it happens. The country is where the company owning the SDK is registered, not where its servers are. Some code may have been renamed at build time, so the SDK list is a lower bound.
The legal assessment is made by the competent supervisory authority.
Evidence
com.payme.app · version 1.1.0 (code 11)f42134ad7ab18bb6ac76b2f506e429d285489b340fb6a84dd21dea054a8d4411262b1a58346cf2300f718ea98de10e3d289295218aa57a53b8b6a8e654fbb1702769b78c1753The same file (same SHA-256) with the same library version gives the same result — check it on the APK check page. Licence CC BY 4.0, source — gdpru.eu; report errors to contact@gdpru.eu.