Trust

Data handling

Draft for owner review. This page describes intended practice. It has not been approved for publication and is not yet a binding statement. Items marked “to be confirmed” need a decision before launch.

Principles

  • Customer GDS files, simulation inputs, results and voice data are private by default.
  • Every read, download and change is checked against project ownership on the server.
  • Proprietary inputs, credentials and personal data are kept out of logs and analytics.
  • Prompts, uploads and generated output are treated as untrusted input at the job boundary.

Where work runs

The public site, account services and each design application are separate origins. Solver workers are isolated from the public web tier and from other customers, with limits on compute, time, concurrency and storage.

Design files and results

Stored against your account and project. Download links are short-lived where the application supports them. Retention and deletion periods (to be confirmed).

Prompts and conversations

Sent to the language-model provider that powers the designer in order to produce a response. Provider list and their data-use terms (to be confirmed).

Voice data

Audio from voice conversations is processed by speech providers (to be confirmed). Whether audio is stored, and for how long, will be stated here before any voice feature is enabled.

What we can and cannot claim today

The controls above are the design target, measured against OWASP ASVS Level 2. This page will only state a control as in place once the deployed system demonstrates it.