App analysis · 20.10.2026
RKNHardering
com.notcvnt.rknhardering · version 2.11.0
In short
SDKs found: 0. Companies: 0, of which outside the EEA — 0. Sensitive permissions: 5 — all code inside the app, including embedded SDKs, can use them.
Sensitive permissions (5)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - scan for nearby Wi-Fi devices —
android.permission.NEARBY_WIFI_DEVICES - list of all installed apps —
android.permission.QUERY_ALL_PACKAGES - phone data (carrier, call state) —
android.permission.READ_PHONE_STATE
All manifest permissions (11)
android.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.CHANGE_WIFI_STATEandroid.permission.INTERNETandroid.permission.NEARBY_WIFI_DEVICESandroid.permission.QUERY_ALL_PACKAGESandroid.permission.READ_PHONE_STATEcom.notcvnt.rknhardering.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONmoe.shizuku.manager.permission.API_V23
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.notcvnt.rknhardering · version 2.11.0 (code 21100)77d64f300534f9068fb8441fc62d8baa97698d2cf5e7b04e5133f0736399fc594411856721b2876200bfee9c50c4a4ba3050e74785b3518a986bbf1a1a7cddcaThe 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.