Outsourcing Development to the Philippines: GDPR and IP — Security & GDPR article by Rui Codex

Before outsourcing development to the Philippines, a Belgian company should check three things: the GDPR basis for sending personal data outside the EU, whether the contract transfers ownership of the code, and whether the agreement sets clear acceptance, security and exit terms. Each check can fail on its own, so each needs a separate sign-off.

Key takeaways

  • Giving a Philippine team access to personal data is a transfer under the GDPR, even when the team only logs in remotely.
  • The EU Standard Contractual Clauses, backed by a documented transfer assessment, are the usual starting point for these transfers.
  • Ownership of code and other work product must be assigned in writing, because it does not reliably follow from the working relationship.
  • Acceptance criteria, sub-processor rules and data return on exit belong in the contract before the first sprint starts.

Does remote access count as a GDPR transfer?

Yes, in most cases it does. A transfer happens when personal data is made available to a recipient outside the EU or EEA, and a developer who can open a database or a support ticket from Manila has access to that data even if nothing is copied. The European Data Protection Board publishes guidance on how these rules apply, and its work is collected on the EDPB website.

Chapter V of the General Data Protection Regulation sets the conditions for transfers. Article 44 states that a transfer to a third country is allowed only if the conditions in that chapter are met, and Article 46 lists the appropriate safeguards, the most common being standard data protection clauses adopted by the Commission. You can read the full text in Regulation (EU) 2016/679 on EUR-Lex.

The Philippines does not appear on the European Commission's list of adequacy decisions, so an adequacy finding cannot be assumed. Check that list again before you rely on it, because the Commission adds countries over time.

This article is general information and not legal or tax advice.

Tip: Map every system a developer can reach, including staging databases, ticketing tools that contain customer names and backups. Remote access to any of them can count as a transfer, so the map is the starting point for your analysis.

Which transfer safeguard should you use?

For most offshore development setups, the practical choice is the EU Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914, combined with a written transfer assessment. The clauses are not a template you sign and forget, because their content depends on the roles of the parties.

The decision provides modules for different roles. A Belgian company acting as controller that engages a Philippine vendor acting as processor will usually use a different module than a vendor that subcontracts part of the work onward. Choosing the module requires an honest description of who decides what happens to the data.

After the Court of Justice's Schrems II judgment, exporters must also assess whether the law and practice in the recipient country undermines the protection the clauses give, and add supplementary measures where needed. The EDPB's recommendations on this assessment are available on the EDPB website.

Trade-offs and failure points

  • Wrong module: a clause set that does not match the real roles leaves the contract misaligned with how the vendor actually works.
  • Sub-processors: if the vendor brings in freelancers or a hosting provider, each onward transfer needs its own agreement and disclosure.
  • Assessment drift: an assessment written at kick-off does not cover a new tool, a new access path or a new country of residence for staff.

Clear transfer rules are also part of a wider security posture. Our security, GDPR and compliance engineering guides cover the technical controls that support these contracts.

Who owns the code a Philippine developer writes?

Your company owns that code only when the contract assigns it to you in writing, so do not rely on default positions. Ownership depends on the employment arrangements of the developer and on the agreement between the parties, and the first owner may be the individual author or their employer.

The Berne Convention, administered by the World Intellectual Property Organization, provides that copyright protection does not depend on registration or other formalities. In practice this means a Philippine developer's code is protected from the moment it is written, which is exactly why the transfer of rights must be documented. Background on the convention is available on the WIPO website.

Clauses to check

  • An assignment of all work product, including unfinished code, documentation, scripts and configuration.
  • A list of pre-existing material the vendor brings in, with a licence that lets you use it inside your product.
  • A list of open-source components and their licences, delivered before the first release.
  • Clear rules on who holds the repositories, accounts and credentials, so that access does not sit in a personal account.
Tip: Ask for the open-source inventory before the first sprint. Reconstructing that list after delivery is far harder and often incomplete.

Which contract terms matter most for an offshore team?

Acceptance criteria, security obligations, sub-processor control, data return and termination rights matter most, because they decide what you receive and how you can leave. A contract that covers price and timelines but not these points leaves you with limited options when something goes wrong.

