List of Subprocessors
Version v1.0 · Effective date: 2026-10-16 · This page is a component of Section 5 of the Privacy Policy
| Processor | Activity (what it does for us) | Hosting region | HQ or registered location | Data types involved | Basis of verification |
|---|---|---|---|---|---|
| This site’s server (图译工坊’s own service) | Account and sessions, quoting and binding, task dispatch, settlement and billing, receiving troubleshooting information | Singapore · Tencent Cloud CVM (ap-singapore availability zone ap-singapore-4) | The operating entity of this Service; entity information is not publicly disclosed on this page — for compliance inquiries contact the email at the end of this page | Email address, IP hash, anonymous device identifier, login-failure counter; layer source and translated text in tables; local path strings of design and output directories; troubleshooting snapshots and content packages you opt to upload | Cloud-provider identifier: `dmidecode -s system-manufacturer` = Tencent Cloud; region: Tencent Cloud instance metadata placement/region = ap-singapore, placement/zone = ap-singapore-4 |
| DeepSeek text-generation service (API) | Bilingual-alignment review of layer source and current translation, producing smart-detection hints | Public internet API endpoint (api.deepseek.com); actual storage location is per its published policy | DeepSeek | Layer source, current translation, line identifiers, detection hints | Production deployment keys DEEPSEEK_BASE_URL = https://api.deepseek.com/v1, DEEPSEEK_MODEL = deepseek-chat verified in practice (not merely code defaults) |
| Tencent Cloud SES email-sending service (International) | Sending email-verification and password-reset emails | Singapore (ap-singapore) | Tencent Cloud International | Recipient email address, one-time verification and reset token content | Production deployment keys TENCENT_SES_REGION = ap-singapore, TENCENT_SES_HOST = ses.intl.tencentcloudapi.com verified in practice; domain resolution falls under AS132203 Tencent Cloud |
| Network-acceleration (CDN) and security-protection service (Cloudflare) | Transmission acceleration and temporary caching, request-side protection and rate limiting | Global edge nodes (scheduled by nearest access); this observation landed on the Los Angeles (LAX) node | Cloudflare, Inc. (United States) | Request metadata (IP, browser type), page content | Site response headers Server: cloudflare / cf-cache-status / CF-RAY; `/cdn-cgi/trace` returns Cloudflare’s proprietary format; production deployment key CF_ACCESS_TEAM_DOMAIN points to cloudflareaccess.com |
| PaddleOCR image text-recognition service (API) | Extracting text from images (interface-level capability; not yet wired into the product flow) | Public internet API endpoint (paddleocr.aistudio-app.com); actual storage location is per its published policy | Baidu AI Studio (PaddleOCR is provided by Baidu) | Image files fed into the recognition flow | Production deployment keys PADDLEOCR_JOB_URL = https://paddleocr.aistudio-app.com/api/v2/ocr/jobs, PADDLEOCR_MODEL = PaddleOCR-VL-1.6 verified in practice; domain resolution falls under AS38365 (Beijing Baidu Netcom) |
This table itemizes, row by row, the verification method on which each row’s conclusion rests. For the retention periods and registered entities of third-party processors, their published policies and contracts govern, and this Service does not commit on their behalf; the retention periods this Service itself commits to are in Section 6 of the Privacy Policy.
Per-channel disclosure detail
The table in Section 5 of the Privacy Policy aggregates by content type; here is its per-channel expansion (excluding internal limit parameters).
Expand to view 11 channels
| Channel | Uploaded content type | Leaves your machine? | Processor category | Purpose | Retention |
|---|---|---|---|---|---|
| Design-file bodies (.psd/.psb bytes) | File body | No — only digest computed locally | Your local assistant and Photoshop on your machine | Drive replacement and read-back verification locally | Not uploaded; no server copy |
| Exported images and deliverables after replacement | Rendered / exported files | No — the execution chain only hashes | Your local machine | Delivery and settlement verification | Not uploaded; no server copy |
| Layer source and translations in your tables | Text-layer content | Yes | This Service (this site’s server) | Quoting, match binding, dispatch execution, settlement | Review snapshots at most 7 days |
| Layer source and current translation (smart-detection review) | Text-layer content | Yes | Third-party AI model service (see above table) | Bilingual alignment and issue hints | Review snapshots at most 7 days; that provider’s retention per its published policy |
| Local path strings of design and output directories | Path-type information | Yes | This Service (this site’s server) | Let the local assistant locate files to process and output | No separate retention period: batch and billing records store only irreversible fingerprints; failure-diagnostic directory strings are de-identified before recording |
| Troubleshooting snapshot (auto-uploaded on failure) | Digest and counts: error code, stage, build identity, de-identified diagnostics | Yes | This Service (this site’s server) | Locate failure cause | At most 7 days |
| Troubleshooting content package (uploaded after you separately opt in at the failure site) | Text-layer content: source and translation snippets within your chosen scope | Yes | This Service (this site’s server) | Deep diagnosis of this failure | At most 7 days |
| Image text-recognition interface | Images fed into the recognition flow | Leaves when the interface is used; no caller in the product flow at the time of this List’s verification | Third-party OCR service (see above table) | Extract text from images | Not triggered currently; when connected, handled per this section and the Privacy Policy |
| Account and device information | Identifiers and counts: email, IP hash, anonymous device identifier, login-failure counter | Yes | This Service (this site’s server) | Registration, login, rate limiting, abuse prevention | Account information retained during service; failure and rate-limit records at most 90 days |
| Verification and reset emails | Identifiers: email address, one-time token | Yes | Third-party email-sending service (see above table) | Email verification, password reset | Token void after expiry; event records no more than 7 days |
| Settlement receipts and execution counts | Digest and counts | Yes | This Service (this site’s server) | Billing, settlement, and reconciliation | Credit and billing flows retained per financial and tax compliance |
Change notice
- When a processor is added or replaced, we announce it on this page at least 30 days in advance; the announcement includes the processor name, activity, hosting region, headquarters or registered location, data types involved, and effective date.
- If the storage location or jurisdiction changes, we simultaneously notify you per the notice method of Section 10 of the Privacy Policy; where providing personal information outside the territory of the PRC is involved, we separately obtain your separate consent.
- Removing a processor is not a matter that increases your obligations and takes effect immediately upon update on this page.
- There are currently no announced changes.