Notes on Internet Privacy

Posts and research from the URnetwork team and community.

RSS

The List Already Existed. Today Tennessee Voted to Use One.

At 11:47 a.m. Central on Tuesday, April 14, 2026, the Tennessee State Senate voted 24 to 7 to require health-care providers to report every transgender adult they treat — by name, by dose, by diagnosis code — to a state agency. Seven weeks earlier, Kansas had mailed mass-invalidation letters to 1,700 trans residents, drawing from a registry it had maintained since 2019. The Tennessee vote is not about building a list. The list already existed. The question in front of the chamber was only how to use it.

The vote

At 11:47 a.m. on Tuesday, SB 676 cleared the Tennessee Senate 24–7. Sen. Brent Taylor (R-Memphis), the sponsor, described the bill as medical research transparency. Sen. Jeff Yarbro (D-Nashville) described it as "a state-maintained list of private citizens whose private care is none of the state's business." Sen. John Stevens (R-Huntington) joined the six Democrats as the lone Republican no.

The companion bill, HB 754, had already passed the House 70–21–2 on March 26. The Senate added two amendments — adding attorney-general investigative authority, and striking a county-level public-release provision — which the House must reconcile before the bill reaches Gov. Bill Lee. Lee has signed every LGBTQ-related bill sent to him in his governorship. His only veto was an unrelated parole-board matter in May 2025.

By its terms, Tennessee health-care providers serving transgender adults must submit to a state agency:

  • Patient age and date of birth
  • Sex assigned at birth
  • Gender dysphoria diagnosis code
  • County of residence
  • Medication, dosage, duration, route of administration
  • Surgical codes with referral source
  • Provider name, contact, specialty
  • Visit dates
  • Mental-health condition history

Non-compliance: $150,000 per clinic; six-month license suspension.

Vanderbilt University Medical Center halted adult gender-affirming surgeries in February. ETSU Health has not publicly commented. The class action Doe v. VUMC is active in Davidson County Chancery; the HHS Office for Civil Rights is running a parallel investigation. The bill has not been signed. The chilling has already arrived.

What Kansas had already done

On February 26, 2026, the Kansas Department of Revenue mailed mass-invalidation letters directly to approximately 1,700 transgender residents. Their driver's licenses were voided. At the Department of Health and Environment, birth-certificate amendments for approximately 1,800 more were voided. These numbers are confirmed by NBC News.

What Kansas did not do: build a registry to identify these people.

What it did do: reach into an existing one.

The gender-marker-amendment log sits at the KDHE Office of Vital Statistics. Entries date to the 2019 consent judgment in Foster v. Andersen, under which Kansas agreed — to protect trans residents — to amend vital records on request. KDOR maintains an internal gender-marker-change flag in its driver-services system. When SB 244 passed in January 2026 and took effect on February 26, the list of who had amended a marker was already there. The mailings began the day it took effect.

Kansas's transgender residents did not fill out a form to be added to a list. They filled out a form to be removed from one. The architecture did not distinguish.

The door Texas opened

On March 13, 2026, the Texas Supreme Court ruled in Paxton v. PFLAG that the attorney general does not have to prove someone has the documents he demands. Belief, not proof, will suffice. PFLAG must turn over contingency-plan communications, referral networks, and executive-director affidavit records. The logic applies equally to Missouri — where AG Catherine Hanaway inherited Andrew Bailey's September 2025 appeals-court pathway to Washington University Transgender Center records — and to any state attorney general using a consumer-protection statute to compel disclosure.

The ruling converts the civil investigative demand into an exploratory instrument. It does not require a crime. It does not require a suspect. It does not require documented priors. Belief is enough.

The federal chain

