Last updated: October 2026.

Here is what happens to your information, in the order it happens — which turns out to be a short story, because almost everything stays on your side of the screen.

When you open a page

Your browser requests the page and its assets from Cloudflare’s edge network. Like every web host, Cloudflare necessarily sees the connection metadata needed to answer: your IP address, the URL, a timestamp, your user-agent string. Those serve the response and filter abuse. On our side there is no account system, no user record, no database — nothing for that metadata to attach to.

When you use the estimator

You type quantities, hours and a rate into a form. That form has no submit button pointed at a server — the script on the page reads your inputs, does the multiplication and repaints the result locally. There is no fetch, beacon, websocket or analytics callback carrying your appliance list anywhere. You can open dev tools and watch: the page fetches its own files and goes quiet. Or disconnect the network after it loads; every row still computes.

When ads are shown

If an ad slot is filled, a third-party network such as Google AdSense may set its own cookies or identifiers to count impressions and, where permitted, tailor what appears. That happens between your browser and the ad network — the numbers you typed are never in those requests because they were never on the wire. Opting out is yours to choose: Google’s ad settings, a content blocker, or a private-browsing session all work, and the estimator is unaffected either way.

What never happens

• No first-party cookies — the site sets none.
• Nothing in localStorage, sessionStorage or IndexedDB — close the tab and nothing of the session persists.
• No sign-in, email capture, or “create an account to see results.”
• No sale or sharing of usage data — there is no usage data on our side to sell.

Changes

If this policy changes, the revision appears on this page under a new date. Questions: hello@nxtolerance.com.