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

A message may show as read, seen or opened.

Evidential caution: that a read receipt proves the intended person personally read and understood the message.

What this means¶

A read receipt is usually an event generated by the service when the conversation or message is displayed in a way that meets that service’s rules. Those rules vary between platforms and may also depend on settings, linked devices and application behaviour.

Then seek contextual corroboration. A reply addressing the content, an action taken shortly afterwards, a later reference to the message or other account activity may support awareness. But attribution still matters: who controlled the account or device when the read event occurred?

Report the evidence at the level it supports. “The service recorded the message as read” is normally safer than “The recipient read the message.”

What to check or do next¶

• Preserve the visible status, the associated time and the platform involved. If the meaning is important, establish how that service generated the event at the relevant time rather than relying on assumptions from another application.

Evidential limits¶

The event may have been generated on a phone, tablet, desktop application or web session. The person who opened it may not have been the account holder. The device may have been shared, unlocked or accessed by someone else.

Some applications may mark messages as read when a conversation is opened, even if the user does not focus on every message. A preview, accessibility feature or notification interaction may also affect status depending on the service.

Read receipts can also be disabled, delayed or synchronised later. Their absence does not prove that the message was not seen. Their presence does not prove careful reading, comprehension, agreement or intent.