confidential information

Compilations from the public domain – confidential or not?

by

reviewed by

Malcolm Burrows

In the case of Ezystay Systems Pty Ltd v Link 2 Pty Ltd [2014] NSWSC 180 (Ezystay) it was held that the plaintiff’s business manuals were confidential despite having been compiled from the documents in “public domain”.  On Appeal, the Court had to re-visit the test for confidential information to determine whether or not the respondents’ software, business manuals and other documents collated from the public domain were in fact capable of being protected as confidential information.

Background to Ezystay

Link 2 Pty Ltd ACN 158 841 386 (Appellant) owned and operated a student accommodation business in Sydney.  Mr Riches (Third Appellant) was the sole director and secretary of the Appellant.  Ezystay Systems Pty Ltd ACN 147 054 037 (First Respondent) also provided student accommodation services.  Prior to the establishment of the Appellant, Mr Riches was a director and shareholder of Ezystay and various other group companies.

Ezystay Systems Pty Ltd ACN 147 054 037 commenced proceedings in the Supreme Court of New South Wales alleging that Mr Riches had copied and used Ezystay’s confidential information for the benefit of Link 2.  The confidential information was alleged to have included documents such as the ‘Business Manual’ and ‘Systems Manual’ (Manuals).  Ezystay was successful at first instance and the Appellant was subject to a permanent injunction.  On appeal the Appellants argued that the primary judge erred in finding that the Manuals were confidential, because they were merely a compilation of publicly available documents.

Compilations prepared from documents in the public domain

One of the grounds of appeal was that the Manuals were not in fact confidential, because they were largely compiled from information which was in the public domain.  The Court of Appeal found that:

Her Honour erred in finding that the Business Manual and the Systems Manual (collectively, the Manuals) were confidential, and thus Confidential Information within the meaning of the Deed, having regard to the fact that neither document had the necessary attributes of confidentiality in that their contents:

(a)  were in the public domain;

(b)  were common knowledge, commonplace and trivial;

(c)  could be ascertained or duplicated without expenditure of time, effort or money;

(d)  were not preserved as a matter of secrecy by the respondents; and

(e)  were not valuable.[1]

In assessing whether or not the Manuals were truly confidential, the Court said:

The real issue is whether skill and ingenuity were used in the compilation of the Manuals so as to confer confidentiality on the finished product notwithstanding the commonplace nature of much of their contents.[2]

The Court of Appeal adopted statements of Campbell JA in Del Casale v Artodemus (2007) 73 IPR 326 where it was said:

… information is “of a confidential nature” if it is not “public property and public knowledge“, or if it is “constructed solely from materials in the public domain“, to which “the skill and ingenuity of the human brain” has been applied. This is a fairly undemanding test.[3] (Human Brain Test)

The appellants’ argument was based largely on the observation made by Laddie J in Ocular Sciences Ltd v Aspect Vision Care Ltd [1996] EWHC Patents 1 that:

It is a commonplace that valuable and novel ideas may be produced by the judicious selection and combination of a number of items which, separately, are in the public domain. No one would suggest that such ideas are incapable of being the subject of an obligation of confidence. But, to adopt Megarry J’s words, there must be some product of the skill of the human brain. A mere non-selective list of publicly available information should not be treated as confidential even if putting it together involves some time and effort. No relevant skill is employed. Were this not the case, it would be possible for individual competitors to copy or make use of the individual items of information but they could not get together to make use of all or most of them.[4]

[Items in bold are our emphasis]

Therefore to assess whether information which is in the public domain can have the required qualities to be confidence it is necessary to determine the source of the information and whether the skill and ingenuity of the human brain has been used to prepare the collation.  An individual document or list of documents sourced from the public domain is unlikely to be confidential whereas a compilation of a number of documents for a particular purpose, depending on the circumstances, is more likely to be capable of being confidential.

Takeaways for those wanting to protect their confidential information

