Skip to content

Confidentiality

Version
v5 · 2026-09-28 · History
Prime #
1337
Domain group
Professional & Organizational Practice
Origin domain
Law & Governance
Subdomain
Information Duties → Law & Governance
Aliases
Duty of Confidentiality, Nondisclosure Duty, Entrusted Information Protection
Related primes
Constraint

Core Idea

Confidentiality is a governed information relation in which an authorized holder may access protected information but is constrained in how it may use or disclose it. The obligation has a subject, protected content, permitted purposes, recipients, release conditions, exceptions, and breach consequences. Information is not universally public; a holder obtains legitimate access; a rule restricts downstream use or disclosure; and the restriction persists across transfer until release, expiry, or an authorized exception. Confidentiality therefore binds use after access.

How would you explain it like I'm…

The Secret-Keeping Promise

Your friend tells you a secret and says, "You can know it, but don't tell anyone." You were allowed to hear it. The rule is about what you do next: you keep it to yourself. Only someone who knows the secret can spill it.

Allowed to Know, Not to Tell

Confidentiality is a rule for people who are allowed to know something private. A doctor, a lawyer, or a friend may be told your information on purpose. The rule doesn't stop them from knowing it; it limits who they can share it with and what they can use it for. The rule keeps going, too: if they pass it to someone allowed to have it, that person has to follow the same rule. It only ends when you release it or an allowed exception applies.

Duty That Binds After Access

Confidentiality is a relationship in which someone has legitimate access to protected information but is limited in how they may use or disclose it. It is different from secrecy or security, which are about keeping people from getting the information in the first place. Four things must be true: the information is designated as protected about a specific person or source, the holder got it by permission rather than by stealing it, a rule limits what happens after access, and that rule follows the information when it is passed on. So the only people who can break confidentiality are the people trusted to hold the information. Mixing this up with questions of who should be told in the first place is the typical mistake.

 

Confidentiality is a governed information relation: an authorized holder may access protected information but is constrained in its subsequent use and disclosure. A full specification names the subject or source, the protected content, the permitted purposes and recipients, the release conditions, the enumerated exceptions, and the consequences that fall on the holder for exceeding scope. Four features are constitutive. The content is designated as protected relative to an identified subject, not merely hard to find; the holder's access is legitimate, granted rather than breached; the rule restricts downstream use and disclosure rather than acquisition; and the restriction persists across authorized transfers until release, expiry, or an exception discharges it. The organizing principle is that confidentiality binds use after access. It follows that the set of parties able to breach the duty is identical to the set entitled to hold the information, so no perimeter defense can exclude them. Access control, meaning who may be told and on what basis, is a distinct problem, and confusing the two is the typical error.

Broad Use

Medicine, law, research, diplomacy, commerce, and system security preserve the same holder–information–purpose–disclosure relation. Institutions supply the rule, but the roles transfer intact.

Clarity

Secrecy can rely on nobody knowing the information. Privacy concerns control over a person or sphere. Encryption prevents unauthorized access but does not govern an authorized recipient's later disclosure. Anonymity hides identity rather than constraining information use.

Manages Complexity

The abstraction turns scattered cases into one role-based test: identify the required elements, test their relation, and reject the classification when a constitutive commitment is missing.

Abstract Reasoning

Use the structural signature rather than the label, then challenge the nearest counterexample. Public data protected only against alteration has an integrity requirement, not a confidentiality requirement.

Knowledge Transfer

Medicine, law, research, diplomacy, commerce, and system security preserve the same holder–information–purpose–disclosure relation. Institutions supply the rule, but the roles transfer intact.

Example

A case qualifies only when the definition and every load-bearing role remain present. Public data protected only against alteration has an integrity requirement, not a confidentiality requirement.

Relationships to Other Abstractions

Local relationship map for ConfidentialityParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.ConfidentialityPRIMEPrime abstraction: Constraint — is a kind ofConstraintPRIMEDomain-specific abstraction: Born secret — is a kind ofBorn secretDOMAINDomain-specific abstraction: Quantum key distribution — is a kind ofQuantum keydistributionDOMAIN

Current abstraction Confidentiality Prime

Parents (1) — outgoing typed relations

  • Confidentiality is a kind of Constraint Prime

    Confidentiality is the information-use species of constraint, restricting an authorized holder's admissible disclosures and downstream actions.

Children (2) — abstractions linked here by typed relations

  • Born secret Domain-specific is a kind of Confidentiality

    Born Secret instantiates Confidentiality because it is a rule architecture for restricting information access, specialized by statutory subject-matter attachment from creation rather than only an official designation event.

  • Quantum key distribution Domain-specific is a kind of Confidentiality

    It remains its own entry because its identity is fixed by protocol, quantum state and measurement model, authenticated classical channel, sampling, error threshold, finite-key analysis, device assumptions, leakage accounting, and composable security claim.

Hierarchy path (1) — routes to 1 parentless root

Not to Be Confused With

Secrecy can rely on nobody knowing the information. Privacy concerns control over a person or sphere. Encryption prevents unauthorized access but does not govern an authorized recipient's later disclosure. Anonymity hides identity rather than constraining information use.