Documentation · Reference

Declared Android permissions

Exact list of the 5 permissions declared in STALMAS's AndroidManifest.xml and the real purpose of each one.

STALMAS requests only the minimum Android permissions needed to connect to your servers, download optional local AI models, and display alerts. This reference matches AndroidManifest.xml verbatim.

Declared permissions

Android permission Actual technical purpose When it is used
android.permission.INTERNET Connect straight to your Portainer and SSH hosts, send requests with your optional Gemini key (BYOK), download .litertlm models, and sync encrypted Drive backups if enabled. During user actions, model downloads, and background monitoring checks.
android.permission.ACCESS_NETWORK_STATE Verify network availability before making API requests or starting multi-gigabyte model downloads. Before Portainer/AI calls, downloads, and monitor ticks.
android.permission.FOREGROUND_SERVICE Keep large local AI model downloads alive when the screen turns off so multi-gigabyte files do not silently fail. Only while downloading a local .litertlm model in ModelDownloadService.
android.permission.FOREGROUND_SERVICE_DATA_SYNC Required Android 14+ service type (dataSync) declared on ModelDownloadService. Only during an active local model download.
android.permission.POST_NOTIFICATIONS Display download progress notifications and optional Pro container health alerts (stopped, unhealthy, restart loop). On Android 13+, only if you grant notification permission.

Additional manifest protections

  • android:allowBackup="false": prevents Android’s standard OS backup from extracting local app data outside your encrypted backup flow.
  • android:networkSecurityConfig: pairs with runtime CleartextGuard so cleartext HTTP stays restricted to private/local networks.
  • No location, camera, microphone, contacts, or broad storage permissions: importing .pem/.key files and exporting archives runs through Android’s standard document picker (Storage Access Framework).