Network designs, firewall policies and device configurations are sensitive artifacts. This page states plainly what runs in your browser, what we store, who processes it, and how the platform is secured — so your security review has something concrete to check.
The analysis engines — design validation, Firewall Studio rule and NAT analysis, what-if reachability simulation, and Config Compare — are client-side code. When you drop a firewall policy workbook, a hit-count CSV or a pair of configs into those tools, the parsing and analysis happen in your browser tab.
Check it yourself:open your browser's DevTools Network panel and run a comparison or policy analysis — you will see no request carrying your file's contents.
Designs are saved to your account when you are signed in and press save (or autosave on your own project) — storage is the product. Guest playground work is not persisted server-side. Publishing is explicit and two-gated: making a design public requires it to be published and the public toggle set, and public copies are automatically scrubbed — management IPs, DNS/NTP servers, AAA and SNMP secrets, credential references, banners and raw configs are removed from what public viewers receive.
A third-party-style penetration assessment of the platform was completed in July 2026. Findings were remediated, including infrastructure exposure hardening and origin-access restrictions; the exercise found no evidence of compromise. Security reports are welcome at [email protected] (see security.txt).
Every feature is free for every account — there are no paid tiers, and your data is not the product. Features with per-use costs (AI review) are gated to administrator accounts rather than monetized.
Questions your review still needs answered? Write to [email protected]. See also Privacy and Terms.