·By Ablola, Saribong & Gueco Law Offices · researched and citation-checked against the firm's law library

Software Escrow in the Philippines: How Source Code Protection Works

Software escrow in the Philippines protects source code through copyright and undisclosed information rules under the Intellectual Property Code.


Software escrow is a private commercial arrangement, not a government registration. In the Philippines, there is no law that specifically regulates software escrow. Instead, source code is protected mainly through copyright and the protection of undisclosed information, both recognized as intellectual property rights under Section 4.1 of the Intellectual Property Code of the Philippines (Republic Act No. 8293). An escrow agreement typically names a neutral third party who holds a copy of the source code and releases it to the licensee if the developer defaults, stops operating, or breaches the contract.

What software escrow means in practice

Software escrow is a tripartite arrangement among three parties:

  • The developer or vendor, who owns the source code;
  • The client or licensee, who uses the software under a license; and
  • The escrow agent, a neutral third party who stores the source code and related materials.

The source code is deposited with the escrow agent and kept confidential. It is released only when a defined release event occurs — for example, the developer's insolvency, failure to maintain the software, or breach of a support obligation.

This matters because a client usually receives only the compiled or object code, not the human-readable source code. Without access to the source code, the client cannot maintain, update, or fix the software if the developer disappears.

How Philippine law protects source code

The Intellectual Property Code does not treat computer programs as a separate category of protected work. Protection comes from the general intellectual property rights listed in Section 4.1:

  • Copyright and related rights;
  • Protection of undisclosed information; and
  • Other rights such as patents, trademarks, and industrial designs.

The Code also addresses software in the context of technology transfer arrangements. Under Section 4.2, this term covers contracts or agreements involving the transfer of systematic knowledge for the manufacture of a product, the application of a process, or the rendering of a service, including management contracts, and the transfer, assignment or licensing of all forms of intellectual property rights, including licensing of computer software except computer software developed for mass market.

Two practical consequences follow:

  1. A software license that is not a mass-market product may fall within the technology transfer rules under the Code.
  2. The Documentation, Information and Technology Transfer Bureau of the Intellectual Property Office is tasked under Section 11.8 to register technology transfer arrangements and settle disputes involving technology transfer payments.

Why escrow is not a registration with the IPO

Software escrow is a contractual safeguard, not a government filing. Nothing in the Intellectual Property Code requires source code to be deposited with the Intellectual Property Office.

The Intellectual Property Office's functions under Section 5 relate to patents, trademarks, geographic indications, integrated circuits, and the registration of technology transfer arrangements. It does not operate a public source code registry.

The escrow agent is therefore a private party chosen by the contracting parties. The protection comes from the escrow contract and from the underlying intellectual property rights of the developer.

Key clauses in a software escrow agreement

Because the Code does not prescribe escrow terms, the contract does the work. A well-drafted agreement typically covers:

  • What is deposited. Source code, build instructions, documentation, libraries, and configuration files needed to compile and run the software.
  • Verification. Whether the escrow agent or an independent expert confirms that the deposited materials actually compile and match the licensed version.
  • Release events. The specific triggers — insolvency, cessation of business, failure to cure a material breach, or abandonment of the product.
  • Release conditions. Who may request release, what notice must be given, and whether the developer can object.
  • License scope on release. What the client may do with the source code after release — usually a limited right to use, maintain, and modify it for internal purposes only.
  • Confidentiality. Obligations on the escrow agent and the client to keep the source code secret.
  • Updates. How new versions of the software are deposited over time.

Protecting source code as undisclosed information

Even without escrow, Philippine law recognizes the protection of undisclosed information as an intellectual property right under Section 4.1 of the Code. This is the trade secret route.

For source code to enjoy this protection, the developer must treat it as confidential. Practical measures include:

  • Restricting access to authorized personnel;
  • Using non-disclosure agreements with employees, contractors, and clients;
  • Marking documents as confidential; and
  • Avoiding public disclosure of the source code.

If confidentiality is lost, the undisclosed information protection is weakened. Escrow supports this framework because the deposited code remains confidential and is released only under controlled conditions.

Frequently asked questions

Is software escrow required by law in the Philippines? No. The Intellectual Property Code does not require software escrow. It is a voluntary commercial arrangement between the developer, the client, and an escrow agent.

Can I patent software in the Philippines? The Intellectual Property Code's provisions on patentability are set out in Part II. The exact treatment of computer programs under the patent provisions is not reproduced in the materials available here, so this should be confirmed against the specific text of the Code before relying on it.

Does a software license need to be registered with the IPO? A license involving computer software that is not developed for mass market may qualify as a technology transfer arrangement. Under Section 11.8, the Documentation, Information and Technology Transfer Bureau registers technology transfer arrangements and settles disputes involving technology transfer payments.

Practical takeaways

  • Software escrow in the Philippines is a private contract, not a government registration.
  • Source code is protected mainly through copyright and the protection of undisclosed information under Section 4.1 of the Intellectual Property Code.
  • Software licenses that are not for mass-market products may fall under the technology transfer rules, with the Documentation, Information and Technology Transfer Bureau handling registration and disputes.
  • A strong escrow agreement should define the deposit, verification, release events, and the license scope after release.

Primary sources

The rules discussed above are drawn from the following primary sources, as published in the Official Gazette and the national statute book.

  • REPUBLIC ACT NO. 8293 - AN ACT PRESCRIBING THE INTELLECTUAL PROPERTY CODE AND ESTABLISHING THE INTELLECTUAL PROPERTY OFFICE, PROVIDING FOR ITS POWERS AND FUNCTIONS, AND FOR OTHER PURPOSES

This article is general information and not legal advice. For your specific situation, consult a lawyer or ask ASG Legal AI.

Related reading

Have a question about this topic?

This article is general information, not legal advice. Ask ASG Legal AI for a cited, plain-language answer on your own situation — free, no sign-up.