DATA HANDLING & RESPONSIBILITIES

Your data deserves
a clear explanation.

Understand what SinoRouter processes, what operational records remain, and where upstream model policies apply.

What happens to an API request

  1. 01 / YOUR APPLICATIONYou send a request

    The model ID and content needed for the task are sent to the gateway.

  2. 02 / SINOROUTERWe forward the request

    The gateway handles access, forwarding, usage accounting, and the return path.

  3. 03 / UPSTREAM SERVICEThe model generates a result

    The upstream service processes the content under its applicable policies.

The result returns through the gateway to your application. Gateway hosting does not determine where an upstream model processes data.

CUSTOMER CONTENT

No training by SinoRouter.

SinoRouter does not use customer API prompts, uploaded content, or generated outputs to train models. We process request content to deliver the requested service, rather than maintain a content archive.

This commitment covers SinoRouter's own handling. It does not replace the policies of the upstream services involved in your request.

OPERATIONAL RECORDS

Usage records are different.

Usage and billing records are retained for account visibility, accounting, troubleshooting, and incident response. These records can include model/version, request time, usage quantities, charges, and request status.

Retaining operational records is different from retaining a library of your prompts and outputs. Support attachments you choose to send are handled separately.

HOSTING & ACCESS

Know the processing boundaries.

SinoRouter's operational records are hosted on servers in Singapore. Administrative access is restricted to the super-administrator role. Customers can view the usage information exposed in their own console.

This is not a promise that every upstream processes or stores content in Singapore. Confirm the applicable upstream service and region before sending regulated or location-sensitive data.

RETENTION & DELETION

Ask about your specific records.

You can request deletion of eligible account and service records. We review the request and explain any records that must remain for billing, legal obligations, security, or dispute handling.

No universal retention period or upstream deletion deadline is promised here. If your organisation requires a fixed period, confirm it in writing before production use.

UPSTREAM SERVICES

Check the policy for the route you use.

A model name alone does not identify the service operator, region, or contract used to deliver it. Ask us which upstream terms apply to your intended workload, including content retention, training use, and geographic restrictions.

Before sending sensitive data

  • Remove unnecessary personal or confidential information.
  • Confirm the upstream service and processing locations.
  • Request the applicable terms and any required data-processing agreement.
  • Agree on retention and deletion requirements in advance.
Request the applicable upstream policies →