High Court · Decided 14 May 2019
I-Admin (Singapore) Pte Ltd v Hong Ying Ting and others and another suit
Feedback & support[2019] SGHC 127 · Case no. Suit No 585 of 2013
✱ What happened, in plain English
There is no plain-English summary of this judgment yet.
Ask about this judgment →Grounds of decision
Official text from eLitigation
Introduction
- [1]
[1] The plaintiff’s claims in Suit Nos 585 of 2013 and 965 of 2015 (respectively “Suit 585/2013” and “Suit 965/2015”, and collectively “the Suits”) were that three of the defendants in the Suits, being ex-employees of the plaintiff and its subsidiaries, conspired to infringe its copyright by taking and using its confidential information to set up a competitor firm in the business of payroll processing. The plaintiff’s claims were for copyright infringement, breach of confidence, breach of contract, conspiracy and inducing breach of contract.
- [2]
[2] For the reasons given in these grounds of decision, I dismissed the plaintiff’s claims in the Suits, save an award for nominal damages for breach of contract against Mr Hong Ying Ting (“Mr Hong”) in Suit 585/2013. The plaintiff has since appealed against my decision.
Facts
The parties
- [3]
[3] The plaintiff in the Suits is i-Admin (Singapore) Pte Ltd. It is a Singapore-incorporated company in the business of providing outsourcing services and systems software, primarily in the areas of payroll and human resource (“HR”) management. It began developing the “payAdmin” system comprising its core payroll engine from 2000 onwards.
- [4]
[4] The defendants in Suit 585/2013 are Mr Hong, an ex-employee of the plaintiff; Mr Liu Jia Wei (“Mr Liu”), an ex-employee of i-Admin (Shanghai) Ltd (“i-Admin (Shanghai)”), the plaintiff’s wholly owned Chinese subsidiary; Nice Payroll Pte Ltd (“Nice Payroll”), a Singapore-incorporated company in the business of providing payroll outsourcing services and HR management functions; and Mr Li Yong (“Mr Li”), a Chinese national and Singapore permanent resident who invested in Nice Payroll.
- [5]
[5] Mr Hong, Mr Liu and Mr Li are Nice Payroll’s directors. Unless otherwise specified, references to “the defendants” and their submissions should generally be taken to refer to the defendants in Suit 585/2013.
- [6]
[6] The defendant in Suit 965/2015 is Mr Tan Kim Liat Errol (“Mr Tan”). He was employed by the plaintiff from November 2002 to December 2006. He became acquainted with Mr Hong during this period. He was later employed by Olabo Pte Ltd (“Olabo”), one of the plaintiff’s subsidiary companies, from February to June 2011, and worked for Nice Payroll from June 2011 to October 2012.
Background to the dispute
Mr Hong, Mr Liu and Mr Tan’s employment from 2010 to 2011
- [7]
[7] Mr Hong, Mr Liu and Mr Tan were each employed by the plaintiff or its subsidiaries during the period from 2010 to 2011 in the following capacities.
- [8]
[8] Mr Hong was a general manager in the plaintiff’s systems department. By his account, Mr Liu was an operations manager in i-Admin (Shanghai)’s operations department from May 2009 to April 2010. He was moved to i-Admin (Shanghai)’s business development department from May to June 2010, and then to its implementation department from July to November 2010. He managed i-Admin (Shanghai)’s applications department from 1 December 2010 to April 2011.
- [9]
[9] Mr Tan began working for Olabo in 2011 upon Mr Hong’s recommendation, and worked on network and server maintenance.
The Kikocci Project and setting up Nice Payroll
- [10]
[10] In 2009, Mr Hong and Mr Liu shared their frustrations about the plaintiff’s payroll engine, which they both had experience using. They discussed creating a better payroll software and named their proposed project the “Kikocci Project”. During this period, Mr Liu began coding for the Kikocci Project using an online web-based application development tool, Oracle Application Express (“APEX”). The Kikocci Project was designed to be a portal that stored and displayed employee records in different APEX pages. In December 2009, Mr Hong and Mr Liu incorporated the Kikocci Corporation in the British Virgin Islands, and Mr Liu bought the domain name “www.kikocci.com”. Mr Hong and Mr Liu designed the Kikocci website as a mock-up of their intended payroll service. They continued to discuss the Kikocci Project over Skype on various occasions from 2010 to 2011. Mr Liu stopped coding on the Kikocci Project in November 2010.
- [11]
[11] It would appear that from August 2010 to March 2011, Mr Hong shared with Mr Li that he and Mr Liu were keen on starting a payroll business and were looking for an investor. Mr Hong suggested that Mr Li could invest in the Kikocci Corporation, but Mr Li preferred to invest in a new company instead. On 18 March 2011, Mr Li and Mr Hong incorporated Nice Payroll, with Mr Li as the only director and 100% shareholder. Mr Li invested $100,000 in paid-up capital and provided a loan of $900,000 pursuant to a Cooperation Agreement dated December 2011. Mr Hong and Mr Liu agreed to develop Nice Payroll’s business and its payroll software, and they would in return receive ⅓ ownership each by June 2013. Mr Hong and Mr Liu also agreed to close the Kikocci Corporation and its website. This Cooperation Agreement was based on verbal discussions from March 2011.
Resignations from the plaintiff and its subsidiaries
- [12]
[12] On 30 April 2011, Mr Liu resigned from i-Admin Shanghai. Mr Hong left the plaintiff’s employment on 30 June 2011. Mr Tan also left the plaintiff’s employment in June 2011. They began working for Nice Payroll thereafter. Ms Zaza Shen (“Ms Shen”), a software engineer employed by i-Admin (Shanghai), also resigned on 30 June 2011. She began working for Nice Payroll from 5 August 2011 onwards.
The plaintiff’s discovery of Nice Payroll and subsequent events
- [13]
[13] In 2013, the plaintiff came across Nice Payroll’s website while conducting market research. The plaintiff noted that Nice Payroll advertised itself as providing services and systems similar to the plaintiff’s, and that Mr Hong and Mr Liu were its directors. The plaintiff was suspicious of Nice Payroll’s activities and conducted forensic investigations into the defendants’ affairs.
The parties’ cases in Suit 585/2013
The plaintiff’s case
- [16]
[16] The plaintiff’s case was that Mr Hong and Mr Liu had, since 2009, schemed to set up a competing company. To this end, they set up the Kikocci Corporation and worked on the Kikocci Project during their working hours while still employed by the plaintiff, using the plaintiff’s resources. They eventually decided to incorporate Nice Payroll with Mr Li, and used the plaintiff’s copyrighted and/or confidential materials to develop Nice Payroll’s business and software codes. Five claims were made against the defendants.
- [17]
[17] First, Mr Hong and Mr Liu’s reproduction of the plaintiff’s copyrighted material amounted to copyright infringement. Nice Payroll’s products and/or services also infringed the plaintiff’s copyright.
- [18]
[18] Second, the defendants acted in breach of their duties of confidence to the plaintiff by reproducing its confidential material, by using its source codes and databases to generate Nice Payroll’s payroll reports, and by reporting data breaches to HSBC and ADP. Mr Hong also breached his duty of confidence by accessing the plaintiff’s demonstration platform without its authorisation.
- [19]
[19] Third, Mr Hong acted in breach of contract. He breached his non-disclosure agreement (“NDA”) by retaining the plaintiff’s confidential information and using it for Nice Payroll’s business purposes; breached its Information Technology (“IT”) security policy; and breached his implied duty of good faith by working on the Kikocci Corporation and/or Nice Payroll during the plaintiff’s working hours and by taking its confidential information.
- [20]
[20] Fourth, Mr Hong and Mr Liu engaged in the tort of conspiracy to set up a competitor firm in breach of the plaintiff’s confidence. Mr Li was involved in their conspiracy to infringe the plaintiff’s copyright and breach its confidence.
- [21]
[21] Fifth, Mr Li induced Mr Hong and Mr Liu to breach their respective NDAs with the plaintiff.
The defendants’ case
- [22]
[22] The defendants denied any infringement of copyright. Copyright did not subsist in the plaintiff’s software as it was insufficiently original, and the plaintiff did not own copyright in the Kikocci files. In any case, Nice Payroll’s software products and services did not constitute a substantial reproduction of the plaintiff’s software products, source codes and database structures: its software had been independently developed using programming language that differed from the plaintiff’s.
- [23]
[23] The breach of confidence claim was denied. The plaintiff was estopped from invoking its NDAs as it had not strictly enforced its security policies. The defendants had not used the plaintiff’s source codes, systems and databases to generate payroll reports. Mr Hong had not accessed the plaintiff’s demonstration platform to utilise its confidential information. Mr Hong and Mr Liu had not reported the plaintiff’s data breaches to interfere with its relations with HSBC and ADP. The breach of contract claim was denied on similar grounds.
- [24]
[24] No conspiracy existed: Mr Li was an angel investor who had been unaware of Mr Hong’s and Mr Liu’s previous employment. His lack of knowledge as to Nice Payroll’s possession of the plaintiff’s materials and the arrangements between Mr Hong and Mr Liu and their previous employers also meant that no inducement of breach of contract occurred.
The parties’ cases in Suit 965/2015
- [25]
[25] The plaintiff claimed that Mr Tan had reproduced and/or adapted the plaintiff’s copyright material in the development of Nice Payroll’s source codes, systems, materials and other documents and to generate payroll reports for Nice Payroll and its customers. This amounted to copyright infringement and breach of confidence. He conspired with Mr Hong and Mr Liu to commit these offending acts.
- [26]
[26] Mr Tan denied the claims against him as unsubstantiated by evidence. He had not accessed the plaintiff’s source codes for the purposes of copying, reproducing or adapting them. He had also not breached the plaintiff’s confidence: even if he was sent some of its materials as email attachments, it was not proved that he had actually referred to and used the plaintiff’s confidential materials when programming and preparing documents for Nice Payroll. Comparisons of the alleged source material with Nice Payroll’s materials would show that no reproduction or adaptation took place.
My decision
- [27]
[27] I was not satisfied that the plaintiff’s claims had been made out on the balance of probabilities. While there were perhaps strands of evidence that pointed to a suspicion of breaches by the defendants in the Suits, this was not enough to bring the plaintiff over the requisite evidential threshold. The strength of the inferences drawn from the evidence was not to the extent that it was more likely than not that the plaintiff’s assertions were true, as opposed to the alternative explanations proffered by the defendants.
- [28]
[28] Much of the parties’ cases turned on the strength of the respective sides’ expert evidence. To this end, concurrent evidence sessions were held for the software and forensic experts. The approach adopted here was as follows. The experts first summarised their positions in presentations. Based on these presentations, counsel identified issues that remained contentious, which set the parameters for the witness conferencing that followed. The contested issues were then raised in sequence. The plaintiff’s expert would raise matters directly to the defendants’ expert for his response or clarification; the plaintiff’s expert would afterwards be given time to make further responses. Finally, the defendants’ expert would raise any further points on that specific topic for the plaintiff’s expert to respond to. Given the technical nature of the canvassed matters, I was of the view that this format permitted the experts to raise matters directly to the court rather than through counsel, and allowed them to reach consensus where possible, or otherwise to identify more clearly the areas of contention between the parties.
- [29]
[29] In general, I preferred the defendants’ expert evidence in respect of the questions of both coding and forensics. I found the defendants’ experts’ opinions to generally be more cogent, in terms of their explanations and reasoning. I would emphasise, however, that I did not find that the plaintiff’s experts’ testimony was in any way partial or in breach of the obligation owed to the court, as the defendants contended in their submissions.
- [30]
[30] I also proceeded on the basis that as the factual bases and issues relating to liability in the plaintiff’s causes of action overlapped considerably, the resolution of issues in respect of one cause of action would have an impact on the remaining claims left to be decided. It bears noting that the plaintiff’s submissions departed at various points from its pleadings. Where this occurred to a great extent, I limited my consideration to its claims as pleaded.
- [31]
[31] I now turn to the specific issues raised.
Issue 1: Copyright infringement
- [32]
[32] I found that copyright generally subsisted in the plaintiff’s materials and that the plaintiff had ownership of the copyright. Any possible lack of distinction or quality was not sufficient here to deny that copyright subsisted in the claimed materials. However, I did not find that the plaintiff’s copyright was infringed. While the plaintiff showed that the defendants had access to its materials, there was no substantial copying of the plaintiff’s software and source codes in the generation of Nice Payroll’s various databases, templates, and other files and documents. While there may have been some similarity between the materials, it did not follow and was not proved that copying had occurred.
Preliminary matters
Categorisations and whether pleadings were properly made
- [33]
[33] The plaintiff set out a list of materials over which it claimed copyright. It submitted that its copyrighted material fell into five categories:
(a) source codes for its payroll software systems and human resource information system (“HRIS”) (“Category 1 materials”);
(b) databases and other materials constituting the technical infrastructure supporting its payroll software systems and HRIS (“Category 2 materials”);
(c) business development and client-related materials (“Category 3 materials”);
(d) materials related to its operations, eg, documents setting out internal guidelines and policies (“Category 4 materials”); and
(e) source codes developed as part of the Kikocci Project (“Category 5 materials”).
- [34]
[34] The defendants took objection to the plaintiff’s copyright claims over materials not covered by its pleadings. The plaintiff had claimed copyright to materials set out at Annex A of the amended statement of claim in Suit 585/2013 (“2ASOC”), and had listed materials that were allegedly infringing copies of its materials at Annex B of the 2ASOC. However, some of the materials in the plaintiff’s proposed categorisation were pleaded only in relation to the breach of confidence claim, and listed at Annex C of the 2ASOC (eg, the files “Payitem_Singapore.xls” and “LenovoSG.xls” in Category 2 and “HK Statutory_rev28Feb2011.doc” in Category 3).
- [35]
[35] I had some sympathy for the defendants on this point; the plaintiff’s pleadings could have been clearer as to which of the defendants’ materials allegedly infringed its copyright. However, the ultimate question at the end of the day was whether the plaintiff’s pleadings were sufficient: see Invenpro (M) Sdn Bhd v JCS Automation Pte Ltd and another [2014] 2 SLR 1045 (“Invenpro”) at [127]. This issue arose in Global Yellow Pages Ltd v Promedia Directories Pte Ltd and another matter [2017] 2 SLR 185 (“Global Yellow Pages”) at [54] to [56], where the Court of Appeal disagreed with the High Court that the statement of claim in question had been framed in sufficiently broad and general terms as to include a temporary database which had not been referenced in the initial pleadings. The Court of Appeal noted as follows:
- [36]
[36] The result in Global Yellow Pages turned on the use of the word “namely”, which suggested that the list of infringing materials contained in the statement of claim was exhaustive. The present case, however, differs. Given the interlinked nature of the causes of actions and looking at the pleadings as a whole, I found that the defendant was not prejudiced by any insufficient particularity in the pleadings. Critically, the plaintiff’s case in relation to breach of confidence asserted that the defendants had reproduced and copied its confidential information and materials as listed at Annex C. The agreed list of issues in Suit 585/2013 between the parties also included the question of whether copyright subsisted in the materials listed at Annexes A to C of the 2ASOC. I thus considered the merits of the plaintiff’s copyright claim in relation to the Annex C materials as well, as raised in its submissions.
Basic terminology: Database architecture, tables and components
- [37]
[37] For clarity, I set out some definitions of terms that will be used. Other terms will be defined in my grounds of decision where necessary.
- [38]
[38] The current case concerns payroll software used to record employee information, compute and record payroll items, and generate payrolls. These payrolls contain payitems, which are payment components in payslips, eg, salary amounts, Central Provident Fund (“CPF”) contributions and bonuses.
- [39]
[39] Associate Professor Roland Yap (“Prof Yap”), the defendants’ coding expert, helpfully defined elements of software programs. I reproduce his definitions here. Software, which is developed as source code, is written in programming languages. These vary in syntax, expressive power and areas of application. The present case concerned two programming languages: Java, a general purpose programming language, and Structured Query Language (“SQL”), a more domain-specific programming language whose purpose is to query and manipulate databases. An SQL “query” causes a database to give a result without changing the database itself. Prof Yap explained that software which deals with large amounts of data may choose to utilise a database. To expand:
(a) Many types of databases exist. In this context, a “database” refers to a relational database that organises, processes and stores data as relations. Databases do not appear visually as tables or spreadsheets; they are logical constructions which the database software presents to the programmer.
(b) The plaintiff’s and Nice Payroll’s systems used the Oracle database, a relational database management system. The Oracle database uses PL/SQL, a proprietary programming language extension to SQL.
(c) A database is made up of one or more schemas, which comprise the database’s architecture. Each schema contains one or more “database tables”, which organise data into columns and rows. Each column, or “field”, stores data of a certain logical type, eg, “birthday” fields store data having a “date” type. Data is stored as rows in the tables.
(d) A schema does not define the data contained in the tables. In Oracle, the schema defines the structural relationships in the database by specifying the tables and fields, and the relationships between the data in rows of a table, etc. The schema may also define one or more columns to be “primary keys”. The values in the primary key should be unique within the table, giving rise to a “uniqueness constraint”, such that rows with duplicate keys cannot be inserted in the same table.
- [40]
[40] The following table illustrates how the above terms are used:
The applicable law
- [41]
[41] The defendants disputed the subsistence of copyright in the plaintiff’s materials, the plaintiff’s ownership of this copyright and whether such copyright was infringed. I briefly set out the applicable law in relation to these issues.
- [42]
[42] To succeed in a claim for copyright infringement, a plaintiff must prove that copying has taken place, which can come in the form of establishing similarity combined with proof of access to the plaintiff’s works: Flamelite (S) Pte Ltd and others v Lam Heng Chung and others [2001] 3 SLR(R) 610 at [27]; Invenpro at [202].
- [43]
[43] Copyright subsists in original literary works: s 27 of the Copyright Act (Cap 63, 2006 Rev Ed) (“Copyright Act”). Literary works include compilations in any form and computer programs: s 7A(1) of the Copyright Act. In the context of compilations, the compiler must exercise sufficient creativity in selecting or arranging the material within the compilation. The resulting copyright only protects the original expression in the form of the selection or arrangement of the material. Ultimately, the court is guided by the fundamental principle that copyright law protects not ideas, facts or data, but the expression thereof: Global Yellow Pages at [24] and [30].
- [44]
[44] For copyright to subsist in any literary work, there must be an authorial creation that is causally connected with the engagement of the human intellect: Global Yellow Pages at [24]. The concept of authorship is integral to copyright, and a human author must first be identified before the work in question can be deemed to be original: see Asia Pacific Publishing Pte Ltd v Pioneers & Leaders (Publishers) Pte Ltd [2011] 4 SLR 381 (“Asia Pacific Publishing”) at [94]. It is not necessary to name each and every author to make out a claim, but it must be shown that the product was generated from a human author or human authors working alone or collaboratively, ie, the existence of such persons must be clearly established: Asia Pacific Publishing at [75]. A body corporate may not be considered the author of an original work, but may be the copyright owner by virtue of the operation of a contract of employment or an assignment: see s 194 of the Copyright Act and Asia Pacific Publishing at [56].
- [45]
[45] Having established that copyright subsists in an original work and that a plaintiff owns such copyright and has locus standi to bring a claim, the court considers whether copyright has prima facie been infringed. Copyright is only infringed if there has been a copying of a substantial part of the protected works. Substantiality depends on the quality, not quantity, of the material copied; the defendant must have copied or taken the parts of the work that contributed towards the finding of originality: Global Yellow Pages Ltd v Promedia Directories Pte Ltd [2016] 2 SLR 165 at [239]. A causal connection between the plaintiff’s copyrighted work and the defendant’s infringing work must also be shown: Asia Pacific Publishing at [108]; Invenpro at [213].
Category 1 materials: Source codes
Whether copyright subsisted in the materials
- [46]
[46] The defendants submitted that the plaintiff’s software was not original. There was no evidence of the creation and intellectual effort expended on the source codes, or of the plaintiff’s creative process. Prof Yap’s unrebutted evidence also showed that the plaintiff’s software lacked originality in respect of its source codes. Payroll tasks are conceptually straightforward, involving (a) storing and retrieving HR information, which can be carried out through a database; (b) computing payroll items, which is governed by the definition of the particular payitem (eg, the amount of CPF due, which is defined by the CPF Board rules); and (c) generating reports or bank statements, which is straightforward.
- [47]
[47] The plaintiff responded that the defendants’ denial of the subsistence of copyright had not been properly pleaded. Regardless, affidavit evidence attested to the efforts of the plaintiff’s employees in developing its software. Its software was sufficiently original: while its functions might be predefined, copyright subsisted in the expression of the codes and databases to achieve those functions. Intellectual effort would also have been required to ensure that the source code and databases properly operated, and to determine how the input data was to be expressed, presented and collated.
- [48]
[48] I observed that the plaintiff did not identify specific authors of the materials. To this end, I considered Asia Pacific Publishing, where a body corporate asserted authorship over horse-racing information organised in various tables. The respondent could only identify its employees as having gathered and organised the information and data in the tables (at [77]); the Court of Appeal found that such facilitative work did not amount to authorship: at [78]. As the collection, organisation and selection of data were done by separate people, each individual employee’s contribution (which had not been particularised) was insufficient to render them an author or joint authors of the tables: at [79]. The Court of Appeal also considered that the respondents might have been unable to identify authors as a high degree of automation might have been involved in compiling the tables: at [81]. In the circumstances, without the identification of a human author, there could be no “original work” capable of copyright protection, and the respondent’s claim that copyright subsisted in the tables that were “authored” by it failed: at [82].
- [49]
[49] This, however, was not a case where it was seriously disputed that some human intellectual input resulted in the creation of the Category 1 materials. Indeed, there was no suggestion that the materials came from anywhere else. The evidence before me was sufficient for me to draw the conclusion that they were authored by the plaintiff’s employees.
- [50]
[50] As regards the originality of the plaintiff’s software, I did not find Prof Yap’s evidence to be relevant: the expert witnesses had been brought in to consider the question of copyright infringement, and not the issue of originality. I ultimately considered copyright to subsist in the plaintiff’s software, which was a computer program under s 7A(1)(b) of the Copyright Act. The criteria for originality within the meaning of ss 7A and 27 of the Copyright Act requires merely that the work was independently created by the author and that it possesses some minimal degree of creativity: see Global Yellow Pages at [15]. The plaintiff’s independent work in creating the source codes exceeded this low threshold.
Whether the plaintiff owned the copyright
- [51]
[51] The defendant contended that no evidence was led as to who the authors of the plaintiff’s software were, and that no development documents were produced by the plaintiff. This was not fatal to the plaintiff’s claim, and I was satisfied that the plaintiff owned any copyright subsisting in its software by virtue of the assignment clauses in its employees’ contracts of employment. I accepted that copyright was assigned to the plaintiff by operation of cl 3.1 of the plaintiff’s standard form employment contracts and cl 4.1(a) of its Employee IT Security Policy 2007 (the “2007 IT Policy”). Copyright owned by i-Admin (Shanghai) was also assigned to the plaintiff through a deed of assignment.
Whether the plaintiff’s copyright was prima facie infringed
- [52]
[52] Although the plaintiff claimed that its copyright in specific source codes and software materials (eg, the files “BankDiskOCBCSGONI.java” and “BankDiskSGP7144.java”) was infringed, it only submitted that two main aspects of its software were substantially reproduced as part of Nice Payroll’s software: its database structures and result upload functionality. Mr Harish Pillay (“Mr Pillay”), the plaintiff’s coding expert, did not opine on the other files listed. I therefore did not consider these files as part of the copyright claim. Claims that the plaintiff’s materials were “utilised” to develop Nice Payroll’s software will instead be considered as part of the plaintiff’s breach of confidence claim.
- [53]
[53] I first explain the software aspects which the plaintiff sought to compare. The database structures referred to different database tables which were structured to serve given purposes, eg, to calculate Hong Kong tax declarations (the plaintiff’s “TAX_VTA_RRP”) and to collect calculated results from the payroll engine (the plaintiff’s “PR_PAYROLL_RESULT”). Both software’s “result upload functionality” referred to the use of Java codes whose function was to upload payroll results in Microsoft Excel spreadsheets into the respective payroll databases, bypassing the payroll engine in the process.
(1) Database structures and software elements
- [55]
[55] The defendants disputed Mr Pillay’s methodology on two grounds. First, the database structures could not be compared in isolation from the overall database architecture and design of the source code. Second, the plaintiff’s expert had selectively compared only four of the plaintiff’s 32 database tables, and had compared only the column names in the database tables. These were insufficient bases to conclude that there were substantial similarities between the selected tables, let alone Nice Payroll’s entire database.
- [56]
[56] I found the defendants’ submissions compelling. I understood from the expert evidence that the database tables were but a component of the overall database architecture. While the tables contained data, their contents were only given meaning when they were “called upon” or referred to by the source code. In this sense, the meaning to be ascribed to the data would be encoded in the source code; the “logic” of the software was found in the source code. I agreed with the defendants that it was thus necessary to consider the overall architecture and design of its software to determine whether the plaintiff’s copyright in its software had been infringed. This would entail a consideration of the programming language used and the logic of the source code, as well as the database components which the source code drew upon. It was not sufficient to focus on the contents of the database tables alone.
- [57]
[57] To this end, Dr Yap explained the plaintiff’s software architecture to be a three-tier application architecture: (a) the software was presented on webpages using JavaServer Pages on the “presentation tier”; (b) the main application logic was written in Java on the “logic tier”; and (c) the logic tier interfaced with the “data tier” (the Oracle database) using SQL. In comparison, Nice Payroll’s software architecture was written in APEX, an application development tool that ran within the Oracle database. Nice Payroll’s data, application logic and user interface were stored in and on the Oracle database. Nice Payroll’s application development required the application logic (code) to be written in PL/SQL. This was not disputed by Mr Pillay, who explained that the two software environments had been built upon inherently different programming languages, such that it was of “no good value” comparing the two. Instead, he compared “what was left”, ie, the database tables which the code relied upon, and the output of the payroll systems: the payroll report itself.
(a) The plaintiff’s source code was larger than Nice Payroll’s. Much of Nice Payroll’s PL/SQL code was automatically generated by the APEX application builder used by its human programmers, which meant that the actual code written by its programmers was even smaller. A great deal of effort would have been required to reproduce the plaintiff’s code by translating it into a different language and then shrinking it.
(b) The plaintiff made extensive use of Java’s language features, Java being a much more powerful programming language than PL/SQL. The difference in programming languages meant that the plaintiff’s program could not be meaningfully compared to Nice Payroll’s.
(c) The plaintiff isolated its database by client. This allowed it to engage in specific database customisation. Its SQL queries were embedded into its Java code and called upon multiple database tables. In comparison, Nice Payroll’s client data was stored in a single database and its PL/SQL code was integrated with its SQL queries and called on a single database schema.
(d) The core functionality in the two payroll systems differed. For instance, the payroll calculation algorithms differed: the plaintiff’s Java code computed payrolls at the individual payroll item level, sequentially processing each employee’s payroll; Nice Payroll’s algorithm computed payrolls at the employee level, computing payroll items per employee. As the inner and outer loops for calculation were completely different, the plaintiff’s code would have required complete rewriting to be converted into Nice Payroll’s.
In addition, the database architectures of the two systems differed: the plaintiff’s software included more schemas and tables, the contents of the database tables were organised differently, and different primary keys were used. Prof Yap additionally disagreed with Mr Pillay’s focus on the software output, as different software could produce similar or identical payroll reports.
- [59]
[59] For the plaintiff’s claim in respect of the software to succeed, it had to prove that the defendants copied a substantial part of the work that contributed towards the finding of originality. As I noted above at [50], what distinguished the plaintiff’s software was its organisation of its database architecture and its development of its source codes. The defendants’ expert evidence demonstrated on the balance of probabilities that Nice Payroll’s software was so fundamentally different that it could not have been copied from the plaintiff’s. To the extent that some similarities existed across the two systems, I accepted the defendants’ position that any similarities in Nice Payroll’s software and payroll output could be attributed to the functional and statutory requirements that informed what payroll reports should generally contain. I will comment on the payitem and CPF database tables in more detail below.
(2) Result upload functionality
- [60]
[60] Mr Pillay gave evidence that it was unusual that Nice Payroll’s and the plaintiff’s result upload coding did not read data from the “Employee Name” field. The defendants responded that Mr Pillay should have compared the source codes before reaching a conclusion. They explained that Nice Payroll’s code read from the “Employee ID” field to minimise human error, and that the “Employee Name” field was retained to assist persons reading and uploading spreadsheets into the database. From a computer science viewpoint, the two codes were different as they were based on different algorithms involving different error handling and processing logic.
- [61]
[61] I accepted the defendants’ argument that the mere fact that both source codes did not read data from the “Employee Name” field did not constitute the copying of a substantial part of the plaintiff’s work. This quality alone did not render the plaintiff’s source code original, especially given that the other aspects of the codes were different. The copyright infringement claim in respect of this specific functionality therefore did not succeed.
Category 2 materials: Databases and technical infrastructure
- [62]
[62] The plaintiff classified its Category 2 materials to comprise:
(a) its payitem databases, comprised in the Microsoft Excel (“Excel”) files “payitem setup_iAdmin.xls”, “Payitem_Singapore.xls” and “LenovoSG.xls”; and
(b) its CPF database, which was “comprised in a form … substantially similar to the document ‘cpf.xls’”.
- [63]
[63] The parties understood the plaintiff’s case to be that:
(a) The files “Payitem_Singapore.xls” and “LenovoSG.xls” (“the plaintiff’s Payitem Bibles”) were created by the plaintiff and generated from its database tables. They were circulated between the defendants and used to create the file “payitem_bible.xls” which was integrated into Nice Payroll’s payitem database table “PR_PAYITEM”.
(b) The plaintiff’s database table “PAY_CPF_RULE”, which sets out the CPF Board calculation rules, was used to generate the file “cpf.xls”. The defendants used this file to generate their own CPF database table “PR_CPF_RATES_SGP”.
- [65]
[65] I also noted that the plaintiff’s use of technical language was not as precise as it could have been. I agreed with the defendants that the Excel files were not technically “databases and other infrastructure materials” (the plaintiff’s description of the Category 2 materials), as it was not shown that the files were part of the plaintiff’s source code or database architecture. Rather, they were compilations of data or representations of the data in the database tables within the software, and I will refer to them as such.
Whether copyright subsisted in the materials
- [66]
[66] I took the plaintiff’s copyright claim to concern its database tables, and not the Excel files per se. It was thus not strictly necessary for me to consider the latter. However, given that the plaintiff alleged the defendants to have used the Excel files to develop Nice Payroll’s infringing databases, I shall address them as well.
- [67]
[67] I accepted the plaintiff’s position that the Excel files were generated from its database tables. The defendants did not dispute that the Payitem Bibles were the plaintiff’s, but contended that the “cpf.xls” file had not been generated from the plaintiff’s CPF database table. Mr Liu had sent “cpf.xls” to Mr Tan in an email on 29 September 2011, such that it was later found in the defendants’ possession. Although Mr Liu claimed in his affidavit of evidence-in-chief (“AEIC”) that he did not recall how he had obtained a copy of the file, he subsequently admitted under cross-examination that he had generated the file from i-Admin (Shanghai)’s system during his previous employment with it, but claimed that the file had only included headers with no data when he created it:
Mr Liu further claimed that he only populated the file with data subsequently.
- [68]
[68] On the plaintiff’s end, Mr Pillay’s evidence was that the file “cpf.xls” and the Excel file which the plaintiff generated from its CPF database table for the purposes of comparison (ie, the file “pay_cpf_rule.xls”) were more than 90% identical. The defendants focused on the dissimilar data entries in these two Excel files to submit that “cpf.xls” could not have been generated from the plaintiff’s database. I found on the balance of probabilities that while the file “cpf.xls” had been generated from the plaintiff’s database table, the evidence only went so far as to establish that the generated file included headers and not data at the time of its creation.
- [69]
[69] I next considered whether copyright subsisted in the plaintiff’s databases and the Excel files generated from them. I agreed with the defendants’ characterisation of the plaintiff’s Payitem Bibles. They were compilations of information on items calculated in the payroll process: inter alia, the worksheets in the Excel files listed descriptions of payitems and their natures. The data in “cpf.xls” set out CPF calculation rule data and CPF contribution rates for different income and age ranges as of September 2011.
- [70]
[70] The defendants submitted that copyright did not subsist in the plaintiff’s Payitem Bibles. First, there was no information about the time, effort and skill taken to compile the payitem information in the Payitem Bibles. Second, there was no originality in listing the payitems and their natures, which were dictated by statutory regulations and client instructions. Third, payroll systems are expected to store relevant payroll information, eg, information pertaining to the company and personal details of employees. The content and arrangement of the plaintiff’s database tables were typical of payroll systems generally and thus unoriginal in that respect. Payroll processing is also constrained by mandatory statutory requirements, eg, the CPF Board rules. Similarly, the plaintiff’s CPF database structure did not attract copyright protection as it was a transliteration of the data in the CPF Board rules, which were widely available on the Internet. Excel files derived from the database tables would also not attract copyright.
- [71]
[71] I did not agree with the defendants. I preferred the plaintiff’s position that even if payitem and CPF information was publicly available, intellectual effort, analysis, industry knowledge, and knowledge of regulatory rules, HR policies and employment best practices were still required to organise the information into a format that was suitable for processing by a computer program. I was satisfied that the organisation of the relevant information into columns and rows in a database table involved a minimal degree of creativity, and that the database tables therefore constituted compilations of facts under s 7A(1)(a) of the Copyright Act that were original and attracted copyright protection: Global Yellow Pages at [15]. I also found that such copyright protection extended to any Excel files generated from the database tables. To the extent the information was publicly available, this only affected whether the resultant copyright protection was “thin”’, as copyright protection would not extend to the data contained in the tables and Excel files. I will return to this below.
Whether the plaintiff owned the copyright
- [72]
[72] As with the plaintiff’s software, it was not crucial for the plaintiff to prove which human authors created the database tables in question. I found that the plaintiff’s employees had created the database tables and that it owned the copyright subsisting in these works by operation of the assignment clauses in the relevant employment contracts.
Whether the plaintiff’s copyright was prima facie infringed
- [73]
[73] The plaintiff claimed that the defendants had utilised its payitem and CPF databases to create Nice Payroll’s databases and other materials. I was persuaded by the defendants’ arguments that there was no substantial copying of the database tables, given the structural differences between the plaintiff’s and Nice Payroll’s payitem and CPF database tables.
(1) Payitem database tables
- [75]
[75] In response, the defendants first submitted that the plaintiff had conflated two files: “Payitem Bible_Singapore.xls” and “payitem_bible.xls”. They implicitly accepted that the first Excel file had been adapted from the plaintiff’s Payitem Bibles. However, as “Payitem Bible_Singapore.xls” was not part of the source codes, the defendants rejected Mr Pillay’s evidence as given outside his field of expertise: being a coding expert, it was impermissible for him to comment on the similarities of the plaintiff’s Payitem Bibles and the file “Payitem Bible_Singapore.xls”. In any case, the defendants denied the claim of copyright infringement. Any similarities between these files were limited to the copied facts, and not the arrangement of those facts; there was hence no copyright infringement.
- [76]
[76] I agreed with the defendants in this regard. As I alluded to above at [71], the copyright protection extended to compilations of facts does not extend also to the facts and data contained therein. It was clear that there was no reproduction of the plaintiff’s arrangement of the contents per se; otherwise, the plaintiff would have compared the database tables or the Excel files directly, without having to rely on document comparisons showing the “evolution” of the plaintiff’s Payitem Bibles into the file “Payitem Bible_Singapore.xls”. This indicated to me that the final product in the form of “Payitem Bible_Singapore.xls” was sufficiently distinct from the plaintiff’s Payitem Bibles such that no copying could be said to have taken place.
- [77]
[77] As for the file “payitem_bible.xls”, the defendants submitted that this was an Excel file generated from Nice Payroll’s database table “PR_PAYITEM”, and therefore a representation of “PR_PAYITEM”. An assessment of its similarity to the plaintiff’s payitem database tables required consideration of the development and design of the respective source codes; Mr Pillay’s focus on whether “PR_PAYITEM” was referred to in Nice Payroll’s source codes was irrelevant since the source codes would necessarily draw on the data contained in the database tables to operate and produce output.
- [78]
[78] To this end, Prof Yap compared the plaintiff’s and Nice Payroll’s source codes, how they interacted with the payitem database tables, and the schemas of the database tables. He concluded that Nice Payroll’s code differed from the plaintiff’s in that it did not include the non-statutory “hard-coded” payitems found in the plaintiff’s code. He explained that most payitems are generic and simply serve as data to be drawn upon by the code; they are added or deducted from an employee’s payroll computation. However, certain payitems may be hard-coded if they require specific computation: code may be written to cater for a particular statutory computation. The plaintiff’s codes referred to at least 21 statutory and two non-statutory hard-coded payitems; Nice Payroll’s only included 12 statutory hard-coded payitems. Furthermore, the defendants’ payitem bible used a naming convention that contained more information that the plaintiff’s. The defendants concluded that as the source code’s logic differed such that the parties’ database tables were used differently in their respective software, no copying had occurred. Any similarities that Nice Payroll’s payitem database table had to the plaintiff’s Payitem Bibles were explained by the fact that the data contained therein reflected what was found in the relevant statutory rules.
- [79]
[79] I agreed with the defendants’ conclusion in relation to this matter as well. The question of whether substantial copying has occurred must consider what makes the copyrighted material original. I mentioned at [71] that the plaintiff’s database tables were original by dint of the creative effort invested to organise the relevant information into a format suitable for computer processing. It was therefore relevant to consider whether the defendants’ organisation of the database tables – both within the database schema and vis-à-vis the source code – was a reproduction of the plaintiff’s. I found Mr Pillay’s assessment of the defendants’ emails to be irrelevant to this analysis, and preferred Prof Yap’s evidence instead. It was on the basis of the latter that I was satisfied that differences in the naming conventions and the number and type of hard-coded payitems sufficiently distinguished Nice Payroll’s payitem database table from the plaintiff’s, and that no copying could be said to have occurred.
(2) CPF database tables
- [80]
[80] Parties took similar positions as regards the CPF database tables. As the plaintiff submitted, this aspect of its claim did not concern the parties’ respective source codes per se. Mr Pillay compared the cells and fields of the parties’ respective database tables to conclude that Nice Payroll’s CPF database had been “lifted or evolved” from the plaintiff’s. Conversely, the defendants identified differences between the tables: Nice Payroll’s CPF database table was a more compact reformulation of the CPF Board rules, and had 17 columns to the plaintiff’s 24. Nice Payroll’s CPF calculation rules also involved algebraically equivalent but different arithmetic computations that optimised the CPF Board rules, resulting in more streamlined and simpler formulae.
- [81]
[81] As above, I preferred the defendants’ more holistic approach towards the comparison of the database tables. I accepted that some similarities between the tables were a given, as both were limited by requirements in the CPF Board rules. But on the whole, there was clear evidence that Nice Payroll’s CPF database table was organised differently from the plaintiff’s. No copying had therefore occurred.
Category 3 materials: Business development and client-related materials
- [82]
[82] I only considered the materials that the plaintiff made submissions on:
(a) the file “Copy of ePayroll eHR pricing for all regions(04 Jan 2011).xls”, which contained the plaintiff’s pricing information and business strategy material, stating fees offered for services rendered;
(b) the compressed folder “RR to Li Lian.zip”, which contained documents relating to the plaintiff’s operations, including its software and hardware technical platform, data security and security design architecture; and
(c) the compressed folder “Standard Imp Template.zip”, containing the plaintiff’s implementation templates for six jurisdictions. It included the file “SG Client_Imp Template.xls”, which the plaintiff’s Singapore clients would input their data into for the plaintiff to process.
Whether copyright subsisted in the materials
- [83]
[83] The plaintiff submitted that copyright subsisted in these materials which had been created through a process of development of the plaintiff’s systems, pricing and business strategy.
- [84]
[84] The defendants argued that the Category 3 materials were not original as no evidence had been led on why they were protected by copyright. In particular, the implementation templates were used for the purely functional purpose of collecting client data, and thus required no creative input to create. I disagreed. Regardless of the purpose for which these materials had been created, the plaintiff had utilised business skill to arrange the templates in a manner that was thought to be most conducive to its clients’ data input. They had a “quality of character not possessed by the raw material”: Asia Pacific Publishing at [103] and [105], citing Fortuity Pty Ltd v Barcza (1995) 32 IPR 517. The Category 3 materials were therefore protected by copyright.
Whether the plaintiff owned the copyright
- [85]
[85] The defendants contended that the plaintiff had not led sufficient evidence as to the creation of the templates. I followed the approach I adopted towards the materials in Categories 1 and 2, and found that the plaintiff owned the copyright subsisting in the material.
Whether the plaintiff’s copyright was prima facie infringed
- [86]
[86] The plaintiff submitted that the defendants had utilised its business development materials to develop Nice Payroll’s business development materials. The defendants responded that the plaintiff had not compared the allegedly infringing materials in question; indeed, Ms Fan Wenli, who managed the plaintiff’s database, agreed in cross-examination that the defendants’ and plaintiff’s implementation templates were dissimilar. I also noted that the plaintiff did not identify infringing materials belonging to the defendants that were alleged to have been copied from its copyrighted Category 3 materials. I therefore dismissed the copyright claim in relation to the Category 3 materials.
Category 4 materials: Operational materials
- [87]
[87] The defendants contended that the plaintiff failed to identify any materials that fell within Category 4. I noted that the plaintiff did identify these materials in appendices to its submissions, but did not make substantive submissions in relation to them. Accordingly, no decision could be reached on whether copyright was infringed in relation to these materials.
Category 5 materials: Source codes for the Kikocci Project
- [88]
[88] It was not disputed that copyright subsisted in the Category 5 materials, ie, the source codes for the Kikocci software (“the Kikocci files”) which were created by Mr Liu during his employment with i-Admin (Shanghai). Rather, parties were concerned with the ownership of said copyright.
- [89]
[89] Both sides called foreign law experts to give evidence on People’s Republic of China (“PRC”) law relating to copyright in software. Ms Zhou Yan (“Ms Zhou”) and Ms He Wei (“Ms He”) were called for the plaintiff and defendants respectively.
The relevant PRC legal materials relating to copyright ownership
- [91]
[91] I considered that Art 1 of both Regulations, which Ms He drew attention to, specified that the Regulations were “formulated in accordance with the Copyright Law”. As Ms He explained, the Regulations are administrative regulations formulated by the State Council, an administrative body, and are subject to the Copyright Law, which is enacted by PRC legislative bodies. Ms He did note that the Computer Software Regulations were specific laws that took “precedence” over the general Copyright Law, but I agreed with the defendants that they still had to be read in conjunction with the Copyright Law and the Copyright Law Implementation Regulations, and considered them together.
- [92]
[92] The relevant sections of Art 16 of the Copyright Law state:
Ms He’s expert opinion cited Art 11 of the Copyright Law Implementation Regulations as defining two terms used in Art 16 of the Copyright Law:
- [93]
[93] Article 13 of the Computer Software Regulations states:
Both experts agreed that copyright ownership by the plaintiff only required one of the three circumstances under Art 13 to be fulfilled.
Application to the present facts
- [94]
[94] Assessing the evidence as a whole, I agreed with the defendants that the circumstances under Art 13 of the Computer Software Regulations read with Art 16 of the Copyright Law had not been fulfilled.
- [95]
[95] I first considered whether either Arts 13(1) or 13(2) had been fulfilled. The plaintiff submitted that it sufficed that Mr Liu had performed work on the Kikocci files from late 2009 to 30 April 2011, while employed by i-Admin (Shanghai). During this period, he was obliged under the terms of his employment to perform i-Admin (Shanghai)’s work.
- [96]
[96] Conversely, the defendants looked into the capacity that Mr Liu had been employed in when he coded the Kikocci files. Although Ms Zhou’s expert opinion had not considered this aspect of the evidence, I found that consideration of this factor was required by the wording in Arts 13(1) and 13(2), which focus on whether a work has been developed in “the line of [an employee’s] service duty”. This was also supported by the Second-Instance Written Civil Judgment of Dispute Over Ownership of Copyright Among Shanghai Enfang Information Technology Co., Ltd., Wang Siping and Taizhou Juyi Information Technology Co., Ltd. (2013) Zhe Tai Zhi Zhong No 1, a judgment by Taizhou City’s Intermediate People’s Court. The Intermediate People’s Court upheld the finding at first instance that the appellant company could not claim ownership over software developed by the respondent as there was inadequate evidence that there was a request or assignment for the respondent to develop the software in question. Although Chinese judgments are not binding on other courts, I accepted Ms He’s evidence that they still serve as references.
- [97]
[97] It was in this vein that the defendants submitted that Arts 13(1) and 13(2) of the Computer Software Regulations had not been fulfilled. I agreed. Mr Liu developed the Kikocci files in April or May 2010 when he was not employed in a software development capacity. Indeed, i-Admin (Shanghai) had been unware of the Kikocci files until 2013, after Mr Liu left its employment. I also considered that the “last written dates” of the recovered Kikocci files dated from June to November 2010, predating Mr Liu’s move to i-Admin (Shanghai)’s applications department in December 2010, when he recommenced programming work at i-Admin (Shanghai). These factors together showed that the development of the Kikocci files were neither an “explicitly designated” development objective in the line of Mr Liu’s service duty nor a “foreseeable or natural result of his work activities in the line of his service duty”. I thus found that Arts 13(1) and 13(2) of the Computer Software Regulations had not been fulfilled.
- [98]
[98] Turning to Art 13(3) of the Computer Software Regulations, the plaintiff submitted that Mr Liu had created the Kikocci files using its material and technical resources. He had access to the plaintiff’s payroll source codes, databases, business information and client data, and utilised its hardware, software and other resources when developing the files. He used its computers to create the source code and used its servers and networks to communicate with Mr Hong about the Kikocci Project, and did both during office hours.
- [99]
[99] The defendants contended that the plaintiff failed to show that Mr Liu had used the plaintiff’s “special and dedicated [programming] tools” to develop the Kikocci files. They relied on another Chinese judgment in support of their arguments: the Second-Instance Written Civil Judgment of Dispute Over Infringement of the Right of Publication Between Zhanyu Enterprise Development (Shanghai) Co., Ltd. and Li Xiaochu (2017) Hu 73 Min Zhong No 3 (“Zhanyu Enterprise”).
- [100]
[100] This decision did not apply the Computer Software Regulations, but considered whether para 2 of Art 16 of the Copyright Law entitled the appellant company to claim ownership of copyright subsisting in three posters. The first instance court held that the appellant company’s computer, hard disk and office hours were not “specially provided” for the respondent to create the copyrighted works for the appellant company. The Shanghai Intellectual Property Court upheld this decision on appeal. It held that “material and technical resources” within the meaning of Art 16 referred to the “legal entity or other organisation specially [providing] funds, equipment or information and materials for the citizen to complete the creation(s)”. The created works had not required “special and specialised equipment … for their specific expressions”. The materials allegedly provided by the appellant, ie, funds, the computer, hard disk and office hours, were for “general use” and “[did] not possess the indispensability and specificity of the works created”. Paragraph 2 of Article 16 was therefore not fulfilled.
- [101]
[101] Applying Zhanyu Enterprise to the present facts, the defendants argued that the plaintiff’s “material and technical resources” had not been used in the creation of the Kikocci files. Even if the files had been programmed on i-Admin (Shanghai)’s laptop, the software used was not a “special-use” equipment that fell within Art 13(3). Authorship and ownership of the copyright files therefore lay with Mr Liu.
- [102]
[102] There was some dispute between the forensic experts regarding the extent to which Mr Liu had coded the Kikocci files during office hours. Both experts raised concerns about using the metadata timings of the “f109.sql” application files relating to the Kikocci Project as a proxy to measure the amount of time that Mr Liu spent on the Kikocci files.
(a) The plaintiff’s expert concluded that 40% of the Kikocci files were written during office hours by relying on “last saved” timings in the “f109.sql” files that recorded user activity and when particular functions and modules in a file were written and last saved. The defendants’ expert criticised the use of these timings as creating inconsistency: the “last saved” timings only showed that changes happened within a particular file, and did not reflect whether these changes were substantive: for instance, merely navigating back and forth within a file would cause the “last saved” timing to be updated.
(b) Instead, the defendants’ expert relied on the “last written” and export timings of the files to conclude that 19–22% of the Kikocci files were created during working hours. “Last written” timings show the last time changes were made to the overall file, and export timings are generated when a user saves and exports his work. These timings would reflect when a person makes “essential” changes to the files. The plaintiff’s expert’s response was that these timings were biased towards showing that Mr Liu only worked on the file outside of his working hours: the “last written” timing only shows when a back-up file is created, and cannot indicate when the codes contained therein were last written or worked on. Mr Liu could have worked on the Kikocci files during office hours, saving and exporting them after he ended work.
- [103]
[103] In my view, both experts raised valid concerns about using these timings to measure the time Mr Liu spent working on the Kikocci files while at work. But what seemed more methodologically concerning was the fact that the forensic experts were only able to analyse the deleted Kikocci files that were successfully recovered. As the plaintiff’s forensic expert observed, there may well have been more files that had been deleted and which could not be recovered. As the existing evidence could only portray an incomplete picture, it was unsafe to draw any conclusions regarding the extent to which Mr Liu had worked on the files during office hours. I therefore did not place much weight on this aspect of the parties’ cases.
- [104]
[104] Instead, I focused on the software and equipment that Mr Liu had used to create the Kikocci files, and whether their use caused the Kikocci files to fall within the meaning of “works” under para 2 of Art 16 of the Copyright Law which the plaintiff could claim copyright ownership over. It was clear from the foreign law evidence that this required the software and equipment to be “purposely” or “specially” provided by the plaintiff for Mr Liu to create the Kikocci files: see Art 11 of the Copyright Law Implementation Regulations and the first instance decision that was upheld in Zhanyu Enterprise. This requirement was not fulfilled in the present case, for the following two reasons:
(a) I found that Mr Liu had used i-Admin (Shanghai)’s laptop for some of the Kikocci coding work: the Kikocci files that were forensically assessed were found on the laptop which i-Admin (Shanghai) had assigned to him. But it was crucial that this laptop had not been purposely or specially provided to him for coding the Kikocci files. Rather, it was provided for his general use, as part of his employment in i-Admin (Shanghai)’s operations and business development departments at the time.
(b) Neither was the software used to code the Kikocci files proprietary to the plaintiff or provided to Mr Liu for the purpose of coding those files. I believed Mr Hong and Mr Liu’s evidence to the effect that Mr Liu had downloaded and installed Oracle APEX from Oracle’s website following a Skype conversation that they had on 12 February 2010, and that this software was free-to-download and publically accessible.
As the plaintiff had not provided the material and technical resources which Mr Liu had used to code the Kikocci files, it did not own the copyright in the said files pursuant to Art 13(3) of the Computer Software Regulations read with para 2 of Art 16 of the Copyright Law.
- [105]
[105] Accordingly, as none of the conditions in Art 13 of the Computer Software Regulations read with Art 16 of the Copyright Law were fulfilled, the plaintiff did not have ownership over the copyright in the Kikocci files. These files were authored by Mr Liu outside the scope of his employment at i-Admin (Shanghai), using free-to-download and publically available software. Ownership of the copyright thus resided with him.
Conclusions on the copyright claim
- [106]
[106] Having compared the copyrighted materials with the allegedly infringing materials, I concluded that no substantial copying was proved in relation to the materials in Category 1 and 2. Although the evidence showed that the defendants had access to some of the plaintiff’s materials when they developed Nice Payroll’s payroll systems, I could not conclude that there was copying on this basis alone. The process by which Nice Payroll’s materials were created did not go towards the quality of those materials. This went towards the breach of confidence claim instead, which I turn to next.
Issue 2: Breaches of the plaintiff’s confidence
- [107]
[107] I found that the defendants indeed owed obligations of confidence to the plaintiff, but there was, in the end, no use of the plaintiff’s confidential information in the relevant sense.
- [108]
[108] The elements that have to be settled for an action in breach of confidence to succeed are listed in Clearlab SG Pte Ltd v Ting Chong Chai and others [2015] 1 SLR 163 (“Clearlab”) at [64]:
(a) The information must possess the necessary quality of confidentiality. This is satisfied if it is relatively inaccessible to the public, ie, it has not become public knowledge (at [66]).
(b) The information must have been imparted in circumstances importing an obligation of confidence. Where there is a contract expressly or impliedly imposing an obligation of confidence, this element may be satisfied simply by reference to the contract (at [65]).
(c) There must be an unauthorised use of that information to the detriment of the party communicating it.
- [109]
[109] The plaintiff identified four incidents that allegedly amounted to breaches of confidence on the part of one or more defendants. I shall categorise and deal with them in turn. I first turn to the general question of whether the individual defendants owed the plaintiff obligations of confidence.
Whether the defendants owed the plaintiff obligations of confidence
- [110]
[110] The defendants generally rejected the plaintiff’s arguments that all the defendants owed it duties of confidence. They submitted that only Mr Hong owed a contractual obligation of confidence to the plaintiff through the NDA he signed; even then, it had to be proved that the restrictive covenant in the NDA was reasonable. Mr Liu and Mr Tan did not owe duties of confidence to the plaintiff as their NDAs had been signed with the plaintiff’s subsidiaries. There was insufficient evidence as to Nice Payroll’s or Mr Li’s knowledge of the alleged confidential materials; they thus could not be said to have owed an equitable obligation of confidence to the plaintiff.
- [111]
[111] I found that Mr Hong was bound by cl 1 of the NDA he signed. He owed the plaintiff a contractual duty of confidence, regardless of the extent to which the plaintiff enforced its security protocols. I rejected the argument that his NDA was unenforceable. The plaintiff’s enforcement of the NDA did not seek to restrict Mr Hong’s ability to utilise his skill and knowledge to compete with the plaintiff. Rather, it sought to protect its confidential information, as it was legally permitted to do: see Clearlab at [67] and [75]. This is separate from information that should be regarded as part of an ex-employee’s skill and knowledge acquired in the course of employment which he is entitled to use and which the plaintiff may not protect for its own: Clearlab at [80].
The judgment continues past this page. Read the rest at eLitigation.