Conversation reconstruction
Available individual and group messages, replies, reactions, edits, delivery states and system events reconstructed in context.
Messaging application evidence
Forensic examination of WhatsApp communications, calls, media, accounts and associated artefacts across available devices, linked computers and backups.
Discuss a deviceExamination
Every instruction begins with the questions to be answered. Available evidence depends on the device, software, state, credentials, backups and prior handling.
Available individual and group messages, replies, reactions, edits, delivery states and system events reconstructed in context.
Images, video, audio, documents, thumbnails and cached copies assessed with available metadata and file-system traces.
Call records, identifiers, group membership, administrators, profile changes and account events correlated with other evidence.
Database remnants, notifications, quoted replies, media, backups and counterpart devices examined without promising deleted-data recovery.
Available cloud or local backups, WhatsApp Web and desktop artefacts considered to extend or corroborate the handset record.
Claimed conversations tested against databases, internal identifiers, timestamps, account activity and surrounding device artefacts, not screenshots alone.
Evidence source map
Absence from one screen or device does not resolve the evidential question. Relevant records may be distributed across several sources.
Accessible chat databases, calls, identifiers, attachments, media and database remnants.
Configured iCloud or Google application backup, with encryption material where required. Authorised linked-session collection is a separate, state-changing route.
Existing WhatsApp Desktop or Web data may hold only synchronised history.
A newly linked session is not a historic archive. Linking may notify the account holder and alter state. Lawfully obtained counterpart records may corroborate the source.
Evidential perspective
End-to-end encryption protects messages in transit. It does not remove every trace from participating devices, linked systems or backups. The forensic question is what records remain, who controlled the relevant account and whether the material reliably supports the asserted conversation.
Preserve now
Typical deliverables
Device details, condition, method, tool, integrity information and material acquisition limitations.
Relevant conversations, attachments, timestamps, identifiers and supporting artefacts in a reviewable form.
Plain-English findings with source references, alternative explanations and express evidential limitations.
Our approach
Each entry identifies its limited supporting proposition and documentation-check date. General methodology is not a current device-support list. These checks are not laboratory validation; availability and method suitability require assessment for the exact source and configuration.
Linked endpoints may receive only part of the history.
Platform documentation · Documentation checked
Linking is an account operation, not a passive historic archive.
Platform documentation · Documentation checked
Configuration changes encryption and key availability.
Platform documentation · Documentation checked
Synchronised content and device backups are distinct.
Platform documentation · Documentation checked
Methodological background (2014), not a current device-support list.
General methodology · Documentation checked
Confidential case review
Direct first contact
Scan with your phone camera, or select the service, to contact D3Forensics on +852 9103 1852. Do not send evidence, passwords or confidential case material until a transfer method has been agreed. These third-party messaging services process account and metadata under their own terms.