Backfrom Tencent’s own policies · verified 2026-09-02 · some facts not published
Tencent: data residency & retention
Headquarters
🇨🇳 China (China)
Where inference runs
Not disclosed
International LLM API (TokenHub) docs do not publish inference/data-center regions; OpenRouter's SG hint is unverified. Contracting entity varies by region (EEA/UK/CH controller is Tencent Cloud Europe B.V., Netherlands; elsewhere per Terms of Service, typically the Singapore intl entity). Privacy policy discloses that for some services personal-data servers are located in mainland China and lists Tencent Cloud Computing (Beijing) Co., Ltd. as a controller in some cases, with cross-border transfers under SCCs — so mainland-China transfer language exists, but the intl LLM API's actual serving region is not disclosed.
Region pinning
Not disclosed
No region-pinning controls documented for the intl LLM API; TokenHub terms defer all data handling to the general ToS/Privacy Policy/DPSA.
Prompt retention
Not disclosed
LLM-service privacy module: usage and configuration data 'generally retain[ed] for up to 30 days after your task request', possibly longer for billing; general policy retains log data 3 months. Whether prompt/response content itself is retained is not explicitly stated.
Trains on API data
Not disclosed
Neither the LLM privacy module nor the general privacy policy states whether customer/API data is used to train models; not disclosed.
Zero data retention
Not disclosed
No zero-data-retention option mentioned.
Compiled from Tencent’s published privacy policy, terms, and documentation on 2026-09-02. “Not disclosed” means Tencent publishes nothing on the point. Policies change without notice, so verify against the sources above before relying on this for compliance decisions.