Cross-border transfer

How it works

The DPA contemplates cross-border flows with accountability. Standard clauses, purpose limits, and security matter more than a slogan about ‘adequacy.’ Payroll data goes PH agencies. Customer data often sits on U.S. processors accessed from PH. For a U.S. company hiring one Filipino teammate, write this into the brief, the employment contract, and the peso payroll file before the start date. Slack habits do not override the Labor Code, BIR, or NPC. If the local employer of record holds the paper, they run the statutory step; you still owe a clean operating definition so the seat does not fail in week three. Put a number on the example when you budget loaded cost, because a nameless allowance always returns as a December surprise or a missed SLA.

Example: EA in Cebu opens Salesforce on U.S. servers. That is a transfer in practice. Lock device and access, not just a privacy policy page.

How it differs

DSA documents it. Sensitive personal information raises the bar. Company device vs BYOD changes the leak surface.

Common errors

Emailing a full customer export to a personal Yahoo to ‘work offline.’

In practice

Treat Cross-border transfer as a week-one operating object. Name the system of record, the device, and who can still log in on the last day. If the answer is a shared password, stop. Write an owner - founder, local employer, or worker - and a date you will look at it again: first cutoff, first holiday, or first miss. If nobody can show a contract clause, a payslip line, a calendar block, or a checklist box, you do not have cross-border transfer yet. You have a conversation. Convert the conversation before the person starts, while changing the deal still costs a paragraph rather than a resignation. Re-read the worked example above against the actual hire in front of you. If the numbers in that example cannot be swapped for this seat’s pesos, hours, and start date, the brief is still unfinished.