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

Yes. A read action may become a synchronised account or provider event visible on other endpoints or to the sender, rather than changing only the local screen.

Read state can propagate¶

Opening a conversation, notification or message on one endpoint can update read receipts, unread counts, conversation order, last-active status and session records. The precise trigger depends on service design, settings, connectivity and application version.

Automated processes or another linked device may also change the status. A read receipt therefore describes a service-recognised event and does not automatically prove personal attention to the content.

Keep investigative actions out of the original timeline¶

Before interaction, preserve the unread marker, notification, message and account IDs, device, linked sessions and observation time. Compare sender and recipient records where the status matters.

Do not clear unread items merely to navigate the interface. If marking as read is unavoidable, record the endpoint, user, exact time and resulting changes so the new event cannot be mistaken for activity under investigation. Opening disappearing content can carry an additional risk of loss.