App analysis · 19.10.2026
Etar - OpenSource Calendar
ws.xsoh.etar · version 1.0.57
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 (15)
android.permission.ACCESS_NETWORK_STATEandroid.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_SYSTEM_EXEMPTEDandroid.permission.GET_ACCOUNTSandroid.permission.POST_NOTIFICATIONSandroid.permission.READ_CALENDARandroid.permission.READ_CONTACTSandroid.permission.READ_SYNC_SETTINGSandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONSandroid.permission.SCHEDULE_EXACT_ALARMandroid.permission.VIBRATEandroid.permission.WAKE_LOCKandroid.permission.WRITE_CALENDARws.xsoh.etar.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
ws.xsoh.etar · version 1.0.57 (code 57)dae01d93c8920aa63845868db2190bcc4aa6ff8410b1289de1ce27b1bb89c5993f3176c3ce189c98054ff9e1d32daecf00a41572f4c7bd2b2f80607252ddb06e13c27d15ac2eThe 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.