App analysis · 20.10.2026
ShizuCallRecorder
com.kitsumed.shizucallrecorder · version 1.3.3
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)
- call log —
android.permission.READ_CALL_LOG - contacts —
android.permission.READ_CONTACTS - list of all installed apps —
android.permission.QUERY_ALL_PACKAGES - phone data (carrier, call state) —
android.permission.READ_PHONE_STATE - draw over other apps —
android.permission.SYSTEM_ALERT_WINDOW
All manifest permissions (14)
android.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_DATA_SYNCandroid.permission.FOREGROUND_SERVICE_SPECIAL_USEandroid.permission.MANAGE_ONGOING_CALLSandroid.permission.POST_NOTIFICATIONSandroid.permission.QUERY_ALL_PACKAGESandroid.permission.READ_CALL_LOGandroid.permission.READ_CONTACTSandroid.permission.READ_PHONE_STATEandroid.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONSandroid.permission.SYSTEM_ALERT_WINDOWandroid.permission.VIBRATEcom.kitsumed.shizucallrecorder.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.kitsumed.shizucallrecorder · version 1.3.3 (code 19)55d4dcbb453f0050617fad5a41f5fbccb667350e3af34809ae40ec6a97285f7e9d3565f7c56e00ad830be8572684bb95b2f2a555e1c3ca403f948819125877eaThe 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.