Notifications
Used to show alarm status, foreground service status, check-in reminders, and parent-visible safety activity.
Permission explanations
Permissions and Location Disclosure
Plain-language explanations for the permissions Parent Call Alarm may request on Android.
Current standalone APK permission model
Full-screen alarm intent
Used so an active alarm can bring the alarm screen forward, similar to an alarm-clock safety interruption. This is presented as an alarm feature, not as hidden behavior.
Exact alarm scheduling
Used for time-sensitive check-ins and alarm-related reminders where the family expects the app to alert at a configured time.
Foreground service, vibration, and wake lock
Used while the alarm is active so the alarm can remain visible, audible, and difficult to miss until stopped by an authorized method or safety timeout.
Boot completed
Used to restore alarm and check-in scheduling after the device restarts.
Location
Used only for visible family safety features. The current standalone APK requests foreground location and does not request background location. If future geofence or background-location builds are released, they must include a separate prominent disclosure and Google Play review.
Permissions not requested
The current child APK does not request camera, microphone, contacts, SMS, call log, accessibility service, device admin, or background location permissions. The separate parent APK is dashboard-focused and does not request the child alarm, location, exact-alarm, full-screen, boot, vibration, wake-lock, or foreground-service permissions.
Parent-supervised safety model.
Parent Call Alarm is positioned around visible safety controls, protected parent setup, clear permission explanations, and no hidden surveillance features.