EVIDENCE PRESERVATION: RECORD WHAT HAPPENED BEFORE YOU DELETE IT
When something goes wrong, your first instinct may be to clean everything up.
You may want to delete the suspicious message.
You may want to uninstall the strange application.
You may want to clear the browser.
You may want to reset the phone.
You may want to delete the conversation.
Sometimes immediate containment is necessary.
But when it is safe and practical, preserve useful evidence before changing or deleting it.
Evidence preservation is not about becoming an investigator. It is about keeping enough accurate information to understand what happened, explain it to the right organisation and support legitimate response and recovery.
THE CORE PRINCIPLE
PRESERVE USEFUL INFORMATION BEFORE CLEANING UP AN INCIDENT — UNLESS IMMEDIATE SAFETY OR CONTAINMENT REQUIRES ACTION FIRST.
A useful incident-response sequence is:
STOP → PRESERVE → SECURE → REPORT → VERIFY → RECOVER → ESCALATE
Not every incident needs every step, and immediate containment can take priority when an active threat is still present.
01 · FIRST, STOP THE RISK
Before preserving evidence, stop the activity that could cause further harm.
If you are on a suspicious website, stop entering information.
If someone is pressuring you to send money, do not send more.
If you are being asked for an OTP, PIN, password or recovery phrase, do not provide it.
If you are about to approve a suspicious transaction, stop before signing.
Preservation should never become an excuse to continue interacting with an attacker.
02 · UNDERSTAND WHAT YOU ARE PRESERVING
Evidence is information that may help establish what happened.
Depending on the incident, useful records may include:
- Original messages
- Emails
- Phone numbers
- Usernames
- URLs
- Website addresses
- Screenshots
- Login alerts
- Security notifications
- Transaction references
- Payment receipts
- Wallet addresses
- Transaction hashes
- Account activity
- Device information
- Dates and times
- Names or identities used by the person contacting you
Not every item will be relevant to every incident.
Preserve what helps answer the basic questions:
WHAT happened?
WHEN did it happen?
WHO or WHAT was involved?
WHAT information was requested or exposed?
WHAT action was taken?
WHERE did money or digital assets go?
WHICH account, device or service was affected?
03 · BUILD A SIMPLE TIMELINE
A timeline can be more useful than a large collection of disconnected screenshots.
Write down events while they are still fresh.
10:15 — Received WhatsApp message.
10:18 — Opened the link.
10:20 — Entered password.
10:21 — Received OTP.
10:22 — Entered OTP.
10:25 — Received account-security notification.
10:30 — Contacted the bank through its official channel.
A timeline helps separate what happened from what you later assumed happened.
04 · PRESERVE THE ORIGINAL CONTEXT
A cropped screenshot may show only part of the story.
Where safe, preserve the original conversation, email thread or notification rather than relying only on a screenshot.
Context may reveal:
- Who sent the message
- When it was sent
- What happened before it
- The exact request
- The link or attachment
- The account used
- Changes in the conversation
- Follow-up messages
Do not edit or manipulate the original record unnecessarily.
05 · SCREENSHOTS ARE USEFUL — BUT THEY ARE NOT EVERYTHING
Screenshots can quickly capture information that may disappear later.
For example, a screenshot may preserve:
- A suspicious message
- A transaction status
- A security alert
- A profile claiming to be support
- A payment instruction
- A suspicious website
But a screenshot can be incomplete or altered.
When possible, preserve the original source as well.
A screenshot of a payment is not the same thing as independently verified payment information.
A screenshot of an account alert is not the same thing as the account's current security record.
Use screenshots as evidence of what was displayed, then verify important facts through the appropriate official system.
06 · RECORD DATES AND TIMES
Time can matter.
Record:
- Date
- Approximate time
- Time zone when relevant
- When the message arrived
- When you clicked
- When information was entered
- When a transaction occurred
- When you noticed something unusual
- When you contacted the provider
Do not invent precision you do not have.
If you only remember that something happened around 2:30 PM, record it as approximately 2:30 PM rather than pretending you know the exact second.
07 · PRESERVE TRANSACTION INFORMATION
For financial incidents, preserve the information that identifies the transaction.
Depending on the service, this may include:
- Transaction reference
- Amount
- Currency or asset
- Recipient
- Sender
- Account used
- Date
- Time
- Payment method
- Receipt
- Status shown by the service
For cryptocurrency incidents, useful information may include:
- Wallet address
- Destination address
- Asset
- Amount
- Network
- Transaction hash
- Block explorer record
Do not expose a recovery phrase or private key while trying to document a crypto incident.
08 · PROTECT SENSITIVE INFORMATION
Evidence can contain secrets and personal information.
Do not publicly post:
- Passwords
- OTPs
- PINs
- Recovery codes
- Recovery phrases
- Private keys
- Full card details
- Authentication credentials
- Identity documents unless legitimately required
A person can be both a victim and a source of sensitive information.
Preserving evidence does not mean exposing everything.
09 · REDACT WHEN APPROPRIATE
If a legitimate organisation needs a screenshot, check whether unnecessary sensitive information can be hidden without destroying the information needed to understand the incident.
For example, you may be able to obscure unrelated personal information while keeping:
- The relevant date
- Time
- Sender
- Transaction reference
- Warning message
- Relevant URL
Do not alter evidence in a way that changes its meaning.
If the evidence may be important for a formal investigation, follow the receiving organisation's instructions about what should be preserved and how.
10 · DO NOT DELETE THE ATTACKER'S MESSAGE TOO QUICKLY
A suspicious message may feel like something you should immediately remove.
But deleting it may remove useful information about:
- The sender
- The account
- The wording
- The link
- The time
- The requested action
- The social-engineering technique
If the message itself is still creating risk, stop interacting with it.
Preserve what is useful, then report or delete it according to the appropriate service or incident process.
11 · DO NOT KEEP CLICKING THE LINK TO COLLECT EVIDENCE
You do not need to repeatedly visit a suspicious website to document it.
Do not:
- Log in again
- Enter test passwords
- Enter fake OTPs
- Download another file
- Connect a wallet
- Approve a transaction
- Give remote access
Use the information already available to you and rely on legitimate technical or reporting processes when additional investigation is required.
12 · DO NOT FACTORY-RESET TOO QUICKLY
A factory reset may sometimes be appropriate for a seriously compromised device.
But wiping the device can remove information that could help establish what happened.
Before taking an irreversible action, consider:
Is there an active threat that requires immediate containment?
Is important evidence still on the device?
Does the affected service or professional adviser recommend a particular response?
Can the device be safely isolated while appropriate guidance is obtained?
Immediate safety takes priority when necessary, but unnecessary destruction of evidence should be avoided.
13 · DO NOT UNINSTALL EVERYTHING AUTOMATICALLY
If you discover a suspicious application, uninstalling it may feel like the obvious solution.
But first consider what happened.
Did the application receive sensitive permissions?
Did you enter credentials after installing it?
Did you grant accessibility access?
Did you allow remote control?
Did unusual activity occur?
Preserve relevant information where practical and seek appropriate technical assistance when the device may have been compromised.
14 · KEEP THE ORIGINAL FILE OR MESSAGE WHERE PRACTICAL
If an attachment, document or suspicious file is relevant to the incident, avoid repeatedly opening it.
Do not forward it casually.
Do not upload it to random online services for analysis.
Keep the original safely where practical and use an appropriate security or professional process if analysis is required.
15 · PRESERVE ACCOUNT AND SECURITY ALERTS
Security notifications can help establish what happened.
Examples include:
- New-login alerts
- Password-change notifications
- MFA changes
- Recovery-email changes
- Device-registration alerts
- Payment notifications
- Transaction alerts
- Wallet notifications
Record the information before it disappears from the interface.
If the alert contains a link, do not automatically use the link in the message. Open the official service independently when you need to verify the event.
16 · VERIFY BEFORE TRUSTING THE RECORD
Not everything presented as evidence is necessarily authentic.
A screenshot can be fabricated.
A receipt can be edited.
A message can be impersonated.
A transaction claim can be false.
A profile can use another organisation's branding.
Evidence should therefore be evaluated in context.
Ask:
WHERE did this information come from?
CAN the underlying event be checked independently?
DOES the official account or transaction record agree?
HAS anything been cropped, edited or omitted?
17 · USE OFFICIAL SOURCES TO CONFIRM IMPORTANT FACTS
If a person says:
“Your bank transfer failed.”
Check your bank's official account.
If someone says:
“Your crypto transaction is stuck.”
Check the transaction through a trusted wallet or appropriate blockchain record.
If someone says:
“Your account has been hacked.”
Check the official security activity.
If someone says:
“Give me the code so I can investigate.”
Do not give them the code.
The purpose of evidence preservation is to support accurate understanding, not to replace verification.
18 · PRESERVE THE SOURCE OF THE INFORMATION
When recording evidence, note where it came from.
- WhatsApp message
- SMS
- Banking application
- Website
- Phone call
- Social-media account
- Wallet application
- Blockchain record
This makes it easier to distinguish direct evidence from something someone merely told you.
19 · KEEP FACTS SEPARATE FROM ASSUMPTIONS
Write:
“At 10:21 AM, I received an OTP.”
Not:
“The hacker definitely used the OTP at 10:21 AM.”
The first is something you observed.
The second may be an assumption unless the evidence establishes it.
Good incident records separate:
WHAT I KNOW
WHAT I OBSERVED
WHAT I WAS TOLD
WHAT I SUSPECT
WHAT I HAVE VERIFIED
20 · CREATE A SIMPLE INCIDENT RECORD
For a significant incident, create a short record containing:
INCIDENT:
What happened?
DATE/TIME:
When did it occur?
ACCOUNT/DEVICE:
What was affected?
EXPOSURE:
What information or access may have been exposed?
ACTION:
What did you do?
EVIDENCE:
What records have been preserved?
REPORT:
Who was contacted through an official channel?
STATUS:
What is currently known?
NEXT STEP:
What still needs to be verified or secured?
This structure can make a confusing event much easier to communicate.
21 · PRESERVE EVIDENCE WITHOUT SHARING IT PUBLICLY
You may be tempted to post:
“Someone hacked me. Here is the number.”
or:
“This is the scammer's account. Everyone should attack them.”
Do not expose sensitive information or encourage retaliation.
Public posting can create privacy, legal and security problems.
Preserve the information for the appropriate provider, investigator, authority or professional process.
22 · REPORT THROUGH THE RIGHT CHANNEL
Depending on the incident, the appropriate channel may be:
- Bank or financial institution
- Payment provider
- Mobile network provider
- Platform's official support
- Employer or IT/security team
- Cryptocurrency service provider
- Relevant law-enforcement or regulatory channel
- Qualified cybersecurity professional
Verify the reporting channel independently.
Do not use contact details supplied by the person you suspect caused the problem.
23 · DO NOT PAY TO PRESERVE OR RECOVER YOUR EVIDENCE
After an incident, someone may say:
“We can recover your messages.”
“We can trace the attacker.”
“We can unlock your account.”
“We can recover your crypto.”
“We need a processing fee first.”
Treat such offers as unverified until independently established.
A victim can be targeted a second time.
24 · EVIDENCE PRESERVATION IN A CRYPTO INCIDENT
If cryptocurrency moved without your authorisation, preserve:
- Wallet address
- Destination address
- Transaction hash
- Asset
- Amount
- Network
- Date and time
- Relevant messages
Do not send another transaction simply because someone says it will “reverse” the first one.
Do not provide your recovery phrase or private key.
Use independently verified wallet or service guidance.
25 · EVIDENCE PRESERVATION IN A BANKING INCIDENT
If money moved unexpectedly:
- Record the amount
- Record the transaction reference
- Record the date and time
- Preserve the receipt
- Preserve relevant messages
- Note the account or payment channel involved
- Contact the financial institution through its official channel
Do not rely on a suspicious caller's explanation of what happened.
Verify the transaction in your own official account.
26 · EVIDENCE PRESERVATION AFTER A LOST PHONE
Record useful device information such as:
- Device model
- IMEI where available
- Mobile number
- Approximate time and location of loss
- Device-management status
- Important account sessions
Use official device-management tools and contact the mobile provider through legitimate channels.
27 · EVIDENCE PRESERVATION AFTER ACCOUNT COMPROMISE
Preserve:
- Security alerts
- Unfamiliar device information
- Login times
- Password-change notifications
- Recovery-method changes
- MFA changes
- Suspicious messages
- Relevant transaction activity
Then secure the account through the official service.
Do not allow evidence preservation to delay urgent account protection when an attacker may still have active access.
28 · WHEN CONTAINMENT COMES FIRST
There are situations where preserving evidence must not delay immediate safety.
- An attacker may still be controlling a device.
- A financial account may still be actively losing money.
- A stolen credential may still be usable.
- A malicious application may still have access.
- A compromised account may still be sending messages.
In these cases, follow the appropriate containment or account-security process first, while preserving whatever information can safely be retained.
29 · WHEN TO GET PROFESSIONAL HELP
Consider qualified assistance when:
- Significant money is involved.
- Cryptocurrency has been stolen.
- A device may be infected.
- Multiple accounts may be compromised.
- Business systems are affected.
- Sensitive customer or identity information is exposed.
- You cannot determine what happened.
- The attacker may still have access.
- The incident may require formal investigation.
Do not allow an unverified online “expert” to become your investigator simply because they contacted you first.
30 · THE EVIDENCE PRESERVATION CHECKLIST
Before cleaning up an incident, ask:
□ Have I stopped the risky activity?
□ Have I recorded the date and time?
□ Have I preserved relevant original messages or emails?
□ Have I saved important screenshots where appropriate?
□ Have I recorded transaction references or hashes?
□ Have I recorded relevant account, device or wallet information?
□ Have I kept the original context where safe?
□ Have I avoided exposing passwords, OTPs, PINs, recovery codes or private keys?
□ Have I separated facts from assumptions?
□ Have I identified the official reporting channel?
□ Have I verified important claims independently?
□ Have I considered whether immediate containment is more urgent than preservation?
□ Have I documented what I have already done?
31 · THE MOST IMPORTANT QUESTION
When something goes wrong, do not ask only:
“How do I delete this?”
Ask:
“What information will help me understand and respond to this safely?”
Preserve what you can.
Protect what is sensitive.
Verify what matters.
Report through legitimate channels.
Then recover.
