The arrest, the data center, and the records fight that followed
A city-council meeting in Claremore, Oklahoma, should have been one of those familiar local-government scenes where a handful of residents gripe into a microphone, someone checks the clock and everybody goes home with only mild heartburn. Instead, in February, it became the opening scene in a much messier fight over a planned data-center campus tied to Project Mustang.
Darren Blanchard, a Claremore resident, showed up to argue against the project. He spoke, went a little past the time he’d been given, and then kept talking just long enough for the meeting to stop feeling like a meeting and start feeling like a problem. Police arrested him in front of the room.
A few extra seconds at a microphone can end up costing a lot more than anyone in the room expects.
The city responded with a trespassing charge under a local ordinance that carried a relatively small fine. Blanchard pleaded not guilty and treated the case as something bigger than a run-of-the-mill citation. In his telling, this wasn’t about a speaker who ignored the clock. It was about whether city officials could cut off public criticism of a data center, then use the criminal sequence to make a point about who gets to control the room.
That framing matters because data centers have become one of those civic flashpoints that rarely stay local for long. A project like Project Mustang sounds technical and dry on paper. In practice, it drags in land use, power and politics, water use, neighborhood anxiety and all the usual tensions that show up when tech news lands in a town hall instead of a product launch. The debate is about servers, yes, but also about who bears the costs and who gets to object when the project arrives.
Blanchard’s legal team answered the arrest with a records request. They wanted bodycam video from the arrest itself, along with records about earlier disturbances at public meetings. And they also asked for documents showing the city’s ties to security contractors and to Rogers State University, a combination that suggests they were trying to map out how the city managed public meetings before this one went sideways.
That’s where the dispute stopped being a simple criminal-defense file pull and turned into a public-records brawl. Claremore replied with a bill of roughly seventeen thousand dollars for the material, a number that tends to make people blink twice. For a request tied to a single arrest and a handful of related records. It was the sort of invoice that makes transparency feel less like a right and more like a luxury add-on.
The city’s price tag also gave the fight a second life. What began as a dispute over a protest at a council meeting was now a test of how far a local government can go when a resident wants the paperwork behind an arrest. That matters well beyond Claremore. In digital culture, and especially in power and politics, local clashes often spill into broader arguments about speech, policing, and access to government records. The tech angle here isn’t just the proposed campus itself. It’s the machinery around it, from security contractors to the records people need when they want to challenge what happened in public.
For Blanchard, the bodycam footage and related documents were part of the defense. And for the city. They apparently became a line item. That alone tells you how fast a civic dispute can mutate. One minute it’s a resident talking too long at a microphone. The next, the whole case’s about what the public can see, what it has to pay for and whether a city can make transparency expensive enough to discourage the asking.
The bill set up the next round of the fight.
How Claremore tried to justify the bill
The city’s answer to the records request came back less like a housekeeping note and more like a spreadsheet with a headache. Its lawyers said the real work wasn’t printing pages. It was review. Nearly 3,000 records, they said, had to be checked for material tied to the arrest, the city’s security setup, and the people who happened to be caught up in both.
That redaction step mattered in the city’s telling because public records can include information that does not belong in the public square quite so neatly. Names of private citizens can appear in complaints, witness statements, emails and meeting notes. City staff can show up too, and not every internal detail is meant to leave the file cabinet untouched. Claremore said the request would force staff to comb through the files one by one before anything could be released.
And the bill didn’t stop there. The city also added a search charge tied to roughly 15 hours of staff time, arguing that the request was broad enough to pull people away from normal duties. In other words, if clerks and lawyers had to stop everything to chase down the records, somebody had to pay for that interruption. That’s the city’s theory, at least. It treats the request less as a quick copy job and more as a drain on staff that the city shouldn’t have to absorb.
A records fee stops looking like cost recovery the minute it starts looking like a deterrent.
Claremore also seemed to suspect the request was designed to be expansive on purpose. The city’s response suggested the records would be spread widely online once released, which is probably not a shocking guess in a case that already mixed public comment, an arrest, and a data center fight. Once something like that hits a local agenda, the paperwork rarely stays in a folder for long. Still, expecting documents to travel fast’s one thing. Using that possibility to justify a bigger bill is another.
For Blanchard’s lawyers, that was the problem. They argued the city wasn’t trying to recover the cost of copying or even the cost of a narrow records search. It was, in their view, turning price into a barrier. That’s a different animal entirely. A genuine records fee is supposed to reflect what it costs to retrieve and prepare the files. A fee that feels like a wall starts to look less like administration and more like a warning shot.
Anyone who has spent time around Oklahoma open records law knows how quickly a simple request can grow teeth. The state’s open-records request guidance and one-page summary lay out the basic framework in plain English: access is the rule, but agencies still talk about copying, search time, and redaction with a straight face. The Public Access Counselor opinion sits in the same paperwork neighborhood, where fee disputes and access fights get translated into legal language after everybody else has already had enough.
That’s where Claremore’s reply landed. It leaned hard on the burden argument and tried to make the request look like an all-hands scramble rather than a routine public-records ask. Blanchard’s side saw something else: a records request fee that had become a pressure tactic, dressed up as bookkeeping.
What Oklahoma’s attorney general said instead
That’s where the state stepped in and, basically, told Claremore to put the calculator down.
An assistant attorney general rejected the idea that the city could bill a requester for whatever it wanted just because staff had to hunt through records and a lawyer wanted to take a look before release. Under Oklahoma’s open-records law, the city can recover direct costs tied to copying or mechanical reproduction. It cannot simply invent a search fee, pile on legal review time, and call the whole thing transparency with a receipt. The statute itself, in Title 51, is much narrower than the city’s invoice suggested, and that’s the heart of the dispute. Oklahoma’s open-records law does not give local governments a blank check.
Open-records law lets a city recover the cost of making copies. It does not let the city turn ordinary staff time into a profit center.
That distinction matters because Claremore had treated the public records request almost like a special project. The state’s response said, in effect, that this isn’t how open records are supposed to work. If a document can be copied, scanned, or otherwise mechanically reproduced, the city may charge for that. If the request requires someone to search, sort and pull files, the city has to point to a lawful basis for passing those costs along. And even then, the rules aren’t as loose as the city’s bill implied.
One problem for Claremore was procedural. The city had not posted the public fee schedule the law requires. Without that posted schedule, the state said, the city couldn’t lawfully shift search costs to the requester in the first place. That point may sound bureaucratic, but it’s the sort of detail that decides whether a public records request costs a few dollars or feels like a dare. The law is built around notice. If a city wants to charge for more than simple copying, the public’s supposed to be able to see the rate in advance, not discover it after the bill lands.
The attorney general’s office has said similar things before in its public-access counselor opinions, which is part of why Claremore’s position looked thin on paper. The city was not working from some obscure, brand-new theory. It was running into a fairly plain rule: open records may be released with limited fees, but agencies do not get to improvise extra charges because a request feels annoying or broad.
The state also pushed back on the city’s claim that filling the request would disrupt normal operations enough to justify the fee. That argument can work in some situations, but it needs evidence. The response said Claremore had not shown that the staff time involved would create the sort of serious disruption the law contemplates. In other words, “this will take a while” is not the same thing as “this will break city hall.” Governments are busy. That part is not a shock. But busy is not a legal standard.
There was another wrinkle, and it reads a little like a finance committee argument that wandered into a records case. Claremore billed search time at the city clerk’s rate, yet it had not explained why that was the proper rate if search time were chargeable at all. The attorney general’s position was that the city had not shown why a cheaper employee couldn’t handle the task. If the work is mostly locating files and checking them against the request, the law doesn’t automatically bless the highest hourly rate in the building. The city has to explain the choice.
That matters because public records disputes often turn on labor costs rather than photocopies. A request can be awkward, broad and time-consuming. It can even be the sort that makes a clerk sigh into a coffee cup. Still, Oklahoma’s rules don’t let a city use labor costs as a kind of soft veto. If the city wants to charge, it has to stay inside the statute and explain the math.
At the same time, the background here also helps. This all grew out of a public meeting, not a private grievance, and the meeting itself was the sort of thing that should be easy to document. Claremore city council agendas and minutes are posted online, which is as it should be for a local government wrestling with a proposed data center and an upset room full of residents. The public already had a stake in the conversation. That’s one reason the records fight landed so hard. It wasn’t a random fishing expedition. It was a request tied to a visible city proceeding, and the state’s answer treated it that way.
Read plainly, the attorney general’s response said Claremore had tried to add charges that Oklahoma law doesn’t clearly permit, then failed to justify the parts of the bill that might’ve needed justification. The city’s legal theory leaned on broad discretion. And the state answered with something a little less glamorous and a lot more useful: the rules are narrower than that.
Why the footage matters beyond one meeting
Claremore’s argument for holding back the bodycam footage came down to the setting as much as the arrest. City officials said officers recorded more than ten hours of video from the meeting, and they wanted a legal review before handing it over because the room was packed. That sounds tidy enough on paper. In practice, it can turn a routine records request into a waiting game, which is exactly where open-records disputes start to get sticky.
A public meeting is public for a reason. The camera doesn’t owe the room a curtain.
The state’s response cut straight through that logic. A public meeting room, the attorney general’s office said, isn’t the kind of place where people can expect privacy just because the seats are full and the tension’s high. If the city wanted to redact parts of the footage, it needed to point to an actual law that justified doing so. It didn’t. And without that legal hook, the argument for a prolonged review looked a lot thinner.
That matters because bodycam video’s often treated as if it belongs in some gray area between police work and public life. Sometimes it does. Footage from private homes, schools, or sensitive investigations can raise real concerns. A city council meeting is different. Once a crowd’s assembled to watch officials handle public business, the case for secrecy gets much harder to make. The attorney general’s position was basically: don’t turn municipal transparency into a scavenger hunt for excuses.
There’s also the time factor. The state said the footage should be released promptly, not parked in legal review limbo while everyone waits for a conclusion that may never arrive. That’s a familiar move in records fights. Delay can feel neutral, but it often works like a denial with softer edges. By the time the documents show up, the meeting’s old news, the video’s lost its immediacy, and the public’s moved on to the next flare-up.
Blanchard, for his part, is still fighting the trespassing charge that followed his confrontation with city officials. He says the arrest crossed a line into free-speech territory, and that claim is likely to keep the case alive long after the paperwork over the video is sorted out. The legal fight may seem narrow at first glance, but it sits right at the awkward intersection of protest and local power. Once someone’s arrested for pushing past their speaking time by a few seconds, the question stops being just about a city ordinance.
That question’s shown up elsewhere too. Public meetings in other states have already produced arrests tied to disputes over development projects, including data centers. Those fights often begin with zoning, noise, water, or traffic. Then someone gets removed, handcuffed, or charged and the argument widens fast. Protesters talk about being shut down. Cities talk about order. Police get pulled into the middle. Records requests follow. So do accusations that officials are hiding the ball.
For readers watching the Claremore dispute, that broader pattern may be the part that lingers. A data center proposal can be technical on its face, the sort of thing people usually expect to die in planning packets and engineer reports. Yet once a resident’s arrested during a council meeting and the city starts charging eye-watering fees for records, the story stops being about servers and zoning maps alone. It becomes a test of how much daylight a local government will allow when the room gets loud.
