Skip to main content
Print

EFTA01618219: May 2019 iMessage Meeting Arrangements and Advice

Snapshot

Evidence snapshot: EFTA01618219
Field Details
DocumentEFTA01618219 to EFTA01618223
Evidence typeiMessage export
Length and format5-page PDF
Date informationDisplayed conversation: May 20 and 21, 2019
Direct evidence linkEFTA01618219 on epstein-data.com
Source and provenanceReleased under the Epstein Files Transparency Act (EFTA) and indexed as EFTA01618219 on epstein-data.com. Participant identifiers are redacted, and the device and accounts are not identified.
Content warning and privacyPrivate personal correspondence.

What Is This Record?

EFTA01618219 is a five-page iMessage export dated May 20 and 21, 2019. It preserves meeting arrangements, travel-related questions, a later thank-you message and personal advice. Both participant identifiers are redacted in the visible header. One message addresses the other participant as “Jeffrey”; this is an internal identification cue, not a complete independent attribution of the devices or senders.

The record can document the exchange and its sequence. It does not establish the participants’ complete identities, their ages, the precise meeting location or all events that occurred between messages.


Key Takeaways

  • The export records meeting arrangements, travel questions, a thank-you message and personal advice, including book and article links. [1, pp. 1 to 5]
  • The timing runs from an 8 p.m. proposal, later moved to 8:30, to “On my way : 4 min away” at 00:30 UTC and a thank-you at 01:55 UTC. [1, pp. 1 to 3]
  • The name Jeffrey in a message is an internal cue, not independent authentication of both account holders. Arrangements do not alone prove attendance.

Document Identification

  • Record: EFTA01618219, five pages, Epstein Files Transparency Act release.
  • Stamped range: EFTA01618219 to EFTA01618223.
  • Platform: iMessage.
  • Displayed timezone: UTC+0000.
  • Displayed dates: May 20 and 21, 2019.
  • Redactions: Participant identifiers and other names are obscured in the released record.

Meeting Arrangements

On May 20, a participant greets “Jeffrey” and asks when to come. The reply introduces a sexual interpretation of that wording and then recasts the question as asking for a convenient meeting time and place. The first participant says no such meaning was intended. This exchange documents the participants’ words, not a sexual encounter. [1, p. 1]

A meeting at 8 p.m. is proposed and accepted. The proposed time is subsequently changed to 8:30, followed by an acknowledgment. There are also questions about planned travel. The travel discussion is prospective and does not establish that a trip occurred. [1, pp. 1 and 2]

Shortly after midnight on the export’s May 21 UTC date, one participant asks whether the other is on the way. The reply says the sender is four minutes away. At 01:55:04, a message thanks the recipient for their time and advice. Together these messages are consistent with a meeting, but they are not an independent attendance record and do not establish its location or everything discussed. [1, pp. 2 and 3]


Advice and Linked Material

The subsequent exchange discusses interpersonal sensitivity, a family relationship and ways of expressing appreciation. The personal details and a sexually explicit analogy are not reproduced here. The final visible message urges the correspondent to offer appreciation through words or small gestures. The record does not establish a payment obligation or agreement to provide a service. [1, pp. 3 to 5]

A link and preview for John Gray’s Men Are from Mars, Women Are from Venus appear in the export. A later link and preview identify a James Dobson article about resentment and a father. These are reading recommendations within the exchange. Their appearance does not establish contact with the authors, an endorsement by them of the participants’ conduct, or the authors’ involvement in any event described. [1, pp. 3 to 5]


Page-by-Page Guide

  • Page 1, EFTA01618219: Date and platform header; greeting to “Jeffrey”; initial meeting arrangement and clarification of wording.
  • Page 2, EFTA01618220: Travel-related and hospitality discussion; change to 8:30; next-day UTC heading and an “On your way?” message.
  • Page 3, EFTA01618221: Arrival-related reply, later thanks, advice and book-link metadata.
  • Page 4, EFTA01618222: Book preview, continuing personal discussion and an article link.
  • Page 5, EFTA01618223: Article-preview metadata and a final message about showing appreciation.

Time and Interpretation

The export expressly uses UTC+0000. A date change at midnight in that display should not automatically be treated as a new local evening. The participants’ references to “tonight,” 8 p.m. and 8:30 do not identify a local timezone. This article retains the export’s dates rather than assigning a location-based conversion not established by the document.


What the Record Does and Does Not Prove

The participant labels are redacted. Addressing someone as Jeffrey is not enough, by itself, to identify every speaker. No assumption is made that this correspondent is the same person as a redacted participant in another email or chat. The record also supplies no basis for inferring a person’s age from their style of writing.

Private health references, family identifiers and unnecessary intimate details are omitted. The article does not treat the advice as clinical care or infer an offense from the conversation. A fuller account would require independent identity attribution and corroborating records of any meeting or subsequent events.


Timestamp Guide

