Local math · share links · analytics

Privacy and Data Handling

The calculators are ordinary static pages: the arithmetic runs in your browser, and there is no account or database. The two places data can travel are share links and optional analytics, both described below.

Calculations are local

Address parsing, subnet math, VLSM planning, aggregation and IPv6 tools all run as JavaScript in your browser. What you type is not posted to the site: there is no API call and no form submission behind the results. The page files themselves are served by a static host, and the site keeps no copy of your input.

What a share link contains

When you use a share button, the current inputs are placed in the link's query string, for example /?q=192.168.1.0/26 or /vlsm/?p=10.0.0.0/24&r=Sales:120. That is what makes the link reproduce your result.

Because the values are in the URL, opening the link sends them to the host serving the page as part of the request, where they may appear in standard server or CDN logs. This is normal web behavior, not something the site reads or stores itself. Treat a share link like the input it carries: do not post links containing addresses, department names or plans you would not share with the recipient.

Analytics

Google Analytics 4 and Microsoft Clarity are optional. Their scripts are not loaded until you choose Allow analytics. Your choice is kept in this browser's localStorage; after you allow analytics, each provider also receives the consent signal its API requires. Use the Analytics settings button in the bottom-right corner to change your choice. If you withdraw permission after allowing analytics, the page reloads to stop scripts already running in that tab.

GA4 receives one manually sent page view and a small set of events: a calculation completed, a copy, a share, a download, and the type of an input error. The site sends only the path (without query or fragment), an input-free page title, and a referrer stripped of query and fragment. The Google tag's automatic page view is disabled, and Enhanced Measurement is off, so it adds no browser-history, scroll, link, search, form, video or file-download events. GA4 still sends standard session events such as first_visit, session_start and user_engagement, and can process browser/device details and approximate location. Event metadata is restricted to short fixed values such as the tool name, event kind, error code, format name or count. Addresses, MAC addresses, subnet names, host counts and full parameter URLs are not sent as event data. GA4's stream also has email and 15 URL query-parameter redaction keys enabled. See Google's data collection details.

Clarity is loaded only on the privacy page and the Learn index, and only when the current URL and referrer contain no query string or fragment and page links contain no query string. This matters because share links can carry calculator inputs, and Clarity's URL parameter masking does not cover referrer URLs or clicked URLs. Clarity records interactions on those eligible pages and may use IP-based geolocation. The project uses strict text masking and has its Cookie setting turned off, so recordings are not linked into multi-page sessions. See Clarity's masking FAQ.

After you allow analytics, GA4 may use first-party _ga cookies to distinguish users and sessions. Both providers process the events they receive under their own policies: Google privacy policy and Microsoft privacy statement. Consent details are in the Google consent-mode guide and Clarity Consent API v2 guide.

Local storage and hosting

The site stores your theme choice, any VLSM plans you explicitly save, and your analytics permission choice in this browser's localStorage. The stored choice remains in this browser; provider consent signals and analytics events are described above. Saved plans hold only the planner inputs (parent, subnet names and host counts, capacity rule and options), not addresses or results from other tools; delete a plan or clear site data to remove them.

Hosting is static, with no accounts, no cookies set by the site itself and no server-side database. The hosting provider processes standard request data (such as IP address, user agent and requested path) to serve and protect the site under its own terms.

Contact

Questions or corrections: open an issue at github.com/heymi/Subnetcalc/issues. The verification page explains how results are checked and how to report a wrong one.