SPEAKER_1: Alright, last time we established that a Glomar response isn't a standard denial — it's a refusal to confirm whether a record even exists. I want to get into the legal skeleton of that today, because I think that's where it gets complicated. SPEAKER_2: That's exactly the right place to go next. And the key insight from last time that carries forward is this: the Glomar doctrine requires the agency to prove that existence itself is the secret. That's a high bar — and it's the bar most state attorneys general quietly ignore. SPEAKER_1: So what statutes actually authorize a Glomar response at the state level? Because our listener — someone like Henk, who filed a consumer complaint and got silence for months — might be wondering what legal hook the AG's office is even hanging this on. SPEAKER_2: Right, and that's where it gets murky. There's no single state statute that says 'you may issue a Glomar response.' Instead, agencies invoke law enforcement exemptions or privacy exemptions baked into each state's public records law — the state equivalent of FOIA. They argue that acknowledging a record exists would itself reveal protected information, usually either an ongoing investigation or a third party's privacy interest. SPEAKER_1: But how does a closed consumer complaint qualify as an ongoing investigation? The complaint is closed. SPEAKER_2: Exactly — and that's the crack in the wall. The exemption is meant for active law enforcement proceedings. Once a complaint is closed, the investigative privilege is significantly weakened. Courts have pushed back on this. The agency would need to show that even confirming the record exists would expose something still sensitive — which, for a routine consumer complaint closure, is a very hard argument to make. SPEAKER_1: So how do courts actually evaluate whether the Glomar response was valid? Is there a formal test? SPEAKER_2: There is. Courts apply what's called a balancing test — they weigh the government's interest in withholding against the public's interest in disclosure. The agency has to submit something, often a sworn declaration, explaining why mere acknowledgment causes harm. If that explanation is vague or conclusory, courts can reject it. The burden is on the agency, not the requester. SPEAKER_1: That's interesting — the burden is on the agency. So for our listener, that means the AG's office has to justify the silence, not the other way around. SPEAKER_2: Precisely. And this maps onto something important from denial law more broadly. In insurance denial cases, for instance, courts have consistently held that the party issuing the denial bears the onus to prove it met all legal requirements — clarity, completeness, and proper notice of dispute rights. The same logic applies here. The AG can't just say 'Glomar' and walk away. They have to demonstrate the legal basis. SPEAKER_1: What does a valid denial actually require, then? Because I think most people assume any official-sounding letter is legally sufficient. SPEAKER_2: That assumption is dangerous. A proper denial — whether from an insurer or a government agency — must be unequivocal, provide reasons, and outline the recipient's right to dispute it. Courts have been explicit: ambiguous language doesn't start the clock on appeal windows. If the denial implies reconsideration is possible, or fails to explain dispute rights in plain language, it may not be legally valid at all. SPEAKER_1: So the months of delay before the Glomar response — could that actually work in our listener's favor legally? SPEAKER_2: It can, yes. If the denial is procedurally defective — missing required elements, unclear on its face, or failing to notify the requester of their challenge rights — the limitation period for filing an appeal may not have started running. The denial date has to be unambiguous for that clock to tick. Delay plus a defective response could actually preserve more legal options, not fewer. SPEAKER_1: Why would the AG's office treat a consumer complaint as something sensitive enough to warrant this level of protection in the first place? SPEAKER_2: A few possible reasons. One is institutional habit — these offices borrow federal intelligence-era tools without scrutinizing whether they fit. Another is that the complaint may touch a company the AG has a separate, ongoing relationship with. And a third, frankly, is that a Glomar response is easier to issue than a substantive explanation. It forecloses the conversation without requiring the office to justify its decision on the merits. SPEAKER_1: That third reason is troubling. It's not a legal shield — it's an administrative shortcut. SPEAKER_2: That's a fair characterization. And it's why successful challenges exist. There have been state court cases where Glomar responses were rejected precisely because the agency couldn't demonstrate that acknowledging the record's existence — not its contents, just its existence — would cause any concrete harm. The doctrine requires specificity. Generalized assertions of sensitivity don't clear the bar. SPEAKER_1: So what should our listener take away from all of this — what's the core legal insight that changes how they approach what happened to them? SPEAKER_2: The core insight is this: the legal justification for a Glomar response rests entirely on the premise that confirming a record's existence would itself reveal protected information. That's a precise, narrow claim — and it's one the agency must prove, not assume. For someone whose consumer complaint was closed and who received months of silence followed by a 'neither confirm nor deny,' the question to press is simple: what specific harm comes from acknowledging this record exists? If the answer is vague, the response is vulnerable.