{"efta_number": "EFTA00027510", "page_count": 18, "url": "https://epstein-data.com/EFTA00027510", "pdf_url": "https://epstein-data.com/pdf/EFTA00027510.pdf", "pages": [{"efta_number": "EFTA00027510", "page_number": 0, "text_content": "From: ' \n(USANYS)\" ci \nTo: ' \n(USANYS)\" \n \nSubject: RE: Epstein search warrant documents \nDate: Mon, 06 Jul 2020 13:18:51 +0000 \nThe team says it's not a PDF, it's indecipherable data. \nFrom: \n(USANYS)<\n> \nSent: Monday, July 6, 2020 8:53 AM \nTo: \n(USANYS) \nSubject: RE: Epstein search warrant documents \nWith respect to the iphone seized from Epstein, for which FBI gave us an extraction, are we not into it because FBI can't \nget in, or is there a transmission issue with the way FBI sent us the extraction? \nFrom: \n(USANYS) < \nSent: Monday, July 6, 2020 8:49 AM \nTo: \n(USANYS) < \nSubject: RE: Epstein search warrant documents \nPretty sure it's everything. The estimate references 57 devices, as noted below, I think we're now up to 62, but we're into \none of them, so really 61. We can get an updated estimate for the 61 if that would be helpful, but given how much \nbusiness the PC unit gives \nhe should be good to us on that... \nFrom: \n(USANYS)<\n> \nSent: Monday, July 6, 2020 8:44 AM \nTo: \n(USANYS) \nSubject: RE: Epstein search warrant documents \nWhat is the estimate for? All of these? Just UVI? \nFrom: \n(USANYS) < \nSent: Friday, July 3, 2020 2:50 PM \nTo: \n(USANYS) < \nSubject: RE: Epstein search warrant documents \nYes, there are a total of 62 devices which can be divided into three main buckets based on how/where we obtained them, \nthe second and third of which are by far and away the biggest: \n• \n1 Phone and 1 iPad seized from Epstein at the time of his arrest on July 6, 2019. The FBI first delivered copies of \nthe extractions from these devices last week. We were able to review the iPad, but we have not been able to \nopen the iPhone data. IS THIS AN FBI TRANSMISSION ISSUE WITH THE IPHONE DATA, OR IS IT THAT IT WAS UN-\nOPENABLE? \n• \n33 electronic devices seized from the New York residence on July 11, 2019. These include multiple hard drives, \nmultiple computers, multiple USB drives, and multiple iPads. We currently have extractions from/access to none \nof them. \n• \n27 electroni\n... [truncated, 2220 chars — for the full page use /api/corpus/document/EFTA00027510/0 or ?id=EFTA00027510&page=0]", "char_count": 2220}, {"efta_number": "EFTA00027510", "page_number": 1, "text_content": "From: \n(USANYS) <\n> \nSent: Friday, July 3, 20201:51 PM \nTo: \n(USANYS) \nSubject: Re: Epstein search warrant documents \nCan you have the team summarize status of different buckets of devices for me? I'll push this to resolution, \npossibly through vendor. \nOn Jul 2, 2020, at 7:13 PM, \n(USANYS) < \n wrote: \nLet's discuss. I just don't have a lot of confidence that is going to get this done. \nSent from my iPhone \nOn Jul 2, 2020, at 6:35 PM, \n(USANYS) MEMO. \nwrote: \nOk. Audrey is also prepared to call \nabout pushing this issue if need be. \nOn Jul 2, 2020, at 6:32 PM, \n(USANYS)  \nI> wrote: \nOn this issue of the Epstein devices, the team got an estimate from BRG that seems reasonable in terms of both cost \nand time line. At this point, I would be inclined to do this, but let's find some time to chat more about it tomorrow if \nyou're around or early next week if that's better. Thanks \nFrom: \nSent: Thursday, July 2, 2020 5:11 PM \n(USANYS) \n(LISANYS)< \nTo: \nCc: \n)°c \nSubject: RE: Epstein search warrant documents \n>; \ncS; \nFollowing up on the below, I think we've given this our absolute best efforts with FBI — they are now well over a \nmonth later than their estimate from April on when we would get the New York materials, they're also past their \nestimate of getting us the New York materials from just this Monday, and we don't have anything close to an \nestimate on the USVI materials, which constitute the overwhelming majority of the data and are vastly more \nvoluminous than the New York devices. We have kept pushing the timeline back for this option, hoping that CART \nwill finalize, but I think at this point we 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-\nfriendly format, in a range of $85-135K. BRG has done this for our office multiple times in the past and are very \neffective and efficient, and they get the materials we need. And most importantly, they estimate they can do it all in\n... [truncated, 2215 chars — for the full page use /api/corpus/document/EFTA00027510/1 or ?id=EFTA00027510&page=1]", "char_count": 2215}, {"efta_number": "EFTA00027510", "page_number": 2, "text_content": "Cc: \n(USANYS) < \n \n(NY) (FBI) <->; \n>; \n) < \n(NY) \n(FBI) <->; \n(USANYS) < \nSubject: RE: Epstein search warrant documents \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) <\nII>; \nCc: \n(USANYS) < \n<I\n>; \n(FBI) < \n(USANYS) \nSubject: RE: Epstein search warrant documents \n(USANYS) [Contractor] \n(NY) (FBI) < \n(NY) \nOkay thanks — good luck with the cardiologist! And if you can let us know tomorrow that would be great. Thanks \nagain. \nFrom: \n(NY) (FBI) <\n> \nSent: Monday, June 29, 2020 12:59 \nTo: \n(USANYS) [Contractor] a \nCc: \n(USANYS) < \nCla; \n>; \n(NY) (FBI) <->; \n<S• \n(FBI) < \n(USANYS) ‹\n> \nSubject: RE: Epstein search warrant documents \nWhen I'm in the office tomorrow, I will be better able to estimate. I'm at my cardiologist right now. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \n(NY) \nOn Jun 29, 2020 12:56 PM,' \nwrote: \nGreat, thanks. Is there even a rough estimate of when we will get the USVI materials? Or an estimate of when you'll \nbe able 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] <a; \nEFTA00027512\n", "char_count": 1262}, {"efta_number": "EFTA00027510", "page_number": 3, "text_content": "Cc: \n(USANYS) c\n> \n(NY) (FBI) <->• \n) < \nI ca \n(NY) \n(FBI) < \n(USANYS)<\nI> \nSubject: RE: Epstein search warrant documents \nYep \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Jun 29, 2020 12:52 PM, ' \nPO\nwrote: \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(NY) (FBI) <->, \n<=e \n(FBI) < \n(USANYS) ‹\n> \nSubject: RE: Epstein search warrant documents \n(NY) \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 \nmany items I have to export. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Jun 29, 2020 12:40 PM,' \nwrote: \nOkay thanks, and just to clarify, a few days to finalize the New York materials, and then what about the USVI \nmaterials? I think 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) <\nM> \nSent: Monday, June 29, 2020 12:34 \nTo: \n(USANYS) [Contractor] <\n>; \nCc: \n(USANYS)\n; \n(NY) (FBI) <->; \nEFTA00027513\n", "char_count": 1390}, {"efta_number": "EFTA00027510", "page_number": 4, "text_content": "< \nI \n(NY) \n(FBI) < \n(USANYS) \nSubject: RE: Epstein search warrant documents \nI am in the process ofAttporting 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 \n1 item in particular has over 500,000 emails. We will be able to provide discovery once Defense Council \nhas provided drives for us to copy items over to. This goes quicker as there is no processing involved. I'll let \nyou know when everything is complete. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Jun 29, 2020 11:03 AM, \" \nwrote: \nFollowing up on this, I understand from \nthat she was able to provide you with a 12 TB drive last week — could \nyou please let us know when we will be able to get the materials? I expect a judge will ask us about discovery as \nearly as this week. \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==.>; \nCc: \n(USANYS) \n•<\n>; \n(NY) (FBI) <->; \n(FBI) <->; \n(USANYS) <=\n> \nSubject: RE: Epstein search warrant documents \n(NY) \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 \nwhen I can expect the drives. Thanks. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \nOn Jun 19, 2020 1:09 PM,' \nII < \nwrote: \nEFTA00027514\n", "char_count": 1976}, {"efta_number": "EFTA00027510", "page_number": 5, "text_content": "a, \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) sc\n>; \n(USANYS) [Contractor] \n<S. \nCc: \n(NY) (FBI)\n \nc \n) \n(NY) (FBI) <\nI>; \n(USANYS) < \nSubject: RE: Epstein search warrant documents \n(USANYS) \nWanted to circle back on this and check in, particularly because we desperately need to get the results from the July \nand September searches before moving forward with possible additional charges in the case. I know you had \nmentioned you needed to push back your prior estimate of complete production by early June, by a couple weeks, so \nwanted to see what the current estimate is? I don't think we've started to get anything yet but please correct me if \nI'm wrong. \nthanks, \nFrom: \n(NY) (FBI) <\n> \nSent: Monday, June 01, 2020 16:28 \nTo: \n(USANYS) [Contractor] < \nCc: \n(NY) (FBI) <\nEM>: \n) \n> \nSubject: RE: Epstein search warrant documents \nWill do. \nNY CART Coordinator \nSenior Forensic Examiner \ncell \ndesk \n(NY) (FBI) <\n> \nOn Jun I, 2020 4:26 PM,' \n\" < \nwrote: \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) <M\n> \nSent: Monday, June 01, 2020 16:23 \nTo: \n(USANYS) [Contractor] <a; \nCc: \n(NY) (FBI) a \n) \n(NY) (FBI) \nSubject: RE: Epstein search warrant documents \nEFTA00027515\n", "char_count": 1541}, {"efta_number": "EFTA00027510", "page_number": 6, "text_content": "Unfortunately, recent events and our staffing levels have conspired to put a kink in just about everything. If \nwe can't make heads or tails of the stuff I've already produced, we'll do it again. They have told us that our \nstaffing levels will be steadily increasing over the next few weeks, but I'm going to have to push back my \nestimate by a week or 2. Sony about that. My next day in the office is Thursday, so I'll be able to see if I can \neasily identify what I already gave you and marry it to a reliable identifier. \nNY CART Coordinator \nSenior Forensic Examiner \n \n cell \ndesk \nOn Jun 1, 2020 4:13 PM,' \n< \nThanks for this update — we'll take a look and circle back if any questions. \nwrote: \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 \nwe've gotten 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)\nSent: Friday, May 29, 2020 12:53 \nTo: \nsc\n> \nCc: \n*c\n>; \n(NY) (FBI) •::\n>; \nSubject: Re: Epstein search warrant documents \n(USANYS) [Contractor] \n> \n(NY) (FBI) <\n> \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: \nSent: Friday,\n... [truncated, 2036 chars — for the full page use /api/corpus/document/EFTA00027510/6 or ?id=EFTA00027510&page=6]", "char_count": 2036}, {"efta_number": "EFTA00027510", "page_number": 7, "text_content": "To: \n. (NY) (FBI) ic\n>, \n<christopherRozier@usdoj.gov>\nCc: \n(NY) (FBI) <->; \n(NY) (FBI) < \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 \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 \nthe following 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 \nUSVI spreadsheet 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 \nreproduce all the materials so that we can get them in searchable format, but just wanted to confirm? Currently, we \naren't able to match any of the prior productions to specific devices — so if we're able to match them up by Bates \nnumber now, that might work, but otherwise I think it makes sense for us to get everything. But let us know if any \nissue with that. \nthanks very much, \nFrom: \n(NY) (FBI) <\n> \nSent: Thursday, May 14, 2020 15:54 \nTo: \nCc: \n) < \n(NY) (FBI) .c\n>; \n. (NY) (FBI) <\n> \nSu\n... [truncated, 2407 chars — for the full page use /api/corpus/document/EFTA00027510/7 or ?id=EFTA00027510&page=7]", "char_count": 2407}, {"efta_number": "EFTA00027510", "page_number": 8, "text_content": "approximate size, it is in GB, totaled at the bottom and converted to TB. In the materials contained column, \nI put what load file group the data was transferred over in (Mac, Windows, Loose Media, IDE, or Blacklight) \nIf there is no entry in that column, that data has yet to be transferred. There are 2 Macs and a DVR you \ndon't have as well as an iPhone and an iPad. IF the descriptions are a bit light, let me know and I'll do what \nI can to beef them up. I will get you the Island stuff tomorrow. \nFBI NY CART Coordinator \nSenior Examiner \nFrom: \nSent: Wednesday, May 13, 2020 12:25 PM \nTo: \n. (NY) (FBI) <11\n,•; \nChnstopherRozier@usdoi.gov>\nCc: \n(NY) (FBI) <->; \n. (NY) (FBI) < \nSubject: RE: Epstein search warrant documents \n(USANYS) [Contractor] \nRespectfully, I think there are some miscommunications here — all we have asked is to receive the materials in a \nformat such that we can view them using a system we have access to. We're not able to get web-enabled access \nthrough any FBI tool, so we asked for the materials to be transferred in a loadable format so we could put them on \nRelativity, which both we and the agents can access. We're required to have the files in a format that we can \nproduce them to defense counsel. I've done that in many other cases and it hasn't previously been an issue. My \nunderstanding from \nis that the best way to do it now is just for us (the U.S. Attorney's Office) to get the original \nfiles, which our vendor will process—by which I just mean converting into file formats that are loadable onto \nRelativity. It doesn't really have anything to do with the taint review—we have to have access to the docs in our \nsystems 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 =that the best way forward is to just get copies \n... [truncated, 2402 chars — for the full page use /api/corpus/document/EFTA00027510/8 or ?id=EFTA00027510&page=8]", "char_count": 2402}, {"efta_number": "EFTA00027510", "page_number": 9, "text_content": "Just to be clear. The US Attorney's Office (or it's contractors) are not \"processing\" anything. You are taking \nfiles that I will be extracting from processed evidence and putting them into an E-Discovery tool (Relativity) \nto do a taint review. \nRelativity is NOT a forensic tool. It is incapable of dealing with many things that are found forensically on a \ncomputer like free space, slack space, and system files to name a few. When we started this, and you \ninsisted you do the taint review in Relativity, I warned you that it was adding months worth of work on top \nof what was already done, and that Relativity was incapable of viewing everything. You insisted we do it \nthis way. So now \nand I have come up with a way to fit this round peg into this square hole. We will get \nit done. \nSorry 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 \nwhile back was lacking. \nFBI NY CART Coordinator \nSenior Examiner \nFrom: \nSent: Tuesday, May 12, 2020 11:33 AM \nTo: \n. (NY) (FBI) \n<ChristopherRozier@usdoj.gov> \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 \n... [truncated, 2686 chars — for the full page use /api/corpus/document/EFTA00027510/9 or ?id=EFTA00027510&page=9]", "char_count": 2686}, {"efta_number": "EFTA00027510", "page_number": 10, "text_content": "NY CART Coordinator \nSenior Forensic Examiner \n \n cell \ndesk \nOn May 12, 2020 11:15 AM, ' \n)\" c \nwrote: \nI have no doubt you do, but can you please tell us what that plan is? Thanks! \nFrom: \n(NY) (FBI) <\nM> \nSent: Tuesday, May 12, 2020 11:11 \nTo: \n(USANYS) [Contractor] <\n=M>; \nCc: \nc\n>; \nSubject: RE: Epstein search warrant documents \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 \n \n cell \ndesk \nOn May 12, 2020 10:34 AM, \nwrote: \nit would be very helpful for us if you could please use the attached spreadsheet in transmitting that info so \nwe make sure we get all the info we need. I think you had previously sent us a list of certain information that \nunfortunately wasn'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 \nit on our end? I ask to make sure we don't lose any searchability — when FBI sent versions before, it had already \nbeen processed. I think what we talked about on the phone a month ago was getting, for example, data from one \ndevice to make sure it transfers correctly, before sending over literally everything — is that still the plan? \nthanks, \nIM• \nFrom: \n(USANYS) [Contractor] \nSent: Tuesday, May 12, 2020 10:27 \nTo: \nCc: \n. (NY) (FBI) \nSubject: RE: Epstein search warrant documents \nHello \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 \nand send 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. \nEFTA00027520\n", "char_count": 1867}, {"efta_number": "EFTA00027510", "page_number": 11, "text_content": "Thank you. \nFrom: \nSent: Friday, May 8, 2020 2:15 PM \nTo: \n. (NY) (FBI) \n(USANYS) \n(NY) (FBI) c \n>; \n(USANYS) \nCc: \n(USANYS) [Contractor] <->; \n) `:\n>; \n(NY) (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 \nreview the returns in earlyJune. Thanks again. \nFrom: \n(NY) (FBI) <a\n,\nSent: Friday, May 08, 2020 14:14 \nTo: \n(USANYS) \n(NY) (FBI) ''; \n(USANYS) < \nCc: \n(USANYS) [Contractor] <->; \n(NY) (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 \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< \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 \ncomplete transmission of the search warrant returns is no longer likely? If so could you please let us know what the \ncurrent estimate would be, so we can factor that in? Thanks very much. \nFrom: \n(NY) (FBI) <\n> \nSent: Friday, May 08, 2020 13:50 \nTo: \nCc: \n(USANYS) \n(NY) (FBI) <->; \n(USANYS) [Contractor] <I \n(USANYS) < \n(NY) (FBI) < \nSubject: RE: Epstein search warrant documents \n>; \n< \n) <\n>; \nEFTA00027521\n", "char_count": 1485}, {"efta_number": "EFTA00027510", "page_number": 12, "text_content": "Sony for the delay, they reduced us to 1 day a week, so things have been stretched out by a factor of 5. I \nwill be back in the office on Thursday and will be able to get you the list then as I have to access some of \nour systems to do 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, ' \ny.\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 \ncurrent timeline — and also the current timeline on producing the results from those August and September \nsearches? I think you and \nwere going to coordinate on that, and you had mentioned you expected we'd have it \na couple months from our call, which would be about a month from now. Wanted to make sure we're still on track. \nthanks, \nFrom: \n(NY) (FBI) <\n> \nSent: Tuesday, April 07, 2020 15:27 \nTo: \n(USANYS) \n(NY) (FBI) <\nM>; \n(USANYS) \nCc: \n(USANYS) [Contractor] <M\nI>; \n1`\n›; \n) `\n›; \n(NY) (FBI) <\n> \nSubject: RE: Epstein search warrant documents \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: \n(NY) (FBI) <\n:.; \n(USANYS) \n(NY) (FBI) .:\n>; \n(USANYS) \nCc: \n(USANYS) [Contractor] Christopher.Rozier@usdoj.gov>;\n; \n(NY) (FBI) <[=\n> \nSubject: RE: Epstein search warrant documents \nYes, I can do anytime tomorrow, and ME Rozier can also join anytime tomorrow. So whenever is good on your end. \nEFTA00027522\n", "char_count": 1992}, {"efta_number": "EFTA00027510", "page_number": 13, "text_content": "Also, 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 \nknow, otherwise I'd propose we do: \n3) \n4) \n5) \n/ \n6) \nM, 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) \n. (NY) (FBI) < \n1 < \n> \n(USANYS) \nCc: \n(USANYS) [Contractor] < \n1 < \n> \n•<\n:'; \n(NY) (FBI) < \nSubject: RE: Epstein search warrant documents \nAre\n available tomorrow for a conference call to discuss this issue? \nSSA \nFBI New York \nOn Apr 7, 2020 1:55 PM, \" \n>; \n>; \nwrote: \nFollowing up on this from a month ago — I know we're living in a different world than what existed four weeks ago, \nbut are you at all able to assist while working remotely? This has been pending for almost two months and we still \ndon't have 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 \nis the 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) <\n>; \n(USANYS) \n(NY) (FBI) < \n>; \n(USANYS) \nCc: \n(USANYS) [Contractor] <\n>; \n) \nCa; \n(NY) (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? \nThe excel file you sent has descriptions that don't match up to the items listed in the search warrant returns (that we \nsent on 2/23), and we don't have the 1B or CART numbers to be able to cross-reference. We also can't tell what you \nEFTA00027523\n", "char_count": 1718}, {"efta_number": "EFTA00027510", "page_number": 14, "text_content": "mean by \"loose media\" without a specific comparison to what was seized, we don't know which items you're \nreferring to as \"Windows machines,\" and we can't tell whether the entirety of any particular item has been \ntransferred, or just partial. For 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 \nthe attached flight records,\" for example, we have no way of linking that up with the records themselves. \nNot only is that a big problem for us in review, it's going to be a huge problem for producing the documents \nto defense counsel. \nThe load file has no link to the native file, so when we load the data to the database, there's no way to have \nthe native files show up in the database. Because many of the files are too large to open in the viewer, it \neffectively means that there are many files that are completely invisible to us. \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 \nto get a similar reproduction of the data we received a couple months ago. Otherwise we're sifting through more \nthan a million 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 \nrecord-keeping, and we need that info at the very least, as well as anything else you think would be useful. Also \nattaching the SW returns for reference. And again, we're happy to meet up anytime and hash all \n... [truncated, 3035 chars — for the full page use /api/corpus/document/EFTA00027510/14 or ?id=EFTA00027510&page=14]", "char_count": 3035}, {"efta_number": "EFTA00027510", "page_number": 15, "text_content": "Senior Forensic Examiner \n(office) \n(cell) \nFrom: \n[mailto \nSent: Tuesday, March 03, 2020 12:25 PM \nTo: \n. (NY) (FBI) 2.\n; \n(USANYS) \n(NY) (FBI) < \n>; \n(USANYS) \n<a> \nCc: \n(USANYS) [Contractor] <Christopher.Rozier@usdoj.gov>.\nSubject: RE: Epstein search warrant documents \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 \nwe can figure out in advance what (if any) additional steps we need — is that possible? \nFrom: \n(NY) (FBI) <a. \nSent: Tuesday, March 03, 2020 09:59 \nTo: \n(USANYS) < \n>; \n(NY) (F81) \n(USANYS) \nCc: \n(USANYS) [Contractor] <\n:.; \ncc\n> \n(NY) (FBI) <I\n> \nSubject: RE: Epstein search warrant documents \n>; \ncS; \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, '1 \nwrote: \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>; \n(USANYS) < \n(NY) (FBI) <\n>; \n(USANYS) cca \nCc: \n(USANYS) [Contractor] <\n>; \ncc\n> \n(NY) (FBI) <E\n> \nSubject: RE: Epstein search warrant documents \nEFTA00027525\n", "char_count": 1244}, {"efta_number": "EFTA00027510", "page_number": 16, "text_content": "Totally understand about the network issues—we can relate. I do still think it will be helpful to all sit down together \nto have an in-person discussion, to make sure everybody is on the same page. Are folks available for that next \nweek? And what I think would be most helpful to facilitate that would be a spreadsheet of each separate device \nreferenced in the two search warrant returns, with columns for whether we've dumped the contents, whether \nthey've been reviewed and/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 \nattached is mostly hypothetical, obviously, just as examples. That will help us fully understand what's been reviewed, \ntransferred, and 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 \nthink FBI 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 \nthose to be able to review them as well.) \nmany thanks, \nFrom: \n(NY) (FBI) <\n> \nSent: Monday, February 24, 2020 09:24 \nTo: \n(USANYS) \n(NY) (F81)\n>;—(USANYS) \n< \nCc: \n(USANYS) [Contractor] <\nI>; \n) <\n>; \n<=a \n) <\n>; \n(NY) (FBI) <\nEMS> \nSubject: RE: Epstein search warrant documents \nSony for the delayed response. They are tearing out our old network and giving us a new one, they \nmandated we delete old stuff (about 400 TB worth). Now that they are working on replacing the network, \nwe can do only local work. I should be able to give you an accounting of what is what. I can say, off the top \nof my head, that all windows based items from the NY search have been handed over as well as all loose \nmedia. The CDs from NY only contained pictures, no documents. There are still some Apple items from NY \nthat need to be produced. As far as the Island stuff goes, the 1st item on your spreadsheet, the \"kitchen\" mac \nhas been produced. Still worki\n... [truncated, 2953 chars — for the full page use /api/corpus/document/EFTA00027510/16 or ?id=EFTA00027510&page=16]", "char_count": 2953}, {"efta_number": "EFTA00027510", "page_number": 17, "text_content": "counting 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 we've already received, what remains, anticipated schedule, etc, and I know it's a lot of \nmoving pieces on all sides so wanted to loop in everybody at once. The case team will be in California this coming \nweek from Tuesday through Friday, but then I think generally around the first week of March, which will hopefully be \nplenty of time to schedule a productive meeting. \nthanks all, \nFrom: \nSent: Saturday, February 15, 2020 16:30 \nTo: \n. (NY) (FBI) .:\n>; \nCc: \n(USANYS) [Contractor] <\nM>, \nSubject: RE: Epstein search warrant documents \nss \n(NY) (FBI) <\nM=> \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 \nold materials (that I think we had previously received and uploaded??) on the hard drive, and so I'm not sure what's \nnew. \nJust generally, and \nand I talked about this last week too, but it's basically impossible for us to keep track of \nwhat we're getting, and what has been completed, without some kind of identification or labeling system, along with \na list of which 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 \nreceived? That folder by itself has more than 600,000 items. \nI don't want to give I= \nanything that we've already previously received and uploaded, and \n... [truncated, 2757 chars — for the full page use /api/corpus/document/EFTA00027510/17 or ?id=EFTA00027510&page=17]", "char_count": 2757}]}