Can a linked or web device send messages independently?¶

A message may be sent while the primary phone is elsewhere or apparently unused.

Evidential caution: that the phone must have been handled when the message was sent.

What this means¶

A linked desktop application, tablet or web session may be able to send messages independently through the account.

Some services require the primary device for initial linking but allow the secondary device to continue operating afterwards. Others may depend more directly on the phone’s connection.

This behaviour varies by service and may change over time, so verify the current platform position where it matters.

A message sent from a linked device may still appear on the primary phone after synchronisation, creating the impression that the phone originated it.

Consider shared computers, unattended sessions, remote access and compromise.

Where the distinction matters, compare provider or account metadata with device artefacts from the phone and linked system.

In reports, say that the account sent the message unless the originating device is established.

Where the position is unclear, compare device records, provider metadata and the account’s security history.

What to check or do next¶

• Preserve linked-device lists, session records, device names, browser history, application data and account-security notifications.
• Look for evidence showing when the linked session was created and whether it was active during the relevant event.
• Do not infer personal presence at the phone from the message alone.
• Preserve the original source and collection method so another investigator can test the same conclusion.