Keeping privileged email inside your firm

Ask a firm where its most sensitive data lives and you will hear about the document management system, the deal room, maybe the billing records. The honest answer is almost always the mailbox. Email is where clients confess the bad facts, where strategy gets argued out, where settlement numbers move, where the work-product actually happens between the drafts. It is the densest concentration of privileged material a firm holds — and at most firms, every byte of it lives on infrastructure the firm does not operate, under retention defaults the firm did not write, mixed in with newsletters and lunch plans.

That arrangement is so universal it has stopped looking like a choice. But it is one, and it is worth examining what the alternative looks like: a mail system that runs inside the firm, knows what a matter is, understands privilege as a property of a message, and lets AI help with the flood without ever acting on its own.

The mailbox is the crown jewels, treated like a commodity

Privilege attaches to attorney-client communication because it is confidential, and confidentiality is a fact about who can access something, not just a label on it. Every party in the path of a message is part of the confidentiality analysis. When the entire archive of a firm's client communication sits in a third-party cloud, the firm has added a permanent participant to every privileged conversation it has ever had — one with its own administrators, its own retention machinery, its own legal process obligations, and its own breach surface.

None of this means cloud mail providers are careless. It means the firm's most privileged data is governed by someone else's decisions, and the firm's role has quietly shrunk from custodian to customer. For plenty of businesses that trade is fine. For an institution whose product is confidentiality, it deserves more scrutiny than it usually gets.

There is a second, less discussed problem: generic mail has no idea what your practice is. It does not know that three threads, a forwarded court notice, and an attachment chain are all one matter. It cannot tell privileged communication from a bar association mailer. Every organizing structure that matters to a law practice has to be imposed by hand — foldering, tagging, hunting — forever, by every lawyer, in every inbox.

EdgeMail: a mail system that runs where the firm's data lives

EdgeMail is the mail system inside EdgeLex — the firm's own mailboxes and domains, running as part of the same platform that runs the firm's matters, documents, and deadlines. Message bodies and attachments are stored locally in firm-controlled storage; there is no shadow copy of your client communication accumulating in an outside service as a byproduct of the platform's design. Whether the firm runs EdgeLex self-hosted or chooses the EdgeLex-managed cloud, the mail stack is part of the firm's governed deployment, under the firm's identity system, the firm's policies, and the firm's audit trail.

Because the mail system and the practice platform are the same system, email stops being an undifferentiated pile. Messages link to matters, so a thread with opposing counsel in a hypothetical matter like Hale v. Northstar Logistics lives with the Hale record — alongside the documents, deadlines, and tasks it relates to — instead of floating in a personal inbox until someone remembers to file it. Court eService and e-filing notices are captured on the client's communication timeline automatically. The mailbox becomes part of the record of the representation, which is what it always was in substance.

Privilege becomes a property the system understands rather than a fact everyone carries in their heads. Communications can be classified as attorney-client or work product, and that classification travels with the message inside a platform where access control, retention, and audit are firm-governed. When production obligations arrive, privileged material is an identified class you can reason about — not a discovery exercise conducted against your own inbox.

The mailbox is part of the record of the representation. It always was — most firms just run it as if it weren't.

AI in the inbox — with a hard line it cannot cross

Email is also where lawyers drown, which makes it the most tempting place to deploy AI and the most dangerous place to deploy it carelessly. An AI that reads your mail is reading privileged material; an AI that sends your mail is speaking for the firm. EdgeLex draws the line accordingly.

Lex, the AI layer of the platform, works as a triage layer in EdgeMail. It reads the flood so you can prioritize it — and because the mail runs inside the firm's deployment, that reading happens under the firm's model policy. A firm that wants no privileged email processed by any outside model can run local models on its own hardware, and the analysis never leaves the building.

On the action side, the rule is absolute: nothing sends without a human approving it. Sending email is an approval-gated action in EdgeLex — Lex can draft a reply, propose a response to a scheduling request, or prepare an update to a client, but the send happens only when a lawyer explicitly approves it, and the approval itself is recorded. That holds everywhere the platform runs, including the phone: from EdgeMobile you can approve or reject a proposed send from anywhere, and the mobile mail client adds a Legal Send Check that clears, flags, or blocks an outbound message before it leaves. The gate is structural, not a setting someone can talk the model out of.

The deeper point is that inbox AI and email sovereignty are not separate features — the second is what makes the first defensible. AI triage of privileged mail is only a responsible idea when the firm controls where the mail lives, which models read it, and what happens before anything leaves.

One more structural safeguard is easy to miss and important to have: in EdgeLex, messaging a colleague and asking the AI are two separate modes with separate composers and separate records. A message meant for a person can never be silently routed to the AI, and a matter thread cannot trigger an ungoverned AI action — Lex's work always runs through its own governed path, approval gates included. In a system where AI lives alongside privileged communication, keeping those channels structurally distinct is not a UX nicety. It is what makes the privilege analysis clean.

One honest limitation

A boundary worth stating plainly: EdgeMail is the firm's mail system on the firm's domains. Connecting external personal accounts — Gmail, Outlook.com, arbitrary IMAP — is not currently supported. That is a deliberate line, not a gap on a roadmap slide: the governance story above depends on the mail actually living inside the governed deployment, and a personal cloud inbox bridged into the platform would quietly break the very properties the system exists to provide.

What this looks like in practice

Pull the pieces together and the daily experience is less exotic than the architecture suggests. Mail arrives on the firm's own domains and lands in a real mail client — web, desktop, and mobile. The differences show up in the details that matter to a practice:

• A message about a matter is linked to the matter, so the thread, the documents it references, and the deadlines it triggers live in one place.
• Privileged and work-product communications are classified as such, inside a platform where that classification is enforceable and auditable.
• An incoming court order does not stop at the inbox — it can flow into the platform's deadline engine and become reviewed, source-backed calendar obligations.
• Lex triages and drafts under the firm's model policy; every send waits for a named human's approval, and the approval is on the record.
• Bodies and attachments sit in firm-controlled storage, under the firm's retention rules — not a provider's defaults.

None of that requires lawyers to change how they think about email. It requires the mail system to finally know what the lawyers already know: that this is not correspondence in general — it is the confidential record of client representation, and it should live where the rest of that record lives, under the people who answer for it.