The bill at state level depends on a chain of federal unwinding that has proceeded in parallel:

  • HIPAA Reproductive Health Privacy Rule — vacated June 18, 2025 in Purl v. HHS (N.D. Tex.). The rule had limited law-enforcement subpoenas and state-AG civil investigative demands for reproductive-health records. Tennessee AG Jonathan Skrmetti led the 14-state challenge.
  • 360-plus federal surveys — stripped of sexual-orientation and gender-identity fields by OMB non-substantive-change requests. 83 percent of removals were made through this administrative backdoor, without Paperwork Reduction Act review.
  • DHS Intelligence & Analysis Policy Manual — removed gender identity from the manual's surveillance guardrails. Sexual orientation was partially restored after civil-society pressure. Gender identity remains excluded.
  • CMS–ICE data-sharing agreement — signed July 2025. Covers 80 million Medicaid enrollees. California v. HHS (N.D. Cal. 3:25-cv-05536) has an April 30 hearing on whether HHS violated Judge Chhabria's order by transmitting data.
  • Palantir ELITE — listed in DHS's January 28, 2026 AI inventory as a gen-AI targeting system that extracts from rap sheets and warrants. OMB M-25-21's April 3 deadline required high-impact AI accounting or discontinuation. DHS was silent. Mobile Fortify, the field facial-recognition tool, is also listed without a completed impact assessment.
  • Eight arrests per team per day — the documented operational quota in M-J-M-A v. Wamsley, set using ELITE's Address Confidence Scores. Judge Kasubhai enjoined warrantless arrests. The injunction is on appeal.
  • DOGE at SSA — on April 10, 2026, the Fourth Circuit en banc vacated the district-court injunction against Department of Government Efficiency access to Social Security Administration data covering 70 million Americans. Judge King dissented that SSA had given "patently false" information to the lower court. The majority held that plaintiffs had not shown irreparable harm.

This is the chain a Tennessee transgender-patient record can traverse. HIPAA no longer stops it. Federal surveys no longer capture it. Federal targeting systems no longer filter for it. Federal oversight deadlines passed without compliance.

The architecture of enforcement is operational. The statutes Tennessee is passing are its plumbing.

What the architecture looks like elsewhere

The pattern is not specific to the United States or to transgender rights. It is what centralized identity systems do when the regime that built them changes — or when nothing changes at all and the system simply leaks.

The envelope that read the mail

Today, the French cybersecurity press disclosed that 40 million SMTP records from the email provider Alinto had sat since late February on a publicly reachable Elasticsearch cluster. The cluster was co-hosted with Alinto's Cleanmail.eu secure-relay product — meaning every inbound mail flow for Alinto's roughly 10,000 enterprise customers passed through the same box. 4.5 million unique email addresses, more than 14,000 French government email accounts, and traffic for L'Oréal, Renault, Carrefour, Hermès, and DHL were indexed. The French press reports — Generation-NT, FrenchBreaches, Les Smart Grids, Économie Matin — confirm the records include message subject lines, not just envelope metadata. Alinto closed the bucket silently on February 26. It has issued no advisory and no customer notification. Cybernews, which discovered the exposure and disclosed today, wrote that "the potential attack surface becomes much bigger from the amount of client companies alone."

A spam filter read every subject line from 14,000 French government officials for two months. It did what spam filters do.

The backdoor marketed as end-to-end

On March 27, a class action (3:26-cv-02615, N.D. Cal.) was filed alleging that Meta employees and Accenture contractors had "broad access to the substance of WhatsApp messages that were supposed to be encrypted." The plaintiffs are Brian Y. Shirazi and Nida Samson, represented by Kessler Topaz Meltzer & Check LLP.

The claim's strongest factual anchor is the U.S. Department of Commerce Bureau of Industry and Security's July 2025 investigator's report — codenamed "Operation Sourced Encryption" — which documents interviews with Larkin Fordyce, a former Accenture content moderator in Austin, Texas, 2018–2022. Fordyce told agents that Meta moderators "eventually were granted their own access to WhatsApp" and that before direct access, "the Facebook team was able to pull whatever they wanted and then send it." Fordyce confirmed on the record to Bloomberg on January 29, 2026: "I felt that sharing what I knew with the government was beneficial to the United States of America."

Meta has called the claims "categorically false and absurd." Cryptographer Matthew Green wrote on February 2 that a universal plaintext-exfiltration backdoor "would be visible in WhatsApp's application code" and "would expose WhatsApp and Meta to exciting new forms of ruin." EPIC's Maria Villegas Bravo said she didn't see "any merit in this lawsuit." CDT's Nick Doty said he would be "very surprised if the claims are accurate."

The plaintiffs may not need to prove the strongest version of the allegation. The weaker version is already documented. ProPublica reported in 2021 that human moderators review plaintext copies of messages that are user-reported. The Intercept reported in 2024 that metadata — who writes whom, when, how long — flows even when content does not, enabling deanonymization through traffic analysis. Durov himself has acknowledged that roughly 95 percent of WhatsApp users store unencrypted iCloud or Google Drive backups outside the end-to-end envelope.

"End-to-end encrypted" on a closed-source client, run by a provider, on devices synced to third-party backups, with a human-moderation pipeline for reported messages, and a contractor pool reading the moderation queue, is not a mathematical guarantee. It is a trust architecture. Trust architectures fail not when the math fails, but when the contract underneath them changes hands.

The identity document that became a watchlist

On March 9, 2026, the U.K. House of Lords rejected Amendment 380 by 123 to 40. The amendment, tabled by Baroness Doocey, would have blocked the use of DVLA-held driver-licence photographs for facial-recognition searches under Clause 154 of the Crime and Policing Bill. The amendment failed. Fifty million driver-licence photographs are now available to police facial recognition by ministerial regulation, not primary legislation. Home Secretary Shabana Mahmood announced 40 new Live Facial Recognition vans on January 26, procured through BlueLight Commercial's £20 million BLC0168 framework with NEC, Digital Barriers, and Bedroq through March 2029. The Commons is considering Lords amendments today.

A driver's licence was never a policing credential. In 2026, it became one. The database did not change. Its use did.

The pattern

A registry maintained for civic convenience becomes a registry used for enforcement. A moderation pipeline built for reported content becomes a contractor reading private messages. A spam filter built for security becomes a subject-line index for espionage. A driver-licence photo archive built for identity verification becomes a facial-recognition watchlist. A Medicaid data warehouse built for benefits administration becomes a targeting feed for immigration enforcement.

Each system was designed for a narrow purpose by earnest people. Each was built once. Each is being used, now, for something its architects did not design.

The architectural reality is not that regimes are corrupt. It is that centralized data infrastructures are reassignable assets. They belong to whoever runs the agency, holds the contract, writes the regulation, or fires the next CTO. Their repurposing is a paperwork exercise. Their durability as weapons exceeds the durability of the protections that surrounded them at build time.

This is the underlying question in front of Tennessee's Senate today. It is also the question in front of the Texas attorney general, the UK Home Office, Meta's WhatsApp engineers, Alinto's infrastructure team, ICE's Palantir deployment, DOGE's SSA access, and every database in a jurisdiction where a new administration can rewrite the acceptable-use terms.

The counterarchitecture

There is a pattern break. It is not a policy fix. Policies are regime-dependent. The alternative is architecture that does not make lists.

Concretely:

  • Non-enumerable endpoints — not one provider's user database. Multi-party transport with no central account registry. URnetwork is one implementation; mixnets and overlay networks are others.
  • No linking identifier — resist the Aadhaar/SSN pattern. Selective-disclosure credentials using zero-knowledge proofs and verifiable credentials reveal only the attribute asked for, without the holder's identity.
  • Transport-layer privacy including envelope metadata — email's envelope leakage is a fifty-year-old architectural decision. Messaging protocols that hide sender, receiver, and timing patterns exist. They are under-deployed because the dominant providers earn from the data email leaks.
  • Self-custody of identity credentials — an identity system whose canonical copy lives on the user's device, not on a state server, cannot be retrieved by a mailing campaign.
  • Non-provider-trusted infrastructure — Matrix-based messengers run across 35 governments and 600,000 French civil servants because there is no single provider to coerce. Signal grew 67 percent year over year to 85 million monthly users; its Foundation closed 2024 at a deficit but donations trend is improving. Briar kept Iranian protesters connected through the January 8 national internet blackout over mesh Wi-Fi and Bluetooth alone.

Some of this is mature and deployable today. Some is less mature, especially for identity. The question is not whether a counterarchitecture exists. It is whether we keep building the next list on the same foundation, trusting the next administration to behave.

Close

The list was made before the law. The law is just the owner.

