{"efta_number": "EFTA00020213", "page_count": 15, "url": "https://epstein-data.com/EFTA00020213", "pdf_url": "https://epstein-data.com/pdf/EFTA00020213.pdf", "pages": [{"efta_number": "EFTA00020213", "page_number": 0, "text_content": "From: ' \nTo: \"I \n)\"  \nSubject: RE: Epstein search warrant documents \nDate: Fri, 19 Jun 2020 18:55:07 +0000 \nI want to see what FBI sends to us — i.e., whether it's usable or not. If it is, great! And if not, hopefully at that point we'll \nhave an estimate to forward along. \nFrom: \n) \nSent: Friday, June 19, 2020 13:52 \nTo: \nI < \nSubject: RE: Epstein search warrant documents \nGreat, and thanks. What's the game plan with BRG? \nFrom: \n< \nSent: Friday, June 19, 2020 1:43 PM \nTo: \nSubject: FW: Epstein search warrant documents \nJust FYI — lots of calls about this today. \n>; \nFrom: \nSent: Friday, June 19, 2020 13:43 \nTo: \n(USANYS) < \nCc: \n(USANYS) \nSubject: RE: Epstein search warrant documents \n>;I\nI just had positive conversations with \nand \n(and =) -= \nhad understood that FBI was getting their own \nhard drive to transfer the data, which obviously makes sense. \nresponse to \nemail was to just have \norder a 12 TB drive, which she expects will get to \nnext week. I also think that's a better option than the 2 TB \ndrive that \nsays we have available on short notice, given that we expect the data to be somewhere around 20-40 TB \n(the capacity of the devices we seized is around 40-50 TB). \nI take it from \nemail that he's otherwise ready to give us the data, although that certainly would be a new \ndevelopment, but we're obviously hopeful that's the case. The key question then will be whether what we get from him \nthis time is actually usable. If it's not, I think at that point it will make sense to just have BRG do it — they can physically \ntake the devices themselves and do it. We had asked about that possibility from the beginning and CART was resistant, \nbut given the past nine months I think we should do it if necessary. But, hopefully the intervention of higher-ups solves \nthe problem and we can get the data in the next couple weeks, which would be great. \nFrom: \n(USANYS) \nSent: Friday, June 19, 2020 13:36 \nTo: \nCc: \n(USANYS) \nSubject: FW: Epstein search warrant documents \nEFT\n... [truncated, 2010 chars — for the full page use /api/corpus/document/EFTA00020213/0 or ?id=EFTA00020213&page=0]", "char_count": 2010}, {"efta_number": "EFTA00020213", "page_number": 1, "text_content": "Are we just talking about getting these across the street? He should not ship them. \ncan bring. \nFrom: \n(USANYS) [Contractor) <a> \nSent: Friday, June 19, 2020 1:35 PM \nTo: \n(NY) (FBI) <1.\n:›; \nCc: \n(USANYS) <a; \nc\n>; \n(USANYS) \nSubject: RE: Epstein search warrant documents \nHello \n(NY) (FBI) < \n>; \n(NY) (FBI) \nI can have the drives shipped to you or if you want you can come and pick up the drives from Saint Andrews. Someone \nwould be available for you to meet up with between 9:30 am — 12:30 pm Monday — Friday. Please let me know which you \nprefer. \nThank you. \nFrom: \n(NY) (FBI) <E\n> \nSent: Friday, June 19, 2020 1:14 PM \nTo: \n(USANYS) [Contractor] a; \nCc: \n(USANYS) \n(NY) (FBI) <->; \nc\n>; \n(NY) (FBI) \nc\n>; \n(USANYS) \nSubject: RE: Epstein search warrant documents \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< \nwrote: \na, \nfollowing up on the below— please let us know? Given case developments in recent days, this has become \nurgent. Thanks. \nFrom: \nSent: Wednesday, June 17, 2020 14:28 \nTo: \n(NY) (FBI) <\n:.; \n(USANYS) [Contractor] a> \nCc: \n(NY) (FBI) <a \nl c\n''; \n< \n>, \n(NY) (FBI) <\n:•; \n(USANYS) \n(USANYS) \nSubject: RE: Epstein search warrant documents \nEFTA00020214\n", "char_count": 1468}, {"efta_number": "EFTA00020213", "page_number": 2, "text_content": "Wanted 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 what \nthe 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) <\nII> \nSent: Monday, June 01, 2020 16:28 \nTo: \n(USANYS) [Contractor] <\n>; \nCc: \n(NY) (FBI) <\n>; \nSubject: RE: Epstein search warrant documents \nWill do. \nNY CART Coordinator \nSenior Forensic Examiner \n \n \ncell \ndesk \n(NY) (FBI) •:\n=> \nOn Jun I, 2020 4:26 PM, \" \n< \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 from \nthere. \nFrom: \n(NY) (FBI) <\n> \nSent: Monday, June 01, 2020 16:23 \nTo: \n(USANYS) [Contractor] S; \nCc: \n(NY) (FBI) <e \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 \nweek or 2. Sorry about that. My next day in the office is Thursday, so I'll 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, '7 \nwrote: \nEFTA00020215\n", "char_count": 1826}, {"efta_number": "EFTA00020213", "page_number": 3, "text_content": "Thanks for this update — we'll take a look and circle back if any questions. \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 searchable \nformat, but just wanted to confirm? Currently, we aren't able to match any of the prior productions to specific devices —\nso if we're able to match them up by Bates number now, that might work, but otherwise I think it makes sense for us to \nget 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(NY) (FBI) < \nSubject: Re: Epstein search warrant documents \n>; \n>; \n(USANYS) [Contractor] \n> \n(NY) (FBI) .:\n=1). \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 numbers. \nAny questions, let me know. \nFBI NY CART Coordinator \nSenior Examiner \nFrom: \nSent: Friday, May 15, 2020 4:11 PM \nTo: \n. (NY) (FBI) <M\nME:•; \nCc: \n(NY) (FBI) S.; \n(NY) (FBI) <\n> \nSubject: RE: Epstein search warrant documents \n(USANYS) [Contractor] \nThanks for this, it's a helpful start. In terms of being able to write our search warrant, one additional piece of information \nwe need is the serial number, or some other specific identifier, ideally for each device but at least for any device that there \nis more than one of the same thing. So for example, we need to be able to somehow differentiate the following devices — \nThe two Dell power edge T310 hard drives (NYCO24323 and NYCO24324) \nThe two Sony Vaio la\n... [truncated, 2097 chars — for the full page use /api/corpus/document/EFTA00020213/3 or ?id=EFTA00020213&page=3]", "char_count": 2097}, {"efta_number": "EFTA00020213", "page_number": 4, "text_content": "o 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 USVI \nlist 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) <\n> \nSent: Thursday, May 14, 2020 15:54 \nTo: \n> \nCc: \nc\n>; \n(NY) (FBI) < \nSubject: Re: Epstein search warrant documents \n(USANYS) [Contractor) \n. (NY) (FBI) •t:\n> \nHere is The listing of all the evidence gathered in NY that I have. I added some columns to guide you to the \nunique numbers CART NY uses fro their evidence. The template wasn't a slam dunk over, so I did what I could to \nconvey the information. If you are confused by anything, please let me know. In the column for approximate \nsize, it is in GB, totaled at the bottom and converted to TB. In the materials contained column, I put what load \nfile group the data was transferred over in (Mac, Windows, Loose Media, IDE, or Blacklight) If there is no entry \nin that column, that data has yet to be transferred. There are 2 Macs and a DVR you \n... [truncated, 2328 chars — for the full page use /api/corpus/document/EFTA00020213/4 or ?id=EFTA00020213&page=4]", "char_count": 2328}, {"efta_number": "EFTA00020213", "page_number": 5, "text_content": "Cc: \n(NY) (FBI) .c\n>, \nSubject: RE: Epstein search warrant documents \n(NY) (FBI) 'c\n> \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 FBI \ntool, so we asked for the materials to be transferred in a loadable format so we could put them on Relativity, which both \nwe and the agents can access. We're required to have the files in a format that we can produce them to defense counsel. \nI've done that in many other cases and it hasn't previously been an issue. My understanding from \nis that the best \nway to do it now is just for us (the U.S. Attorney's Office) to get the original files, which our vendor will process—by which \nI just mean converting into file formats that are loadable onto Relativity. It doesn't really have anything to do with the \ntaint 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 earlier \nthis year, they were in a format that wasn't usable for the reasons described in the email I sent on March 9. Again, I \nunderstand from \nthat the best way forward is to just get copies of the materials in their original formats, which I \nunderstand will be segregated and designated by device. That should work for us! I was just trying to understand the \napproach, as well as the timeline. \nthanks, \nFrom: \n(NY) (FBI) <\n> \nSent: Tuesday, May 12, 2020 13:03 \nTo: \n> \nCc: \n<\n.>; \n(NY) (FBI) < \nSubject: Re: Epstein search warrant documents \n>; \n(USANYS) [Contractor) \n. (NY) (FBI) •c\n> \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 extracting from processed evidence and putting them into an E-Discovery tool (Relativity) to do a \ntaint review. \nRelativity is NOT a f\n... [truncated, 3321 chars — for the full page use /api/corpus/document/EFTA00020213/5 or ?id=EFTA00020213&page=5]", "char_count": 3321}, {"efta_number": "EFTA00020213", "page_number": 6, "text_content": "back was lacking. \nFBI NY CART Coordinator \nSenior Examiner \nFrom: \nSent: Tuesday, May 12, 2020 11:33 AM \nTo: \n. (NY) (FBI) <\n>; \nCc: \nSubject: RE: Epstein search warrant documents \nC \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 basically \nsending us copies of everything? I don't totally understand why we couldn't have done that eight months ago, but \nregardless of the passage of time, I want to make sure we understand so we can report to our supervisors. I assume that \nmeans 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] <=a; \nCc: \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 please tell us what that plan is? Thanks! \nFrom: \n(NY) (FBI) C \nSent: Tuesday, May 12, 202011:11 \nTo: \n(USANYS) [Contractor] <\n>; \nCc: \nSubject: RE: Epstein search warrant documents \n>; \nwrote: \nI will use the spreadsheet, no problem. \nand 1 ironed out all the details. We've got a good plan moving \nforward that will meet your needs. \nNY CART Coordinator \nEFTA00020219\n", "char_count": 1581}, {"efta_number": "EFTA00020213", "page_number": 7, "text_content": "Senior Forensic Examiner \ncell \ndesk \nOn May 12, 2020 10:34 AM, \" \n< \nwrote: \nit 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 on \nour 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 \nM\n,\n \nMe and \njust finished our phone call regarding the data. \nwill put together a list of the all of the data and \nwhere the data was collected. I will work to send some hard drives to \nso he can begin to copy the data and send \nit 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: \n) c \nSent: Friday, May 8, 2020 2:15 PM \nTo: \n. (NY) (FBI) <\n>; \n \n(USANYS) \n(NY) (FBI) <->; \n(USANYS)<\n> \nCc: \n(USANYS) [Contractor] <\n>; \n(FBI) <\n> \nSubject: RE: Epstein search warrant documents \n) \n(NY) \nOkay thanks — please do let us know if at any point that changes, otherwise we'll look forward to being able to review the \nreturns in early June. Thanks again. \nFrom: \n(NY) (FBI) <\n> \nSent: Friday, May 08, 2020 14:14 \nTo: \n(USANYS) <\n(NY) (FBI) <->, \n(USANYS) \nEFTA00020220\n", "char_count": 1863}, {"efta_number": "EFTA00020213", "page_number": 8, "text_content": "Cc: \n(USANYS) [Contractor] <\n>; \n1<\n›; \n(NY) \n(FBI) \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 you. \nIf it does, I'll let you know. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn May 8, 2020 1:58 PM,' \n< \n> wrote: \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) <=\n> \nSent: Friday, May 08, 2020 13:50 \nTo: \n(USANYS)\n;\n) < \n(NY) (FBI) c\n>; \n(USANYS) \nCc: \n(USANYS) [Contractor] <\n:.; \n(FBI) \nSubject: RE: Epstein search warrant documents \n1<\n›; \n(NY) \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 to \ndo so. \nAlso, \nplease reach out to me at one of the numbers below so we can brain storm. Thanks. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn May 8, 2020 12:10 PM,' \nI' < \n> wrote: \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 waiting \non that list to be able to do an updated search warrant on all of those devices. Please let us know the current timeline —\nand also the current timeline on producing the results from those August and Sept\n... [truncated, 2245 chars — for the full page use /api/corpus/document/EFTA00020213/8 or ?id=EFTA00020213&page=8]", "char_count": 2245}, {"efta_number": "EFTA00020213", "page_number": 9, "text_content": "From: \n(NY) (FBI) <=M=.> \nSent: Tuesday, April 07, 2020 15:27 \nTo: \nCc: \n. (NY) (FBI) <M\n>, \n(USANYS) < \n(USANYS) [Contractor] a\nl>; \n(FBI) <-> \nSubject: RE: Epstein search warrant documents \n(USANYS) \n> \n(NY) \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 \nTo: \nCc: \n(NY) (FBI) la; \n(NY) (FBI) an; \n \n(USANYS) [Contractor] <\n>; \n1 \n(USANYS) < \n(USANYS) \n(NY) (FBI) sc\n> \nSubject: RE: Epstein search warrant documents \nYes, I can do anytime tomorrow, and \nRozier can 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) MI \n3) Mi \n4) MI \n5) \n/MI \n6) \n/ \n, if either of you wants to join (and if not, one of \nFrom: \n(NY) (FBI) < \nSent: Tuesday, April 07, 2020 14:13 \nTo: \n(USANYS)  \nCc: \n> \n(NY) (FBI) <1\n:›; \n(USANYS) \n(USANYS) [Contractor] <la; \nce; \n(FBI) <M\n> \nSubject: RE: Epstein search warrant documents \n(NY) \nAre you available tomorrow for a conference call to discuss this issue? \nEFTA00020222\n", "char_count": 1263}, {"efta_number": "EFTA00020213", "page_number": 10, "text_content": "SSA \nFBI New York \nOn Apr 7, 2020 1:55 PM, \" \n> wrote: \nFollowing up on this from a month ago — I know we're living in a different world than what existed four weeks ago, but are \nyou at all able to assist while working remotely? This has been pending for almost two months and we still don't have a \nvery basic list of each device or item that was seized and searched, or for which of those we've received materials. We're \nhappy to have a call if that would be useful, but as a first step the most basic thing we're looking for is the info in the \ntemplate spreadsheet we sent earlier (that's also attached). \nthanks, \nFrom: \nSent: Monday, March 09, 2020 12:00 \nTo: \n(NY) (FBI) < \nCc: \n. (NY) (FBI) <I\n>: \n(USANYS) . \n(USANYS) \n(USANYS) [Contractor] <\n>; \n(FBI) < \nSubject: RE: Epstein search warrant documents \n'c\n>; \n) <a; \n(NY) \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 attachments together. So if an email says, \"see the \nattached flight records,\" for example, we have no way of linking that up with the records themselves. Not only is \nthat a big problem for us in review, it's going to be a huge problem for producing the documents to defense \ncouns\n... [truncated, 2877 chars — for the full page use /api/corpus/document/EFTA00020213/10 or ?id=EFTA00020213&page=10]", "char_count": 2877}, {"efta_number": "EFTA00020213", "page_number": 11, "text_content": "I'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 SW \nreturns 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(USANYS) \n(NY) (FBI) \n>; \n(USANYS) < \nCc: \n(USANYS) [Contractor] <->; \n't\n>; \n) ‹\n) \n(NY) \n(FBI) <\n> \nSubject: RE: Epstein search warrant documents \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 of \nclarification: There were 9 IDE hard drives found in the Manhattan apartment, they turned out to be 3 copies of 3 drives \n(9 drives in total) from a July 2007 search on one of his properties. I only processed 3 (as they were all copies). All the \nloose media from the NY apartment is included. All the Windows machines from the NY apartment are included. Only 2 \nMacs from NY and 1 from the Island are included. \nI will have to more closely coordinate with whoever is loading up Relativity with the remaining Macs as the tool \nthey have to be processed with does not easily re-name the load files. \nSpreadsheet is attached. \nNYO CART Coordinator \nSenior Forensic Examiner \n(office) \n(cell) \nFrom: \n) [mailto. \nSent: Tuesday, March 03, 2020 12:25 PM \nTo: \n. (NY) (FBI) <\nI>: \n(NY) (FBI) \nCc: \n(USANYS) [Contractor] < \n(USANYS) \nSubject: RE: Epstein search warrant documents \n(USANYS) \n(NY) (FBI) <\n> \nI 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) < \n(NY) (FBI) <->, \nCc: \n(USANYS) [Contractor] < \n(USANYS) \n>; \n>; \n(NY) \nEFTA00020224\n", "char_count": 1989}, {"efta_number": "EFTA00020213", "page_number": 12, "text_content": "(FBI) ‹\n> \nSubject: RE: Epstein search warrant documents \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) dc\n:.; \n(USANYS) \n(NY) (FBI) <\n>; \n(USANYS) \nCc: \n(USANYS) [Contractor] <\n>; \n) \n) 'c\ne; \n(NY) \n(FBI) <\n> \nSubject: RE: Epstein search warrant documents \nwrote: \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 two \nsearch warrant returns, with columns for whether we've dumped the contents, whether they've been reviewed and/or \ntransferred, 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 is \nmostly 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 FBI \nwas 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 be \nable to review them as well.) \nmany thanks, \nFrom: \n(NY) (FBI) <\n> \nSent: Monday, February 24, 2020 09:24 \nTo: \n(USANYS)\n) \n< \n .. \n(NY) (FBI) c\n>; \n(USANYS) < \n> \nCc: \n(USANYS) [Contractor] <\n>; \n<a; \nc\n); \n) ca; \n(NY) \n(FBI) ‹\n> \nSubject: RE: Epstein search warrant documents \nEFTA00020225\n", "char_count": 1934}, {"efta_number": "EFTA00020213", "page_number": 13, "text_content": "Sony for the delayed response. They are tearing out our old network and giving us a new one, they mandated we \ndelete old stuff (about 400 TB worth). Now that they are working on replacing the network, we can do only local \nwork. 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 working \non the rest. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Feb 23, 2020 12:21 AM, '1 \nTeam, \n> wrote: \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., which \ndevices 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 approximately \n40 devices that would have storage (computers, hard drives, thumb drives, etc.) and that's not even counting at least 60+ \nCDs. And then from the Virgin Islands (the Excel spreadsheet), at least more than 25 devices, including multiple servers / \nserver racks. \nSo we gotta know what we've already received, what remains, anticipated schedule, etc, and I know it's a lot of moving \npieces on all sides so wanted to loop in everybody at once. The case team will be in California this coming week \n... [truncated, 3007 chars — for the full page use /api/corpus/document/EFTA00020213/13 or ?id=EFTA00020213&page=13]", "char_count": 3007}, {"efta_number": "EFTA00020213", "page_number": 14, "text_content": "So for example on the hard drive currently, there are 38 folders labeled \"loadFiles\" through \"37loadFiles\" with a modified \ndate of 11/14/19, which I think we may have already previously received — but I'm not sure, because we haven't gotten \nany info on which folders match up to which devices, etc. And then there's another folder titled \"NYC024362\" that has a \nmodified date of 1/27/20, so I think that may be the materials we hadn't previously received? That folder by itself has \nmore 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 or \nfile names whether everything on the drive is new, or whether just additional materials were saved onto it in addition to \nwhat 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 \nEFTA00020227\n", "char_count": 1336}]}