Enforcing Confidentiality in Solar Farm Operations and Maintenance Contracts in the Philippines

Introduction: why confidentiality disputes arise in solar O&M work

Solar farm operations and maintenance (O&M) contracts often require third-party crews to work inside a plant and handle sensitive operational know-how: cleaning methods, tracker calibration routines, performance analytics, site documentation, and vendor-specific configurations. Conflicts usually arise when an O&M contractor or its personnel later use the same methods for another client, or when documentation and field-developed improvements are copied, shared, or reverse-engineered.

In the Philippines, protecting these interests typically rests on (a) contract drafting and enforcement, (b) evidentiary rules on trade secrets, and (c) sector-specific confidentiality rules that can supplement contractual obligations. Courts also weigh confidentiality against transparency policies when government is involved in the project.

Governing legal sources relevant to solar confidentiality and proprietary methods

1) Contract-based confidentiality: enforceability and common carve-outs

Confidentiality is generally enforced primarily as a contractual undertaking. In large infrastructure and project agreements, confidentiality clauses are treated as standard commercial protections for proprietary data and intellectual property, and may be upheld especially when they include reasonable exceptions for disclosures required by law or to tribunals in proceedings.

The Supreme Court recognized that confidentiality clauses are common in finance-related project agreements and are not automatically unconstitutional, especially where there are exceptions for disclosures “required by law” and to tribunals handling disputes related to the agreement. This approach is shown in Francisco, Jr., et al. v. Toll Regulatory Board, et al. (2010), where the Court noted that such clauses typically aim to protect proprietary data or intellectual property rights and pointed to a “required by law” exception as an important limiting feature.

2) Court protection of trade secrets during litigation

Even with a strong confidentiality clause, disputes often end up in court or arbitration where one side seeks disclosure of internal processes, formulas, field procedures, or manuals. Philippine evidence rules provide a direct trade secret protection: a person cannot be compelled to testify about a trade secret unless non-disclosure would conceal fraud or otherwise work injustice. If disclosure is ordered, the court must adopt protective measures to protect the trade secret owner while ensuring fair adjudication.

This is expressly stated in the 2019 Amendments to the 1989 Revised Rules on Evidence (A.M. No. 19-8-15-SC, effective 2019), Rule 130, Section 26 on privilege relating to trade secrets.

3) When a solar project is tied to government procurement or PPP arrangements

If the solar farm is a public-private partnership (PPP) project, the PPP Code contains a statutory confidentiality rule for confidential business information submitted in relation to activities under the Code, including related deliberations. It prohibits disclosure unless the private entity consents or disclosure is mandated by law or by a valid court order or a valid order of a competent government/regulatory body.

This statutory protection is found in Republic Act No. 11966 (PPP Code of the Philippines, 2023), Section 30(c). The IRR of RA 11966 (2024) also recognizes that entities may claim confidentiality over information submitted in relation to PPP activities, subject to procedures in the IRR (including for tender documents).

4) Transparency limits where government foreign loans or sovereign commitments are involved

When a solar project is connected to government-contracted foreign loans or similar arrangements, confidentiality language cannot be drafted to defeat constitutionally mandated public access to information. The Supreme Court held that a confidentiality clause that makes disclosure the exception (e.g., requiring lender consent to disclose “all terms”) unduly diminishes the State’s obligation to allow public access to information on government-contracted foreign loans.

This warning is discussed in Colmenares, et al. v. Duterte, et al. (2022). For O&M contracts, the point is not that confidentiality is barred, but that clauses must be carefully scoped if the State’s transparency obligations are in play.

5) Energy-sector confidentiality rules that may reinforce contract protections

Certain energy-related statutes expressly impose confidentiality duties on agencies or institutions handling proprietary data, which can support an argument that the parties reasonably treated the information as confidential. For example, the Energy Virtual One-Stop Shop Act restricts disclosure of documents submitted by energy project proponents, subjecting any release to the Freedom of Information manual of the agency concerned.

