Core Commitment: Absolute Zero Data Collection Philosophy
PrivaGuard is engineered on a fundamental security principle: software cannot leak or compromise data it never collects in the first place. Augionix Technologies ("we", "us", or "our") has intentionally designed PrivaGuard as an air-gapped, zero-knowledge endpoint utility for Windows 10 and Windows 11 (see our technical architecture on how PrivaGuard works).
Unlike conventional software that embeds background telemetry daemons, usage aggregators, or crash collectors, PrivaGuard contains zero third-party tracking software development kits (SDKs), zero user behavioral analytics, and zero remote logging endpoints. We do not inspect, log, or transmit:
- The names, file paths, or executables of the applications you choose to lock.
- Your Master Password, secondary PINs, or recovery passphrases (which are salted, hashed, and stored strictly locally).
- File names, file extensions, or contents stored inside the PrivaGuard Vault.
- Hardware identifiers, Windows Product Keys, MAC addresses, or IP addresses.
- Timestamps of application launches, panic hotkey activations, or charger unplug alerts.
Zero-Telemetry Technical Guarantee & Code Auditability
You can independently verify our zero-telemetry architecture at any time using standard Windows network auditing utilities (Wireshark, Fiddler Classic, GlassWire, or Sysinternals TCPView). PrivaGuard establishes zero outbound TCP/UDP connections during routine protection, background monitoring, and vault encryption operations. Security researchers can inspect our cryptographic implementation in the Official GitHub Open-Core Repository.
Cryptographic Storage & Local Encryption Architecture
All configuration parameters, protection policies, and cryptographic anchors created in PrivaGuard are stored strictly on your local machine within the authenticated user directory:
%LOCALAPPDATA%\PrivaGuard\
Our local cryptographic storage architecture leverages industry-standard primitives to ensure that even users with physical access to your hard drive cannot extract your vault contents or reverse-engineer your master credentials:
-
Master Password Hashing: We utilize PBKDF2 with HMAC-SHA256 executed across 600,000 computation iterations in strict adherence to NIST SP 800-132 recommendations, combined with a unique, cryptographically secure 32-byte pseudo-random salt generated via Windows CryptoAPI (
BCryptGenRandom). The plain-text password is never written to disk or preserved in memory. - Vault File Encryption: Encrypted files and folder containers are ciphered using AES-256 in Galois/Counter Mode (GCM) under NIST SP 800-38D standards. GCM provides authenticated encryption with associated data (AEAD), generating a 128-bit authentication tag that guarantees mathematical integrity and prevents bit-flipping attacks. Learn more in our Folder & File Vault User Guide.
- Windows DPAPI Protection: High-entropy cryptographic secrets are wrapped using the Windows Data Protection API (DPAPI) CryptProtectData, binding access exclusively to your active Windows logon security identifier (SID).
Windows Kernel, Service & API Permissions
To defend running processes against termination by malicious actors, local intruders, or automated Taskkill scripts, PrivaGuard requires administrative privileges during setup to register native Windows system hooks (check our Windows System Compatibility & Requirements Checklist):
-
Process DACL Hardening: PrivaGuard invokes Windows Win32 security APIs (
SetKernelObjectSecurity) to modify the Discretionary Access Control List (DACL) of protected processes. This stripsPROCESS_TERMINATEandPROCESS_SUSPEND_RESUMErights from non-elevated callers. - Session 0 NT Service: PrivaGuard registers a lightweight Windows Service running in isolated Session 0. This service monitors process launch hooks and ensures continuous anti-tamper enforcement even when users lock their desktop or switch active profiles.
-
Safe Mode Execution: PrivaGuard configures minimal registry keys under
HKLM\SYSTEM\CurrentControlSet\Control\SafeBootto ensure protection policies persist if an unauthorized user attempts to reboot into Diagnostic Safe Mode.
No Elevated Privilege Abuse: PrivaGuard never leverages administrative privileges to access private browser history, keystrokes, personal documents outside the designated vault, or remote registry hives. Elevated rights are restricted solely to process enforcement and tamper defense.
Network Independence & Telemetry Auditability
PrivaGuard is deliberately engineered to operate in mission-critical, air-gapped environments. The desktop application has zero dependencies on an active internet connection:
- No Cloud Activation Calls: License validation and software authorization for our perpetual and lifetime license tiers occur entirely on-device using local cryptographic verification.
- Manual Update Checks: If an update notification feature is provided, it performs a lightweight, read-only
GETrequest for a version manifest file over HTTPS without transmitting user metadata or hardware signatures. - Firewall Compatibility: You may block PrivaGuard in Windows Defender Firewall or enterprise endpoint protection software. Blocking all outbound traffic will have zero adverse effect on app locking, password authentication, or vault access.
Regulatory Compliance by Design (GDPR, DPDP 2023, CCPA/CPRA, HIPAA)
Because PrivaGuard is architected as an offline endpoint tool that neither collects nor processes personal data on external systems, compliance with global data privacy frameworks is achieved by mathematical omission:
| Regulatory Framework | Compliance Status | Architectural Mechanism |
|---|---|---|
| GDPR (EU) 2016/679 Articles 5, 25 & 32 |
Fully Compliant | Privacy by Design & Default. Zero personal data collected, stored remotely, or transferred across borders. |
| DPDP Act 2023 (India) Section 6 & 8 (MeitY) |
Fully Compliant | Primary domicile compliance. True data minimization — zero collection, zero storage, and zero cross-border transfer. |
| CCPA / CPRA (California) Cal. Civ. Code § 1798.100 |
Exempt / Safe Harbor | No consumer personal information is ever collected, retained, shared, or sold to third parties. |
| HIPAA Security Rule 45 CFR Part 164 |
Workstation Ready | Provides AES-256 GCM encryption and local process locking to safeguard ePHI stored on clinical endpoints. |
| SOC 2 Type II Alignment Trust Services Criteria |
Least-Privilege Model | Strict process boundary DACL controls; zero persistence of unencrypted master credentials. |
Website Orders & Merchant of Record Privacy: When purchasing software licenses on our website, checkout and payment transactions are processed securely by our global Merchant of Record, Paddle. Transaction data (billing email, invoice records, and fraud screening) is governed by Paddle's Official Privacy Policy. PrivaGuard's desktop application never has access to, nor receives, your payment card or billing details.
In-App Camera Intruder Photo Isolation
When the optional Silent Webcam Intruder Photo module is activated by the user, PrivaGuard leverages the native Windows Media Foundation framework to capture an encrypted photo upon consecutive incorrect master password entries (default: 3 failed attempts):
- Local Capture Only: Intruder photos are encoded and stored directly to
%LOCALAPPDATA%\PrivaGuard\Snapshots\. - Encrypted On-Disk: Snapshot files are immediately encrypted using the local AES-256 subsystem to prevent unauthorized viewing by other local users.
- Zero Cloud Sync: PrivaGuard will never automatically upload, email, or transmit captured intruder images to any server, webhook, or external cloud bucket.
- User Retention Control: You retain complete discretion to configure retention windows (e.g. 7 days, 30 days) or one-click delete all captured security logs directly from the PrivaGuard UI.
Security Inquiries, Policy Amendments & Legal Desk
We may update this Privacy Policy periodically to reflect new software capabilities, security enhancements, or Windows OS modifications. When material updates occur, we will revise the document version and update timestamp at the top of this page.
If you have questions regarding our cryptographic implementation, wish to request an enterprise architectural attestation, or need to report a potential security issue, please contact our dedicated teams: