Meta's 'A/C Priv' Hats and the Privilege Fight in Teen-Safety Cases

The Meta product team that built Instagram Teen Accounts ordered baseball caps embroidered with "a/c priv." The shorthand stands for attorney-client privilege, the rule that keeps confidential requests for legal advice private. The team worked under the internal name Project Nido. Instagram Teen Accounts launched in 2024. The caps came to light in the ongoing teen-safety litigation against Meta, as reported by The Verge.

Lawyers suing Meta say the hats point to a "culture of privilege abuse at Meta." That argument is now part of a wider fight over discovery, the court process in which each side must share relevant documents. The fight centers on internal discussions about youth safety, and on the line between legal advice and ordinary product decisions.

U.S. District Judge Yvonne Gonzalez Rogers has criticized some of Meta's decisions. She called certain privilege redactions "entirely inappropriate." Under federal rules, privilege is narrow. It covers confidential messages sent to seek or give legal advice. It does not cover underlying facts, product data, or business choices simply because a lawyer was copied.

In April 2025, Meta de-designated about 65,000 documents it had previously withheld or blacked out, returning them to discovery. Meta has asked for time through the end of this year to re-review other privilege claims in the teen-safety cases. Plaintiffs' lawyers have asked for a neutral reviewer, paid for by Meta, to lead that re-review.

The caps themselves do not settle any single privilege claim. A joke on a hat is not a record of why a document was withheld. In fights over privilege logs, which are lists explaining what was withheld and why, courts look closely at intent and process. Plaintiffs are pointing to the caps to question that process, and Meta is answering document by document.

This discovery dispute is one part of several related proceedings. A jury found Meta and YouTube harmed a young user through addictive design features linked to mental health distress, according to The New York Times. Meta agreed to pay $18 billion to settle U.S. lawsuits over children's social media addiction, according to Reuters. Meta Platforms lobbied the U.S. Congress for legal immunity from child-harm claims tied to social media products, according to Reuters. Meta and U.S. states discussed settling the teen social media harm case, according to Reuters.

The broader context here is familiar from three decades of covering enterprise software. Product teams and company lawyers now work in the same chats, ticket queues, and shared documents. Legal review starts early, especially on youth safety, privacy, and content policy. That closeness helps work move fast. It also creates confusion when privilege labels get added inside quick product discussions.

In my view, the number to watch is not the hats but the 65,000. A correction on that scale points to review rules that were drawn too broadly, or applied without clear guidance on business messages versus legal messages. Judges usually treat that kind of pattern as a breakdown in the system, not a few close calls. That is why the schedule matters. Who leads the re-review will shape what evidence the court eventually sees.

Looking at what this means for engineering and legal teams, the fix is practical. Privilege needs clear habits inside the tools people already use. Keep legal-advice threads separate from product-decision threads, note the legal purpose at the time, and have lawyers sample large document sets before they go out. Built that way, it does not slow product work. For readers who run those systems, retention settings, access controls, and default labels now show up as facts in court.

Worth flagging, a clear outcome here could help safety work get written down better. Teams could talk openly with lawyers while leaving facts, test results, and design choices available where the rules require it. That takes discipline about recording what was decided, why, and based on what evidence, without stamping routine product talk as privileged by default. Over time, that kind of record tends to support safer products and companies that can defend their choices.