Confidential arbitration and confidential information are not the same thing.
Technology, finance, M&A and IP disputes may expose source code, pricing, customer data, trade secrets, models, board material and commercially sensitive settlement positions. The clause should distinguish process confidentiality from substantive information protection.
The Confidentiality Ring
The point is to make hidden drafting decisions visible before they become procedural disputes.
The Confidentiality Ring
Clause decision architectureWho may know arbitration exists?
What materials can be used or disclosed?
Enhanced protection for highly sensitive material.
Publication / disclosure / regulatory use.
Return, destruction and surviving obligations.
What the drafting is actually trying to control.
This is drafting intelligence, not a substitute for transaction-specific legal advice.
Default privacy
Define scope around parties, tribunal and institution.
Use limitation
Restrict use to dispute resolution.
Attorneys' eyes / clean team
Create enhanced handling for extreme sensitivity where appropriate.
Storage / transfer
Set secure data-handling expectations.
Disclosure
Address enforcement, auditors, regulators and financing.
Post-case
Confidentiality may continue after award.
Where sophisticated-looking clauses break.
Most drafting defects only become expensive when the parties need the clause urgently.
| Failure mode | What happens | Why it matters |
|---|---|---|
| Absolute secrecy promise | Impossible compliance | Courts, regulators or auditors may require disclosure. |
| No protected tier | Trade-secret exposure | Ordinary confidentiality may be insufficient. |
| No digital security | Operational leak | Sensitive material can be mishandled despite legal confidentiality. |
| Award publication unclear | Reputational risk | Parties dispute whether anonymised publication is permitted. |
| Third-party experts ignored | Disclosure gap | Experts / funders / insurers may need controlled access. |
The clause can activate an institutional lifecycle, not merely a hearing.
Article 36 provides a rules-based confidentiality layer, while CP5 of the DPC Standard tests confidentiality scope upstream. Contract drafting can then add transaction-specific protection.
The clause becomes important only after breach.
Clause language is treated as boilerplate until the dispute makes every word operational.
The clause manages the relationship from uncertainty to outcome.
The clause is designed as an operating system for the full dispute lifecycle.
Turn the clause into a controlled decision.
The same workflow can be used by outside counsel, in-house legal teams and procurement / contracting functions.
Find the exact commercial / legal problem.
Separate parties, contracts, seat and assets.
Choose the minimum architecture that solves the problem.
Run DPC / CIS™ checkpoints where appropriate.
Sign the reviewed version and govern deviations.