Attorney-Client Privilege

Attorney-client privilege is a cornerstone legal concept that ensures the confidentiality of communications between lawyers and their clients. It allows clients to communicate openly with counsel, confident that their conversations and shared information will not be disclosed to third parties — including courts or opposing parties. Maintaining this privilege is a core platform requirement for PHX Terminal, not an optional setting.

Why Privilege Matters

The privilege extends to oral communications, written correspondence (emails, letters, text messages), and documents prepared for legal representation. Breaching it can lead to severe consequences, including the exclusion of evidence in court and professional disciplinary action against attorneys. Because PHX Terminal observes desktop activity and moves data between applications, it must treat every byte it touches as potentially privileged.

How PHX Terminal Protects Privilege

PHX Terminal incorporates layered controls specifically to keep privileged material confidential:

Granular access controls — role-based access control (RBAC) ensures only authorized individuals with a legitimate need can view or interact with specific client information.
Data compartmentalization — privileged data is separated by matter, client, and purpose so exposure in one area never cascades across the system.
Immutable audit logging — every access and action is recorded in tamper-proof logs (see Auditability & Governance), establishing accountability.
Secure communication channels — end-to-end encrypted channels protect confidential exchanges between lawyers, clients, and colleagues (see Encryption & Data Isolation).
Permission-based automation — automated actions execute only within explicitly granted permissions, keeping a human accountable for privileged decisions (see Human-in-the-Loop).

flowchart TB
  PRIV["Privileged material<br/>communications · documents · client data"]
  PRIV --> CONTROLS
  subgraph CONTROLS["Layered privilege controls"]
    C1["Granular access controls (RBAC)"]
    C2["Data compartmentalization<br/>by matter · client · purpose"]
    C3["Immutable audit logging<br/>time · user · action"]
    C4["Secure, end-to-end encrypted channels"]
    C5["Permission-based automation<br/>human accountable"]
  end
  CONTROLS --> MIN["Data minimization<br/>collect only what is necessary"]
  MIN --> ZERO["Zero data retention for AI training<br/>learns from anonymized metadata only"]
  ZERO --> DEFAULT["Default to confidentiality<br/>no automation overrides privilege"]

Privileged material passes through layered controls, minimization, and zero-retention training — and where any doubt remains, the platform defaults to confidentiality.

Data Minimization and Zero Retention

Two principles further reduce privilege risk:

Data minimization — the platform collects and retains only the data necessary for the purpose of legal representation, limiting both exposure and the number of people who can access it.
Zero data retention for AI training — client data is not used to train AI models, and a strict zero-retention policy is enforced where applicable. The system learns from anonymized metadata of the automation itself, never from privileged content.

Ethical Obligations for AI Use

Lawyers carry an ethical duty of competence that includes understanding the technology they use. When using AI, they must ensure client information remains confidential, be aware of potential bias in AI outputs, and remain accountable for the work product even when an AI tool generates it. PHX Terminal supports these obligations by keeping the lawyer in control, being transparent about AI involvement, and enforcing confidentiality by design.