App analysis · 11.10.2026
SIXT
com.sixt.reservation · version 26.38.1-21167
In short
SDKs found: 13. Companies: 10, of which outside the EEA — 8. Sensitive permissions: 12 — 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
- Firebase Crashlytics — Google LLC, United States outside EEA crash reporting
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- ironSource — Unity Technologies, Israel outside EEA advertising
- Unity Ads — Unity Technologies, United States outside EEA advertising
- Adjust — Adjust GmbH, Germany EEA атрибуция установок
- AppLovin — AppLovin Corp., United States outside EEA advertising
- AppsFlyer — AppsFlyer Ltd, Israel outside EEA атрибуция установок
- Braze — Braze Inc., United States outside EEA маркетинг / push
- Chartboost — Chartboost, United States outside EEA advertising
- Sentry — Functional Software Inc., United States outside EEA crash reporting
- Singular — Singular Labs, United States outside EEA атрибуция установок
- Usercentrics — Usercentrics GmbH, Germany EEA consent platform
Sensitive permissions (12)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - calendar —
android.permission.READ_CALENDAR - modify calendar —
android.permission.WRITE_CALENDAR - camera —
android.permission.CAMERA - microphone —
android.permission.RECORD_AUDIO - NFC: reading cards, documents and tags —
android.permission.NFC - biometrics (fingerprint, face) —
android.permission.USE_BIOMETRIC - fingerprint —
android.permission.USE_FINGERPRINT - advertising ID (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_AD_ID - ad attribution (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_ATTRIBUTION - advertising ID —
com.google.android.gms.permission.AD_ID
All manifest permissions (32)
android.permission.ACCESS_ADSERVICES_AD_IDandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONandroid.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.BLUETOOTHandroid.permission.BLUETOOTH_ADMINandroid.permission.BLUETOOTH_ADVERTISEandroid.permission.BLUETOOTH_CONNECTandroid.permission.CAMERAandroid.permission.CHANGE_NETWORK_STATEandroid.permission.CHANGE_WIFI_STATEandroid.permission.EXPAND_STATUS_BARandroid.permission.FLASHLIGHTandroid.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_SPECIAL_USEandroid.permission.INTERNETandroid.permission.NFCandroid.permission.POST_NOTIFICATIONSandroid.permission.READ_CALENDARandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.RECORD_AUDIOandroid.permission.USE_BIOMETRICandroid.permission.USE_FINGERPRINTandroid.permission.VIBRATEandroid.permission.WAKE_LOCKandroid.permission.WRITE_CALENDARcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEcom.google.android.gms.permission.AD_IDcom.sixt.reservation.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
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.sixt.reservation · version 26.38.1-21167 (code 21167)021aa6280c6e8c0834fb30cc45e6efb0e7e05d8395a2bf6578e77abd84df86fd7d752ccec522797374316ef6ef3132c80584aa2e83f75a00189d39c4e21a6d722769b78c1753The 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.