Back to blog index
Privacy deep-dive

Japanese tax and social-insurance calculators: why browser-only processing matters most here

Salary figures, freelance gross income, household composition, property valuations, estate estimates — the inputs to Japanese tax and social-insurance calculators rank among the most sensitive numbers in a person's life. Here is why the gap between "free online tax calculator" and "browser-only calculator" is especially meaningful for this category of tools.

What goes into a tax or social-insurance calculation — and why it is sensitive

Japanese tax and social-insurance calculations require a dense cluster of personal data. The National Health Insurance simulator (kokuho-hoken-jp) takes the number and ages of household members, municipal rates across the medical / support / long-term-care / child-care categories, and then tests for the 7/5/2-tier household-income reductions. The Kyokai-kenpo simulator (kenpo-kyokai-jp) matches prefecture-specific rates against the 50-tier health-insurance and 32-tier welfare-pension standard-remuneration grade tables. The freelance tax estimator (freelance-tax-jp) combines annual gross sales, business expenses, blue-return deduction, family composition, and the sum of income deductions.

The loan repayment calculator (loan-calc) takes loan principal, interest rate, and term. The inheritance tax estimator (inheritance-tax-jp) takes the gross estate and heir composition. The property tax estimator (property-tax-jp) takes assessed values for land and building. Each of these data points is sensitive on its own; in combination — annual income x family structure x outstanding debt x assessed assets — they form a detailed financial profile. Even without a name or address, that combination is linkable. If it were to reach an advertising platform's data pipeline, the exposure would be qualitatively different from an ordinary file upload.

The structural risks of ad-supported online tax calculators

Most Japanese tax calculator sites that rank on the first page of search results load third-party advertising SDKs or analytics scripts. When a page is instrumented with those scripts, the operator's JavaScript can observe user interactions — including values typed into form fields — before the user presses "calculate". Whether those values are transmitted to third parties depends entirely on implementation choices the user cannot inspect. This is not a hypothetical; ad network SDKs are designed to collect behavioral signals precisely because those signals improve targeting.

Services that require registration go one step further: they store the submitted income, assets, and household data server-side, often under terms that allow "statistical" or "quality improvement" use. The gap between what a user believes they are agreeing to and what the terms permit for data reuse is difficult to close from the user's side. For tax data specifically, where the numbers directly reflect wealth and income, that gap matters.

There is also a correctness risk. Japan revises tax rates and social-insurance premiums every fiscal year. Consumption tax already runs at two rates (10% standard / 8% reduced). Employment insurance (koyo-hoken-jp) rates were updated for FY2026. The new-build property-tax reduction was extended to March 2031 by the FY2026 tax reform. Sites that do not actively maintain their calculation logic may be running on stale rate tables without prominently disclosing it. Choosing a calculator means choosing a question of freshness too.

How each tool achieves in-browser processing — and the regulatory anchors

All of the tax and social-insurance tools on NoSend Tools evaluate every formula inside the browser. There is no server-side calculation endpoint. The grade tables, reduction thresholds, quick-deduction amounts, and payment schedules are embedded as constants in the page's JavaScript bundle and evaluated against user input in local memory. Opening DevTools, switching to the Network tab, and running a calculation produces zero outgoing requests to any external domain.

Each tool's constants are anchored to specific official sources and fiscal years. kenpo-kyokai-jp uses the Kyokai-kenpo prefecture-by-prefecture rate tables (applicable from April 2026). koyo-hoken-jp uses the FY2026 employment-insurance rates published by the Ministry of Health, Labour and Welfare (general industry: 13.5 per 1,000). rosai-hoken-jp embeds the FY2024 workers' compensation rate table for 54 industry categories. kaigo-hoken-jp uses the MHLW 9-tier standard and the FY2026 national average base amount of JPY 6,225 per month. pension-calc-jp uses the FY2026 full basic-pension figure of JPY 847,300 per year and the 5.481/1000 earnings-related multiplier. inheritance-tax-jp implements the NTA quick-deduction table across 8 brackets (top rate 55%) and the JPY 30M + JPY 6M x heirs basic deduction. These citations are present as source-code comments, auditable on GitHub.

freelance-tax-calendar-jp lays out an annual cashflow calendar for sole proprietors that integrates all the deadlines that normally require consulting multiple ministries and municipal governments: the two income-tax prepayment dates, four resident-tax installments, eight NHI installments, business tax, and the mid-year consumption-tax payment. furusato-calc-freelance-jp estimates the hometown-tax (furusato-nozei) donation cap for sole proprietors, accounting for the blue-return deduction and self-employment income — a calculation that many salaried-worker-oriented tools get wrong. Both run entirely in the browser.

Calculation without exposure — and what that means in practice

Tax and social-insurance calculation is arithmetically straightforward: substitute parameters into formulas and return results. There is no technical reason it needs to cross a network. The decision to run calculations server-side has historically been a tooling constraint (before WebAssembly) or a business-model choice (server-side logging provides engagement data). With modern browsers, the constraint is gone. The business-model incentive is the remaining difference.

For a user estimating their NHI premium after going freelance, their kenpo-kyokai premium for a new employer, their inheritance exposure on a parent's estate, or their cash position month by month across a tax year, the numbers entered are not abstract. They reflect real financial decisions. Browser-only processing means that the calculation runs on the user's machine, the inputs do not pass through any third-party infrastructure, and the result is available immediately without a network round-trip. For estimates that inform significant life decisions — leaving corporate employment, taking on a mortgage, planning an estate — that combination of privacy, correctness, and verifiability is the actual product.