Data inventory
Identify personal, sensitive, regulated, confidential and prohibited data before production.
Bring Data to Compute · 来数加工
Atomic Cloud’s intended delivery model sends customer API requests into the Shantou data center for model inference and returns generated output through an encrypted API response path.
Reference architecture
Application prepares and sends the request.
Credentials, encrypted transit and routing controls.
Model inference under the agreed processing scope.
API response returns to the overseas application.
Encrypted transit
Client credentials
Contracted scope
Usage reconciliation
Compliance gates
“Bring Data to Compute” does not automatically exempt an international transfer. Production approval depends on the source country, data category, customer role, processing purpose and contract terms.
Identify personal, sensitive, regulated, confidential and prohibited data before production.
Confirm the lawful basis and cross-border transfer mechanism required in the customer’s source jurisdiction.
Define the permitted model, purpose, data fields, sub-processors and operating boundaries in writing.
Agree transport protection, credential handling, access boundaries and incident responsibilities.
Document whether payloads, metadata and outputs are retained, for how long and for which purpose.
Apply application-level review, content controls and human oversight appropriate to the use case.
Atomic Cloud may describe this route as designed to support compliant and secure processing. A guarantee that every transaction is legally compliant or completely secure should only be made after jurisdiction-specific legal review, technical verification and signed service terms.
Shared responsibility
The customer controls what it sends and why. Atomic Cloud controls the agreed delivery and processing service. Both sides must document their responsibilities before regulated data is used.