The Safeguard download page offers Safeguard-1.0.2.apk, 69 MB, for phones without Google Play or for company distribution. To install it safely, download only from safeguard.sh, compare the SHA-256 checksum on the page, allow installs for your browser only for the install, and turn that permission off afterward.
What does the download page say?
- The file is Safeguard-1.0.2.apk, 69 MB.
- It is for phones without Play, or for company distribution.
- You must allow installs from your browser.
- Updates for the APK come from the Safeguard site, not Google Play.
- You should check the SHA-256 checksum before installing.
Step 1: Verify the source
Type safeguard.sh/download yourself or use a bookmark. Do not follow a link from a message, even a convincing one, because APKs are a favorite way to deliver malware. Check the address bar shows the safeguard.sh domain over HTTPS.
Step 2: Check the file before you open it
After downloading, confirm the file name and size match: Safeguard-1.0.2.apk and about 69 MB. A very different size is a reason to delete it.
Then compare the SHA-256 checksum with the one on the download page. On a computer this is a single command, and on a phone a file manager or checksum app can show it. If the values differ in any character, delete the file. We cannot print the checksum here, since it can change with each release and the page is the source.
Step 3: Allow installs narrowly
Android asks you to allow installs from the app you used to download, in this case your browser. Allow it for that one app only. Do not enable a general unknown sources switch for everything, where your Android version offers a choice.
Step 4: Install, then turn it back off
Install the app. Then return to settings and remove the install permission from your browser. This stops a later malicious download from installing in the same way. Check that the app shows in your app list under the right name.
Step 5: Plan for updates
Because updates come from the Safeguard site, put a reminder in your calendar to check for new versions. An old APK keeps old bugs. If Google Play is available to you, the store route is simpler and handles updates.
What to check for a company rollout
Distribute the file from your own device management system, with the checksum recorded. Tell people not to install from anywhere else. Keep a list of who has the APK, since the usual store update path does not cover them.
What we cannot verify
We did not see the APK's signing details or its permissions list, so we make no claim about them. Review the permissions Android shows during install and ask Safeguard if anything surprises you.
Why take this much care?
An APK bypasses the review a store provides, so the checks move to you. None of them is hard, and together they make a tampered file very unlikely to get through: a trusted source, a matching checksum and a narrow, temporary permission.
What to do
- Use the official page only.
- Compare name, size and SHA-256.
- Allow installs for the browser only, briefly.
- Remove the permission after installing.
- Track updates yourself.
Quick check
What if the checksum does not match?
Delete the file and do not install it. Download again from safeguard.sh/download. If it still differs, contact Safeguard.
Will Google Play update the APK?
No. The page says updates for the APK come from the Safeguard site.
Sources
Last reviewed: 18 October 2026.