What happens when you type your salary into a form
Most calculators on the web work the same way underneath: you fill in a form, click submit, and your browser sends that data to a server somewhere, which does the math and sends back a result. That’s true of most login forms, checkout pages, and yes, most paycheck calculators too.
There’s nothing inherently malicious about that pattern — it’s just how most of the web works. But it does mean your salary, filing status, and state briefly become a piece of data sitting on someone else’s server, subject to whatever that site’s privacy policy, retention practices, and business model actually are. Some financial tools are funded by matching users with paid advisors or affiliate financial products, which means the form data serves double duty: giving you a number, and generating a lead.
What “client-side” means, concretely
This calculator works differently: every number you enter — salary, filing status, state, pay frequency — is computed entirely inside your own browser, in JavaScript, using the same tax-bracket logic published in this site’s own open calculation code. Nothing is transmitted anywhere. There’s no form submission, no server round-trip, no account, no database row with your salary in it.
You don’t have to take that on faith. Here’s how to check it yourself:
- Open your browser’s developer tools (F12 or right-click → Inspect).
- Go to the Network tab.
- Enter a salary into the calculator and watch what happens.
You’ll see the page’s own assets load once. You won’t see a new network request fire off every time you change an input — because nothing needs to be sent anywhere for the result to update. It’s the same reason the numbers themselves can be checked independently too — see Is This Paycheck Calculator Actually Accurate? for how to verify the math against the primary IRS sources.
Why this is the harder thing to build, not the easier one
Server-side calculation is, if anything, simpler to build: send data, run a function, return a number. Doing everything client-side means the entire tax-bracket engine has to ship to the browser and run correctly on every device, with no server to fall back on if something’s wrong. It’s a deliberate choice, not a shortcut.
What this doesn’t mean
This isn’t a claim that this site collects zero information about visits — see the Privacy Policy for what Google Analytics and, eventually, Google AdSense actually do collect (aggregate traffic patterns and ad-serving cookies, respectively — neither ever sees what you type into the calculator itself). The distinction that matters here is specific: the salary and filing details you enter into the calculator never leave your browser, full stop.