Privacy policy.

1. Scope and operator

This policy covers CYBERGUARD 360 for Android, its optional configured security-center API and the public pages at cyberguard360.in. The stated app operator is Buildnova Technologies Private Limited. The app is designed to provide best-effort security assistance; it does not guarantee that any device, app, file, message or link is safe.

The public website is static and, in the included version, does not use advertising, analytics tags, visitor accounts, contact forms or non-essential cookies. A hosting provider may process technical request information such as IP address, requested page, time and browser details in server logs according to its configuration and policy. Confirm the selected host’s logging and retention before launch.

2. Information processed on your device

On-device-only mode is enabled by default. Supported checks run locally when possible. Depending on features and permissions you choose, the app may process:

• Selected Android security and network posture signals, such as Android version and patch level, screen-lock and encryption status, developer/debugging settings and selected high-impact access.
• Installed-app labels, package identifiers, requested permissions, install sources and APK information that Android exposes, for app inventory and local heuristic checks.
• App names, selected sensitive permissions and special-access status for a Privacy Advisor review that you start and consent to. This inventory is not uploaded.
• A file or APK you select, for local hashing and metadata checks. Contents are not uploaded by a local check.
• Accessible photos or videos only during a gallery scan you start; hashes are compared locally with cached indicators.
• Links, QR-image contents or text you deliberately share with the app for local analysis. That content is not uploaded by the local check.
• Supported text included in notifications when you separately enable message checks and grant Android Notification Access. The listener filters notifications locally for supported messaging and email apps. Text is used only for the in-memory check, not written to history or logs and not uploaded. Android’s notification previews determine what text is available.
• When optional monitoring is active, Android camera-availability or audio-recording callbacks can indicate sustained screen-off sensor activity. The app stores only the sensor type and time locally (up to 50 events); it cannot identify the app responsible or access camera/microphone content.
• Files in shared storage only when you start a full scan and grant the relevant access. Other apps’ private storage remains inaccessible. File contents are not uploaded.
• Local settings, cached indicators, recent activity and—if used—call-reputation/history, scan findings, quarantine copies and vault notes. Selected account and security records are encrypted locally with an Android Keystore-managed AES-256-GCM key. Other settings and cached threat indicators do not receive that additional record-level encryption. Hardware backing depends on the device; app backups are disabled.

3. Permissions and access

Android permissions and special access are requested in connection with enabled features. You can decline or revoke access; the associated feature may then be unavailable.

The app does not request SMS permission, contacts, call logs, Accessibility Service, usage access or device-admin control to read private content or control the device.

4. Account and subscription information

For registration, the app sends your international phone number, name, email, country, state, city and password to the configured security center. Phone and email ownership are not verified by the app. The server stores the password as a salted PBKDF2-HMAC-SHA256 hash rather than plaintext. The app stores account profile and session data locally encrypted with an Android Keystore-managed key.

Google Play handles subscription checkout, renewals and cancellation. The app sends a generated installation identifier and Play purchase token to the configured security center over HTTPS for entitlement verification. The server stores an encrypted token copy and entitlement information such as product, plan, status and expiry. This verification is required by the current app access flow and can still occur when on-device-only mode is enabled. It does not send scan data or message contents.

Google Play checkout is the source for current localized prices, trial eligibility, renewal terms and cancellation options. See the store information page.

If you explicitly submit a complaint from an enrolled device, its subject and description are sent with the device's identity to the configured security center. Administrators can read the complaint, change its status and reply. Do not submit passwords, one-time codes or payment information. The security-center operator must establish appropriate access, retention, backup and deletion practices.

5. Optional sharing and server features

On-device-only mode blocks optional security reporting and threat synchronization. Turning it off does not automatically grant permission to every feature. Manual scan submissions require a separate sharing confirmation; automatic reports require the corresponding automatic protection setting, consent and enrollment.

Depending on an enabled feature and your action, the security center may receive:

• Enrollment and device profiles: device name, model, Android/app version, security score and selected checks, findings or capabilities.
• Scan reports: limited metadata such as scan type, indicator, risk score, summary or evidence. The API does not accept message or file contents. Reports may be stored as incidents when they match a known threat or meet a configured severity threshold.
• Threat synchronization: downloads a curated indicator list; it does not upload scan results or file contents.
• Community caller reputation: if opted in and server sync is allowed, a one-way hash of a caller number, report category and optional label may be sent. A hash can be guessed and is pseudonymous, not anonymous. The API uses keyed values and returns aggregated reputation information; contacts are not uploaded.
• Family emergency alerts: alert message and, if you choose, location while active. Optional medical details are sent only when you select the per-alert share option. Push payloads contain the alert identifier and a short notification, not coordinates or medical information.

The optional security center may be operated by an organization or another party. Its operator controls server access, hosting, backups and some retention. The app does not designate a single centrally operated vendor cloud.

6. Other services contacted

Some features contact third-party services directly or through configured integrations:

• Google Play: purchase processing and subscription management; the configured server uses Google Play purchase verification.
• Firebase Cloud Messaging: optional family emergency push delivery when configured. Firebase can process the delivery token and message metadata. Push receipt is not guaranteed.
• Have I Been Pwned Pwned Passwords: for a password breach check you start, the app sends only the first five characters of the password’s SHA-1 hash and compares returned suffixes locally. The password itself is not sent.
• CountriesNow: optional state and city suggestions may send the selected country and state; the app caches results. Manual entry remains available.
• GitHub-hosted threat indicators: a plain HTTPS download of public indicator files; no device, app list or user data is sent with the feed request, though the server sees standard network information such as IP address.
• Maps application: when a recipient opens a shared emergency location, coordinates may be passed to the maps application they choose.

These services have their own privacy terms and policies. Confirm current providers and integrations for the deployed version.

7. Retention and deletion

Local history is limited to recent entries (up to 50) and can be removed by clearing app storage or uninstalling. Community caller reports have a 180-day retention window; expired entries are filtered from lookups and purged when reports are submitted. Emergency records older than 30 days are purged when the alert/history API next processes a request, so they may remain longer if the service is unused. Expired refresh sessions are removed during token issuance.

The API does not configure a fixed deletion period for device profiles, incidents, subscription records or audit events. The security-center operator is responsible for setting and documenting retention, protecting backups, restricting administrator access and handling requests to access or delete server-side records. Switching to on-device-only mode, turning off consent or signing out stops future applicable requests but does not erase existing server records.

See account and data deletion for request instructions. To cancel an auto-renewing subscription, use Google Play; cancellation and account deletion are separate.

8. Security

The app encrypts selected local credentials, sessions and security records using AES-256-GCM with Android Keystore-managed keys. The API is intended to use HTTPS outside local development; operators must configure TLS, secure secrets, databases, hosts and backups. No method of transmission or storage is completely secure, and server-side security depends on the operator of the configured service.

9. Children

The app is not designed to collect personal information from children. Do not enroll a child’s device or submit a child’s data unless permitted by applicable law and the security-center operator’s policies.

10. Changes and contact

This policy should be updated if app permissions, data flows, hosting or retention practices change. Material changes will be reflected on this page with an updated effective date.

Data controller / stated operator: Buildnova Technologies Private Limited

Privacy email: support@cyberguard360.in