App analysis · 20.10.2026
SAI
com.aefyr.sai.fdroid · version 4.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)
- files on the device —
android.permission.READ_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - request to delete apps —
android.permission.REQUEST_DELETE_PACKAGES - request to install apps —
android.permission.REQUEST_INSTALL_PACKAGES
All manifest permissions (6)
android.permission.FOREGROUND_SERVICEandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.REQUEST_DELETE_PACKAGESandroid.permission.REQUEST_INSTALL_PACKAGESandroid.permission.WRITE_EXTERNAL_STORAGEmoe.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.aefyr.sai.fdroid · version 4.5 (code 60)cb96838c9a64b401bfff8c604b10712cdc7a1d96ea09b6a445cfd5b35702fc72The 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.