throbber
Case 1:22-cv-00216-APM Document 1 Filed 01/27/22 Page 1 of 7
`
`IN THE UNITED STATES DISTRICT COURT
`OF THE DISTRICT OF COLUMBIA
`
`
`
`
`AARON GREENSPAN,
`
`
`956 Carolina Street
`
`
`
`San Francisco, CA 94107
`
`
`
`
`
`
`
`
`Plaintiff,
`
`
`
`
`
`
`v.
`
`
`
`
`
`
`
`
`
`
`U.S. SECURITIES AND EXCHANGE
`COMMISSION,
`
`
`
`100 F Street, NE
`
`
`
`Washington, D.C. 20549
`
`
`
`
`
`
`
`
`Defendant.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`COMPLAINT
`
`
`
`1.
`
`Plaintiff AARON GREENSPAN brings this Freedom of Information Act suit to
`
`force Defendant U.S. SECURITIES AND EXCHANGE COMMISSION (“SEC”) to produce
`
`various agency records regarding SEC’s investigations into a business founded by television
`
`personality Jim Cramer and other issues. In violation of FOIA, Defendant failed to issue a
`
`determination within the statutory deadline and failed to produce records responsive to the
`
`requests.
`
`PARTIES
`
`2.
`
`AARON GREENSPAN made the FOIA requests at issue in this case.
`
`GREENSPAN is a data journalist. He founded and operates the website PlainSite, an online
`
`platform created as an initiative to further legal transparency and anti-corruption by making
`
`government and business dealings more accessible and transparent to the general public.
`
`3.
`
`Defendant U.S. SECURITIES AND EXCHANGE COMMISSION (“SEC”) is a
`
`federal agency subject to the Freedom of Information Act, 5 U.S.C. § 552.
`
`
`
`

`

`Case 1:22-cv-00216-APM Document 1 Filed 01/27/22 Page 2 of 7
`
`JURISDICTION AND VENUE
`
`4.
`
`This case is brought under 5 U.S.C. § 552(a)(4)(B) and presents a federal question
`
`conferring jurisdiction on this Court. See 28 U.S.C. § 1331.
`
`5.
`
`Venue is proper under 5 U.S.C. § 552(a)(4)(B).
`
`APRIL 16, 2021 FOIA REQUEST (THESTREET.COM)
`
`6.
`
`On April 16, 2021, GREENSPAN submitted a FOIA request (the “First Request”)
`
`to SEC for records concerning CNBC anchor Jim Cramer’s business initiative, TheStreet.com.
`
`SEC’s acknowledgement letter that summarizes the First Request is attached as Exhibit 1.
`
`7.
`
`On June 15, 2021, SEC acknowledged receipt of the First Request and assigned
`
`reference number 21-01565-FOIA to the matter. Ex. 1.
`
`8.
`
`On June 21, 2021, SEC stated that it had identified “approximately 41 boxes” of
`
`records responsive to the First Request and asked GREENSPAN if he would be willing to
`
`narrow the scope of the Request. Ex. 2.
`
`9.
`
`On June 21, 2021, GREENSPAN asked whether SEC could provide the types of
`
`records it identified in its search so he could make an informed decision on narrowing the scope
`
`of the First Request. Ex. 3.
`
`10.
`
`SEC stated that it does not know what boxes contain which records. Instead, SEC
`
`asked GREENSPAN to identify specific types of investigation records. Id.
`
`11.
`
`On December 10, 2021, GREENSPAN sought an estimated date of completion
`
`for the First Request and asked SEC to provide a description of the records in each box so he
`
`could potentially narrow the scope of the First Request. Id.
`
`12.
`
`On December 13, 2021, SEC stated that it is not able to “determine the contents
`
`of the records that were located.” Id.
`
`
`
`- 2 -
`
`

`

