Cross-Border Personal Data Transfer Assessment
Operated by Tek Asia Sdn Bhd · SSM 202501011675 (1613089-U) · DPO [email protected]
Section 129 of the Personal Data Protection Act 2010 prohibits the transfer of personal data outside Malaysia except in specified circumstances. This memo identifies every cross-border transfer Tek Asia Sdn Bhd makes in the course of operating the WABI service, the lawful basis for each, and the safeguards in place.
1 · Summary
Personal data at rest is stored exclusively in Singapore (DigitalOcean SGP1). Personal data in transit is processed by a small, named set of sub-processors operating from the United States and globally. Each transfer below is justified under one or more Section 129 conditions.
2 · Transfers in scope
Transfer 01
OpenAI, L.L.C.
Embeddings for knowledge-base search — every inbound message and knowledge-base entry — and LLM inference when a tenant selects an OpenAI model
United States
Customer message content (current message + recent context window), tenant business context, retrieved knowledge base snippets. No tenant or end-user identifiers (no phone numbers, no names) are sent.
Section 129(1)(a) — written consent of the data subject. Tenant grants consent on signup; tenant has its own basis to relay end-user messages (Section 6) within its existing privacy notice to its customers.
- OpenAI does not use API data to train its models (OpenAI's published API data policy)
- Retention per OpenAI's standard API policy: abuse-monitoring logs kept up to 30 days. WABI does not hold a zero-data-retention agreement
- TLS in transit; customer names and phone numbers are never sent
- Per-tenant daily AI spend cap bounds exposure
- Pre-inference keyword gate skips LLM entirely for sensitive intents (e.g. 'lawyer', 'complaint')
Low. No customer names or phone numbers sent; retention limited to OpenAI's standard 30-day policy; no model training.
Transfer 02
Anthropic, PBC
LLM inference for Spark AI auto-replies and learning (when tenant has selected a Claude model)
United States
Same as OpenAI transfer.
Section 129(1)(a) — same as OpenAI transfer above.
- Anthropic does not use API data to train its models by default (Anthropic's published commercial terms)
- Retention per Anthropic's standard API policy: deleted within 30 days. WABI does not hold a zero-data-retention agreement
- TLS in transit; customer names and phone numbers are never sent
- Per-tenant daily AI spend cap and pre-inference keyword gate (same as OpenAI)
Low. Same posture as OpenAI.
Transfer 03
Stripe, Inc. / Stripe Payments Malaysia Sdn Bhd
Payment processing for SaaS subscriptions
United States / Malaysia (Stripe operates a Malaysian entity)
Cardholder name, email, billing address. Card PAN never transits our infrastructure — tokenised at Stripe.
Section 129(1)(b) — necessary for performance of the contract; and (a) consent.
- PCI-DSS Level 1 certified processor
- Stripe Malaysia local entity available where required
- We hold only Stripe customer/subscription IDs, never raw card data
Very low. Card data never touches WABI infrastructure.
Transfer 04
Meta Platforms, Inc. (WhatsApp Cloud API)
Inbound and outbound WhatsApp message delivery — the core protocol layer
Global (Meta's edge network)
All message content, sender phone numbers, profile names. This is unavoidable — Meta IS WhatsApp.
Section 129(1)(b) — strictly necessary for performance of the contract (delivering WhatsApp customer service). The tenant has independently agreed to Meta's terms when registering its WhatsApp Business number.
- HMAC-SHA256 webhook signature verification on every inbound message
- TLS in transit
- Per-tenant encrypted Meta access tokens (AES-256-GCM at rest)
- Tenants accept Meta's WhatsApp Business policies as part of WABI onboarding
N/A — this transfer is intrinsic to the WhatsApp protocol the tenant has chosen to use.
Transfer 05
Resend, Inc.
Transactional email delivery (onboarding, alerts, DSAR responses, breach notifications)
United States
Recipient email address, message subject + body.
Section 129(1)(b) — performance of the contract.
- TLS in transit
- No customer message content sent in transactional emails — only WABI service events
Low. Transactional metadata only.
Transfer 06
DigitalOcean, LLC
Compute and storage (application hosting, Postgres, Redis)
Singapore — SGP1 region only
All tenant data.
Section 129(1)(e) — the data is to be processed only in a place that ensures an equivalent level of protection. Singapore's PDPA 2012 is recognised as comparable to Malaysia's PDPA 2010.
- DigitalOcean Data Processing Agreement
- All application and database resources provisioned in SGP1 only
- Managed Postgres and Valkey encrypted at rest (LUKS) and in transit (TLS), per DigitalOcean's documentation
- Database access restricted to WABI's own application (trusted sources)
Very low. Singapore residency, regulator-recognised regime.
3 · Transfers we will NOT make
- We do not sell, lease, or share personal data with advertising networks, data brokers, or analytics processors that aggregate across our customers.
- We do not use customer message content to train generally-available LLMs. The Spark AI learning loop is strictly per-tenant: a correction made by Tenant A's agent never influences Tenant B's replies.
- We do not transfer data to jurisdictions without recognised data protection regimes; this rules out a number of common LLM providers we have explicitly evaluated and declined.
4 · Tenant communication obligations
Tenants must (a) include WABI as a processor in their own privacy notice to end customers, (b) name OpenAI / Anthropic / Stripe / Meta / DigitalOcean / Resend as sub-processors where their lawful basis analysis requires that level of detail, and (c) update their notice within 14 days when we publish a sub-processor change.
5 · Review and ownership
Owner: Data Protection Officer ([email protected]).
Review cadence: annually, or whenever a new sub-processor is added, or whenever a sub-processor changes its data-residency posture.