Privacy notice

Version 1.0-beta · 29 September 2026

Information the service handles

Accounts contain a name, email address, password hash or Google sign-in identity, verification status and accepted terms version. Cloud features store your projects, versions, scenarios, jobs and results. Engineering files you open locally may remain in your browser; submitting a simulation sends the model to the server.

Why we use it

We use this information to authenticate you, provide the requested engineering service, enforce access and capacity limits, answer support requests and operate the service. Operational records include account/job identifiers, status, timing and resource counts. IP-derived identifiers are pseudonymous, not guaranteed anonymous. Authorised administrators can access account and operational information for support and service administration.

Service providers and external requests

Hosting infrastructure processes cloud data. Resend handles transactional and Contact email; the support mailbox receives Contact messages and your reply address. Google handles optional Google sign-in. Map providers receive map requests, and an explicit elevation lookup sends the selected geographic coordinates to the identified elevation provider. These services may process information outside Australia. Contact us for current hosting and provider-location details before uploading information with residency requirements.

Browser storage and security

The application uses browser storage for sign-in state, preferences and account-scoped engineering work. Signing out clears the active session but may retain local engineering data in that account's browser namespace. Use a trusted device. Access controls, transport encryption and backups reduce risk but do not guarantee security or availability.

Retention, export and deletion

Use the established model, project and result exports to keep your own copies. Stored versions and results remain subject to the service's retention settings. Deleting a project or result does not immediately erase copies in backups. An account deletion request disables login and sessions while the operator reviews removal and any required records. Backups are separate: the scheduled policy retains the latest 14 dumps, while release backups can remain longer pending review. Support messages remain in the support mailbox under operator management. No fixed legal deletion deadline is promised here.

Access, corrections and concerns

Use Contact with the Privacy topic to request access, correction, deletion or to raise a concern. We may need to verify your identity before acting. Do not send passwords, reset links or confidential engineering models through the form.