This is reflected in Republic Act No. 11234 (Energy Virtual One-Stop Shop Act, 2019), Section 18. Separately, the Philippine Energy Research and Policy Institute Act provides that proprietary or confidential data should not be posted or disclosed without prior consent of the source/owner, under Republic Act No. 11572 (2021), Section 14.

What information in solar O&M is typically protectable as “confidential” or a “trade secret”

Philippine disputes often turn on whether the information was truly confidential and treated as such. In solar O&M, the following are commonly asserted as confidential business information or trade secrets (subject to proof):

• Proprietary cleaning method documentation (chemical mix ratios, equipment settings, crew timing, water treatment or reuse process, anti-soiling approaches, quality-control tests).
• Tracker tuning and calibration routines (alignment procedures, control parameter sets, diagnostic sequences, field fixes, and adjustment thresholds).
• Performance analytics and site-specific playbooks (SCADA tags mapping, alarm triage logic, predictive maintenance rules, degradation analyses, loss tree design).
• Training materials and manuals created for local crews that reflect proprietary methods.
• Field-created improvements (work instructions, jigs, checklists, templates, custom scripts) developed while implementing the foreign developer’s approach.

Information is harder to protect when it is already public, is standard industry know-how, or was not handled as confidential (e.g., broadly shared without controls or markings).

Drafting O&M confidentiality clauses that address third-party crews and replication risk

To reduce the chance that a third-party O&M contractor can replicate a foreign developer’s proprietary cleaning or tracking systems, the confidentiality package should combine definitions, controls, and remedies. The following items are commonly used in Philippine contracts and are consistent with how courts evaluate reasonableness:

1) Define confidential information by category and by handling

A definition that covers (a) technical information, (b) operational procedures, (c) documentation, and (d) improvements created in the field tends to be easier to enforce than a vague catch-all. Treating marked information as confidential and imposing similar duties on unmarked information disclosed under controlled circumstances can help.

2) Bind the entire contractor “chain”

Replication risk is often caused by subcontractors, project hires, and rotating personnel. The contract should require the O&M contractor to impose back-to-back confidentiality obligations on employees and subcontractors, and to remain liable for their breaches.

3) Add a “use restriction,” not just “non-disclosure”

Non-disclosure alone may not stop copying if the contractor claims it merely applied “experience.” A use restriction can prohibit using proprietary methods except for performing services for the project, and can forbid applying the same manuals, settings, templates, or process documents to another solar site.

4) Handle “field-created IP” and improvements expressly

Because the focus involves “intellectual property created in the field,” the contract should clarify ownership of deliverables, documentation, work instructions, scripts, and improvements produced during the O&M term. If the intent is that the developer (or project company) owns improvements derived from confidential materials, say so clearly, and require assignment of rights and turnover of source files.

5) Include audit, return/destruction, and access controls

Protective operational controls strengthen later court claims that the information was genuinely secret. Typical measures include device restrictions, controlled access to SCADA/analytics platforms, secure repositories, and an end-of-contract certificate of return/destruction.

Summary table: contract provisions that directly address replication by third-party crews

Clause element	What it prevents	Drafting notes
Use restriction	Contractor reusing proprietary cleaning/tracker methods on other sites	Limit use “solely for performing the Services” and prohibit derivative application elsewhere.
Improvement and deliverables ownership	Contractor claiming rights to field-created manuals/scripts/templates	State ownership, assignment, and turnover requirements; include “derivative works.”
Back-to-back obligations	Subcontractor leakage	Require written NDAs for personnel/subcontractors and keep the main contractor liable.
Return/destruction + certification	Copies retained after termination	Cover hard copy, digital, backups where feasible, and cloud repositories used by contractor.
Remedies and injunctive relief language	Delay in stopping misuse	Provide for interim relief consistent with applicable dispute forum; specify liquidated damages if appropriate.

