Does a read receipt prove the recipient personally read it?¶

No. A read or seen receipt records that the service's conditions for a viewing-related event were met. It does not by itself establish which person was present, careful reading, comprehension, agreement or intent.

Understand how the event was generated¶

The trigger may be opening a conversation on a phone, tablet, web or desktop session. Some applications mark all visible messages read; previews, accessibility features or notification interaction may affect status. Settings can disable receipts, and events may be delayed or synchronised later.

Preserve message ID, visible state and timestamp, service, account, session and linked-device information. Use the product behaviour relevant to that time rather than assumptions from another app.

Connect the event to awareness¶

A shared or unlocked device and a compromised web session can create the event without the named account holder. Conversely, absence of a receipt does not prove the content was unseen.

A reply addressing the message, later reference or consequential action can support awareness, but the actor must still be attributed. Report that the service recorded the message as read unless the surrounding evidence supports a personal conclusion.