Homeland Security Appears To Be Stalling On FOIA Requests Concerning Domain Seizures

from the violating-the-foia? dept

We're still waiting for the full response to our own Freedom of Information Act request concerning ICE's PSA (though, we have some more info on that which we'll be sharing soon). It's still well within the reasonable period of time to reply, and we've been told that progress is being made on the request, so that all sounds good. However, Michael Robertson passed along the news that back in January, he filed a FOIA request of his own, on behalf of his organization NakedGovernment.org, seeking any information and documents within ICE concerning the domain seizures found in "Operation in Our Sites."

Initially, as is fairly typical with FOIA requests, the ICE FOIA officials were responsive, friendly and helpful. Following a rather broad request, the FOIA official at ICE suggested that NakedGovernment narrow its request to documents concerning the domain seizures that are stored in the TECS (Treasury Enforcement Communications System) database. NakedGovernment also forked over the cash that ICE requested in order to conduct this search. At the end of March, ICE FOIA officials told NakedGovernment that they had received the check and "will begin processing your request and will respond..."

And that's all they wrote. Since the end of March, no additional response has been forthcoming, even though NakedGovernment has followed up with ICE requesting the status of the request. It's difficult to see how this request could possibly take more than two months to process. I'm hopeful that my (quite narrow) request won't take nearly as long. Update: Michael Robertson informs me that ICE has just indicated that it has obtained the documents in question, and they now need to "be processed" which will then be followed by a "supervisory review." So, keep waiting...


Reader Comments (rss)

(Flattened / Threaded)


Add Your Comment

Have a Techdirt Account? Sign in now. Want one? Register here
Get Techdirt’s Daily Email
Save me a cookie
  • Note: A CRLF will be replaced by a break tag (<br>), all other allowable HTML will remain intact
  • Allowed HTML Tags: <b> <i> <a> <em> <br> <strong> <blockquote> <hr> <tt>
Follow Techdirt
A word from our sponsors...
Essential Reading
Techdirt Reading List
Techdirt Insider Chat
A word from our sponsors...
Recent Stories
A word from our sponsors...

Close

Email This