For information to be confidential there needs to be something more than a mere or random or accidental collation of unconnected materials” but can be seen on their face, to be the product of careful and skilled work by someone with detailed knowledge of the workings of the business.[5]  The real take away from this case is that it’s not enough to mark documents as being confidential and then hope that you can enforce the obligations of confidence in future.

Links and further references

Judgements involving Dundas Lawyers

Hill & Smith Holdings PLC v Safe Barriers Pty Ltd (No 2) [2020] FCA 8 (8 January 2020)

Cases on confidential information

Ansell Rubber Co Pty Ltd v Allied Rubber Industries Pty Ltd [1967] VicRp 7

Del Casale v Artodemus (2007) 73 IPR 326

Link 2 Pty Ltd v Ezystay Systems Pty Ltd [2016] NSWCA 317

N P Generations v Fenely [2001] SASC 185

Ocular Sciences Ltd & anor v Aspect Vision Care Ltd & ors [1997] RPC 289

Prime Creative Media Pty Ltd v Vranjkovic [2009] FCA 1030

Legislation

Corporations Act 2001 (Cth)

Copyright Act 1968 (Cth)

Further information about confidential information

If you need advice on protecting your businesses confidential information or enforcing your right to it, please telephone me for an obligation free and confidential discussion.

[1] Ezystay at [85]. Note these were the arguments that the manual was not confidential per se.

[2] Ezystay at [113].

[3] Ezystay at [124].

[4] Ezystay at [123].

[5] Ezystay at [118].


Related insights about confidential information

  • Contesting patent ownership between joint inventors

    Contesting patent ownership between joint inventors

    This article provides an overview of the conditions for patent grant, joint inventorship tests, and standard of proof for disputes in relation to contested patent ownership in Australia.

    Read more …

  • Is exporting a product a trade mark infringement?

    The Trade Marks Act 1995 (Cth) provides protection to Australian trade mark owners, but what happens when their mark is used overseas? Learn more about the protection the Trade Marks Act provides, and the remedies for infringement, by clicking through to the full article.

    Read more …

  • Is using a trade mark in AdWords considered infringement?

    Is using a trade mark in AdWords considered infringement?

    A Court concluded that a company had infringed a trade mark using Google AdWords in Veda Advantage Limited v Malouf Group Enterprises Pty Limited [2016] FCA 255. Click through to learn more about the dispute, and the learning points and takeaways.

    Read more …

  • Be cautious when alleging patent infringement

    Be cautious when alleging patent infringement

    The Court weighed in on the issue of unjust threats of patent infringement and the damages that may be payable. Learn more about the importance of proving direct causation between the threat and the loss, and the implications for patent holders and infringers alike.

    Read more …

  • What are end user licence agreements?

    What are end user licence agreements?

    Understand the legal risks of end-user license agreements (EULAs): learn about the common clauses, conditions, and warranties that can protect both the licensee and the licensor. Find out how to ensure your EULA is legally sound.

    Read more …

  • Copyright infringement for computer code

    Copyright infringement for computer code

    Computer code is automatically protected by copyright. Unauthorised reproduction of it may constitute an infringement, as illustrated by two federal cases. To understand copyright infringement with respect to computer code, read “Who owns the code?”

    Read more …

  • Patents, grace periods and revocation explained

    Patents, grace periods and revocation explained

    Disclosure of an invention prior to applying for a patent can have serious implications. Learn more from Dundas Lawyers to understand the important considerations, including the twelve (12) month grace period and its effect on revocation.

    Read more …

  • Who holds ownership of the code?

    Who holds ownership of the code?

    Understand who owns the computer code used in software development projects. Consider employee or contractor engagement, joint ownership, and assignment of copyright to ensure your project is protected.

    Read more …

  • A guide to intellectual property

    A guide to intellectual property

    This article provides an overview of the grounds of invalidity available for revoking a patent, including lack of novelty, inventive/innovative step, usefulness, secret use, manner of manufacture, fraud, false suggestion/misrepresentation, sufficiency, fair basis, and best method.

    Read more …

Send this to a friend