What the core calculators process
A calculator processes the values you enter to produce a planning estimate, formula trace, sensitivity table, warnings, and next-step suggestions. Those calculations run locally in the browser. A local business profile and saved scenarios remain on that device and in that browser unless you deliberately export a file.
| Data | Where it is handled | User control |
|---|---|---|
| Unsaved calculator inputs | Current browser session | Reset the tool or close the session |
| Business profile | Versioned browser storage | Export, import, reset, delete, or clear all local data |
| Saved scenarios | Versioned browser storage, only after an explicit save | Duplicate, export, delete, or clear all local data |
| CSV or JSON export | A file you intentionally create on your device | You choose where to store, share, or delete it |
| Product analytics event | Event name and safe page/tool context only | Never includes raw financial inputs or export contents |
What analytics must not receive
Analytics and error reporting must not receive raw dollar values, wages, revenue, user-entered margins, employee names, business names, quote descriptions, local profile contents, saved scenario contents, or exported file contents. Product events can record actions such as starting or completing a tool, opening a formula trace, printing, or exporting—without attaching the financial values involved.
Standard web infrastructure may process routine request information needed to serve a page, such as an IP address, browser user agent, requested route, and time. Calculator form fields are not added to URLs, access logs, analytics payloads, or error reports.
Local storage is convenient, not encrypted
Browser storage is not an encrypted vault. Anyone with access to the same browser profile or device may be able to inspect it. Do not save customer names or sensitive descriptions. Use the profile controls to delete an individual profile or scenario, or use Clear all local data to remove TradeQuote Lab's versioned local keys from that browser.
Clearing browser data, private-browsing expiration, device policies, or browser changes can erase local scenarios. Create a JSON backup if you need a portable copy.
Exports and print views
Copy, CSV, JSON, and print actions are initiated by the user. JSON imports are validated and previewed before replacing a local profile. CSV cells are escaped to reduce spreadsheet formula injection risk. Print views omit navigation and partner cards and must not reveal details the user chose to hide.
No account or automatic sync
Core tools do not create a cloud account, synchronize saved calculations, or require contact details. Future optional email or survey features, if introduced, will have their own explicit consent and data minimization controls; they will not receive calculator inputs or saved scenarios.
Questions or privacy corrections
If the product behaves differently from this description, do not include private inputs in your report. Use the correction page to identify the route and behavior. The terms explain the limits of planning estimates.