`Case 1:22-cv-00216-APM Document 1 Filed 01/27/22 Page 3 of 7
`
`13.
`
`Further, in violation of 5 U.S.C. § 552(a)(7)(B)(ii), SEC failed to provide an
`
`estimated date of completion for the First Request. Id.
`
`14.
`
`As of the date of this filing, SEC has not issued a determination within twenty
`
`business days under 5 U.S.C. § 552(a)(6)(A)(i) and has not complied with the statutory
`
`requirement under 5 U.S.C. § 552(a)(3)(A) to make the records promptly available to any person.
`
`JANUARY 12, 2021 FOIA REQUEST (BRADLEY BONDI)
`
`15.
`
`On January 12, 2021, GREENSPAN submitted a FOIA request (the “Second
`
`Request”) to SEC for all emails to or from any sec.gov email address and Bradley Bondi
`
`(bbondi@cahill.com) or his assistant(s) on his behalf from January 1, 2020 to present. SEC’s
`
`acknowledgement letter that paraphrases the FOIA request is attached as Ex. 4.
`
`16.
`
`17.
`
`SEC assigned reference number 21-00677-FOIA to the matter. Id.
`
`Between May and August 2021, GREENSPAN and SEC conferred about the
`
`scope and status of the Second Request.
`
`18.
`
`On August 6, 2021, SEC stated that there are “approximately 3,761 pages of e-
`
`mail records” that are potentially responsive to the Second Request. Based on this information,
`
`GREENSPAN asked SEC to process “the first 32 hours” of the Second Request on the simple
`
`track and the rest on the complex track. SEC agreed to do so on August 6, 2021. Ex. 5.
`
`19.
`
`Having received no further correspondence from SEC, GREENSPAN sought an
`
`estimated date of completion for the Second Request on October 13, 2021. Id.
`
`20.
`
`On October 14, 2021, SEC stated that the estimated date of completion is
`
`“December 31, 2021” and will work towards issuing an “interim response” by November 12,
`
`2021. Id.
`
`21.
`
`On November 12, 2021, SEC stated that it is not able to make a partial release,
`
`but maintained that the estimated date of completion is December 31, 2021. Ex. 6 at 2.
`
`
`
`- 3 -
`
`

`

`Case 1:22-cv-00216-APM Document 1 Filed 01/27/22 Page 4 of 7
`
`22.
`
`On December 12, 2021, GREENSPAN asked whether SEC still plans to produce
`
`the records by December 31, 2021. Id. at 2.
`
`23.
`
`In response, SEC stated that the Second Request is “overly broad” and the results
`
`are “taking a significant amount of time to review.” SEC asked whether GREENSPAN would
`
`narrow his Second Request to by adding keywords such as, “Musk” or “Tesla.” Id. at 1.
`
`24.
`
`On December 22, 2021, GREENSPAN indicated that he does not wish to narrow
`
`the scope of the Second Request and asked SEC to provide all emails involving Bradley Bondi as
`
`stated in his original Second Request. Id. at 1.
`
`25.
`
`As of the date of this filing, SEC has not issued a determination within twenty
`
`business days under 5 U.S.C. § 552(a)(6)(A)(i) and has not complied with the statutory
`
`requirement under 5 U.S.C. § 552(a)(3)(A) to make the records promptly available to any person.
`
`OCTOBER 6, 2021 FOIA REQUEST (ROBOTS.TXT LINE 89)
`
`26.
`
`On October 6, 2021, GREENSPAN submitted a FOIA request (the “Third
`
`Request”) to SEC for records regarding https://www.sec.gov/robots.txt Line 89. SEC’s
`
`acknowledgement letter that paraphrases the FOIA request is attached as Ex. 7.
`
`27.
`
`By way of background, “robots.txt” is a file that is generally used to instruct
`
`search engines, such as Google and Bing, what not to index on a given website.
`
`28.
`
`In this particular incident, the SEC placed a line, which happens to be on the 89th
`
`line in the robots.txt file for the www.sec.gov website, instructing search engines to not index a
`
`previously visible press release concerning the charges of securities fraud filed against Elon
`
`Musk by the SEC in 2018.
`
`29.
`
`30.
`
`SEC assigned reference number 22-00028-FOIA to the matter. Id.
`
`On November 30, 2021, SEC stated that it is not able to respond to the Third
`
`Request within the twenty-day statutory time period due to “unusual circumstances.” SEC also
`
`
`
`- 4 -
`
`

`

