Privacy
The short version: IronWall doesn't send your data anywhere because IronWall doesn't have anywhere to send it.
What stays on your device
All scanning runs locally on your CPU. Files, file paths, scan results, quarantined items, and configuration never leave your machine. There is no cloud sandbox, no upload, no “send sample for analysis” toggle.
What we send over the network
Two things, both anonymized:
- Signature updates. IronWall issues HTTPS HEAD requests to a static signature feed to check whether new signatures are available. No identifiers, no cookies.
- Update checks. The Tauri updater pings a static manifest URL to learn the latest version number. Same: no identifiers, no cookies.
What we don't have
- No user accounts.
- No email collection.
- No analytics SDKs (no Mixpanel, GA, Amplitude, Sentry, etc.).
- No advertising identifiers.
- No backend that knows you exist.
This website
ironwall.app is a static marketing site. It loads Inter from Google Fonts; that's the only third-party request. No analytics scripts. No cookies set by us.
Open source
Privacy claims are easy to make. IronWall is MIT-licensed, so when the repo goes public you'll be able to audit every line of the scanner, the network code, and the updater.
Contact
Questions or concerns: hello@ironwall.app. (Address is a placeholder until the project goes public.)
Last updated: May 2026.