Notify others if you haven't used your device in a given period of time
About this app
Keep Alive will send a custom message via SMS to one or more people if you haven't used your device in a given period of time. Intended to be used as a failsafe for those living alone in case of an accident or other emergency. Once the settings are configured, no further interaction is required.
- 100% Device-based, no cloud services or accounts required - Free with no ads or trackers - Open Source (https://github.com/keepalivedev/KeepAlive) - Minimal Battery Usage - Multiple SMS Recipients - Custom Alert Message - Optional: Include Location Information in SMS - Optional: Place a phone call with speakerphone enabled - Optional: Send an HTTP request to a custom URL
Requirements Keep Alive requires that your device has an active cellular plan. WiFi calling and messaging will be used if the device supports it.
How it Works Keep Alive uses either your device's lock screen or another app(s) to detect activity. If your device hasn't been lock or unlocked for a set period of time, or if you haven't accessed the selected app(s), you will be prompted with an 'Are you there?' notification. If this notification is not acknowledged an Alert will be triggered. Based on the configured Emergency Contact Settings, one or more SMS messages and/or a phone call will be placed to notify others that you may be in need of assistance.
WARNING: If your device restarts, Keep Alive will not be able to check for recent activity until the screen is unlocked. On Android 7.0+, Keep Alive can still send an alert before the screen is unlocked but must assume you have been inactive based on its last saved state. On older Android versions, Keep Alive cannot run at all until the screen is unlocked and alerts will not be sent.
Main Settings - Monitoring Method - Choose between using the lock screen or another app(s) to detect activity. If using another app(s), you will be prompted to select the app(s) to monitor. - Hours of Inactivity Before Prompt - how many hours since your phone was last locked or unlocked before you are prompted with an 'Are you there?' notification. Defaults to 12 hours - Minutes to Wait - if the prompt is not acknowledged within this time, an Alert will be sent based on the configured emergency contact settings. Defaults to 60 minutes - Rest Period Time Range - a range of time during which inactivity will not be counted. For example, with 'Hours of Inactivity' set at 6 hours and a Rest Period of 22:00 – 6:00, if the device is last used at 18:00, the 'Are you there?' check would not be sent until 8:00. Note that an alert can still be sent during a rest period if the 'Are you there?' check was sent BEFORE the start of a rest period. - Auto-Restart Monitoring After Alert - If enabled, monitoring will be automatically restarted after an Alert is sent. - Alert Webhook - Configure an HTTP request to be sent when an Alert is triggered
Emergency Contact Settings - Phone Call Number (Optional) - when an Alert is triggered a phone call will be placed to this number with speakerphone enabled
One or more SMS recipients can be configured with: - Phone Number - the phone number to send the Alert SMS to - Alert Message - the message that will be sent when an Alert is triggered - Include Location - if enabled, your location will be included in a second SMS
Privacy/Data Collection No data is collected other than the configured settings and nothing is shared with the developers or any 3rd parties. The only data transmitted is to the configured emergency contacts.
Disclaimer - Not responsible for SMS or phone call charges incurred by the use of the Keep Alive app - The operation of the Keep Alive app is dependent on the device, software, and network connectivity. The developers are not responsible for any failure due to device malfunctions, software incompatibilities, or network issues.
Licensed under Apache-2.0.
What's New in v1.5.1
Imported from the F-Droid repository index.
- * Add full-screen "Are you there?" prompt
- * Add Spanish translation
- * Alerting now works after a reboot before first unlock
Version history
Jul 1, 2026 · 2.5 MB · Android API 22–36 · code 151
Imported from the F-Droid repository index.
- * Add full-screen "Are you there?" prompt
- * Add Spanish translation
- * Alerting now works after a reboot before first unlock
SHA-256 480621da7c870831cbc4ad4876b4ccb8400014c105a8f8ac48b7a7c30b03f750
Nov 3, 2025 · 2.4 MB · Android API 22–35 · code 133
Imported from the F-Droid repository index.
- * Add Exact Alarm Setting
- * Mask Phone Number in Debug Logs
- * Add Support for Themed Icons
- * Add Chinese Translation (thanks @jondome)
- * Add Italian Translation (thanks @albanobattistella)
- * Create 'Lite' Version That Removes Webhook Functionality and Internet Permission
SHA-256 77fa48d30208377727279bf1a68b57c17ea358dae078b758774cd1cc1ef818b1
Apr 25, 2025 · 2.3 MB · Android API 22–35 · code 132
Imported from the F-Droid repository index.
- * Update dependencies
- * Fix issue with Rest Period alarm time
SHA-256 a106a20e0592142efac62451941a4a1452375393a3438c060ec7d4a64e239d39
Will it run on your device?
78%
- Runs on a broad range of modern Android versions.
- ABI coverage is focused on newer 64-bit devices.
- Aligned with the latest Android target SDK expectations.
Installation Guide
Open Settings on your Android device
Go to Security → Unknown sources (or Install unknown apps)
Enable "Allow from this source" for your browser or file manager
Open the downloaded APK file from your Downloads folder
Tap "Install" and wait for installation to complete
Launch the app from your home screen
Make sure to re-enable Unknown Sources restrictions after installation for security.
How to install this safely
How to verify the file you downloaded
Before you install anything, confirm the file is the one described here. On a computer, run shasum -a 256 your-download.apk (macOS or Linux) or certutil -hashfile your-download.apk SHA256 (Windows), then compare the output character-for-character with the SHA-256 on this page. If a single character differs, the file is not the build we recorded — delete it.
What the signing certificate proves
Every Android app is signed with a private key that only its developer holds. The fingerprint on this page is a hash of the matching public certificate, and it proves continuity rather than identity: it tells you a build came from whoever signed the earlier ones. Android enforces this at install time — if a package claiming to be io.keepalive.android is signed with a different key, the system will refuse to install it over your existing copy. A fingerprint that changes between releases is worth pausing on, because a repackaged app that has been modified by someone else cannot keep the original signature.
How to roll back to an earlier version
If the current release misbehaves, 1.3.3 is the last build before it. Android will not install an older version code over a newer one, so you must uninstall Keep Alive first — which clears its local data unless you have a backup. Reinstall the older APK only if its signing fingerprint matches the build you already trust, and check the API range: an older release may target an Android version your device has moved past.
Why we list sources instead of hosting everything
The official store channel is almost always the right choice: it updates automatically and carries the publisher's own distribution guarantees. A direct APK is useful when a device has no store access, when a rollout has not reached your region, or when you need a specific version — and only when the publisher has authorized that copy. APKBrowse does not list pirated, cracked, or unauthorized rebuilds of Keep Alive, and a listing is removed when the evidence for it stops holding up.
Get Keep Alive
Every source we list for io.keepalive.android is legality-reviewed. Pirated or cracked builds are never offered.
Other sources
F-Droid listing
officialF-Droid builds this app from source and signs it. This is its official listing, with older builds and full release notes.
Source code
verified publisherThe upstream repository this build is compiled from.
We check legality and signature continuity, but device behaviour still varies. Install at your own discretion.
App Information
Security Verification
We record provenance; we do not run malware scans. Verify the hash yourself before installing.
SHA-256 Hash
480621da7c870831cbc4ad4876b4ccb8400014c105a8f8ac48b7a7c30b03f750
Signing certificate
c45567b712d6fd7979df14f66f8a5c25859ee223e1f07e915a7eee201c14baef
Permissions Required
Previous Versions
The signing certificate fingerprint for this release is on record, so a build that does not match it did not come from this publisher.
Report a problem with this listing
A listing is only as good as its corrections. If a source is broken, a signature looks wrong, or this app should not be here, tell the moderation team.