`Case 1:22-cv-00216-APM Document 1 Filed 01/27/22 Page 5 of 7
`
`claimed that it identified “approximately 4.49 gigabytes (equivalent to approximately 269,400
`
`pages or 107.8 boxes) of emails that may be responsive” to the Request. Ex. 8.
`
`31.
`
` On November 30, 2021, GREENSPAN narrowed the scope of the Third Request
`
`to the “e-mail inbox and sent messages for whomever in OIT was and/or is responsible for
`
`maintaining the SEC’s robots.txt file.” Ex. 9 at 3.
`
`32.
`
`On December 10, 2021, GREENSPAN followed up with SEC whether it can
`
`conduct a narrower search based on the parameters he provided. Id. at 2.
`
`33.
`
`On December 13, 2021, SEC stated that it queried the program office regarding
`
`the narrowed search parameter. Id. at 2.
`
`34.
`
`Having received no further correspondence from SEC, GREENSPAN sought an
`
`estimated date of completion for the Third Request on January 14, 2022. SEC stated that it
`
`anticipates sending a response by January 21, 2022. Ex. 9 at 1.
`
`35.
`
`As of the date of this filing, SEC has not issued a determination within twenty
`
`business days under 5 U.S.C. § 552(a)(6)(A)(i) and has not complied with the statutory
`
`requirement under 5 U.S.C. § 552(a)(3)(A) to make the records promptly available to any person.
`
`COUNT I – APRIL 16, 2021 FOIA REQUEST (THESTREET.COM),
`SEC’S FOIA VIOLATION
`
`The above paragraphs are incorporated herein.
`
`The Request seeks disclosure of agency records and were properly made.
`
`SEC is a federal agency and subject to FOIA.
`
`Included within the scope of the Request are one or more records or portions of
`
`36.
`
`37.
`
`38.
`
`39.
`
`records that are not exempt under FOIA.
`
`40.
`
`In violation of 5 U.S.C. § 552(a)(6)(A)(i) and (a)(3)(A), SEC has failed to issue a
`
`determination and has failed to promptly produce records responsive to the First Request.
`
`
`
`
`
`- 5 -
`
`

`

`Case 1:22-cv-00216-APM Document 1 Filed 01/27/22 Page 6 of 7
`
`COUNT II – JANUARY 12, 2021 FOIA REQUEST (BRADLEY BONDI),
`SEC’S FOIA VIOLATION
`
`The above paragraphs are incorporated herein.
`
`41.
`
`42.
`
`43.
`
`44.
`
`The request seeks disclosure of agency records and were properly made.
`
`SEC is a federal agency and subject to FOIA.
`
`Included within the scope of the Request are one or more records or portions of
`
`records that are not exempt under FOIA.
`
`45.
`
`In violation of 5 U.S.C. § 552(a)(6)(A)(i) and (a)(3)(A), SEC has failed to issue a
`
`determination and has failed to promptly produce records responsive to the Second Request.
`
`COUNT III – OCTOBER 6, 2021 FOIA REQUEST (ROBOTS.TXT LINE 89),
`SEC’S FOIA VIOLATION
`
`The above paragraphs are incorporated herein.
`
`46.
`
`47.
`
`48.
`
`49.
`
`The request seeks disclosure of agency records and were properly made.
`
`SEC is a federal agency and subject to FOIA.
`
`Included within the scope of the Request are one or more records or portions of
`
`records that are not exempt under FOIA.
`
`50.
`
`In violation of 5 U.S.C. § 552(a)(6)(A)(i) and (a)(3)(A), SEC has failed to issue a
`
`determination and has failed to promptly produce records responsive to the Third Request.
`
`WHEREFORE, GREENSPAN asks the Court to:
`
`i.
`
`ii.
`
`
`iii.
`
`
`iii.
`
`
`
`
`
`
`
`declare that SEC has violated FOIA;
`
`order SEC to conduct a reasonable search for records responsive to the requests
`and issue determinations pursuant to 5 U.S.C. § 552(a)(3)(B)-(C) and (6)(A)(i);
`
`order SEC promptly produce all non-exempt records responsive to the requests or
`portions of the requests pursuant to 5 U.S.C. § 552(a)(3)(A);
`
`enjoin SEC from withholding non-exempt public records under FOIA pursuant to
`5 U.S.C. § 552(a)(4)(B);
`
`- 6 -
`
`

`

`Case 1:22-cv-00216-APM Document 1 Filed 01/27/22 Page 7 of 7
`
`iv.
`
`
`v.
`
`award Plaintiff attorney’s fees and costs pursuant to 5 U.S.C. § 552(a)(4)(E)(i);
`and
`
`award such other relief the Court considers appropriate.
`
`
`Dated: January 27, 2022
`
`
`
`RESPECTFULLY SUBMITTED,
`
`/s/ Matthew V. Topic
`
`Attorney for Plaintiff
`AARON GREENSPAN
`
`Matthew Topic, D.C. Bar No. IL 0037
`Merrick Wayne, D.C. Bar No. IL 0058
`Shelley Geiszler, D.C. Bar No. IL 0087
`LOEVY & LOEVY
`311 North Aberdeen, 3rd Floor
`Chicago, IL 60607
`312-243-5900
`foia@loevy.com
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`- 7 -
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket