You are using an outdated browser and your browsing experience will not be optimal. Please update to the latest version of Microsoft Edge, Google Chrome or Mozilla Firefox. Install Microsoft Edge

February 20, 2015

Challenges of Protecting Intellectual Property in the Software Industry

Subscribe to Updates
Bangkok Post, Corporate Counsellor Column

In the fast-evolving and highly competitive technology industry, software developers and owners should exercise strong vigilance to ensure that their creations are properly guarded within the ambit of intellectual property rights. Protecting software, however, involves complex, interrelated issues that encompass a mix of copyright, patent, trademark, and trade secrets law.

In this article, we will examine what people in the software industry should know to adequately protect their creations and operate their business with fewer hitches.

Software as a Copyrighted Literary Work

Copyright protection applies to computer source code and is not limited to any particular language. The protection is automatic—i.e. no registration is required—but owners can still record their software as a copyrighted work with the Department of Intellectual Property to better prove ownership, should the need arise. The process, known as recordation, is free and uncomplicated.

Newly developed source code can be filed for recordation at any time. Important documents required include a copy of the first five pages and the last five pages of the source code, or a CD containing the relevant software.

Functions and Features of Software

Copyright law does not protect ideas about functions and features of software, nor does it protect functional user interfaces. For this reason, rival companies can develop the same kind of software and will not be considered to have committed copyright infringement, so long as the software has its own source code.

Ideas about software functions and features may, however, be protected under patent law. Currently, software is not patentable in Thailand, but in some countries, including the United States, it is. Thailand may be moving in this direction, as certain hardware or devices programmed with functions that are novel and involve an inventive step would be deemed patentable under Thai law, but these are considered on a case-by-case basis.

Source Code

Normally, after software has been commercially distributed, the source code is kept confidential and is only disclosed in necessary cases. If the source code is kept under appropriate security measures, it may be protectable under trade secret law, which imposes serious penalties on those who intentionally disclose, deprive, or use another party’s trade secrets without that party’s consent.

Copyright Ownership

The copyright of software developed by an employee under an employment contract is owned by the employee, unless agreed otherwise in writing. By contrast, the copyright of software developed under a specially commissioned contract will belong to the commissioning party. However, developers for other parties and their commissioners may agree that the copyright shall be owned by the developers.

License Agreements

If a customer requires a software developer to deliver source code, the parties should make it clear whether the customer wants to own the source code or merely customize or update the software in the future. This is because a software sale agreement or an agreement to assign copyright to the source code is significantly different from a license agreement.

If the parties agree to a software license agreement, under which the source code is required to be disclosed for the purposes of customizing or updating the software, the developer may include a provision under which the customer is obligated to keep the source code confidential.

Software license agreements do not bar copyright owners from granting licenses to other parties. As copyright is alienable, licensable, and divisible, many types of software license agreements exist, for example:

  • Exclusive Licenses: Only the licensee has the right to make use of the software. The licensor is not allowed to make use of it, nor grant any additional licenses.
  • Sole Licenses: Only the licensee is allowed to make use of the software. The licensor agrees to not grant any additional licenses, but retains the right to make use of the software.
  • Nonexclusive Licenses: The copyright owner may grant licenses to several users simultaneously and the licensor can also make use of the software. General software programs and mobile applications are normally licensed non-exclusively.

Copyright can be licensed to multiple users, unless expressly prohibited, such as under exclusive or sole license agreements. If the licensee does not want the copyright owner to grant licenses to other parties, the copyright license agreement must include a clause to this effect.

Registering Software Brands or Logos as Trademarks

Developers should create a brand name or trademark, for the purpose of internal reference, as well as for copyright recordation and licensing. Words or devices used as trademarks must not directly describe the nature or characteristics of the goods or services—otherwise, the trademark will not be registrable. Words or devices used as trademarks should be distinctive and must not be identical or similar to other parties’ registered trademarks.

Granting a software copyright license to a foreign company does not require registration. Many software products, however, bear widely known trademarks. Therefore, in addition to a software copyright license, a copyright owner may have to grant a trademark license to its customer—such as a distributor appointed in a foreign country. In such a case, the trademark should also be registered in that foreign country.

Products and services relating to software change rapidly, and sometimes existing protection may not completely cover all aspects of a new, innovative piece of software. Therefore, developers, government bodies and lawyers should regularly exchange ideas and opinions and keep themselves up-to-date to be able to deal with new problems effectively.

Download Full Article
Related Professionals

Industries

Technology

Practices

Intellectual Property

Location

RELATED INSIGHTS​ 

