App analysis · 11.10.2026

MACIF

com.macif.mobile.application.android · version 11.27.3

5SDKs found

3companies

3companies outside the EEA

10sensitive permissions

In short

SDKs found: 5. Companies: 3, of which outside the EEA — 3. Sensitive permissions: 10 — 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
Huawei Ads Kit — Huawei, China outside EEA advertising
OneTrust — OneTrust LLC, United States outside EEA consent platform

Sensitive permissions (10)

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
files on the device — android.permission.READ_EXTERNAL_STORAGE
write files on the device — android.permission.WRITE_EXTERNAL_STORAGE
biometrics (fingerprint, face) — android.permission.USE_BIOMETRIC
fingerprint — android.permission.USE_FINGERPRINT
advertising ID — com.google.android.gms.permission.AD_ID

All manifest permissions (18)

android.permission.ACCESS_COARSE_LOCATION
android.permission.ACCESS_FINE_LOCATION
android.permission.ACCESS_NETWORK_STATE
android.permission.CAMERA
android.permission.FOREGROUND_SERVICE
android.permission.INTERNET
android.permission.POST_NOTIFICATIONS
android.permission.READ_CALENDAR
android.permission.READ_EXTERNAL_STORAGE
android.permission.RECEIVE_BOOT_COMPLETED
android.permission.USE_BIOMETRIC
android.permission.USE_FINGERPRINT
android.permission.WAKE_LOCK
android.permission.WRITE_CALENDAR
android.permission.WRITE_EXTERNAL_STORAGE
com.google.android.c2dm.permission.RECEIVE
com.google.android.gms.permission.AD_ID
com.macif.mobile.application.android.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

File: com.macif.mobile.application.android.xapk (56.7 MB)

Package: com.macif.mobile.application.android · version 11.27.3 (code 2026091115)

Android: minimum API 29, target API 36

File SHA-256: fbf45cae79950f8a183632c9795316f1644aae1af63bd1181698376af15fad54

Developer signature (SHA-256): f4b396d79b0e2df7cf4f7e9fd283df9842b440570b4cf4311e27c643ad44af76

Signed by: Macif (Niort, 33) · outside EEA · key since 2014-12-12

Library: 63 SDK · 81 permissions · 2769b78c1753

File source: APKPure (через apkeep)

The 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.

Download card (Markdown)

← All analysed apps · Check your own app