App analysis · 20.10.2026
Birthday Adapter
org.birthdayadapter · version 3.13.7
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)
- accounts on the device —
android.permission.GET_ACCOUNTS - calendar —
android.permission.READ_CALENDAR - contacts —
android.permission.READ_CONTACTS - modify calendar —
android.permission.WRITE_CALENDAR
All manifest permissions (13)
android.permission.FOREGROUND_SERVICEandroid.permission.GET_ACCOUNTSandroid.permission.MANAGE_ACCOUNTSandroid.permission.READ_CALENDARandroid.permission.READ_CONTACTSandroid.permission.READ_SYNC_SETTINGSandroid.permission.READ_SYNC_STATSandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONSandroid.permission.WAKE_LOCKandroid.permission.WRITE_CALENDARandroid.permission.WRITE_SYNC_SETTINGSorg.birthdayadapter.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
org.birthdayadapter · version 3.13.7 (code 31307)542aa6f1184da9d5982c1d151facb1698e66faecd5d86a6a50fe8ed589c864aeb4d50046259eb0c5cf0f6a2ebbf9db465e6e55962c36a5225fc88e33e6fc3d46The 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.