App analysis · 11.10.2026
Sag's Wien
at.gv.wien.sagswien.app.droid · version 3.1.4
In short
SDKs found: 3. Companies: 2, of which outside the EEA — 2. Sensitive permissions: 5 — all code inside the app, including embedded SDKs, can use them.
What is inside — embedded SDKs
- Firebase Cloud Messaging — Google LLC, United States outside EEA push notifications
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Microsoft App Center — Microsoft, United States outside EEA analytics / crash reporting
Sensitive permissions (5)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - camera —
android.permission.CAMERA - files on the device —
android.permission.READ_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE
All manifest permissions (10)
android.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.CAMERAandroid.permission.FOREGROUND_SERVICEandroid.permission.INTERNETandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGEcom.google.android.c2dm.permission.RECEIVE
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
at.gv.wien.sagswien.app.droid · version 3.1.4 (code 122)ce47a2a2bbbfbfcb689370361e58657af6fa8b70f6571db1f3b4b4e0376978ab99efa6c45031933c6941aaec5e44a5d29113ec75fe043eec3788ad6d1ea00ac22769b78c1753The 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.