Confidentiality agreement
|
NDA Anatomy™
|
Also known, to those for whom the glass is half-empty, as a non-disclosure agreement. An agreement whereby you promise not to tell. If Robert Plant were writing one, he would write it like the box on the right.
Anyhoo. Here are the main parts of a normal financial markets confidentiality agreement.[1]
What should be in an NDA
Let’s be blunt about this: there is a special place in hell for any advisor who serves up a confidentiality agreement more than 3 pages long. Even three pages is purgatorially tedious. GET TO THE POINT. It’s a goddamn NDA, not the sale of your soul.
For those of you who can’t see your way clear to embracing the OneNDA, and who have not yet been asked to get your coat, here are the basic things it needs to cover:
Who is who: Who is disclosing, who is receiving, or is it mutual? Mutual is good — as it plays to the idea that this is fair, but sometimes you want to just get across the line quickly, by offering confidentiality, without requiring it. That way, for example, you can just sign without seeking assent.
- The confidential information: What counts as confidential information, and what doesn’t?
- The Purpose: Why are you disclosing the confidential information? What is the project?
- The confidentiality obligation itself: How is the receiver expected to keep it secret? Who can the receiver share with? On what terms?
- Mandatory disclosure beyond the “Purpose”: What about compulsory disclosure under legal process, statutes and regulations?
- Term: How long does the confidentiality obligation last?
- Other: Representations and warranties, governing law, And for God’s sake WHATEVER YOU DO DON’T FORGET THE COUNTERPARTS CLAUSE.
What shouldn’t be in an NDA
The following often make their way into a confi agreement, though none really have any business being there.
What’s in a confi?
Confis can be “one way”, where one party discloses and the other receives, or “two way”, where both parties disclose sensitive information. A broker’s template will tend to be far more generous when it is receiving only, than when it is giving information up. I know this may come as a shock to some of you.
Length
Firstly, let’s be blunt about this: there is a special place in hell for any advisor who serves up a confidentiality agreement more than 3 pages long. Even three pages is purgatorially tedious. GET TO THE POINT. It’s a goddamn confi, not the sale of your soul. Oh hang on. Template:Copyright and confidence
Representations and warranties in a confidentiality agreement
Assiduous attorneys will drivel in some of the usual boilerplate reps[2], to no obvious point, but for the most part confidentiality agreements are characterised by the representations the parties are not making to each other. Thus, this is another one for the “I never said it was” file, a clear disclaimer that when giving you this information, I never said it was accurate or good for anything. So you can’t sue me if you rely on it and lose money. So must your NDA have a term? Some insist on a hard stop, say two years, after which confidential information ceases to be confidential. This seems to us to be artificial. Others may mediate this by “execution of final transaction documents”.
It is not clear why going live on a transaction should suddenly set the negotiating parties free to spill private beans about each other that they learned in its formation. The theory is possibly that the final deal docs will themselves contain confi provisions which will be more sophisticated and can govern — but at least in the derivatives world, typically they don’t. Go figure.
Why have a term at all?
Good question.
Many negotiators declare themselves immutably bound to a term, usually by internal policy. They would sooner be broken upon a wheel than let this one go. This policy, they will intuit, dates from the days of the First Men, possibly was the result of a misunderstanding, but in any case subsequently has hardened, encrusted, calcified, petrified, and finally fossilised itself into a layer so deep in the firm’s organisational substrate that there is no known means of questioning it. In the very act of questioning it invites some kind of opprobrium. If anyone ever did really understand what the issue was, they have long since moved on, or been moved on, and no-one remains who can recall, much less articulate the original reason for this policy, or why it is still needed now.
Furthermore, in the ensuing thirty odd years, generations of employees have left that firm (some voluntarily, many not), taking this deep personal conviction with them, and have circulated the market, wherever they go inculcating a strong sense that some ineffable calamity would befall them, their firm, the market or, indeed, the entire industry should this sacred covenant ever be breached.
Thus the “mandatory confidentiality term” has now become part of the folklore of the financial services markets. You have to have a term, and it can’t be longer than two years at the most.
Now perhaps the JC is that long-prophesied seal of the forthcoming apocalypse (actually that might explain a few things, come to think of it) but, personally, he has never been able to understand what this “term” covenant could possibly achieve? Why, after a couple of years, should I suddenly be entitled to blare all your darkest secrets out from the minarets around town, without so much as a by-your-leave?
While the commercial value of much information does go stale over time (blueprints for a BetaMax, anyone?), this isn’t universally true — a client list is valuable however long you hold it — and the usual justification for the hard stop (“we just don’t have the systems to indefinitely hold information subject to confidence and don’t want indeterminate liability for breach”) is a canard — a palpably false one at that, for a regulated financial institution. Whatever information security systems you do have don’t suddenly stop working after three years. And as for indeterminate liability — well, no harm no foul: if the information really is stale then no loss follows from a breach, right? No loss, no damages.
In any case, it seems to the JC that a term creates more questions than it answers. When does it run from? The date of the NDA itself, or the date of disclosure of the information in question? If the former, and the point is to exclude stale information, why is the NDA date a relevant point? If the latter, who is monitoring what is disclosed when? What is meant to happen when the term expires? Why are we even having this conversation?
What a confi shouldn't have
The following often make their way into a confi agreement, though none really have any business being there.
Special AKA
The same as a: