MalGuardLocal analysis
Files selected for supported local scanning are analyzed on the user's device unless a feature explicitly states otherwise.
Privacy
Local-first, with network use disclosed.
This page summarizes the current repository privacy policy. The source policy in MalGuard Core remains the authoritative project document.
Optional network features
Some features may check signed updates, retrieve threat-intelligence metadata, or look up a file hash or other non-file metadata against a configured reputation service.
File transfer
A file itself must not be uploaded to a third-party service without an explicit user action and clear disclosure.
Diagnostics: MalGuard is designed to keep error reporting local-first. Users may choose to export or submit diagnostic information when asking for support.
Anonymous release metrics: Official download buttons may use GitHub Release assets so GitHub can expose aggregate download counts. Builds that include first-successful-launch counting make one request to a small public GitHub Release beacon and store only a local marker to avoid counting the same installation again. MalGuard does not attach a user, device, advertising, or installation identifier to that request.
Anonymous compatibility report: Packaged Windows builds may send one coarse report after the first successful launch containing only the MalGuard version, Windows build, x64/ARM64 architecture, a bucketed CPU-core range, a bucketed RAM range, and system language. The report excludes account names, computer names, hardware serial numbers, network adapter identifiers, precise location, file paths, scan results, and installation identifiers. The server may forward this report as an administrative notification email when configured.
Website reports
Your report goes to MalGuard Security.
The message and optional name/reply email you enter in the report form are sent through our email provider to malguard.security@gmail.com so we can review and respond. The form accepts text, not files. Our application logs a report reference and mail-provider acknowledgement, not the report body. Request metadata may be processed by our hosting provider for service operation and abuse protection. Do not include passwords, private keys, or real malware.