Illustrated guide to build an identity-theft evidence file
Original trust.you editorial illustration for this guide. Visual cues support the explanation; they are not proof of authenticity.

The short answer: Evidence is most useful when it preserves original dates, sender details, transaction references and actions taken. Editing screenshots or collecting everything without context can make review harder.

A useful evidence file preserves sequence and originals

The useful move is to separate what the claimant controls from evidence you can obtain independently. Names, logos, caller ID, screenshots and a polished page can all be copied. A saved telephone number, a typed official address, a known colleague or a protected transaction route changes the channel instead of merely inspecting the same claim again.

Risk also depends on consequence. Reading a public page is different from granting remote access, sending an identity document or approving an irreversible payment. As the cost of error rises, require stronger verification and prefer a step you can undo.

Warning signals to assess together

These clues become useful when they form a pattern. Treat each one as a prompt to verify, not as a verdict by itself.

  • Missing dates or cropped sender information

    Pair this observation with a separate check: Create a chronological incident log.

  • No record of telephone calls or case numbers

    Pair this observation with a separate check: Keep original files and separate working copies.

  • Sensitive documents stored in an unprotected shared folder

    Pair this observation with a separate check: Record each report, reference number and promised next step.

Do not use one clue as a verdict: Collect what supports the incident. Do not create new exposure by circulating full identity documents more widely than necessary.

Preserve identity-theft evidence without creating more exposure

Keep the verification route separate from any contact detail or instruction supplied in the questionable message.

  • Create a chronological incident log

    This step tests the related concern: Missing dates or cropped sender information.

  • Keep original files and separate working copies

    This step tests the related concern: No record of telephone calls or case numbers.

  • Record each report, reference number and promised next step

    This step tests the related concern: Sensitive documents stored in an unprotected shared folder.

If access may already be exposed, the breach response builder can put containment and recovery steps in a safer order.

Decide what to do after verification

If the independent channel confirms the identity and request, ask whether the proposed method still gives you a record and recourse. Legitimate people and organisations should tolerate a proportionate verification step. Resistance, secrecy or a demand to bypass normal controls is new evidence, not an inconvenience to ignore.

If the evidence remains mixed, reduce exposure: do not send original documents when a redacted copy is enough, do not pay a deposit before verifying authority, and do not approve access broader than the task requires. “Not yet” is a valid decision when the missing fact matters.

A related recovery control appears in the practical scam response plan, especially when one account or channel can unlock another.

What this verification cannot establish

This guide cannot authenticate a specific person, account, website or transaction. Interfaces and attack methods change, and legitimate situations sometimes contain unusual details. For an active loss, account compromise or safety threat, contact the relevant institution or official reporting service through a verified route.

Official sources and further guidance

These primary sources support the topic and provide current reporting or technical guidance. Availability and procedures can differ by country.

Editorial note

Reviewed by the Trust You Editorial Desk on 2026-10-08. We assess title-to-H1 alignment, independent verification steps, limitations and overlap with existing coverage. Request a correction.