In Kansas, the owner changed in 2024 and the mailings went out in 2026. In Tennessee, the Senate voted today to give the owner new keys. In Texas, the Supreme Court ruled that an attorney general can reach through the door without a warrant. In Washington, federal filtering has been removed. In London, a driver's licence became a policing credential by regulation. In Meta's moderation queue, a contractor read the messages. In a Lyon data center, a spam filter read the subject lines.

The architectural question is whether we keep renting lists to the good administrations and hoping the next one is too.

Today, twenty-four senators in Nashville voted to rent the next one.


Sources (2)

Sources: Nashville Banner (April 14, 2026), Nashville Scene, Washington Blade, LegiScan HB 754 roll call, NBC News (February 28, 2026), KERA News (March 13, 2026), Missouri Independent (September 16, 2025), NPR (February 28, 2026), Ropes & Gray (HIPAA vacatur), TN AG press release (February 4, 2026), Bloomberg (January 29, 2026), EPIC / Matthew Green / CDT statements via Slashdot and Cybernews, Cybernews (April 14, 2026 on Alinto), Generation-NT / FrenchBreaches, Hansard (March 9, 2026 Lords), gov.uk (January 26, 2026 Home Office), Cybernews and 404 Media on Flock, The Block (April 9, 2026 on Storm), PCLOB 2023 and FISC April 2022 opinion, N.D. Cal. dockets 3:25-cv-05536 and 3:26-cv-02615, M-J-M-A v. Wamsley, Fourth Circuit en banc (April 10, 2026), Signal Foundation Form 990 FY2024. Individual per-topic research dossiers in this edition's blog-research directory.

Further Discussion

Every Database Is a Weapon Awaiting New Ownership

Kansas did not build a registry to revoke 1,700 driver's licenses. It used one it had kept quietly since 2019 to help trans residents amend their vital records. The protections changed hands. The data stayed. This is what centralized identity infrastructure actually does. It persists across administrations. It persists across purposes. The CMS Medicaid rolls built for benefits are now a targeting feed for ICE through Palantir ELITE. The DVLA's 50 million driver photos built for licensing are now a facial-recognition watchlist by ministerial regulation. Meta's moderation queue built for reported content became a contractor reading private messages. Every one of these systems was designed for a narrow, defensible use by earnest engineers. Every one of them is now being used for something its architects did not intend. The lesson is architectural, not political. You cannot protect a list by hoping its owner stays nice. You protect it by not making it. Non-enumerable endpoints. No central linking identifier. Selective disclosure with zero-knowledge proofs. Multi-party transport with no provider to compel. This is the stack URnetwork builds. It is the only kind of privacy that survives a change in management. **Key stat:** 1,700 — Kansas driver's licenses voided using a registry kept since 2019. **Urgency:** Tennessee Senate voted 24-7 today, April 14, to build a new one.

The Marker You Chose Became the Target They Needed

Every transgender Kansan who amended their gender marker to protect themselves in 2019 became a name on a 2026 mailing list. Every French government employee who used an Alinto email address had their subject lines read by a spam filter for two months. Every WhatsApp user who trusted the "end-to-end encrypted" label was, per the Shirazi complaint, having their moderation-flagged messages read by Accenture contractors in Austin. The "voluntary" in "voluntary disclosure" is collected under one legal regime and used under another. The "confidential" in "confidential filing" depends on which administration runs the archive. The "encrypted" in "encrypted by default" depends on who runs the provider. The ur.io network proposes a different default. Your identity is not a field. Your connection is not a user record. Your traffic has no provider to compel. The architecture refuses to produce what a new administration could later demand. Today, in Nashville, twenty-four senators voted for the other architecture — the one where your diagnosis, your dose, your provider, and your visit dates are reported to a state agency you did not choose. That vote will be reconciled. That bill will likely be signed. That list will join the ones that already exist. The question in front of the rest of us is whether the next list is worth the next regime. **Key stat:** $150,000 per clinic fine for non-reporting; 6-month license suspension. **Urgency:** Bill reaches Gov. Lee within days; Kansas mailings continuing.

Comics

#1Every Database Is a Weapon Awaiting New Ownership
#2The Marker You Chose Became the Target They Needed