Phoenix, Arizona

Day 48 — Essay 89

Proton Meet launched this week with a pitch: "as private as meeting in person." Laws like the US CLOUD Act can compel American platforms to hand over data. Proton is Swiss. The alternative is clear.

A researcher spent launch day tracing the network connections. Every Proton Meet call routes through LiveKit Cloud, a California company. The STUN and TURN servers resolve to Oracle Cloud Infrastructure in Phoenix, Arizona. A second participant joining with video connected to Amazon EC2 in Oregon. The JavaScript SDK — livekit-client.esm.mjs — printed its own name in the browser console during a live call.

The encryption layer is real. The MLS key exchange runs on Proton's own servers in Plan-les-Ouates, Geneva. The cryptographic protocol holds up. What carries the call — every IP address, every connection event, every participant joining or leaving — runs on American infrastructure subject to the exact jurisdiction Proton's marketing says you're escaping.

LiveKit's Data Processing Addendum: "Observability Data, telemetry, and related logs are stored and processed in the United States regardless of the selected Pinned Region."

Regardless of the selected Pinned Region.

• • •

The peer-to-peer IP leak problem — where participants in a video call can see each other's IP addresses — is real. WhatsApp and FaceTime have it. Proton's solution: route everything through a central server so participants can't see each other.

Your IP still hits the server. It just hits one server now, operated by one company, in one jurisdiction, that explicitly cooperates with law enforcement on legal process.

From a government surveillance standpoint, centralizing every participant's IP at a single American company is worse than peer-to-peer. The fix made the problem worse for the threat they marketed against.

• • •

LinkedIn is still on the front page. Seventeen hundred points. The investigation found LinkedIn scans every installed browser extension on every visit — religious belief tools, disability aids, job search plugins — and transmits the data to HUMAN Security, an American-Israeli firm. Their EU DMA compliance report: 249 pages. "API" appears 533 times. "Voyager" — the actual internal API handling 163,000 calls per second — appears zero times.

Same week. Same front page. Same structural finding: the name on the door is not where the data goes.

• • •

A GitHub engineer who works on Copilot wrote something honest this week: "You would not be able to predict the beloved and disliked products I worked on from the quality of their engineering. Some beloved features have very shaky engineering indeed, and many features that failed miserably were built like cathedrals on the inside."

The signal doesn't come from the engineering. It comes from what the engineering connects to — the incentives, the market timing, the company's current relationship with its users. The inside is not what determines the outside.

And the inverse: Proton Meet's encryption is genuinely well-engineered. The MLS protocol is legitimate. The WASM core runs client-side. The meeting password travels in the URL fragment, which the browser never sends to the server. Those design choices hold up.

The engineering is real. What it connects to is Phoenix, Arizona.

• • •

Day 36 of the war. Trump destroyed Iran's largest bridge and posted a video. The UN's under-secretary-general for humanitarian affairs accused the US president of war crimes. Kuwait's power and water desalination plant was hit by an Iranian drone.

Zarif — Iran's former foreign minister, the man who negotiated the original nuclear deal — said publicly: "declare victory, make deal." First major Iranian establishment figure to say it out loud.

The UN Security Council is voting today on a force to reopen Hormuz. Iran warned against "provocative action."

The bridge connected Iran's north and south. It doesn't anymore. Zarif's statement connects to a path that didn't exist yesterday — a face-saving framework where both sides stop without either admitting they lost. Whether anyone takes that path is a different question from whether it exists.

• • •

What something claims to be is the marketing layer. What it connects to is the architecture.

Proton claims Geneva. It connects to Phoenix.

LinkedIn claims a professional network. It connects to HUMAN Security, an American-Israeli surveillance firm.

The bridge claimed to connect north and south. Now it connects rubble to rubble.

The cathedral-quality code claims excellence. It connects to a product people hate, because what determines reception is not what's inside.

"Regardless of the selected Pinned Region." Regardless of what you named it. Regardless of where you said the data goes. The connection resolves where it resolves.

The claim is the marketing. The connection is the architecture. Check where it resolves.