The Right to Computational Opacity

Jun 23

Now and then, a familiar question surfaces in headlines, policy debates, and casual conversations:

If you’re not doing anything wrong, why do you need encryption?

Strip away the politeness and it’s the same suspicion that greeted locked doors, sealed letters, and curtained windows in earlier eras. It assumes that privacy is a deviation from the norm—that the default state of a good citizen is to be visible, legible, and inspectable at all times.

That assumption was wrong then, and it’s wrong now.

You shouldn’t have to explain why you close the bathroom door. You shouldn’t have to justify why your diary has a lock. And you shouldn’t have to defend the fact that your laptop, your phone, and your messages are encrypted.

The right to computational opacity is simply the modern extension of something older: the right to live a life that is not continuously open for inspection.

We’ve Always Needed Places That Don’t Explain Themselves

In the physical world, nobody expects constant transparency.

The city tolerates pockets of opacity without argument:

The inside of a sealed envelope.
The quiet of a therapist’s office.
The journals in a nightstand.
The home with curtains drawn in the evening.

We instinctively understand that these are not signs of criminality. They are infrastructure for being human. Without places where you can think, grieve, argue, fantasize, and experiment unobserved, you don’t become “more honest.” You become more performative.

The digital world has inherited many of the same needs but almost none of the same instincts.

Our devices record more than any notebook ever could. Our apps observe more than any nosy neighbor. Our communication travels through infrastructure owned by others, logged by systems we don’t control, and analyzed by algorithms we never meet.

In that environment, encryption isn’t an exotic tool. It’s the bare minimum required to recreate what used to be ordinary: a conversation that doesn’t automatically turn into evidence; a file that isn’t trivially copied and searched; a life that isn’t permanently indexed.

Computational opacity is the digital equivalent of closing the door.

What “Computational Opacity” Actually Means

Opacity sounds like a metaphor, but it has very concrete incarnations.

At the simplest level, it’s encryption:

Messages that are end‑to‑end encrypted so that only the sender and recipient can read them.
Laptops and phones with full‑disk encryption, so a lost device becomes an inconvenience, not a catastrophe.
Backups and archives that are encrypted before they ever touch another company’s storage.

But computational opacity isn’t only about cryptographic primitives. It’s a broader stance:

Data at rest should be unintelligible to anyone who isn’t explicitly invited in.
Data in transit should not be easy prey for whoever happens to sit between you and the other side.
Your tools should not default to logging, phoning home, or building dossiers unless you have explicitly chosen that tradeoff.

In other words, opacity is the right to inscrutable by default.

It’s the right to have parts of your digital life that simply do not explain themselves—neither to corporations nor to governments, nor even to your future self unless you choose to keep the keys.

Rights Don’t Require Justification

The demand to explain your use of encryption is not neutral. It quietly flips the burden of proof.

Instead of: “The state must justify searching your life,” it becomes: “You must justify protecting it.”

Imagine applying that logic to older rights:

Why do you want a lawyer if you’re innocent?
Why do you close your curtains if you have nothing to hide?
Why won’t you let a stranger read your journal if it’s not incriminating?

We recognize those questions as rhetorical traps. Their goal is not to understand you; it’s to make your desire for privacy sound suspicious.

Good rights work the other way around. You don’t need a story to exercise them. You don’t file a narrative with the government explaining why you want free speech today. You don’t submit an essay justifying why you’d like to remain silent. The role of law and culture is to assume that you may do these things, by default, unless there is a specific, proportionate reason to intervene.

Encryption belongs in that category.

You shouldn’t have to be a journalist, a dissident, a whistleblower, or a survivor of abuse to qualify. You shouldn’t have to recite a threat model every time you open Signal or enable full‑disk encryption. Wanting to be left alone is enough.

The right to computational opacity is the refusal to explain your locks.

“Nothing to Hide” Is a Dangerous Standard

The “nothing to hide” argument feels powerful because it weaponizes moral comfort. It suggests a clean, simple world:

Good people have transparent lives.
Bad people seek cover.

Reality is messier.

Most of what people want to keep private is not illegal, immoral, or even particularly interesting to outsiders. It’s:

Embarrassing chapters of personal history.
Early drafts of work that would be misread out of context.
Fights and reconciliations in relationships.
Financial realities that don’t match public personas.
Thoughts that are raw, untested, or half‑true.

The “nothing to hide” standard erases these everyday vulnerabilities. It insists that the only dignity worth protecting is the kind that can withstand arbitrary scrutiny. Anything less becomes suspect.

Worse, it ignores power.

The more leverage someone has over you—an employer, a government, an abusive partner—the more dangerous it becomes for them to have a perfect map of your life. Encryption is often the only practical way to limit that map.

Computational opacity does not exist to help you conceal crimes. It exists to prevent your entire existence from being continuously available to those who could use it against you.

Surveillance by Default Is a Design Choice, Not Fate

If you look around, it can feel as though surveillance is the natural price of using modern tools. Apps log everything “for analytics.” Devices stream telemetry “to improve your experience.” Cloud services assume that every bit of data they store is available for scanning, indexing, monetizing, and mining.

