Privacy & data flow

Keep engineering data where your team can see it.

This notice describes the current public-site posture and the intended product boundary. Managed-AI processing is not enabled until the dedicated provider, region, retention, deletion, training, and entitlement checkpoints pass.

Current public-site data

The static site currently has no account, checkout, analytics, marketing pixel, or contact mailbox. Checkout remains held pending dedicated Workcell Stripe and tax/provider proof. A normal request can be logged by the hosting and reverse-proxy layers for security and operations. Do not submit project files, credentials, personal data, or confidential engineering material through a public URL.

Support is routed through repository issue and private vulnerability-reporting tools when enabled. Those services have their own terms and privacy practices. Remove sensitive details before submitting a public issue.

Intended product data flow

  1. Customer workspace: native simulation projects, evidence, and local exports remain in customer-selected storage by default.
  2. Bounded proposal: a user chooses whether to request a model-assisted plan. The application should show the material and destination before submission.
  3. Managed service: if the Workcell-managed AI service is enabled for a verified paid release, only the bounded request needed for that plan should leave the device. Provider, region, retention, deletion, training, and entitlement behavior must be published before public cutover.
  4. Evidence: accepted patches, validator output, tool versions, and hashes remain inspectable by the team. A model response is not an authoritative project artifact.

What is not supported

Seller and requests

The seller/publisher is Denis Miclea, an individual developer in Quebec, Canada. This notice intentionally does not publish a residential address or invent a company or tax identity. For a privacy or data request, use the verified support/security route published by the project; do not send personal data to an unverified address.

Changes

This notice must be updated before any material change to hosting, telemetry, managed-AI processing, billing, or support routing. Check the release and site repository history for the exact revision.