Privacy Policy

Our Absolute Commitment to Privacy

Unlike traditional firewalls or security suites, SilentWall was designed from the ground up to operate as a completely local, self-contained Windows utility. We believe your desktop activity and network rules are entirely your business.

1. 100% Offline Architecture

SilentWall contains no network calls, connection pipelines, or external API endpoints. The application is completely incapable of transmitting data over the internet. All firewall operations, ruleset compilations, and log diagnostic audits are processed purely within your local PC's user-mode memory space.

2. Zero Data Collection & Telemetry

We do not collect, store, monitor, or harvest any personal data, application metrics, usage patterns, or device details.

• We do not log the executables you drag and drop onto the interface.
• We do not track active/inactive rule count parameters.
• We do not run update check loops or background telemetry collectors.
• No crash logs or diagnostic reports are ever compiled or transmitted to Webelity servers.

3. Local File Storage Only

SilentWall writes your custom rulesets directly to your local system disk. The ruleset config file is written inside the directory: %LocalAppData%\SilentWall\ruleset.json This directory is fully restricted under Standard Windows ACLs, ensuring it is only accessible to your current Windows user profile and the Local System account.

4. Windows Filtering Platform (WFP) Local API Usage

SilentWall configures system blocks using the Windows Filtering Platform (WFP) and COM firewall interfaces (`INetFwPolicy2`). The application acts as a front-end client layer to register WFP rules inside standard Windows firewall engines. No custom network drivers or external diagnostic filters are loaded, maintaining your local system's pure native integrity.

5. Real-Time Alert Event Logging

Our real-time notification listener hooks exclusively to your local Windows Security Event logs (specifically Event ID 5157). These block events are processed entirely inside the tray client, triggering instant desktop alerts locally. None of these logs are cached on disk or sent over a network.