A cleaner product should also have a clearer privacy posture.
This page explains the product’s current privacy expectations, what stays local, and the limits of what the site should do with calculator-related data.
Last updated
14 March 2026
Core principles
Calculation inputs are intended to stay local in the browser for normal usage flows.
Preference data such as selected options may be stored locally on the device for convenience.
The product does not depend on account creation for basic calculator use.
Analytics, where used, should remain aggregate and non-sensitive rather than tied to personal financial entries.
What we keep minimal
The product is designed around quick calculator usage without forcing unnecessary identity capture. That means no account requirement for normal calculator flows and no need to store sensitive calculation inputs remotely just to deliver a result.
Preferences and local storage
Some user preferences, such as currency or tax mode selection, may be stored locally in the browser to make repeat usage easier. This is device-level convenience data, not the same as storing financial records in a backend system.
Third-party services
Hosting, analytics, and operational tooling may involve third-party infrastructure. These integrations should be limited to operational needs and should not require transmitting detailed calculator entries as user profiles.
Important boundary
For official filings, sensitive commercial workflows, or regulated reporting, users should still rely on professional advice and official channels where required. This site is a product tool, not a substitute for regulated tax advice.
Questions about privacy or data handling?
Use the contact page if you need clarification about data handling, preferences, or a specific product interaction.