Acceptance criteria should define what done means, which test environments count, and who signs off each release. Without them, disputes about quality become disputes about opinion. Security terms should set access controls, device rules and incident notification. Article 33 of the GDPR requires a controller to notify the supervisory authority of a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware of it, as stated in the GDPR on EUR-Lex. Your contract should require the vendor to report far sooner than that.

Exit terms are the most often neglected part. The contract should require return or deletion of personal data, a handover of source code and documentation, and a knowledge transfer period. It should also name key personnel and set notice periods for replacing them.

Hypothetical examples of an offshore project

Here are two hypothetical scenarios: they describe typical situations, not real companies, and they contain no results.

In the first scenario, a logistics firm gives a team in Manila access to its order database so the team can build an integration. No transfer clauses are signed. During a review, the firm recognises the transfer gap, signs the clauses, records an assessment and restricts access to test data until the paperwork is complete.

In the second scenario, a software company's contract says nothing about IP. The developer keeps the repository in a personal account. When the relationship ends, the company has to negotiate access to its own code. An assignment clause and a rule that repositories belong to the client would have prevented the dispute.

When does offshoring to the Philippines not work?

It fails when work depends on frequent real-time decisions, when requirements change weekly, or when governance is thin, because distance amplifies each of these problems. Offshoring works best for well-defined modules with clear interfaces and documented acceptance tests.

The Philippines is several hours ahead of Belgium, so the shared working window is shorter than many teams expect. A product owner in Brussels may only have a short overlap with the developers in the morning. Plan the overlap deliberately, and treat it as a scarce resource rather than an assumption.

Governance is the second failure point. Without a named technical owner on the Belgian side, decisions drift and the vendor fills gaps with its own assumptions. A hybrid model, with a local architect who owns interfaces and a vendor who owns implementation, is often easier to control. Our custom software development services and system integration services describe how this split works in practice.

Tip: Before choosing a vendor, compare the vendor's contract against the checklists in this article. Our guide on choosing a software development partner in Belgium covers the wider selection criteria.

Frequently Asked Questions

Do I need transfer clauses if the Philippine team only works in my own tools?

Yes, if the team can view personal data from the Philippines, that access is generally a transfer that needs a safeguard. Reduce the problem first by limiting access to test data or anonymised records. Where personal data remains in scope, check the official GDPR text and the Commission's clauses before granting access.

Does the contract give my company the code automatically?

No, ownership should not be assumed. Your company receives rights to the code only when the agreement assigns them or grants a licence that is clear enough to use. Include an assignment of all work product, a list of pre-existing material and a rule that repositories and credentials belong to your company.

Is a data processing agreement enough on its own?

No. A data processing agreement under Article 28 of the GDPR governs the processor relationship, but a transfer to a third country also needs a mechanism under Chapter V, such as the Standard Contractual Clauses. The two documents work together, and each one is needed for a complete offshore arrangement.

How quickly must a vendor report a personal data breach?

The vendor should report as soon as it becomes aware of a breach, so that the controller can meet its own deadline. Under Article 33 of the GDPR, the controller must notify the supervisory authority within 72 hours where feasible. Your contract should set a much shorter internal reporting period for the vendor.

Can Rui Codex help with an offshore setup?

Rui Codex is independent and serves businesses across Belgium, the Netherlands and Luxembourg, with custom software development, system integration and AI automation services. It offers technical implementation support for the systems and integrations involved. Contract reviews and transfer documentation are best prepared with qualified counsel, and you can email info@ruicodex.com to discuss your project.

Conclusion

Outsourcing development to the Philippines can work well, but only when the data flows, the code ownership and the contract terms are settled before the first commit. Treat remote access as a transfer, choose clauses that match the real roles, and write IP assignment and exit rights into the agreement. Each of these checks is cheap to do early and expensive to repair later. If you are weighing an offshore model against a hybrid setup, request a project consultation at https://ruicodex.com/Contact and describe the systems and data involved.

Sources

Tags: outsourcing development Philippines GDPR transfers standard contractual clauses intellectual property software contracts Belgium offshore development

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request