CyberGuard // Legal & privacy

Privacy
Policy.

EFFECTIVE DATE: SEPTEMBER 15, 2026

Privacy Summary: CyberGuard operates on a strict privacy-by-default model. We do not require accounts, do not collect personal identifying information, do not track location, and never sell or monetize user data.

1. Overview

This Privacy Policy explains how CyberGuard handles information when you use our mobile application and related audit utilities. CyberGuard is an automated cybersecurity posture analyzer designed to inspect publicly available HTTP response headers, TLS configurations, and DNS anti-spoofing records such as SPF and DMARC for websites and APIs entered by the user.

2. Information We Do Not Collect

CyberGuard does not require personal data for its core features. We do not collect or access:

  • Personal identity details, including name, physical address, phone number, or government identifiers.
  • User accounts, passwords, login credentials, or social-profile authentication.
  • Financial information, including payment-card or bank information.
  • Precise geolocation, device IMEI, MAC address, advertising ID, contacts, media, camera, or microphone data.

3. Information Processed During Use

Target domains and URLs: When you initiate a scan, the public domain or URL you enter is used for passive requests to inspect public HTTP headers, TLS information, and DNS records.

Local audit history: Scan results, calculated grades, and timestamps are designed to be stored strictly on-device in a local Room/SQLite database. This information is not uploaded to a central analytics database.

Diagnostics: The Android application may record standard, non-identifying system diagnostics after unexpected failures to support stability.

4. Android System Permissions

  • android.permission.INTERNET: required for standard outbound HTTP/HTTPS requests and public DNS-over-HTTPS lookups.
  • android.permission.ACCESS_NETWORK_STATE: used to identify active connectivity before an audit starts.

CyberGuard does not request runtime permissions for location, contacts, camera, audio, or external-media storage.

5. Third-Party Network Requests

CyberGuard sends passive outbound requests to the public target servers selected by the user and may query public DNS-over-HTTPS resolvers for public SPF and DMARC TXT records. These requests are intended to contain the public domain being inspected, not personal user data. CyberGuard does not integrate third-party advertising networks, telemetry trackers, social trackers, or data brokers.

6. Data Retention & Deletion

Because Android audit history is stored locally, you can remove individual records or clear the full history through the application. Uninstalling the application or clearing its storage permanently removes its locally stored audit records.

7. Children’s Privacy

CyberGuard is an administrative utility for IT professionals, developers, and general audiences. We do not knowingly collect personal information from children under 13, or under 16 where applicable.

8. Security

Outbound audit traffic uses TLS/HTTPS where supported by the target service. The privacy-first design minimizes external storage of personal information because CyberGuard does not rely on a central user-data repository for audit history.

9. Policy Changes

We may update this policy to reflect new security checks, Android platform requirements, or regulatory changes. Updated versions will be published with a revised effective date.

10. Contact Information

ApplicationCyberGuard (Compliance)
Application IDcom.aistudio.cybercompliance.kcxq
Developer Emailmatrichug@gmail.com