Before you install a security app on a phone that touches work, ask who publishes it, what it collects, what it needs permission to do, how it updates, and what happens when you leave. A store listing answers some of this in two minutes. The rest you can ask the vendor.
1. Who publishes it?
Look at the developer name on the store page and compare it with the company's own site. A mismatch is a reason to stop. The Safeguard iOS listing names Safeguard.sh Inc as the developer, and the download page links to the same listing.
2. Does it need an account?
An app that is useless without an account is a front end to a service. That is fine, but it means your sign in, your organization's data and your session are in play. The Safeguard listing says a Safeguard account is required.
3. What does the privacy label say?
Apple's listing shows a data collection summary supplied by the developer. For the Safeguard iOS app the developer reports no data collected, and the listing notes Apple has not verified that. Treat a label as a claim to compare with the vendor's privacy policy, not as proof.
4. What permissions does it ask for?
At install and first run, note every prompt: notifications, camera, location, files. For a read and review app, notifications make sense. A request for contacts or location needs a reason. Deny what you do not need. You can usually grant it later.
5. How does it update?
Store installs update through the store. A directly downloaded APK does not. The Safeguard download page says APK updates come from its own page, not from Google Play. Know which one you chose, and diarise the check.
6. How do you verify what you downloaded?
Store apps are signed and checked by the store. For a direct file, compare the published SHA-256 with your download. The Safeguard page publishes one for its APK.
7. What can the app do to your data?
Read only is a smaller risk than read and write. Ask what actions the app can take, and whether those need a separate approval. Prefer apps where risky actions are off by default and need explicit enabling by an administrator.
8. What is the exit?
Can you sign out everywhere, revoke the session, and delete the app without leaving tokens active? Ask your admin to show you where sessions are revoked.
On managed devices
If the phone is managed by your employer, tell your IT team before installing. Many policies restrict sideloading and some require app approval. Getting a yes first is faster than being asked to remove the app later.
Scoring it
Give each question a pass, unclear or fail. Any fail on publisher, account handling or update path is a stop. Unclear answers are a question to the vendor, not a deal breaker.
Quick check
Is a no data collected label enough to trust an app?
No. It is the developer's own statement, and the store may not have verified it. Read the privacy policy and ask the vendor how data is handled.
Sources
Last reviewed: 19 October 2026.
