App analysis · 20.10.2026
Material Files
me.zhanghai.android.files · version 1.7.5
In short
SDKs found: 0. Companies: 0, of which outside the EEA — 0. Sensitive permissions: 4 — all code inside the app, including embedded SDKs, can use them.
Sensitive permissions (4)
- full access to all files —
android.permission.MANAGE_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - list of all installed apps —
android.permission.QUERY_ALL_PACKAGES - request to install apps —
android.permission.REQUEST_INSTALL_PACKAGES
All manifest permissions (14)
android.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_SPECIAL_USEandroid.permission.INTERNETandroid.permission.MANAGE_EXTERNAL_STORAGEandroid.permission.POST_NOTIFICATIONSandroid.permission.QUERY_ALL_PACKAGESandroid.permission.REQUEST_INSTALL_PACKAGESandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGEcom.android.launcher.permission.INSTALL_SHORTCUTme.zhanghai.android.files.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
me.zhanghai.android.files · version 1.7.5 (code 40)2fe900bf43d725b655008d438f5ca46d0da0f301e3784403b5b96c3fc2df6e8a9c22a742fa200c85bafbc9924a02ddc8f3a0b975d4d7b5a8da21d7cf34ce2b20The 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.