Healthy institutions protect personal details while still explaining decisions. Unhealthy ones flip the arrangement: they guard their own reasoning like a state secret while treating your details as fair game. The two postures get defended with the same word, confidentiality, which is why the distinction deserves a plain statement and a working checklist.
Privacy protects information about people. Secrecy hides information about power. A clinic that will not discuss your diagnosis in the hallway is practicing privacy. A clinic that will not tell anyone how it decides who gets an appointment is practicing secrecy. Both involve a closed door, and that surface resemblance lets institutions slide from one to the other while sounding principled the whole time.
Households know the distinction instinctively, even without the vocabulary. A teenager's diary is private, and most parents sense that reading it would be a violation rather than good governance. But the household budget, the curfew, the reasons behind a grounding, those are governance, and a parent who refuses to explain them is not protecting anyone's dignity. They are just declining to be questioned. Institutions are households at scale, with lawyers.
The rule that threads the needle
The cleanest working example I know is the U.S. Census Bureau. Under Title 13 of the U.S. Code, the bureau is barred from publishing anything that would let a particular person or business be identified from their answers. Your responses can be used for statistics and nothing else, and an employee who leaks identifiable data faces fines and up to five years in prison.
Yet the bureau is anything but secretive. Its methods are documented in public, its questionnaires are published, its aggregate results are free for anyone to download, and its confidentiality practices are themselves explained on a public page. Maximum protection for the individual record, maximum openness about the machinery. That combination is the whole trick, and it proves the two goals do not have to fight each other.
An audit you can run in ten minutes
When an institution tells you something must stay confidential, run the claim through these seven questions. They work on employers, school boards, homeowner associations, apps, and government offices alike.
- Whose information is being shielded? If it belongs to an individual (health, finances, home address, a child's records), the privacy claim starts out credible. If it belongs to the institution (criteria, budgets, error rates), be skeptical.
- Who benefits from the door being closed? Privacy benefits the person described. Secrecy benefits the organization describing. Follow the benefit, not the vocabulary.
- Can the decision be explained without the personal data? "We picked the candidate with more licensure experience" reveals no one's file. If an institution claims it cannot explain a decision without violating someone's privacy, it usually means it does not want to explain the decision.
- Is the rule written down where you can read it? Real confidentiality policies are public documents with defined categories. Improvised confidentiality, invoked case by case, is a tell.
- Does the shield apply evenly? Watch for institutions that cite privacy when criticized but happily share the same class of information when it flatters them.
- Is there a lawful path to the information for people with standing? Privacy regimes have doors with rules: courts, auditors, the person's own consent. Secrecy has no door at all.
- What happens to someone who breaks the promise? Genuine privacy protection carries penalties, the way Title 13 does. If nothing happens to leakers, the confidentiality was decoration.
Score it roughly. A claim that passes five or more of these is probably privacy. A claim that fails most of them is secrecy wearing privacy's coat.
Where the blend gets sold hardest
Certain phrases should raise your hand toward this checklist automatically. "We don't comment on personnel matters" is legitimate when it protects a fired employee's dignity, and illegitimate when it buries a pattern of complaints against the organization itself. "For your security" often precedes a policy that mostly secures the company against scrutiny. Separate confidential information from public reasoning: the names in a disciplinary case can stay sealed while the standards, the process, and the count of cases are published, giving people a predictable process without exposing anyone. Institutions that refuse even the aggregate numbers are not protecting anyone but themselves.
The same test works in reverse, on transparency demands. Someone insisting that a neighbor's medical situation, salary, or immigration status is a matter of public interest is usually doing surveillance with civic language on top. Openness obligations attach to roles and institutions, not to persons living their lives.
Try it on something near you
Pick one confidentiality claim currently in your life. The HOA that will not share how it chose the paving contractor. The app that will not say who it shares data with. The school that cites privacy to avoid publishing bullying statistics. Run the seven questions and write the answers down, because vague unease becomes a usable position once it is itemized. Then act on the sort. If it is privacy, respect it fully and say so. If it is secrecy, ask for the reasoning, in writing, minus the personal details, the same way an apology needs operational details to be credible. The difference between privacy and secrecy is easiest to defend when you can point to exactly which question the institution failed.