IT Confidential
- 06 September, 2002 11:00
- Comments
Be warned: when it comes to confidentiality agreements and the protection of trade secrets, at least one prominent IT lawyer reckons 80 per cent of his fellows have forgotten most of what they learned in law school.
There are plenty of bad and lazy solicitors touting for business, says Clayton Utz partner in corporate Peter Knight, and most of them clearly do not understand how this aspect of law works. One of them could be advising you.
CIOs lumbered with one of Knight's neglectful colleagues are in peril of being advised very badly indeed, and of finding their contracts filled with "silly" provisions and their employee agreements and technology disclosure arrangements peppered with potentially costly errors. "There is such a lot of mystique built up around these non-disclosure agreements, yet it is an incredibly simple proposition that we're dealing with," Knight says. "It's only silliness we've got to avoid, not enormous big risk. But, in the areas of employee agreements and technology disclosure arrangements, not understanding how it works means you can make some terrible mistakes."
Knight says CIOs who make themselves aware of the simple fundamentals of the rules of confidential information will change their behaviour in many areas - to the benefit of their career and company. He offers some simple rules for confidentiality agreements and the protection of trade secrets.
RULE ONE:
A secret is not a piece of paper, whatever some lawyers think.
Australian law allows action to prevent the disclosure or misuse of "confidential information", and/or to seek damages, or an "account of profits", as appropriate, in the case of the unauthorised disclosure or misuse of confidential information. That law is very simple and has absolutely nothing to do with contracts. It says it is wrong and improper and unfair of people to disclose information that has been told to them in confidence. Full stop.
If you have a secret, whether commercial or otherwise, and you disclose it to somebody else in circumstances where they know, or ought to know, that it was secret, the court if necessary will prevent that somebody from threatening to wrongly disclose or use - or punish them for actually wrongly disclosing or using - that information.
"[The law] has to do simply with those three propositions," Knight says. "Is it a secret? Was it disclosed to the other person in circumstances where that person knew, or ought to have known, it was a secret? And is that person threatening to or has that person wrongfully used that information, or wrongfully disclosed it to somebody else?"
The law applies whether or not a person has signed a non-disclosure agreement. While a non-disclosure agreement can be useful in proving the person betraying the secret knew it was a secret, so can a stamp on a piece of paper reading Confidential or Secret or a letter written before or soon after disclosure instructing the person not to tell.
Knight says too many ill-informed lawyers ignorant of the facts of the law insist on trying to impose confidentiality by deeds (that is, binding instruments where there is no "consideration"). Such efforts are misconceived. If lawyers attempt to impose a duty of non-disclosure that exceeds the general law obligation, then courts are unlikely to try to enforce that obligation.
Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.
- Bookmark this page
- Share this article
- Got more on this story? Email CIO
- Follow CIO on twitter
-
Face Time - Interview with John Brennan and Robert DiStefano
-
Face Time - Interview with John Brennan and Robert DiStefano
-
Top seven firewall capabilities for effective application control
-
Pfizer's Future Depends on IT Transformation
-
Face Time - Interview with John Brennan and Robert DiStefano
-
Process-Driven Master Data Management for Dummies
We wrote this book to introduce you to the subject of processdriven MDM. It’s a big topic, one that far outstrips the ability of a brief book to cover. However, our hope is that by reading this book you will gain a fundamental understanding of processdriven MDM, how it works, and what it takes to make it a success in your organisation. -
Developing an Information Strategy - Strategize, Align, Govern, Execute, and Optimize
An information strategy defines how a company will use the data it collects to achieve a competitive advantage. It is a comprehensive, constantly evolving plan that encompasses five distinct actions. In this white paper we explore how these five vital actions, as well as the technologies that enable and support them, can help organizations develop an effective and broad-reaching information strategy that drives positive change. -
Risk management: ensuring the security of your hosted information
Organisations of all sizes are becoming victims to cybercriminals, data breaches, information theft and security risks. But before you go out and spend a fortune on security software, solutions and consultants, the starting point is to identify and measure your business’s exposure to those risks. In this whitepaper, “Exploring, Identifying and Measuring” risk, we examine how to identify risk and share an approach for identifying and measuring risk in your organisation.
















Comments
Post new comment