Privacy

Short version: all calculations run locally inside your browser. No survey points, CSV files, velocity measurements or location datasets are transmitted to our server, stored on our side, or seen by anyone but you. There is no account, no login and no database in this workbench — by design, not by policy setting.

What happens to your data

• Computation. Every conversion, classification, validation and report is computed in JavaScript on your device, after the page has loaded. The server delivers static files and plays no part in any calculation.
• Storage. Your imported points, results and generated reports exist only in the browser tab's memory and are destroyed when you close or refresh the tab. Nothing is written to localStorage, sessionStorage or cookies by the analysis tools; survey data is never persisted.
• Uploads. There is no upload endpoint in the code. The tools work offline once loaded, and the demo datasets are fetched from the same static host as the pages themselves.

What is stored locally

Only your interface preferences and, where you choose to save them, custom screening thresholds — never points, coordinates or measurement values. Clearing your browser's site data removes these preferences completely.

Third parties

This workbench embeds no third-party analytics, trackers or advertising cookies in its tools. (Should advertising be introduced in the future, this statement will be updated first and the change announced on this page.) The static hosting provider sees ordinary, anonymous access logs — the same records any web server keeps — with no association to your analysis data, because none is ever sent.

Professional confidentiality

Survey coordinates and deformation rates are frequently commercially or contractually sensitive. The local-computation design exists precisely so that you can use the workbench on client data without creating data-processing obligations, cross-border transfer questions or retention liabilities. You stay in control of every copy; exports happen only when you click an export button, to your own device.

Principles of this privacy statement

This statement is organised around four principles that the design of the workbench follows as engineering rules, not as aspirational policy. Local computation: every conversion, classification, validation and report is computed in JavaScript on your device after the page has loaded; the server delivers static files and plays no part in any calculation. No upload: there is no upload endpoint in the code, so no survey point, CSV file, velocity measurement or location dataset can leave your device even by mistake. No account: the workbench has no account, no login and no server-side database, which removes the main categories of privacy risk (credential compromise, unauthorised access, retention of processed data). Minimal persistence: only interface preferences and, where you choose to save them, custom screening thresholds are stored locally — never points, coordinates or measurement values.

Data categories and how each is handled

• Computation. All calculations run locally in the browser tab after the page loads. The imported points, intermediate results and generated reports exist only in the tab's memory and are destroyed when you close or refresh the tab.
• Persistence. The analysis tools do not write to localStorage, sessionStorage or cookies. Survey data is never persisted anywhere on the device, by design; the only local writes on the site are preference keys for the interface, which contain no measurement content.
• Uploads. There is no upload endpoint in the codebase. The tools work offline once loaded, and the demo datasets are fetched from the same static host as the pages themselves.
• Server access logs. The static hosting provider sees ordinary, anonymous access logs — the same records any web server keeps (requested URL, response status, timestamp, IP address in the provider's normal retention window). These logs contain no association with your analysis data, because no analysis data is ever transmitted.

Cookies and tracking

The workbench embeds no third-party analytics, trackers, fingerprinting scripts or advertising cookies in its tools, and no first-party cookies are set by the analysis pages. If advertising is introduced in the future, this statement will be updated and the change announced on this page before it takes effect; until then, the "no advertising" statement is the current and accurate position. If you disable cookies entirely in your browser, the workbench continues to work, because its tools do not depend on cookies for any function.

Professional confidentiality and contractual sensitivity

Survey coordinates and deformation rates are frequently commercially or contractually sensitive — sometimes even subject to export or disclosure restrictions in infrastructure projects. The local-computation design exists precisely so that you can use the workbench on client data without creating data-processing obligations, cross-border transfer questions or retention liabilities under the applicable data protection law of your jurisdiction. You stay in control of every copy: exports happen only when you click an export button, and they are written to your own device. Nothing in this statement is intended to replace your own obligations to your clients — the workbench is a tool, and professional responsibility for how the outputs are used and shared remains with the engineer.

Children's data

The workbench is a professional engineering tool intended for use by qualified engineers and surveyors. It is not directed at children, and it does not knowingly collect, process or store any personal data of children. Because the tools operate entirely in the browser with no account system and no data collection, there is no mechanism by which a child's data could be collected, and no additional age-gating is required for the tool's operation.

Your rights and this policy's governance

Because the workbench stores no personal data about you in any server-side system, there is nothing to access, correct, delete or export on request: the only data associated with your visit is the anonymous access log retained by the hosting provider under its standard policy. If you use a local browser profile that stores interface preferences from this site, you can remove them at any time by clearing your browser's site data for this domain. This policy is reviewed whenever the site changes behaviour that could affect privacy — new third-party resources, new storage mechanisms, or new communication features — and the version date at the top of the page is updated on every review. If you believe any tool communicates with a server, or stores data it should not, that would be a bug against our own iron rule — please report it through the contact channel on the main site, and we will treat the report with priority.

Contact

Questions about this statement or the workbench's behaviour: use the contact channel on the main site. If you believe any tool communicates with a server, we want to hear about it — that would be a bug against our own iron rule. The statement above is the complete current version; no separate annexes apply to the workbench's tools, and the version date on this page is updated on every review. For compliance workflows, the short version at the top of this page is intended to be quotable directly in engineering service agreements and internal data-handling policies.