Links, messages and QR codes
Check links, URLs, text deliberately shared to the app and QR-image contents for suspicious patterns and known threat indicators. Message notification checks are a separate, optional feature that requires Android Notification Access and must be turned on by the user.
- Scan a link or text before deciding whether to open it.
- Analyze a QR code locally after you choose to scan it.
- When enabled, notification checks analyze only supported app notification text Android delivers; the app does not read private chat databases or full message histories.
- Notification message text is used for an in-memory check and is not included in generic risk alerts or sent to the security center.
Checks may miss harmful content or flag something harmless. A result such as “no known match” is not a safety certification.
App, file and media checks
Review installed apps and user-selected files or media using local signatures, metadata and heuristic checks. Optional full-storage scanning requires the user to grant Android’s “All files access” in system settings. Other apps’ private storage remains inaccessible.
- App Shield and scan tools review app information Android makes available, such as package details, permissions and install source.
- File and APK checks can calculate hashes and inspect metadata on the device; file contents are not uploaded by a local check.
- Gallery checks run only when started by the user and only for media Android allows the app to access.
- Optional automatic checks can inspect new downloads or app installs when the relevant setting, permissions and protection consent are enabled.
- Flagged downloads may be copied into encrypted local quarantine. The original file is not automatically deleted.
Device security and privacy tools
Device assessment summarizes selected Android security and network posture signals, such as Android version and patch level, screen-lock and encryption status, developer settings and selected high-impact access. Privacy Advisor can review app permission and special-access information after the user consents.
When the user starts the real-time monitor, Android’s public camera-availability and audio-recording callbacks can help flag sustained sensor activity while the screen is off. The app records the sensor type and time locally, but Android does not identify which app caused the activity. CYBERGUARD 360 does not request camera or microphone permission and does not capture sensor content.
Other tools include a local activity history, optional scheduled app/device checks, selected threat-indicator synchronization and a private vault. Availability and scan scope depend on Android version, permissions and settings.
Caller screening and optional reputation
On supported Android versions, users can request the call-screening role through Android’s own system prompt. The app can check incoming caller numbers against local rules and reputation information, then let the user choose how to handle a call. It does not request contacts or call-log access and does not access call audio.
Community reputation is a separate opt-in. When enabled and connected to a configured security center, a one-way hash of the caller number can be sent for aggregated lookups or reports. A hash can still be guessable, so it is pseudonymous—not anonymous. Contacts are not uploaded.
Family medical emergency alerts
Signed-in users can create one-time family invitations and share alerts with up to seven accepted app accounts. Invitations must be accepted. When the user confirms an alert after a cancelable countdown, the configured security center records it and can send a short Firebase push notification.
- Location permission is requested only when starting an alert. If granted, location is shared only while that alert is active and a visible Android foreground-service notification is shown.
- Medical information is optional and is sent only when the user explicitly selects the per-alert share option.
- Push delivery depends on Firebase setup, device/network settings and notification permission; delivery is not guaranteed.
- Alerts are not a replacement for contacting local emergency services.
Optional security center
The app can connect to a self-hosted security-center API for account access, enrollment, optional reporting, threat synchronization and emergency features. The user’s organization or another operator may run that service; it is not a single central CYBERGUARD 360 cloud by default.
On-device-only mode blocks optional reports and threat synchronization, but account registration/sign-in and subscription entitlement verification still contact the configured security center. Manual reports need separate sharing confirmation; automatic reports require the relevant feature and protection consent.
Subscription access
The current project configuration requires a Google Play subscription for app use. Google Play handles checkout and renewals; the configured security center verifies entitlements. Availability, price, trial eligibility and renewal terms must be confirmed in the live Google Play checkout for the user’s account and region.
Not a guarantee of protection
Risk scores, heuristics and threat-list matches are decision support. They can be incomplete, delayed or incorrect and do not replace device updates, careful judgment, backups or professional incident response. Review details and choose your next step.
For data flows and Android permissions, read the privacy policy. For setup and user controls, see how it works.