Last materially reviewed: September 6, 2026
Intellectual Property → AI-Generated Works
Direct Answer
AI-generated code should not be treated as automatically owned copyright merely because a developer prompted the tool. Philippine copyright protects computer programs, but current IPOPHL guidance still centers authorship on natural persons. Human-written code, original architecture and substantial human modifications may be protected, while purely generated portions can present uncertainty.
Key Takeaways
- Separate human-written code from machine-generated code.
- Check employer, contractor and client ownership rules.
- Review AI-provider terms and code-generation restrictions.
- Scan for open-source or third-party license obligations.
- Keep provenance records for commercially important code.
What Rights Can Exist?
Software copyright can protect source code as expression. It does not generally give monopoly rights over ideas, algorithms, methods or functionality by themselves. Where AI generates code, the first question is which expressive elements came from a human developer.
Decision Snapshot
| Scenario | Main issue |
|---|---|
| Developer writes most code and AI autocompletes small portions | Human authorship remains substantial; review generated snippets separately. |
| AI generates a whole module from a prompt | Copyright ownership in that generated expression may be uncertain. |
| Employee uses AI at work | Employment rules and company policy may affect ownership of human-created portions. |
| Freelancer uses AI for a client | The contract should address disclosure, assignment and third-party license risk. |
Open-Source Risk
Generated code can resemble code from public repositories or include patterns associated with licensed software. Before shipping commercially, use code review and license-scanning processes appropriate to the project. Do not assume that an AI tool eliminates open-source compliance obligations.
What Copyright Protects in Software
Computer programs are expressly listed under Section 172.1(n). Section 175 separately excludes ideas, procedures, systems, methods and principles as such. Protection in code expression is not automatically a monopoly over a business function, algorithm or abstract architecture. IP Code, Sections 172 and 175 (our IP Code explainer).
Separate copyright eligibility, ownership, third-party permissions and software quality. A module can be correctly licensed yet insecure; it can pass tests yet contain code that requires permission. See software copyright and the AI human-authorship framework.
Employee and Contractor Rules
For eligible human-created work, Section 178.3 generally assigns copyright to the employer when work results from regularly assigned duties, unless an express or implied agreement provides otherwise. Work outside regular duties is treated differently under that provision, even where employer resources are used. IP Code, Section 178.3.
For commissioned work under Section 178.4, copyright remains with the creator unless a written stipulation provides otherwise. Receiving a repository or paying an invoice should not be confused with resolving the full copyright allocation. IP Code, Section 178.4. The guides for employee-created software and freelancer-created software address these arrangements.
Apply the rules to eligible human expression. They do not manufacture copyright in purely generated portions. Ownership of a larger application also does not necessarily include ownership of every dependency within it.
Three Development Scenarios
Hypothetical: AI Suggests a Function
A developer writes an application and accepts a suggested function. Record the accepted code and subsequent changes, then review whether a third-party source or license is identifiable. A short common implementation and a distinctive copied implementation require different analysis. Do not assume every suggestion is clear to ship simply because the developer accepted it.
Hypothetical: A Module Matches a Repository
A review identifies a close match with a library. Preserve the match, repository URL, version and license. Determine whether the license permits the intended distribution and which conditions apply. Do not delete a copyright notice and treat the remaining code as new. Isolate the component while unresolved permissions are assessed.
Hypothetical: A Contractor Delivers an Application
A client wants proprietary distribution, but the delivery contains human code, generated code and external components. Request a component inventory and written rights allocation. A promise of full ownership needs to identify licensed dependencies and exclusions. Ask for records supporting the permissions actually available rather than treating a blanket promise as proof.
Reviewing License Obligations
Read the exact license associated with the relevant version. Open source is not one permission set. Some licenses require retained notices; others have additional conditions. Determine how the component is used, modified and distributed instead of assuming that public availability means unrestricted reuse.
Code scanning can identify possible matches, but a clean scan is not conclusive legal clearance. Record both the detected source and the license relied on. If the source is uncertain, do not invent a license. Escalate important unresolved matches for qualified review, especially where a customer expects exclusive proprietary rights.
A Code Provenance Register
| Field | What to record |
|---|---|
| Component | File, module, package and version |
| Origin | Human author, AI-assisted contribution or external repository |
| Creation evidence | Commit history, accepted suggestion and human edits |
| Rights basis | Employment scope, assignment or license |
| Conditions | Notices, permitted uses and unresolved restrictions |
| Review result | Reviewer, date, approved release and open issues |
Keep records without exporting secrets or unnecessary personal information. A commit label is evidence of a recorded contribution, not definitive proof that its committer originally authored every line. Preserve development context and the actual agreement relied on. This register is a practical control, not a government-mandated form.
Before Shipping or Selling
- Inventory components. Include copied source fragments, not only package-manager dependencies.
- Verify allocation. Check employee duties, contractor agreements and relevant assignments.
- Investigate matches. Retain the identified repository version.
- Resolve conditions. Prepare notices and obtain advice on uncertain obligations.
- Review provider terms. Check the actual account arrangement without assuming a universal guarantee.
- Run engineering checks. Test behavior, security and maintainability separately from legal clearance.
- Record approval. Link review to the version delivered.
If an allegation arrives after release, preserve the affected version, notices, agreements and history. Investigate the identified lines rather than deleting the record. A replacement may reduce future exposure but does not automatically resolve earlier distribution. Use the AI infringement guide for response considerations and the vendor contract guide for contractual allocation.
Separate a contractual service dispute from copyright infringement. Software failing acceptance tests does not by itself prove infringement. Conversely, working software does not establish that its creator had permission to distribute every component. The contract, actual code and applicable rights must be examined together.
Related Cybercode Guides
- Software Copyright Philippines
- Software Created by an Employee
- Software Created by a Freelancer
- AI Vendor Contracts
Frequently Asked Questions
Does AI-generated code belong to the employer?
Not automatically. First determine whether copyright exists in the relevant human-created expression, then apply employment and contract rules.
Can I sell software containing AI-generated code?
Possibly, but review provider terms, third-party rights, licenses, warranties and security before commercial release.
Official Sources
- IPOPHL — Copyright, including computer programs
- IPOPHL — Copyright FAQs
- WIPO — AI systems and software copyright
- WIPO — Generative AI and IP
Featured image: Photo by Luca Bravo on Unsplash.
Important: This article provides general educational information about Philippine law and technology. It is not legal advice and does not create an attorney-client relationship. Laws, agency procedures, platform terms and the facts of each situation may change the result. Verify current requirements through the cited official sources and seek qualified professional advice when your rights, deadlines, money or legal exposure may be affected.