Data & access

Agree the data boundaries
before sharing the work.

Tianshu Standard communication, optional remote assistance and a workflow pilot are distinct activities. Each needs a clear purpose and an appropriate data and access arrangement.

Verified current architectureTianshu Standard sends consultation messages and device status over HTTPS to a central service in China. This is not an all-data-local product. The initial workflow discussion does not require installation or remote access.
Standard preview

Communication and device reporting

Standard provides consultation messages and device reporting through the central HTTPS service. It does not bundle the remote-access components.

Messages are sent to the central service. Do not put confidential work into a consultation until the handling arrangements have been agreed.

Separate approval required

Optional remote assistance

Remote assistance requires a separate application, an agreed scope and approval. Installing Standard does not itself establish a remote-access session.

The optional remote plugin is not ready for production use. Discuss the available delivery approach with us first.

Before a pilot receives real samples

DecisionWhat to confirm
Approved dataWhich files and fields may be shared, whether samples can be anonymized, and what must be excluded.
Processing locationWhere the selected workflow and central services process information, including any model-provider processing.
Model processorsWhich providers and models are involved, what they receive and the relevant handling terms.
AccessWho can access the samples, messages, systems and outputs; the purpose and scope of each permission.
Retention & deletionHow long each class of pilot data is retained and how deletion requests are handled. Do not assume website log retention applies to client messages.
Review & releaseWho checks the outputs, resolves uncertain specifications and approves every customer-facing quote.

Start with the smallest useful sample.

A synthetic example can establish the workflow and review rules without revealing customer drawings. An anonymized sample may be useful after its sharing has been approved.

Client message retention is not specified here.This page does not promise a retention period, automatic deletion or a particular model provider for consultation messages. Confirm the applicable handling terms before sending sensitive information.

Website visits are a separate data flow.

The website uses first-party access and event statistics. The website privacy notice covers those logs; it does not establish data-processing terms for a pilot or Tianshu client messages.

Read the website privacy notice

Start with a conversation

Let’s look at your
RFQ workflow.

Tell us what arrives, what your team checks, and where preparation slows down. An initial discussion needs no software installation or confidential drawings.

Contact the SJAITECH team

[email protected]

Use this address in your preferred email app.

Delivery hours, time zone and pilot scope are agreed together.