What stays on your device, what is sent to the server, and how to control locally stored data.
Tool calculations run in your browser. Text, files, measurements, and generated results are not uploaded by the tool pages. Static pages and tool-status metadata are fetched from this site, but tool inputs are not included in those requests.
Virtual Tools does not use advertising trackers or analytics. Favorites, recent tools, usage counts, view preferences, and theme choice are browser-local and are not sent to the server.
Each public tool shows its review status, method, sources, and recorded test count. When extra care is warranted, the page gives concise guidance about what to verify before acting.
The application may use the following localStorage keys. Storage is scoped to this site and remains in this browser profile:
vt-themevt-viewvt-favoritesvt-recent-toolsvt-tool-usagevt.feedback.ids.v1Active search text can also be kept temporarily in sessionStorage so Back navigation restores the catalog. It normally disappears when the tab session ends.
Submitting the feedback form sends the selected kind, optional tool slug, and message to the feedback service. Do not include passwords, medical records, financial account data, or other secrets. A random UUID is returned as the bearer-style key for checking the response.
Feedback becomes eligible for automatic deletion after 365 days by default; the operator can configure a different period. Cleanup is periodic and bounded, so removal can occur later under a large backlog. The service keeps no name or email field. Privacy-preserving rate limiting stores a keyed client token instead of the raw network address; expired one-hour-window counters are purged by later rate-limited activity.
Normal infrastructure may record operational events needed to run and secure the service. Feedback API access logging is disabled so UUID lookup paths and raw client addresses are not retained in application access logs.
The optional service worker pre-caches only the shared application shell. It can keep a bounded set of static assets and tool pages you visit. It never caches API responses, feedback routes, tool trust/status records, the canonical catalog, or URLs containing query parameters. Tool HTML is checked against the network first so releases do not remain stale.
Checking offline storage…
“Reviewed” describes the recorded project review state, not professional certification. When a result could affect an important decision, follow the tool’s verification guidance and consult authoritative sources or qualified advice as appropriate. Use the issue link on any tool page to report incorrect formulas, inaccessible controls, unsafe behavior, or unclear assumptions.