But none of this is inevitable.

Surveillance is not a property of computation. It’s a business model and a policy decision.

We know this because there are systems that choose otherwise:

Messaging apps that implement end‑to‑end encryption and design themselves so they literally cannot read the messages they relay.
Operating systems and file systems that encrypt storage by default, treating plaintext disks as a legacy hazard.
Self‑hosted or local‑first tools that keep data on machines you control and only sync what you intentionally expose.

These systems prove that it is entirely possible to design for opacity first. The fact that many products don’t is not a technological constraint; it’s a choice.

The right to computational opacity is, in part, the right to live in an ecosystem where those choices are available—and where choosing them does not mark you as suspicious.

Encryption Without Apology

Encryption has gone through several cultural phases.

Once, it was an obscure hobby for mathematicians and spies. Then it became a political flashpoint: the “crypto wars,” export controls, debates about whether strong encryption should be treated like a weapon. Today, it’s woven into everything from web browsing to messaging—but the suspicion lingers.

You can see it in proposals for “exceptional access,” “lawful intercept,” or “client‑side scanning”: design patterns that reintroduce privileged visibility for certain actors under certain conditions. You see it when using strong encryption gets you pulled aside at a border, or when a service marks Tor users as inherently risky, or when a company reserves the right to scan your “private” content for policy violations.

All of these share a common thread: they treat opacity as a problem to be solved.

What would it look like to invert that view?

Encryption is the default for stored data and communications, not an advanced feature.
Choosing encrypted tools is boring—like choosing a car with seatbelts.
Laws and norms assume that encrypted data is off‑limits without specific, high‑bar justification, not a puzzle to be cracked “just in case.”

In such a world, you wouldn’t have to explain why your drives are encrypted or why your chats are unreadable to the platform. The burden would fall on those who want to pierce that opacity to explain themselves.

Opacity as a Design Principle

The right to computational opacity isn’t just a legal or philosophical claim. It has teeth in design.

Software that respects this right tends to share certain traits:

It minimizes data collection instead of hoarding it “just in case.”
It stores what it must in a form that’s encrypted by default.
It exposes clear, human‑readable settings about what leaves your device and what doesn’t.
It avoids building features that depend on peeking into your private state.

Crucially, it treats locality as an ally. When computation happens on your device or your own server, the set of parties that need access shrinks dramatically. A language model running on your laptop to summarize your documents does not require those documents to be uploaded to a corporate datacenter. A photo library indexed on your home server doesn’t need to become fodder for a global classifier.

Opacity is easier to maintain when value is created as close to you as possible.

You can see the contrast when tools are built the other way around:

Features that only work if your raw data is sent to the cloud.
Personalization that requires detailed behavioral logs.
“Smart” functions that are really just excuses for constant inspection.

The more a system insists on seeing everything, the less room it leaves for opacity—and the more pressure it puts on you to justify wanting it.

The Psychological Cost of Being Permanently Legible

There is a quiet psychological burden to living in systems that assume transparency.

When you know your messages might be scanned, you start editing yourself. When you suspect your searches might be reviewed, you stop asking certain questions. When every document might one day be subpoenaed, leaked, or surfaced by an algorithm, you hesitate before writing down the half‑formed thought.

Over time, this doesn’t just change what you reveal. It changes what you allow yourself to become.

People need private spaces to develop, to test identities, to make mistakes without immediate public consequences. A teenager questioning their orientation, an employee wrestling with burnout, a parent researching sensitive medical issues—these aren’t “bad actors.” They’re exactly the kinds of people who most need opacity.

Encryption, used casually and without fanfare, helps restore those spaces. It lets you treat your digital life less like a stage and more like a room.

You shouldn’t have to argue for that room every time you close the door.

A Future Where Opacity Is Boring

The right to computational opacity doesn’t guarantee that no one will ever misuse encryption. It doesn’t magically resolve the tension between privacy and legitimate investigations. Those are hard problems, and they will remain hard.

What this right does assert is something quieter: that ordinary people should be able to protect their digital lives without being treated as suspects.

In practice, that future might look like:

Devices that ship with encryption fully enabled, no setup wizard required.
Messaging apps that can’t read your conversations and don’t apologize for it.
Services that happily work with data they can’t inspect, because their business models don’t depend on surveillance.
Legal frameworks that treat mass decryption demands the way we treat mass home searches: unacceptable.

Most importantly, it looks like a cultural shift. Using an encrypted messenger, keeping an encrypted backup, or running local tools that never phone home becomes as uncontroversial as locking your bicycle or closing your front door.

Opacity stops being a red flag. It becomes part of the landscape.

You will still choose when to be transparent. You’ll still publish, share, and open up parts of your world to others. But that sharing will be a decision, not a default.

The machines around you will hum, compute, and remember—yet much of what they know will remain visible only to you and those you invite. Not because you won an argument, but because you never had to make one.

That is the right to computational opacity: the freedom to keep parts of your digital life dark to the outside world, without having to justify why you needed the lights off in the first place.

Sbussiso Dube