July 2, 2026
Thailand’s Electronic Transactions Development Agency (ETDA) released a new version of the draft Act on Artificial Intelligence on July 2, 2026, for a public hearing period expected to be approximately 30 days. The draft act adopts a risk-based regulatory approach modeled in part on international frameworks—particularly the EU’s AI Act—while incorporating provisions tailored to Thailand’s regulatory landscape and digital economy objectives. If enacted in its current form, the law would introduce extraterritorial obligations, a tiered risk classification system, strict liability for AI-related damages, and new transparency requirements for AI-generated content. Scope and Extraterritorial Application The draft act applies to AI development, deployment, or any other action affecting people in Thailand, even if the action occurs outside the country. Of note: This extraterritorial reach creates compliance obligations for global AI companies whose systems impact Thai residents or consumers, even if the provider has no physical presence in Thailand. Foreign AI providers serving Thai deployers or users must appoint a local coordinator or authorized representative. Depending on the type of AI system, the representative may need full authority to act on behalf of the provider without any limitation of liability. Certain activities are exempt from the draft act’s oversight, including AI used by natural persons solely for personal or household activities, AI for educational research conducted by higher education institutions with ethics committee approval, research and development activities conducted prior to distribution or service provision, and other AI systems prescribed by royal decree. Risk-Based Classification Framework The draft act establishes a tiered risk classification system with three main categories: Prohibited AI. The act outright prohibits AI systems employing cognitive-behavioral manipulation using subliminal techniques, AI systems causing unfair broad-scale discrimination from processing irrelevant data, and other categories of serious risk as determined by announcement of a forthcoming committee that will be responsible
Read More
June 25, 2026
On June 18, 2026, Thailand’s Office of the Personal Data Protection Committee (PDPC) published two notifications in the Government Gazette establishing Thailand’s first formal certification framework for personal data protection standards under the Personal Data Protection Act B.E. 2562 (2019) (PDPA). The notifications, which took immediate effect, introduce a voluntary certification framework aimed at promoting accountability, strengthening organizational data protection governance, and aligning Thailand more closely with international frameworks that recognize certification as a key compliance tool. Certification Criteria The first notification sets out the assessment criteria for organizations seeking certification. Applicants must undergo an evaluation against a framework comprising four assessment categories, 10 focus areas, and 128 assessment criteria covering key elements of a privacy management program. These include: Organizational oversight and internal policies and procedures. Human resource development, including staff training and awareness programs. Clearly defined operational processes and procedures covering data subject rights, transparency obligations, records of processing activities, and lawful basis management, as well as contractual safeguards such as data-processing and data-sharing agreements and risk assessments, including Data Protection Impact Assessments. Technical measures encompassing data security controls and breach response capabilities Based on the assessment results, organizations may be awarded either a PDPA Compliance Certificate or a higher-level PDPA Certificate accompanied by a certification mark. Application and Assessment Process The second notification establishes the application and assessment process for obtaining certification. Eligible applicants include government agencies and private-sector entities that demonstrate sufficient privacy governance maturity and meet the prescribed eligibility requirements. Applicants must submit their applications along with supporting documentation for review. Upon receiving an application, the Office of the PDPC will conduct a detailed evaluation, which may include both documentary review and on-site inspections. Incomplete applications may be rejected, though applicants are typically given a limited period to correct deficiencies before a final decision
Read More
June 23, 2026
On May 26, 2026, Thailand’s Department of Land Transport (DLT) published for public consultation a draft amendment to the Ministerial Regulation on Electronic Ride-Hailing Vehicles that would, for the first time, allow juristic persons (legal entities) to register vehicles as electronic ride-hailing cars—a right that currently belongs exclusively to natural persons, limited to one person per one vehicle. If finalized in its current form, the regulation would significantly expand the supply side of Thailand’s ride-hailing market by enabling corporate fleet operators to enter the space. The public comment period is open through June 24, 2026. Key Principles Under the Draft Regulation Under the proposed amendment, juristic persons that maintain a fleet of at least 50 vehicles will be permitted to register vehicles as electronic ride-hailing cars. This represents a fundamental shift from the current framework, which restricts registration to individual natural persons on a one-person-one-car basis. Vehicle Specifications Corporate-owned ride-hailing vehicles must meet the following requirements: Be brand new from the factory, or no more than two years old from first registration with no more than 20,000 km of use. Not be a vehicle that has been reconstructed or repaired after involvement in a serious accident affecting safety—a standard consistent with public transport vehicles (RorYor. 6). Be classified as small, medium, or large in accordance with ministerial or director-general specifications. The vehicles may be equipped with safety devices such as interior or exterior cameras (video/photo recording) and can retain the original factory color of the vehicle body (no mandatory color change is required). License Plates Corporate ride-hailing vehicles will use license plates of the same size, characteristics, and color as those for private passenger vehicles not exceeding seven seats (RorYor. 1), rather than public transport plates. Potential Impact The government has stated that the regulation is intended to: Promote
Read More
June 23, 2026
On May 14, 2026, Thailand published a ministerial regulation in the Government Gazette to prescribe measures for prevention and suppression of technology crimes. The regulation creates a comprehensive procedural framework for returning money and digital assets to victims of technology crimes. It will take effect 90 days after publication (in mid-August 2026), giving affected entities a limited window to prepare. Mandatory Reporting Obligations for Financial Institutions When a deposit account, e-money account, or digital asset wallet is frozen in connection with a technology crime, the relevant financial institution or business operator must report transaction data to the Anti-Money Laundering Office (AMLO) via AMLO’s designated electronic system. Required data elements include account numbers (sender and receiver), names, identification or passport numbers, legal entity registration numbers, phone numbers, remaining balance, damage amount, transaction reference numbers, and the bank case ID. Institutions that already share data through the information-sharing system under the emergency decree are deemed to have satisfied this reporting obligation, creating an incentive for platform participation. When the Royal Thai Police or the Department of Special Investigation seize or freeze assets related to technology crimes, they must provide AMLO with investigation reports, complaint evidence, money-trail data, and account statements. Notification and Claims Process Once the AMLO secretary-general approves verified reports of a technology crime, the account information of persons connected to the crime will be published in the Government Gazette, triggering a 90-day window for victims to file claims and for related persons to file objections. Officers will also publish details on AMLO’s electronic media and send registered mail to identified victims, which will be deemed received after 7 days domestically or 15 days internationally. Victims have 90 days from the date the crime is published in the Government Gazette to file claims through AMLO’s electronic system. Claims must include
Read More