A guided view

Know what happens at each step.

Use the features you need, understand the permission behind them and choose whether a feature stays on-device or uses a configured service.

From setup to a useful check

Set up your account and subscription

The app’s current release flow uses an account and Google Play subscription. Account sign-in and subscription verification contact the security center configured in the app, even with on-device-only mode on.

Choose what you want to review

Start a link, QR, file, app, device or privacy check when you need it. Local scan inputs such as file contents, shared message text and QR-image contents are not uploaded by those checks.

Grant only the access you use

Android asks for runtime and special access where required. For example, location is requested for a location suggestion or an emergency alert; Notification Access is needed only for optional notification checks.

Review the result—not just a score

Heuristics and threat matches are signals. Examine the available explanation, consider the limits of the check and use your judgment before acting.

Decide whether optional services are right for you

Separate settings govern protection monitoring, optional security-center reporting and sync, community caller reputation and family emergency features. Turn off or revoke access when you no longer want a feature.

What “on-device-only” means

On-device-only mode blocks optional security reporting and threat synchronization. Supported offline checks can still run locally. It does not prevent the account registration/sign-in and subscription entitlement requests needed for the app’s current access flow, or optional location requests you initiate for an emergency alert.

Threat matching and local risk heuristics are not malware verdicts. A missing match does not mean an item is safe.

Permissions are tied to features

Android permission and special-access prompts are controlled by Android. Depending on features used, the app may request selected photo/media access, storage access, notification permission, Notification Access, call-screening role, location, or SIM phone-number access. The app does not request SMS permission, contacts, call logs, camera or microphone permissions.

Some access such as installed-app visibility and all-files access is subject to Android and Google Play policy review. Access can be declined or revoked in Android settings; the related feature may then be unavailable.

Connected features are distinct

  • Account and billing: account details and the Play purchase token/installation identifier are sent to the configured security center for access and entitlement verification.
  • Optional reporting: sharing needs a separate user action or the relevant explicit automatic-protection setting and consent. The API accepts security metadata, not message or file contents.
  • Community caller reputation: opt-in and server sync are required. A one-way caller-number hash is pseudonymous, not anonymous.
  • Family emergency alerts: the user starts the alert and can choose whether to share location or medical information. Location sharing is limited to the active alert.

Service operators control server hosting, administrator access, backups and some retention. Ask the operator of your configured security center about its deployment and records.

How to interpret results

Detection depends on available indicators, Android data and the analysis method. A false positive or missed detection is possible. CYBERGUARD 360 does not replace Android security updates, backups, careful handling of sensitive information or professional help.

Want the detail?

See the full feature guide, privacy policy and frequently asked questions.