{"efta_number": "EFTA00032104", "page_count": 18, "url": "https://epstein-data.com/EFTA00032104", "pdf_url": "https://epstein-data.com/pdf/EFTA00032104.pdf", "pages": [{"efta_number": "EFTA00032104", "page_number": 0, "text_content": "From: \" \n)\"  \nTo: ' \n(USANYS)\"  \nSubject: RE: Epstein search warrant documents \nDate: Fri, 10 Jul 2020 20:44:36 +0000 \nSo the estimate from BRG was for less than 30 days, and that was to do everything - extraction plus processing, and I \nthink extraction is the longer part of that. One we get an estimate from PAE, if it's longer than a few weeks to process, we \ncan go back to BRG and get an estimate on just processing (without extraction) and see what they say. I would guess it \nwould be something like a couple weeks. \n(As you can probably tell, I'm trying to catch up on emails from earlier this week!) \nFrom: \n(USANYS) \nSent: Wednesday, July 08, 2020 18:29 \nTo: \nSubject: RE: Epstein search warrant documents \nDo we know how long it would take BRG to do the processing? \nFrom: \nSent: Wednesday, July 8, 2020 5:56 PM \nTo: \n(USANYS) \nSubject: RE: Epstein search warrant documents \nThat's partially right but not completely — the BRG estimate is for dumping the devices but *also* processing all the data. \nThat is, converting all the Word, Excel, PDF, JPEG, BMP, PPT, etc etc files into a loadable file set for Relativity (specifically, \nconverting to TIFF and load files that can be uploaded). \nThat intermediate step is something that the FBI had told us they would do, but now are not doing, because they screwed \nit up so badly last time. So ordinarily we have PAE do the processing, but if they say it will take, say, three months, we can \ndo it faster through BRG. \nEither way we'll review in Relativity, though. \nFrom: \n(USANYS) \nSent: Wednesday, July 08, 2020 17:52 \nTo: \nSubject: RE: Epstein search warrant documents \nI thought the role we wanted BRG to play was the dumping of the devices — I had thought, perhaps incorrectly, that we \nalways planned to use Relatively to review once we were into them. Is that not the case? \nFrom: \nSent: Wednesday, July 8, 2020 5:26 PM \nTo: \n( USANYS) \nSubject: RE: Epstein search warrant documents \nEFTA00032104\n", "char_count": 1964}, {"efta_number": "EFTA00032104", "page_number": 1, "text_content": "=will \nhopefully be able to tell us within a few days whether it's very obviously incorrectly formatted. Then the next \ntest will be once it's on Relativity, and that will be an estimate by PAE (or BRG, if they can do it much faster). \nFrom: \n(USANYS) c\nSent: Wednesday, July 08, 2020 16:40 \nTo: \nSubject: Re: Epstein search warrant documents \nI think probably not if it seems like we're now ,etting what we need from FBI. When will we know if what FBI \ngave us today is correctly formatted - will \nbe able to tell us? \nSent from my iPhone \nOn Jul 8, 2020, at 3:48 PM, \n> wrote: \nHey, I held off on this after we got the update from FBI, but would it still be useful to do? Totally happy to if so, just \nwanted to check — thanks. \nFrom: \n(USANYS) \nSent: Thursday, July 02, 2020 19:15 \nTo: \nCc: \n(USANYS) \nSubject: RE: Epstein search warrant documents \nHave you run this budget/project by Ed yet? If not, would you mind doing so tomorrow or when you next can. Please \ncopy me and make clear it is on Epstein/Maxwell. Thanks. \nFrom: \n< \nSent: Thursday, July 2, 2020 5:11 PM \nTo: \n(USANYS) \nCc: \n(USANYS) \n> \nSubject: RE: Epstein search warrant documents \nFollowing up on the below, I think we've given this our absolute best efforts with FBI —they are now well over a month \nlater than their estimate from April on when we would get the New York materials, they're also past their estimate of \ngetting us the New York materials from just this Monday, and we don't have anything close to an estimate on the USVI \nmaterials, which constitute the overwhelming majority of the data and are vastly more voluminous than the New York \ndevices. We have kept pushing the timeline back for this option, hoping that CART will finalize, but I think at this point \nwe should have a vendor do it. \nAttached is an estimate we got from BRG, which would get everything to us in under a month, and in Relativity-friendly \nformat, in a range of $85-135K. BRG has done this for our office multiple times in the past and ar\n... [truncated, 2252 chars — for the full page use /api/corpus/document/EFTA00032104/1 or ?id=EFTA00032104&page=1]", "char_count": 2252}, {"efta_number": "EFTA00032104", "page_number": 2, "text_content": "From: \nSent: Tuesday, June 30, 2020 16:23 \nTo: '-. \n(NY) (FBI)' a;\n \n(USANYS) [Contractor] \nCc: \n(USANYS) <\n> \n(NY) (FBI) <->, \nI \n>; \n< \n(NY) (FBI) \n`.\n>; \n(USANYS) \nSubject: RE: Epstein search warrant documents \n> \nChecking in for the estimate of when we can expect to get all the USVI materials? \nthanks, \nFrom: \nSent: Monday, June 29, 2020 13:00 \nTo: \n(NY) (FBI) <\n>; \n(USANYS) [Contractor] <E\n> \nCc: \n(USANYS) c\n> \n. (NY) (FBI) < \n>; \n(NY) (FBI) \n(USANYS) \nSubject: RE: Epstein search warrant documents \nOkay thanks — good luck with the cardiologist! And if you can let us know tomorrow that would be great. Thanks again. \nFrom: \n. (NY) (FBI) <\n> \nSent: Monday, June 29, 2020 12:59 \nTo: \n(USANYS) [Contractor] <\nCc: \n(USANYS) \n(USANYS) \nSubject: RE: Epstein search warrant documents \n. (NY) (FBI) < \n(NY) (FBI) \nWhen Pm in the office tomorrow, I will be better able to estimate. Pm at my cardiologist right now. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Jun 29, 2020 12:56 PM, \" \n< \n> wrote: \nGreat, thanks. Is there even a rough estimate of when we will get the USVI materials? Or an estimate of when you'll be \nable to see how many items to export, so we'll have a better sense of when we'll get those? \nFrom: \n. (NY) (FBI) <\n> \nSent: Monday, June 29, 2020 12:55 \nTo: \n(USANYS) [Contractor] <\nCc: \n(USANYS) \n. (NY) (FBI) < \nEFTA00032106\n", "char_count": 1365}, {"efta_number": "EFTA00032104", "page_number": 3, "text_content": ") <->; \n) czi\n; \n(NY) (FBI) \n>, \n(USANYS) <\n7; \nSubject: RE: Epstein search warrant documents \nYep \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Jun 29, 2020 12:52 PM,' \n< \n> wrote: \nOkay, and I'm sorry to ask again, but to make sure, in this production, you're sending us new versions of what you \npreviously sent? \nFrom: \n. (NY) (FBI) <\n> \nSent: Monday, June 29, 2020 12:50 \nTo: \n(USANYS) [Contractor] <\n>; \nCc: \n(USANYS) \n) \nse\nM>; \n(USANYS) \nSubject: RE: Epstein search warrant documents \n. (NY) (FBI) < \n(NY) (FBI) \nYou are getting both NY and USVI. The biggest stumbling block are the newer Mac items that are in APFS \n(there are a bunch from the Island,) so it is difficult to estimate how long those will take until I see how many \nitems I have to export. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Jun 29, 2020 12:40 PM,' \ny. < \n> wrote: \nOkay thanks, and just to clarify, a few days to finalize the New York materials, and then what about the USVI materials? I \nthink that is quite a bit more. Just looking for an estimated completion date for everything. \nAnd on my other question — does this mean you're giving us a new, complete copy of everything from both NY and \nUSVI? \nthanks, \nFrom: \n. (NY) (FBI) <\n> \nSent: Monday, June 29, 2020 12:34 \nTo: \n(USANYS) [Contractor] <\n:,; \nCc: \n(USANYS) \n(NY) (FBI) c \n>; \n(NY) (FBI) \n(USANYS) \nSubject: RE: Epstein search warrant documents \nEFTA00032107\n", "char_count": 1441}, {"efta_number": "EFTA00032104", "page_number": 4, "text_content": "I am in the process ofAtoorting the materials (documents, spreadsheets, emails, etc) for your review as per \nmy discussions with =. \nMost of the NY stuff is done, just Mac items left. This might take a few days as 1 \nitem in particular has over 500,000 emails. We will be able to provide discovery once Defense Council has \nprovided drives for us to copy items over to. This goes quicker as there is no processing involved. I'll let you \nknow when everything is complete. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Jun 29, 2020 11:03 AM, ' \n> wrote: \nFollowing up on this, I understand from \nthat she was able to provide you with a 12 TB drive last week — could you \nplease let us know when we will be able to get the materials? I expect a judge will ask us about discovery as early as this \nweek. \nAlso, the related critical question that I don't think we have clarity on is whether you're giving us a copy of everything \nthat was collected (including reproducing the materials that you previously gave us, but which are not searchable), or \nhave you and \nfigured out a way to categorize the prior productions so they're useful for us? We would strongly \nprefer to just get everything at once in a usable format, but please let us know if you expect to produce materials \ndifferently than that. \nthanks, \nFrom: \n. (NY) (FBI) <\n> \nSent: Friday, June 19, 2020 13:14 \nTo: \n(USANYS) [Contractor] <\n>; \n• \nCc: \n(USANYS) \n) \n(USANYS) \nSubject: RE: Epstein search warrant documents \n. (NY) (FBI) < \n(NY) (FBI) \nWe are going every other day now, ramping up to 75% week after next. I need drives to put things on like \nand I discussed earlier. Once I have those drives, it will take me a couple days to copy stuff. LMK when I can \nexpect the drives. Thanks. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Jun 19, 2020 1:09 PM,' \n< \n> wrote: \nfollowing up on the below — please let us know? Given case developments in recent days, this has become \nurgent. Thanks. \nEFTA0003\n... [truncated, 2005 chars — for the full page use /api/corpus/document/EFTA00032104/4 or ?id=EFTA00032104&page=4]", "char_count": 2005}, {"efta_number": "EFTA00032104", "page_number": 5, "text_content": "From: \nSent: Wednesday, June 17, 2020 14:28 \nTo: \n(NY) (FBI) \n(USANYS) [Contractor] \nCc: \n. (NY) (FBI) •:\n>: \n`1\n›; \n \n); \n(NY) (FBI) <\n=,•; \n(USANYS) \n(USANYS) \nSubject: RE: Epstein search warrant documents \n<\nM> \nWanted to circle back on this and check in, particularly because we desperately need to get the results from the July and \nSeptember searches before moving forward with possible additional charges in the case. I know you had mentioned you \nneeded to push back your prior estimate of complete production by early June, by a couple weeks, so wanted to see \nwhat the current estimate is? I don't think we've started to get anything yet but please correct me if I'm wrong. \nthanks, \nFrom: \n. (NY) (FBI) <\nM> \nSent: Monday, June 01, 2020 16:28 \nTo: \n(USANYS) [Contractor] <a; \nCc: \n. (NY) (FBI) <\n>; \n> \nSubject: RE: Epstein search warrant documents \nWill do. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \n(NY) (FBI) <\nM> \nOn Jun 1, 2020 4:26 PM,' \ny. < \n> wrote: \nUnderstood, and thanks for letting us know. Let's keep in touch both on timing and also on whether there's a way to \nidentify and categorize what's already been produced, or if we'll need to just get all the raw data at this stage and go \nfrom there. \nFrom: \n. (NY) (FBI) <\nM> \nSent: Monday, June 01, 2020 16:23 \nTo: \n(USANYS) [Contractor]\nCc: \n(NY) (FBI) ic=\n> \nSubject: RE: Epstein search warrant documents \n(NY) (FBI) \nUnfortunately, recent events and our staffing levels have conspired to put a kink in just about everything. If we \ncan't make heads or tails of the stuff I've already produced, we'll do it again. They have told us that our staffing \nlevels will be steadily increasing over the next few weeks, but I'm going to have to push back my estimate by a \nEFTA00032109\n", "char_count": 1770}, {"efta_number": "EFTA00032104", "page_number": 6, "text_content": "week or 2. Sony about that. My next day in the office is Thursday, so Ill be able to see if I can easily identify \nwhat I already gave you and many it to a reliable identifier. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Jun 1, 2020 4:13 PM, \" \n)\" < \nThanks for this update — we'll take a look and circle back if any questions. \n> wrote: \nSeparately, to follow up on a question from the May 15 email below, the list has just five devices as still pending to be \ntransferred to us, and I think it's right that the plan is to reproduce all the materials so that we can get them in \nsearchable format, but just wanted to confirm? Currently, we aren't able to match any of the prior productions to \nspecific devices — so if we're able to match them up by Bates number now, that might work, but otherwise I think it \nmakes sense for us to get everything. But let us know if any issue with that. \nAnd related to that question, are we still on track to get the full range of data in the next week or so? I don't think we've \ngotten any updates on that status in the past few weeks, and we're eager to be able to start reviewing. \nthanks again, \nFrom: \n. (NY) (FBI) <\n> \nSent: Friday, May 29, 2020 12:53 \nTo: \n> \nCc: \n<\n)'; \n(NY) (FBI) < \nSubject: Re: Epstein search warrant documents \n>; \n(USANYS) [Contractor] \n(NY) (FBI) <\nEM> \nUpdated item descriptions. Just a side note, many thumb drives and SD cards will not have a serial number \nvisible externally, but will report one through our tools. I included those electronically reported serial \nnumbers. Any questions, let me know. \nFBI NY CART Coordinator \nSenior Examiner \nFrom: \n) \nSent: Friday, May 15, 2020 4:11 PM \nTo: \n(NY) (FBI) <le \nCc: \nC \n(USANYS) [Contractor] \n(NY) (FBI) < \n>; \nSubject: RE: Epstein search warrant documents \n(NY) (FBI) <\n> \nEFTA00032110\n", "char_count": 1829}, {"efta_number": "EFTA00032104", "page_number": 7, "text_content": "Thanks for this, it's a helpful start. In terms of being able to write our search warrant, one additional piece of \ninformation we need is the serial number, or some other specific identifier, ideally for each device but at least for any \ndevice that there is more than one of the same thing. So for example, we need to be able to somehow differentiate the \nfollowing devices — \nThe two Dell power edge T310 hard drives (NYCO24323 and NYCO24324) \nThe two Sony Vaio laptop / Fujitsu hdd (NYCO24336 and NYCO24337) \nthe following loose storage devices: \no Micro SD card (NYCO24339) \no Flash Drive (generic) (NYCO24340) \no Thumbdrive (Emtec) (NYCO24341) \no hard drive (loose) (NYCO24342) \no verbatim thumbdrive (NYCO24343) \nThe four San Disk cruzer-thumbdrives (NYCO24344-47) \nThe three Seagate IDE hard drives (NYCO24348-50) \nThe camera SD card (NYCO24351) \nI think the rest of the devices are either specifically distinguishable and/or have an S/N listed. (By comparison, the USVI \nspreadsheet we have lists an s/n for about 20 of the 25(ish) devices. \nThe other thing we're looking for is the location in the house (and ideally specific location) for each device, which the \nUSVI list also has — is that info available? \nThe list also has just five devices as still pending to be transferred to us, and I think it's right that the plan is to reproduce \nall the materials so that we can get them in searchable format, but just wanted to confirm? Currently, we aren't able to \nmatch any of the prior productions to specific devices — so if we're able to match them up by Bates number now, that \nmight work, but otherwise I think it makes sense for us to get everything. But let us know if any issue with that. \nthanks very much, \nFrom: \n. (NY) (FBI) < \nSent: Thursday, May 14, 2020 15:54 \nTo: \n(USANYS) [Contractor) \nCc: \n>; \n(NY) (FBI) < \nSubject: Re: Epstein search warrant documents \n(NY) (FBI) <\n> \n>; \nHere is The listing of all the evidence gathered in NY that I have. I added some columns to guid\n... [truncated, 2738 chars — for the full page use /api/corpus/document/EFTA00032104/7 or ?id=EFTA00032104&page=7]", "char_count": 2738}, {"efta_number": "EFTA00032104", "page_number": 8, "text_content": "FBI NY CART Coordinator \nSenior Examiner \nFrom: \n) <\n> \nSent: Wednesday, May 13, 2020 12:25 PM \nTo: \n(NY) (FBI) \n(USANYS) [Contractor] \nCc: \n) \n(NY) (FBI) <->; \n(NY) (FBI) < \nSubject: RE: Epstein search warrant documents \nRespectfully, I think there are some miscommunications here — all we have asked is to receive the materials in a format \nsuch that we can view them using a system we have access to. We're not able to get web-enabled access through any \nFBI tool, so we asked for the materials to be transferred in a loadable format so we could put them on Relativity, which \nboth we and the agents can access. We're required to have the files in a format that we can produce them to defense \ncounsel. I've done that in many other cases and it hasn't previously been an issue. My understanding from \nis that \nthe best way to do it now is just for us (the U.S. Attorney's Office) to get the original files, which our vendor will process \n—by which I just mean converting into file formats that are loadable onto Relativity. It doesn't really have anything to \ndo with the taint review—we have to have access to the docs in our systems for discovery purposes. \nAnd we were happy to get the materials as they were processed, but when we received the 1.1 million documents \nearlier this year, they were in a format that wasn't usable for the reasons described in the email I sent on March 9. \nAgain, I understand from =I that the best way forward is to just get copies of the materials in their original formats, \nwhich I understand will be segregated and designated by device. That should work for us! I was just trying to \nunderstand the approach, as well as the timeline. \nthanks, \nFrom: \n. (NY) (FBI) <\n> \nSent: Tuesday, May 12, 2020 13:03 \nTo: \nCc: \n>; \n(NY) (FBI) <->, \nSubject: Re: Epstein search warrant documents \n>; \n(USANYS) [Contractor] \n(NY) (FBI) c \nJust to be clear. The US Attorney's Office (or it's contractors) are not \"processing\" anything. You are taking files \nthat I will be ext\n... [truncated, 2669 chars — for the full page use /api/corpus/document/EFTA00032104/8 or ?id=EFTA00032104&page=8]", "char_count": 2669}, {"efta_number": "EFTA00032104", "page_number": 9, "text_content": "Sorry it has taken so long, but we are talking about terabytes worth of data over multiple forms of digital \nevidence. Phones, tablets, loose media, cameras, DVRs, servers, laptops, and desktop computers. We have \ngotten past encryption on multiple devices. When we review devices on such large cases, we usually do it \npiece by piece as things are processed, I was unaware that you didn't want to review as things were \nprocessed, that you wanted to do it \"all at once\", so that added to the delay. Sorry for that. Just a \ndifferentiation of methodology I suppose. \nand I feel confident that the method we have come up with will be more consistent and preserve the \nattribution of files to devices and links of e-mails to attachments that the load file generation that I did a while \nback was lacking. \nFBI NY CART Coordinator \nSenior Examiner \nFrom: \n) < \nSent: Tuesday, May 12, 2020 11:33 AM \nTo: \n(NY) (FBI) <\nM>: \nCc: \nSubject: RE: Epstein search warrant documents \n(USANYS) [Contractor] \nOkay, so just to check, you both think that there is not a need to do a test run? You're both comfortable with just \nbasically sending us copies of everything? I don't totally understand why we couldn't have done that eight months ago, \nbut regardless of the passage of time, I want to make sure we understand so we can report to our supervisors. I assume \nthat means that we (at the U.S. Attorney's Office and through contractors) will therefore need to do all the processing \nourselves, correct? And thanks again to you both. \nFrom: \n. (NY) (FBI) <\n> \nSent: Tuesday, May 12, 2020 11:30 \nTo: \n(USANYS) [Contractor] \nCc: \nc\n.>; I\nSubject: RE: Epstein search warrant documents \nLike \nsaid in his earlier email. It will be the raw data and it will be marked so it is easier to attribute it to a \nparticular device. Problem now is how to get the data to \nsince he is teleworking. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn May 12, 2020 11:15 AM,' \n< \nI have no doubt you do, but can you pl\n... [truncated, 2064 chars — for the full page use /api/corpus/document/EFTA00032104/9 or ?id=EFTA00032104&page=9]", "char_count": 2064}, {"efta_number": "EFTA00032104", "page_number": 10, "text_content": "From: \n. (NY) (FBI) <\n> \nSent: Tuesday, May 12, 2020 11:11 \nTo: \n(USANYS) [Contractor] <\nCc: \nSubject: RE: Epstein search warrant documents \n> \nI will use the spreadsheet, no problem. \nand I ironed out all the details. We've got a good plan moving \nforward that will meet your needs. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn May 12, 2020 10:34 AM, ' \n< \nwrote: \n, it would be very helpful for us if you could please use the attached spreadsheet in transmitting that info so we \nmake sure we get all the info we need. I think you had previously sent us a list of certain information that unfortunately \nwasn't helpful for us, so we want to make sure we're all on the same page. \nIn terms of data transfer, \nare you just sending a literal copy of all the raw data, and we'll process and upload it \non our end? I ask to make sure we don't lose any searchability — when FBI sent versions before, it had already been \nprocessed. I think what we talked about on the phone a month ago was getting, for example, data from one device to \nmake sure it transfers correctly, before sending over literally everything — is that still the plan? \nthanks, \nFrom: \n(USANYS) [Contractor] \nSent: Tuesday, May 12, 2020 10:27 \nTo: \nCc: \n(NY) (FBI) <\n> \nSubject: RE: Epstein search warrant documents \nHello M, \nMe and \njust finished our phone call regarding the data. \nwill put together a list of the all of the data \nand where the data was collected. I will work to send some hard drives to \nso he can begin to copy the data and \nsend it to us. I will need to figure out a way to get the data off of the hard drives. \nPlease let us know if there are any questions. \nThank you. \nFrom: \nI < \nSent: Friday, May 8, 2020 2:15 PM \nTo: \n(NY) (FBI) \n(USANYS) \nI (NY) (FBI) <->, \n(USANYS) \nCc: \n(USANYS) [Contractor] < \n4:\n>; \nEFTA00032114\n", "char_count": 1831}, {"efta_number": "EFTA00032104", "page_number": 11, "text_content": "(NY) \n(FBI) < \nSubject: RE: Epstein search warrant documents \nOkay thanks — please do let us know if at any point that changes, otherwise we'll look forward to being able to review \nthe returns in early June. Thanks again. \nFrom: \n. (NY) (FBI) <MME\n> \nSent: Friday, May 08, 2020 14:14 \nTo: \n(USANYS) \n(NY) (FBI) < \n(USANYS) < \nCc: \n(USANYS) [Contractor] <\n>; \n<\nM>; \nfl\n \n(NY) \n(FBI) ‹\n> \nSubject: RE: Epstein search warrant documents \nThere has been talk of us returning to normal soon, so I don't think it will effect the timeline I initially gave \nyou. If it does, I'll let you know. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn May 8, 2020 1:58 PM, \" \n< \nwrote: \nUnderstood, thanks—it will be great to get that list on Thursday. As a refresh, the info we are looking for is in the \nattached spreadsheet template. \nOn the returns themselves, do the changes you mentioned mean that the estimate of a month from now for complete \ntransmission of the search warrant returns is no longer likely? If so could you please let us know what the current \nestimate would be, so we can factor that in? Thanks very much. \nFrom: \n. (NY) (FBI) <E\n> \nSent: Friday, May 08, 2020 13:50 \nTo: \n(USANYS)\n(NY) (FBI) c\n>; \n(USANYS) \nCc: \n(USANYS) [Contractor] <\n>; \n<\nM>i \n(NY) \n(F80 <\n> \nSubject: RE: Epstein search warrant documents \nSony for the delay, they reduced us to 1 day a week, so things have been stretched out by a factor of 5. I will be \nback in the office on Thursday and will be able to get you the list then as I have to access some of our systems \nto do so. \nAlso, \n, please reach out to me at one of the numbers below so we can brain storm. Thanks. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \nEFTA00032115\n", "char_count": 1733}, {"efta_number": "EFTA00032104", "page_number": 12, "text_content": "desk \nOn May 8, 2020 12:10 PM, \" \nI/ < \nwrote: \nFollowing up on the below, I think you had said you expected to be able to get us a list of the devices seized from the \nsearch warrants at Epstein's residences in New York and the USVI, as well as from his person upon arrest, in about a \nmonth (during our conference call a month ago) — so wanted to check if we can still expect that very soon? We're \nwaiting on that list to be able to do an updated search warrant on all of those devices. Please let us know the current \ntimeline — and also the current timeline on producing the results from those August and September searches? I think \nyou and I= \nwere going to coordinate on that, and you had mentioned you expected we'd have it a couple months \nfrom our call, which would be about a month from now. Wanted to make sure we're still on track. \nthanks, \nFrom: \n(NY) (FBI) \nSent: Tuesday, April 07, 2020 15:27 \nTo: \nCc: \n. (NY) (FBI) <\nI>; \n(USANYS) \n(USANYS) [Contractor] <\n>; \n(NY) \n(FBI) <\nEM> \nSubject: RE: Epstein search warrant documents \n(USANYS) .ca \nOk let's plan on 11am tomorrow morning, I am trying to get an FBI line with a larger capacity but I won't know until \ntomorrow am. I will push it out when confirmed. \nThanks \nFrom: \n) [mailto: \nSent: Tuesday, April 07, 2020 3:15 PM \n(NY) (FBI) <\n>; \n. (NY) (FBI) <\n>; \n(USANYS) [Contractor] \nTo: \nCc: \n(USANYS) < \n>; \n(USANYS) \n< \n. (NY) (FBI) <\n=> \nSubject: RE: Epstein search warrant documents \n) \nYes, I can do anytime tomorrow, and \ncan also join anytime tomorrow. So whenever is good on your end. \nAlso, we can host a conference call, but only up to six lines at a time — so if FBI has larger capacity than that let us know, \notherwise I'd propose we do: \n1) \n2) I= \n3) I= \n4) MI \n5) \n/MI \n6) \n/ \n, if either of you wants to join (and if not, one of \nEFTA00032116\n", "char_count": 1829}, {"efta_number": "EFTA00032104", "page_number": 13, "text_content": "From: \n(NY) (FBI) < \nSent: Tuesday, April 07, 2020 14:13 \nTo: \n(USANYS) < \n(NY) (FBI) <->; \n(USANYS) \nCc: \n(USANYS) [Contractor] <->; \n(FBI) <\n> \nSubject: RE: Epstein search warrant documents \nAre vou available tomorrow for a conference call to discuss this issue? \nSSA MI \nFBI New York \nOn Apr 7, 2020 1:55 PM, ' \n(NY) \nwrote: \nFollowing up on this from a month ago — I know we're living in a different world than what existed four weeks ago, but \nare you at all able to assist while working remotely? This has been pending for almost two months and we still don't \nhave a very basic list of each device or item that was seized and searched, or for which of those we've received \nmaterials. We're happy to have a call if that would be useful, but as a first step the most basic thing we're looking for is \nthe info in the template spreadsheet we sent earlier (that's also attached). \nthanks, \nFrom: \nSent: Monday, March 09, 2020 12:00 \nTo: \n(NY) (FBI) cffi, \n \n(USANYS) .<\n>: \nI (NY) (FBI) <->; \n(USANYS)\nCc: \n(USANYS) [Contractor] < \n, \n4:\n>; \nc\n''; \n(NY) \n(FBI) \nSubject: RE: Epstein search warrant documents \nUnfortunately I don't think this is very helpful to us. Did you take a look at the example spreadsheet I sent on 2/24? The \nexcel file you sent has descriptions that don't match up to the items listed in the search warrant returns (that we sent on \n2/23), and we don't have the 1B or CART numbers to be able to cross-reference. We also can't tell what you mean by \n\"loose media\" without a specific comparison to what was seized, we don't know which items you're referring to as \n\"Windows machines,\" and we can't tell whether the entirety of any particular item has been transferred, or just partial. \nFor example, it looks like we have gotten very, very few image files, which is surprising. \nWe have also encountered some very significant problems in trying to review the more than 1 million documents we \nrecently received: \nThe data we've received has no way to put any emails and att\n... [truncated, 2297 chars — for the full page use /api/corpus/document/EFTA00032104/13 or ?id=EFTA00032104&page=13]", "char_count": 2297}, {"efta_number": "EFTA00032104", "page_number": 14, "text_content": "The load file has no link to the native file, so when we load the data to the database, there's no way to have the \nnative files show up in the database. Because many of the files are too large to open in the viewer, it effectively \nmeans that there are many files that are completely invisible to us. \n- \nRelated, the control numbers in the load file don't match up to the native files. So we have two sets of \nnumbers and no way to match up anything—that is, even if we were to try to go hunt down every individual \nlarge file in the native files, it would be impossible. \nSo the data that we most recently got, we need to get in a form that addresses those issues, and we likely will need to \nget a similar reproduction of the data we received a couple months ago. Otherwise we're sifting through more than a \nmillion documents without much rhyme or reason. \nI've re-attached the spreadsheet we sent last week — I think that's a good place to start in terms of our necessary record-\nkeeping, and we need that info at the very least, as well as anything else you think would be useful. Also attaching the \nSW returns for reference. And again, we're happy to meet up anytime and hash all this out in person if that's useful. \nthanks, \nFrom: \n. (NY) (FBI) <\n> \nSent: Wednesday, March 04, 2020 16:36 \nTo: \n(NY) (FBI) <->; \n(USANYS) \nCc: \n(USANYS) [Contractor] <\n>; \n(FBI) < \nSubject: RE: Epstein search warrant documents \n(USANYS) \n(NY) \nHere is a listing of what I have already handed over in load files to the US Attorney's Office for taint review. Some points \nof clarification: There were 9 IDE hard drives found in the Manhattan apartment, they turned out to be 3 copies of 3 \ndrives (9 drives in total) from a July 2007 search on one of his properties. I only processed 3 (as they were all copies). All \nthe loose media from the NY apartment is included. All the Windows machines from the NY apartment are included. \nOnly 2 Macs from NY and 1 from the Island are included. \nI will have to more c\n... [truncated, 2474 chars — for the full page use /api/corpus/document/EFTA00032104/14 or ?id=EFTA00032104&page=14]", "char_count": 2474}, {"efta_number": "EFTA00032104", "page_number": 15, "text_content": "I could do Thursday morning, but I think it would be helpful for us to get the accounting in advance of the meeting so we \ncan figure out in advance what (if any) additional steps we need — is that possible? \nFrom: \n. (NY) (FBI) <\n> \nSent: Tuesday, March 03, 2020 09:59 \nTo: \n(USANYS) \nCc: \n(NY) (FBI) < \n(USANYS) \n(USANYS) [Contractor] \n(FBI) < \nSubject: RE: Epstein search warrant documents \n(NY) \nCan we do Thursday morning? My network should be back by then and I can give you a good accounting. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Mar 2, 2020 11:15 AM, ' \nDoing the weekly check in on this — is there a time this week when everyone can meet on this? \nthanks, \nFrom: \nSent: Monday, February 24, 2020 17:38 \nTo: \n(NY) (FBI) \n(USANYS) \nI (NY) (FBI) <—>; \n(USANYS) \nCc: \n(USANYS) [Contractor] <\n>; \n<\n>*, \n(FBI) \nSubject: RE: Epstein search warrant documents \nwrote: \n(NY) \nTotally understand about the network issues—we can relate. I do still think it will be helpful to all sit down together to \nhave an in-person discussion, to make sure everybody is on the same page. Are folks available for that next week? And \nwhat I think would be most helpful to facilitate that would be a spreadsheet of each separate device referenced in the \ntwo search warrant returns, with columns for whether we've dumped the contents, whether they've been reviewed \nand/or transferred, what portions were transferred, etc. \nSomething roughly like the attached, with any other categories you think would be useful — and the info on the attached \nis mostly hypothetical, obviously, just as examples. That will help us fully understand what's been reviewed, transferred, \nand received so far, and what remains. \n(Also just on the pictures, we do want copies of those as well, please including from the discs and the devices — I think \nFBI was going to do an initial screen to make sure no CP, and since I think the answer was no, we'll need to get those to \nbe able to review them as well.) \nm\n... [truncated, 2026 chars — for the full page use /api/corpus/document/EFTA00032104/15 or ?id=EFTA00032104&page=15]", "char_count": 2026}, {"efta_number": "EFTA00032104", "page_number": 16, "text_content": "From: \n. (NY) (FBI) <\n1], \nSent: Monday, February 24, 2020 09:24 \nTo: \n(USANYS)\n) \n(NY) (FBI) c\n>; \nCc: \n(USANYS) [Contractor] <\n>; \n(NY) \n(USANYS) \n(FBI) <a' \nSubject: RE: Epstein search warrant documents \n< \nSony for the delayed response. They are tearing out our old network and giving us a new one, they mandated \nwe delete old stuff (about 400 TB worth). Now that they are working on replacing the network, we can do only \nlocal work. I should be able to give you an accounting of what is what. I can say, off the top of my head, that all \nwindows based items from the NY search have been handed over as well as all loose media. The CDs from NY \nonly contained pictures, no documents. There are still some Apple items from NY that need to be produced. As \nfar as the Island stuff goes, the 1st item on your spreadsheet, the \"kitchen\" mac has been produced. Still \nworking on the rest. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Feb 23, 2020 12:21 AM, \" \nTeam, \n)\" \nwrote: \nFollowing up on the below from last weekend, I'm still not sure how we're addressing this so I thought it would make \nsense for us to all schedule a (hopefully relatively brief) meeting to all get on the same page? We didn't hear back on \nwhich files had previously been provided, but our tech folks did their best to differentiate, and we got access to the \nmaterials yesterday and its well over a million documents, and we don't have any idea what we're looking at — i.e., \nwhich devices the materials came from, whether it's full or partial results, how many more devices we have coming, etc. \nBased on the attached search warrant returns, it looks like from the New York mansion (the PDF) there are \napproximately 40 devices that would have storage (computers, hard drives, thumb drives, etc.) and that's not even \ncounting at least 60+ CDs. And then from the Virgin Islands (the Excel spreadsheet), at least more than 25 devices, \nincluding multiple servers / server racks. \nSo we gotta know what \n... [truncated, 2573 chars — for the full page use /api/corpus/document/EFTA00032104/16 or ?id=EFTA00032104&page=16]", "char_count": 2573}, {"efta_number": "EFTA00032104", "page_number": 17, "text_content": "ss \nI'm not sure who's the exact right person to ask this, so wanted to get everybody on one email chain about it — I have \nthe hard drive that \ndropped off that has new Epstein search warrant materials, but it looks like there are also old \nmaterials (that I think we had previously received and uploaded??) on the hard drive, and so I'm not sure what's new. \nJust generally, and \nand I talked about this last week too, but it's basically impossible for us to keep track of what \nwe're getting, and what has been completed, without some kind of identification or labeling system, along with a list of \nwhich devices have been extracted and downloaded. \nSo for example on the hard drive currently, there are 38 folders labeled \"loadFiles\" through \"37loadFiles\" with a \nmodified date of 11/14/19, which I think we may have already previously received — but I'm not sure, because we \nhaven't gotten any info on which folders match up to which devices, etc. And then there's another folder titled \n\"NYC024362\" that has a modified date of 1/27/20, so I think that may be the materials we hadn't previously received? \nThat folder by itself has more than 600,000 items. \nI don't want to give \nanything that we've already previously received and uploaded, and I can't tell from the folder \nor file names whether everything on the drive is new, or whether just additional materials were saved onto it in addition \nto what we already have. =, \nare you able to give us some guidance on this? Ultimately what we really need is a \nspreadsheet of every device, whether it's been dumped (or partially dumped), and then identifying that same info —\nwhich device, and what materials from it — are being given to us with each data transfer. Otherwise I think \norganizationally and for review purposes it will be a total disaster for us. \nWe're happy to have a meeting on this if that's helpful — and thanks everybody for the assistance. \nAssistant U.S. Attorney \nSouthern District of New York \nEFTA00032121\n", "char_count": 1990}]}