Recipients, Retention and Security Schedule
Document version: 2026-10-17-v2. English translation. This accompanies orders/DPAs and distinguishes verified facts from limitations; it is not supplier-compliance certification.
1. Recipients and locations
| Party | Purpose and information | Status and conditions |
|---|---|---|
| DigitalOcean | Production hosting and hosted content | Read-only metadata returned sgp1 on 17 October 2026; backup regions/rotation were not verified |
| Authorised enterprise administrators/staff | Permission-scoped conversations, QA and statistics | Same-tenant/workspace and feature permissions; shared accounts do not prove authorship |
| Technical support | Necessary fault, billing and privacy assistance | Necessity, authorisation, confidentiality and traceability; no promise of technically impossible content access |
| Telegram | Original platform and approved connection | Actual activity/platform terms determine roles; not automatically our subprocessor |
| Billplz/banks | Necessary payments, reconciliation and refunds | FPX only when available and selected; no banking password/OTP; operator confirmed the transfer account |
| Resend/official support Gmail | Necessary website inquiry contact details, business requirements and correspondence | Read-only checks confirmed Resend configured and inquiry records present; no entire customer conversation database |
| Google Translate/WhatsApp links | Actual translation or user-opened contact service | Respective third-party rules apply; not represented as Singapore-only processing |
| Google Drive | Selected report uploads and necessary OAuth | Customer-selected storage/access; actual international-transfer and retention conditions, not Singapore-only Google data |
| Approved local model/device | Relevant conversations and outputs | Downloaded and processed on customer devices; results return to server; protect local logs/temporary data |
| Optional OpenAI API | Conversation/rule input and output after activation | Reviewed code uses api.openai.com/v1/responses; no API call was made. Account terms, exact model, locations and retention settings were not verified; disclosure/authority required before use |
Other proposed payment, analytics or marketing suppliers are not assumed enabled. This register is also not a claim, without inventory, that no other recipient exists.
2. Retention and deletion
| Category | Stated scope | Verification limits |
|---|---|---|
| Image previews | Code: 128KB each, 512MB company content, thirty days from message time | Not every image guaranteed; no production-deletion exercise |
| Deleted-chat text evidence | Existing notice states one year for this category | Complete purge schedule and final backup removal not verified |
| Ordinary conversations/QA/operations | Purposes, category arrangements, lawful instructions and exceptions; requests available | Neither scoring scan nor evidence period is general retention |
| Accounts/devices/security | Necessary authorisation, security, audit and limited disputes | No invented universal term or immediate deletion of every log on departure |
| Billing/tax/disputes | Applicable statutory periods and particular disputes, limited in scope | No unsupported single tax-retention period or assumed tax status |
| Termination exports | All modes: request retained authorised data within thirty days; internal delay cannot expire timely requests | No restoration guarantee or automatic read-only account |
| Backups | Recovery/necessary retention; reapply deletions after restoration | Region, frequency, longest retention and deletion mechanism not verified; no absolute sixty-day clearance promise |
3. Security and review scope
Reviewed code includes protected receipt/image storage and account/tenant access checks. This does not prove encryption of all fields, backups, local logs or exports. A production-region check is not penetration testing, certification, supplier-contract review or a transfer-adequacy assessment.
Additional security commitments require an order attachment covering encryption, keys, technical access, recovery, incident contacts and responsibilities. Unimplemented twenty-four-hour notices, sixty-day clearance, fixed supplier-change notices or 100% availability are not automatic promises.