TRUST & GOVERNANCE · HONG KONG ENTITY

Compliance Standards and Service Governance

Executing bilateral commercial agreements through a Hong Kong incorporated entity, delineating shared responsibility, data governance perimeters, and compliance support across Paso Fusion, upstream cloud providers, and enterprise clients.

Four Core Governance Principles

Procuring cross-border compute and commercial model services requires mapping security and compliance obligations to specific corporate entities, resource origins, and technical boundaries.

Contracting Entity & Legal Liability

Paso Fusion Hong Kong Limited serves as the commercial contracting entity, assuming contractual liability for architectural design, resource coordination, billing reconciliation, and agreed engineering support.

Upstream Resources & Service Boundaries

Underlying GPU compute capacity, datacenter facilities, and commercial model inference are all provided by major global cloud platforms and third-party upstream providers across Southeast Asia and Australia, with both contracts and architectural documentation clearly distinguishing upstream infrastructure responsibilities from Paso Fusion service responsibilities.

Data Governance & Confidentiality

Client prompts and outputs are protected as confidential information; Paso Fusion does not use them for training and only selects upstream providers whose terms commit to not training on them, with specific data regions, logging, and retention periods agreed upon in the service agreement.

Control Mapping & Compliance Evidence

Assisting clients in organizing publicly released or provided with authorization upstream security and compliance documentation, comparing item by item against enterprise internal control requirements, and clarifying technical measures, providers, and matters pending confirmation.

Governance in practice

Contracting Entity and Commercial Liability Structure

All GPU resource leasing, engineering consulting, and enterprise model API services are governed by formal commercial contracts that clearly specify service scope, delivery standards, support response, reconciliation and invoicing arrangements, and issue escalation paths, with governing law and dispute resolution mechanisms confirmed by both parties in specific project contracts.

Upstream Resource Sourcing and Operational Boundaries

Paso Fusion does not build physical datacenters; underlying hardware is delivered by upstream partners. Upstream providers maintain physical facilities, host hardware, and underlying networks according to their service terms, while Paso Fusion delivers cross-cloud evaluation, validation, procurement, and contractually specified engineering support.

Data Governance, Confidentiality, and Training Restrictions

Paso Fusion strictly fulfills confidentiality obligations regarding business consulting information as well as prompts and outputs during model invocation, never using client data to train internal or third-party models, and verifying commercial term commitments of not using data for training during upstream onboarding. Because hardware execution and model inference occur in upstream environments, geographic processing locations, logging scopes, retention windows, and deletion routines are determined by upstream service documents and project contracts. Paso Fusion provides technical coordination but does not unilaterally warrant the independent operational actions of third-party cloud providers.

Control Mapping and Audit Review Support

When facing enterprise internal security, risk control, or external compliance reviews, the engineering team assists in sorting out data flows, network access boundaries, and privilege divisions, mapping technical control measures of candidate upstream providers against client review checklists item by item; this work aims to provide accurate technical and responsibility explanations, does not replace the client's own legal compliance determinations, and does not promise direct approval from specific regulatory authorities.

Compare customer, Paso and upstream responsibilities

Scope, evidence and responsibilities are confirmed for each project.

Compare customer, Paso and upstream responsibilities
AreaCustomerPaso FusionUpstream
ContractConfirm requirements and acceptance criteriaAgree and fulfil contracted service dutiesConfirm applicable resource or interface terms
Business dataDefine data classification and allowed processingCoordinate confidentiality and contractual processing boundariesProvide agreed processing and retention conditions
Resource deliveryPrepare project inputs and validate application fitCoordinate selection, validation and handoverSupply infrastructure or model service in the agreed scope
Support and escalationReport impact and provide relevant business observationsCoordinate incident communications and contracted engineering supportHandle incidents within the upstream service boundary

Request security architecture briefs, control mappings and governance packs.