1. Introduction & Scope
This Privacy Policy describes how ZMatrix Hyper ("ZMatrix Hyper," "the App," "we," "us," or "our") collects, uses, and protects information when you use our Windows desktop application. ZMatrix Hyper is developed and operated by Halonex.
ZMatrix Hyper is a performance-tuned antivirus built for gamers. It combines the same signature-based detection engine, machine learning classifier, and heuristic/behavioral engine found in ZMatrix Lite, layered with gamer-focused features: Game Mode, an in-game performance overlay, game library-aware whitelisting, and low-latency scan throttling. Like ZMatrix Lite, ZMatrix Hyper is built entirely in user mode — it does not install any kernel-mode driver, minifilter, or other privileged system component.
By downloading, installing, or using ZMatrix Hyper, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with any part of this policy, please discontinue use of the App immediately.
The Human Summary
ZMatrix Hyper protects your PC while you play, without a kernel driver competing for resources or system access. Game Mode and the performance overlay run entirely on your machine, your game library is only used locally to reduce false positives, and your files are never uploaded — only their hashes.
2. Information We Collect
ZMatrix Hyper requires a Halonex account and an active license to run. The categories of information involved in the App's operation are:
- Account Information: When you create a Halonex account, we collect your email address and a salted, hashed password. We never store your password in plain text.
- License Information: Your license key, activation status, and subscription/renewal status, used to validate that your installation is entitled to protection updates.
- Device Install Identifier: A one-way hash derived from hardware identifiers on your machine, used solely to enforce per-license device limits. This identifier cannot be reversed to reveal your actual hardware serial numbers.
- Scan & Detection Metadata: When the real-time or on-demand scanner flags a file, we record the file's SHA-256 hash, the local file path, the detecting engine (signature, ML, or heuristic), the threat classification, and the action taken (quarantine, delete, ignore). The contents of the file itself are not uploaded.
- Cloud Reputation Queries: File hashes for newly encountered or ambiguous files are sent to our reputation service to check them against a global threat database.
- Product Telemetry: App version, detection engine/definition versions, OS build number, and general scan performance statistics, used to monitor product health and prioritize engine improvements.
- Diagnostic Reports (opt-in): If the App crashes or you choose to submit a support ticket, you may optionally include a diagnostic log or crash report.
- Quarantine Sample Submission (opt-in): If you choose to submit a quarantined file for deeper analysis, the file itself is uploaded only after an explicit, per-file consent prompt.
- Local Game Library Index: To power game-aware whitelisting, ZMatrix Hyper reads installed-game manifests from supported launchers (e.g., Steam, Epic Games, GOG) — specifically game titles and executable file paths — to reduce false-positive scan interruptions during play. This index is built and used entirely on your device.
- Local Performance Counters: The in-game overlay reads local hardware performance counters (FPS, CPU/GPU usage, CPU/GPU temperature) via standard Windows and vendor APIs to render the overlay. This data is not transmitted off your device.
- Foreground Process Name (Game Mode): To detect when a game is running in fullscreen, ZMatrix Hyper reads the name of the current foreground process. This is used only to trigger Game Mode locally and is not logged or transmitted.
The Human Summary
The gamer-specific features — Game Mode, the overlay, and game-library whitelisting — all run locally and read only what they need (a process name, a game folder listing, hardware performance counters) to do their job on your machine. None of that gaming data leaves your device by default.
3. Information We Do Not Collect
We want to be explicit about the data we do not collect, access, or store:
- No browsing history — We do not read or log the websites you visit.
- No keystrokes — ZMatrix Hyper does not include a keylogger of any kind.
- No screen or webcam capture — We do not access your camera, microphone, or screen contents, including during gameplay.
- No document or personal file contents — Files are hashed, not read, uploaded, or indexed for content.
- No voice or in-game chat — We do not access voice chat, text chat, or any game-internal communications.
- No gameplay recording — ZMatrix Hyper does not record or transmit gameplay video or input.
- No contacts, chats, or emails — We do not access or scan your messaging or email applications.
- No advertising identifiers — We do not use advertising SDKs or cross-app tracking.
- No sale of data — We do not sell, rent, or trade personal data to third parties.
4. How Your Information Is Used
- Threat Detection: File hashes and behavioral signals are used to classify files as safe, suspicious, or malicious across our three detection engines.
- License Enforcement: Account and device-identifier data confirm that your installation is validly licensed and within your subscription's device limit.
- Game-Aware Protection: Your local game library index and foreground process name are used to whitelist trusted game executables and trigger Game Mode, reducing false positives and scan-related stutter during play.
- Performance Overlay: Local hardware performance counters are used exclusively to render the in-game FPS/system overlay in real time.
- Product Improvement: Aggregated detection and performance telemetry helps us tune detection accuracy and reduce false positives.
- Support: Diagnostic reports you choose to submit are used exclusively to investigate and resolve the issue you reported.
We do not use your information for advertising, behavioral profiling unrelated to threat detection, or any purpose beyond delivering and improving the App.
5. Detection Architecture — User-Mode Only
ZMatrix Hyper is deliberately architected to avoid kernel-mode components — a priority for gamers, where kernel drivers are a common source of crashes, anti-cheat conflicts, and performance overhead. Real-time protection is implemented using standard, documented Windows user-mode facilities — including the Antimalware Scan Interface (AMSI), user-mode consumption of Event Tracing for Windows (ETW) providers, and file-system change notifications — rather than a custom kernel-mode minifilter driver placed directly in the file I/O path.
| Engine | What It Analyzes | Where It Runs |
|---|---|---|
| Signature-Based | File hash and known-malware pattern matching | Local, against a periodically updated definitions database |
| Machine Learning | Static file features (structure, entropy, metadata) — no content upload | Local inference, with optional cloud-assisted classification for ambiguous verdicts |
| Heuristic/Behavioral | Process and file-system behavior patterns observed via user-mode OS APIs | Local, in real time |
Because ZMatrix Hyper holds no kernel-mode driver, it has no elevated system-level access beyond what any standard Windows application can request, and does not compete with anti-cheat kernel drivers for the same privileged space.
The Human Summary
No kernel driver means fewer conflicts with anti-cheat software, fewer blue screens, and no quiet backdoor into the deepest parts of Windows. Everything ZMatrix Hyper sees, it sees through the same front door every other application uses.
6. Gamer Mode & Performance Features
6.1 Game Mode
ZMatrix Hyper detects when a supported game is running in fullscreen by reading the foreground process name. When active, Game Mode automatically silences non-critical notifications and defers scheduled scans until you exit the game. This detection happens entirely on-device and is not logged or transmitted.
6.2 Performance Overlay
The optional in-game overlay displays FPS, CPU/GPU usage, and CPU/GPU temperature, read locally via standard Windows and hardware-vendor performance APIs. This data is rendered directly to your screen and is not stored beyond the current session or transmitted to Halonex.
6.3 Game Library Integration
To reduce false-positive interruptions, ZMatrix Hyper reads installed-game manifests from supported launchers (Steam, Epic Games, GOG) to build a local whitelist of trusted game executables. Only game titles and executable paths are read — no save data, screenshots, achievements, or other launcher account data is accessed.
6.4 Low-Latency Scan Throttling
During active gameplay, ZMatrix Hyper dynamically lowers the CPU and I/O priority of background scanning to minimize impact on frame rate. This is a purely local resource-scheduling decision and involves no additional data collection.
6.5 Optional Cross-Device Settings Sync
If you enable this optional feature, your Game Mode preferences and game whitelist may be synced across your licensed devices via your Halonex account, encrypted in transit and at rest. This feature is off by default.
The Human Summary
The gamer features are built to stay out of your way and out of our servers. FPS numbers, temperatures, and your list of installed games stay on your PC unless you specifically turn on cross-device sync.
7. Third-Party Services
- Cloud Reputation Service: File hashes are checked against our threat-intelligence infrastructure to deliver faster, more accurate verdicts. Only hashes and file metadata are transmitted — never file contents, unless you explicitly submit a sample.
- Payment Processor: License purchases and renewals are handled by a PCI-compliant third-party payment processor. Halonex does not store your full payment card details.
- Transactional Email Provider: Used to deliver license keys, receipts, and account-related notifications to your registered email address.
- Game Launcher Metadata (local only): ZMatrix Hyper reads local manifest files from Steam, Epic Games, and GOG installations on your device. It does not connect to these platforms' servers or accounts.
We do not integrate any advertising networks, social media SDKs, or general-purpose analytics platforms.
8. Data Storage & Security
- Quarantine Vault: Quarantined files are encrypted with AES-256 and stored locally in an isolated vault on your device, inert and unable to execute.
- Account Data: Passwords are hashed and salted; email addresses and license records are encrypted at rest on Halonex servers.
- Data in Transit: All communication between the App and Halonex services is encrypted via TLS 1.3.
- Game Library & Performance Data: Stored locally only, unless you explicitly enable cross-device settings sync, in which case the synced subset is encrypted in transit and at rest.
- No Kernel-Level Storage Access: Because ZMatrix Hyper runs entirely in user mode, it cannot bypass standard Windows file permissions to access data outside what it is explicitly granted.
The Human Summary
Quarantined files are encrypted and isolated on your own machine. Anything that does travel to us — including the optional sync feature — is encrypted in transit, and your account credentials are never stored in plain text.
9. Your Rights & Controls
Under applicable data protection regulations including the GDPR and the CCPA, you have the right to access, correct, delete, and port your personal data. You can exercise these rights directly from the App's account settings or by contacting us at the address below.
10. System Access
ZMatrix Hyper requests the following Windows-level access, all through standard, non-privileged APIs:
| Access | Purpose |
|---|---|
| File System Read Access | Required to compute file hashes and perform scans, and to read installed-game manifest files. ZMatrix Hyper does not transmit file contents. |
| Network Access | Required for cloud reputation lookups, definition updates, and license validation. |
| Process List (read-only) | Required for behavioral/heuristic analysis and to detect the foreground game process for Game Mode. ZMatrix Hyper does not read process memory contents. |
| Hardware Performance Counters | Required to render the FPS/system overlay (CPU/GPU usage and temperature). |
| Windows Startup Entry | Required so real-time protection is active from system boot. |
- No kernel-mode driver installation
- No camera or microphone access
- No browser extension or browsing-history access
- No access to game accounts or online multiplayer data
11. Children's Privacy
ZMatrix Hyper is not directed at children under the age of 13 (or the applicable minimum age in your jurisdiction). Because account creation requires an email address, we do not knowingly permit account registration by children. If we learn that a child's account has been created without appropriate parental consent, we will take steps to delete it.
12. Data Retention
Account and license records are retained for as long as your account remains active, plus a limited period thereafter to comply with financial and legal record-keeping obligations. Scan and detection metadata associated with your device is retained locally and, where transmitted for cloud-assisted detection, is retained on our servers for a limited window to support threat-intelligence correlation before being aggregated or deleted.
Local game library data and performance-overlay readings are not retained beyond your current session unless cross-device sync is enabled, in which case synced settings persist on our servers until you disable sync or delete your account.
You may request deletion of your account and associated server-side data at any time. Locally stored scan history and quarantine contents are removed when you uninstall the App.
13. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in the App's functionality, legal requirements, or our operational practices. When we make material changes, we will update the "Effective Date" and "Last Updated" dates above and, where appropriate, notify you in-app. Your continued use of ZMatrix Hyper after any changes constitutes your acceptance of the revised terms.
14. Contact Information
If you have any questions, concerns, or requests regarding this Privacy Policy or ZMatrix Hyper's data practices, please contact us:
- Developer: Halonex
- Email: [email protected]
- Website: halonex.app
- Privacy Centre: privacy.halonex.app
The Human Summary
Have a question about your privacy? Reach out to us at [email protected]. We take every inquiry seriously and will respond as quickly as possible.
This privacy policy applies to the ZMatrix Hyper Windows application published by Halonex.
© 2026 Halonex. All rights reserved.