App analysis · 19.10.2026
Activity Launcher
de.szalkowski.activitylauncher · version 2.5.0-dev
In short
SDKs found: 0. Companies: 0, of which outside the EEA — 0. Sensitive permissions: 1 — all code inside the app, including embedded SDKs, can use them.
Sensitive permissions (1)
- list of all installed apps —
android.permission.QUERY_ALL_PACKAGES
All manifest permissions (5)
android.permission.QUERY_ALL_PACKAGEScom.android.launcher.permission.INSTALL_SHORTCUTde.szalkowski.activitylauncher.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONde.szalkowski.activitylauncher.permission.CREATE_SHORTCUTde.szalkowski.activitylauncher.permission.LAUNCH_ACTIVITY
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
de.szalkowski.activitylauncher · version 2.5.0-dev (code 20500)0c731f01cb359e133b3c2d1d5655ce21a99de9e44a324fcb4dc64e0dc195c6442015709d519fd686b1e37b334f12082cbafcb9f5126a68a25b172043ebb581de13c27d15ac2eThe 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.