Enforcement options in the Philippines when an O&M contractor copies proprietary methods

1) Contract enforcement and damages

The usual first line is a breach of contract claim for violating confidentiality and use restrictions. Where the contract has a clear definition of confidential information and documented protective controls, the developer’s position strengthens.

2) Injunctive relief and protective orders during proceedings

When a developer needs to stop ongoing disclosure or replication, injunctive relief may be sought (subject to procedural requirements and the dispute forum). In litigation where trade secrets must be discussed, Rule 130, Section 26 allows courts to apply protective measures when disclosure is ordered, helping limit further spread of sensitive data.

3) Handling disclosure requests and government-related disclosure risk

If the project involves a government agency, PPP procurement, or documents submitted to an energy permitting platform, counsel should identify what can be treated as confidential business information under the relevant statute and what may still be subject to lawful disclosure. Under the PPP Code, confidential business information submitted under PPP activities is protected unless an exception applies, including a valid order of a court or government/regulatory body, or a law mandating disclosure.

If the dispute concerns foreign loans used by government, confidentiality clauses should be reviewed against transparency obligations recognized by the Supreme Court in Colmenares v. Duterte (2022), to avoid overbroad language that can be struck down or read narrowly.

Typical scenarios and how the law and contracts interact

Scenario A: cleaning crew transfers to another contractor and brings manuals and checklists

This is primarily addressed by (a) use restrictions, (b) return/destruction obligations, and (c) individual NDAs with personnel. If litigation results, the developer can invoke trade secret protection under Rule 130, Section 26 to limit compelled disclosure and request protective handling of manuals and process documents.

Scenario B: O&M contractor claims the tracker tuning method is “standard” and not confidential

Disputes often become proof-based: what is truly proprietary, how it differs from common practice, and what controls were used to keep it secret. Documentation showing restricted access, confidentiality markings, and limited disclosures helps establish that the information qualifies as protected confidential information or a trade secret.

Scenario C: the solar project is a PPP, and bid/tender documents include proprietary O&M procedures

Here, the PPP Code’s confidentiality of confidential business information may help, but the developer must comply with the IRR’s procedure on claiming confidentiality for submitted information. Drafting should anticipate the possibility of lawful compelled disclosure (e.g., court/regulator orders) and define how disclosures will be handled (notice, redactions, confidentiality undertakings).

Action-oriented guidance for developers and project companies

• Inventory the proprietary elements (cleaning chemistry/steps, tracker parameters, scripts, manuals) and match them to the contract’s definition of confidential information.
• Use both non-disclosure and non-use obligations to directly address replication, not just leaks.
• Control access on-site (segregated files, controlled devices, limited SCADA permissions) so you can later show the information was treated as confidential.
• Require back-to-back NDAs for subcontractors and rotating personnel, with the prime contractor remaining responsible.
• Plan for disputes early: include dispute resolution clauses that allow prompt interim relief and include procedures for protected disclosure in proceedings.

Conclusion

In the Philippines, enforcing confidentiality in solar O&M contracts is mainly a matter of careful contract drafting supported by consistent on-the-ground confidentiality controls. Courts generally recognize confidentiality clauses as standard in commercial and project agreements, while evidence rules provide an added layer of protection for trade secrets through limits on compelled disclosure and protective measures. Where government participation exists—especially PPPs or government-related financing—confidentiality must be written with statutory protections and transparency limits in mind, so the project can protect proprietary cleaning and tracking systems without relying on overbroad restrictions that may not hold.

About Nicolas and De Vega Law Offices

 Nicolas and de Vega Law Offices is a full-service law firm in the Philippines.  You may visit us at the 16th Flr., Suite 1607 AIC Burgundy Empire Tower, ADB Ave., Ortigas Center, 1605 Pasig City, Metro Manila, Philippines.  You may also call us at +632 84706126, +632 84706130, +632 84016392 or e-mail us at [email protected]. Visit our website https://ndvlaw.com.