Could marking a message as read create a new record?¶

A message may show as unread on a device or account.

Evidential caution: that marking it as read changes only the local screen.

What this means¶

A read action may create a service event that synchronises across devices and becomes visible to the sender or provider.

It may update read receipts, notification counts, conversation order, last-active status or linked-session records.

The exact effect depends on the service, account settings and device state.

Automatic processes can also mark content as read. Opening a notification, viewing the conversation on another device or background synchronisation may change the status.

Where operationally necessary, record who performed the action, on which device and at what time.

In reports, separate the original message status from any read event created during examination.

Where the consequence is uncertain, record the risk and the reason for any decision to proceed.

What to check or do next¶

• Preserve the unread indicator, notification, message ID, account, device, linked sessions and observation time before interaction.
• Do not deliberately mark a message as read merely to clear the interface or access later content.
• Compare sender-side and recipient-side records where the read event is relevant.
• Preserve the source and collection method so another investigator can test the same interpretation.
• Preserve the source and collection method so another investigator can test the same interpretation.

Evidential limits¶

Do not assume that a read receipt proves personal attention. It may identify an account or device event rather than the human user.