The following guide uses the export’s UTC+0000 designation and a 24-hour clock. Meeting times mentioned in message bodies remain the participants’ own proposed times; the PDF does not specify their local timezone.

  • May 20, 09:45:51: An opening message says the sender is never too busy to do nice things. Its “As I said” wording refers to prior context not supplied on these pages.
  • 13:42:32: The other participant greets “Jeffrey” and asks for a preferred meeting time.
  • 13:54:42 to 14:26:01: A travel question, clarification of the wording of the invitation, the 8 p.m. proposal at 13:56:42 and acceptance. [1, p. 1]
  • 14:26:35 to 15:25:55: Further travel-related discussion and hospitality arrangements; a message repeats the intended 8 p.m. meeting. These messages are plans, not an itinerary or proof of travel.
  • 17:36:11 and 17:39:03: “830 better” and an acknowledgment. [1, p. 2]
  • May 21, 00:29:47 to 00:30:18: “On your way?”, the reply “On my way : 4 min away,” and a brief acknowledgment.
  • 01:55:04: Thanks for time and advice. The interval between the arrival-related message and this reply is not a documented meeting duration.
  • 02:01:32 and 02:01:56: Continuing personal advice and a statement that the sender will text after finding a schedule. No subsequent appointment is documented here. [1, pp. 2 and 3]
  • 02:34:31: The book-preview message is displayed with a timestamp on page 4, following its URL and attachment metadata on page 3.
  • 02:38:03 to 02:41:22: Further discussion of a family relationship. A reply says an explanation will follow “tomorrow”; this excerpt does not document that later explanation.
  • 03:03:07: The James Dobson article preview is displayed.
  • 03:15:26: The final visible message discusses appreciation and gestures of thanks. [1, pp. 4 and 5]

Attachment and Delivery Fields

Page 3 lists an item described as a plugin-payload attachment, with a reported size of 17 KB and type image/vnd.microsoft.icon; the following page displays the book preview. Page 5 similarly lists a 1 KB item of that type before the article preview. Those are fields printed by the export. They do not establish that a complete book or article was transmitted as a file, that either was bought, or that the recipient read the linked text. The preview images are not evidence that their authors communicated with the chat participants.

A “Read” indicator appears beneath a message on page 4, and “Sent” appears beneath the final message on page 5. These labels should be reported only as displayed interface information. They do not establish agreement with advice, a response to the final message, or conduct outside the chat. [1, pp. 3 to 5]


Provenance and Attribution

The released PDF is a formatted conversation export. It is not presented here as a native device database or a complete forensic report. Both participant names in the header are blacked out, while the message bubbles retain their left/right positions. That layout allows the exchange to be followed within the excerpt; it does not establish the subscriber, device owner or person holding a device at every moment.

The first visible message refers to earlier remarks, and later messages refer to a discussion whose complete contents are not reproduced. The excerpt therefore has meaningful boundaries at both ends. No surrounding correspondence, address-book mapping or extraction certificate in the release resolves them. The Bates stamps identify pages for citation, but do not by themselves supply a chain of custody or authenticate the underlying statements.


Open Questions

  • Does an authenticated source identify the accounts or devices without exposing the unnamed correspondent unnecessarily?
  • Are there surrounding messages that clarify the opening reference and the later proposed follow-up?
  • Is there independent, appropriately redacted corroboration of the meeting’s location and occurrence? The chat’s arrival-related reply should not substitute for that evidence.
  • Does native message data establish timezone treatment and distinguish a link preview from a separately sent attachment?
  • If comparing this record with another article, is there an actual shared identifier or documented event linking them, rather than merely similar personal-advice language?

This article treats EFTA01618219 as its own documentary unit. It does not merge its redacted correspondent with a person in any other email or chat record. The pages support a detailed account of this conversation, but not a biography of the unnamed participant or a determination about the entire relationship.


Chronology

DateDocumented EventSource
May 20, 2019, 13:42 to 14:26 UTCCorrespondent greets “Jeffrey” and asks when to come; 8 p.m. proposed and acceptedEFTA01618219, p. 1
May 20, 2019, about 17:36 UTC“830 better” and an acknowledgmentEFTA01618219, p. 2
May 21, 2019, 00:29 to 00:30 UTC“On your way?” and “On my way : 4 min away”EFTA01618219, p. 2
May 21, 2019, 01:55 to 03:15 UTCThanks for time and advice; personal advice; book and article links; final message marked “Sent”EFTA01618219, pp. 3 to 5

Evidence Appearances

Record or IDDateWhat It ShowsSource
EFTA01618219 to EFTA01618223May 20 and 21, 2019Five-page iMessage export of meeting arrangements and adviceepstein-data.com/EFTA01618219

Conclusion

EFTA01618219 shows a correspondent arranging to meet someone addressed as “Jeffrey” on the evening of May 20, 2019, an “on my way” message shortly after midnight UTC, and a later thank-you for “time and advice” followed by personal advice and links to a John Gray book and a James Dobson article. The messages are consistent with a meeting but do not prove one took place, where it happened or what was discussed. Both participants’ identifiers are redacted and no ages are stated, so the correspondent should not be identified or linked to other records without a shared, verified identifier. [1, pp. 1 to 5]


Questions and Answers

What does this record actually establish?

The export records meeting arrangements, travel questions, a thank-you message and personal advice, including book and article links. [1, pp. 1 to 5]

Where did the record come from?

Released under the Epstein Files Transparency Act (EFTA) and indexed as EFTA01618219 on epstein-data.com. Participant identifiers are redacted, and the device and accounts are not identified.

Does the record prove a meeting happened?

No. An “on my way” message and a later thank-you are consistent with a meeting, but there is no independent record of attendance, location or what took place.

What remains uncertain?

The name Jeffrey in a message is an internal cue, not independent authentication of both account holders. Arrangements do not alone prove attendance.


Sources

  1. EFTA01618219, iMessage export, five pages, EFTA01618219 to EFTA01618223, May 20 and 21, 2019, UTC+0000, Epstein Files Transparency Act release, epstein-data.com.
Previous EFTA01617920: Jabor WhatsApp Export and the Proposed €15 Million Property Offer
Next EFTA01619188: Jeffrey, Milan “Fishing,” and Possible Recruitment
Table of Contents