Preserve digital evidence without altering what matters.
During fraud, impersonation or sensitive publication, an immediate reaction can erase context. Simple, dated and reproducible preservation improves analysis and professional handover.
Secure threatened accounts and payments through official channels, but avoid deleting useful messages, logs or files before preserving them.
2
Capture the context
Save the full address, profile, publication, relevant comments, date and time. A screenshot without URL or context is fragile.
3
Retain originals
Keep emails in their original format, attachments intact and downloaded files without resaving them. Work from copies.
4
Build a timeline
Record what was observed, by whom and when, followed by actions and responses. Separate observation from interpretation.
5
Transfer securely
Share only what is necessary through an agreed channel. Never include passwords, temporary codes or complete identity documents in an initial message.
A screenshot is only one element
A screenshot shows what appeared on a screen but does not by itself prove authorship, integrity or origin. Add the URL, account, time, browsing context and original file where relevant.
For email, retain the exported message and headers. For a site, note the exact address and connected pages. For a conversation, preserve useful continuity without disclosing it to unrelated people.
Keep an understandable action trail
Name copies neutrally, retain an untouched version and log conversions. A file hash can support traceability, but does not replace context or the requirements of an authorised professional.
Store the case in a restricted, backed-up location separate from a potentially compromised system. Limit personal and sensitive data to what is needed.
Know when to hand over
Threats to a person, active compromise, extortion or fraudulent payment require prompt action by the appropriate services. OSINT may clarify public traces but cannot replace technical, judicial or medical response.
Where litigation is possible, ask counsel, an appropriate court officer or expert early about the suitable method of recording and transfer.
Separate collection from readable presentation
Conversion, annotation and cropping can change bytes and metadata. Keep collected and working files distinct. Record reference, format, origin, context and digest if calculated. A descriptive filename does not replace the link between file and observation.
Agree retention rules
Specify who may read, copy and transfer records. Keep access secrets separate from circulated inventories. Agree retention and handoff with responsible professionals, without promising a universal legal deadline or automatic admissibility from a hash alone.
Reading technical evidence
A hash compares files; it does not authenticate their story
SHA-256 produces a 256-bit digest, represented here by 64 hexadecimal characters. It is calculated from the file’s bytes.
Field or situation and its interpretation
Observed item
What it means
Renamed copy
The name is not part of the calculation; the content can retain its hash.
Recompressed image or resaved document
Bytes may change even when the document looks identical.
Hash calculated today
It proves neither creation date, authorship nor authenticity of the scene.
Record algorithm, digest, file and collection context. Compare against a reference retained separately.
Retain the original file or capture and record URL, time, timezone, device, collection method and access conditions. A signed-in page may differ from its public version. Do not put passwords in the collection note. Work on a duplicate when annotating or cropping.
Record each transfer: recipient, time and purpose. Keep file, metadata and collection context together and restrict circulation. A hash helps compare copies but does not prove publication time or truth of the content. A screenshot may omit interactions or hidden material; describe its scope. For a serious incident, preserve the original and involve a competent specialist.
Collection
Document context, time and authorised method.
Integrity
Retain the original and work on a copy.
Transfer
Record recipient, time and purpose.
Does a screenshot preserve an entire page?
It records the visible view, but can omit the URL, interactions and hidden content. State its scope and preserve other available material without altering the original.
Try the reasoning
A copy receives a different filename. Does this establish changed content?
Reasoning: No. Filename and content are separate. Document operations and hashes without attributing unsupported meaning to the name.
For each point, record what the material actually supports. “Supported” applies to the specific observation, not to the entire case. A contradiction needs explanation; missing material remains an open question.
Define the question
Record the source
Test the observation
State the limits
Entries stay in this page until you leave or reload it. Nothing is saved or submitted by this tool. Use neutral references instead of personal data or credentials.
How to write a useful conclusion
Editorial examples, not findings about your case
Material
Useful wording
Next check
One dated source
The consulted source stated X on the recorded date.
Check its origin and whether it still applies.
Multiple copies of one claim
Several pages repeat X; independent corroboration is missing.
Find the original and a source with independent evidence.
Conflicting sources
A states X while B states Y; the difference is unresolved.
Compare dates, scope, identifiers and definitions.
No matching result
No result was found in the recorded scope.
Describe queries, coverage and access limitations.
What to check and what to record
Use this grid to turn the method into a reviewable case file. A missing item remains an open question. The interpretation limit prevents a finding from becoming an unsupported conclusion.
Topic-specific checks
Check
Useful record
Interpretation limit
Email
Native export with headers, untouched attachment and receipt time.
Forwarding can remove useful headers.
Changing page
Full URL, zoned time, contextual capture and signed-in or public state.
A capture records an observation; it does not certify authorship.
Hash
Algorithm, hash, filename and calculation time.
A hash supports later stability, not initial authenticity.
Common pitfalls
Four shortcuts that weaken the result.
Cropping the only copy
Always keep the complete original before annotating or obscuring data.
Renaming without a log
Simple version control preserves order and provenance.
Replying publicly
A response can amplify content, reveal strategy or cause deletion.
Sending everything
Useful collection stays targeted; over-collection exposes third parties.
Practical questions
Frequently asked questions.
Should every screenshot be printed?
No. The digital file, context and traceability are often essential. Printing may supplement but not replace the original.
Is a file hash enough?
No. It can show that a file has not changed since hashing, but does not alone prove its origin or truth.
How long should the file be retained?
That depends on the risk, applicable duties and possible proceedings. Keep it only as necessary and obtain tailored advice for legal matters.
Public references
These primary references support the checks described here. The sequence and working sheet are an IIS editorial method; a cited organisation does not endorse this guide. Read each reference within its stated date, jurisdiction and scope.
HRC Berkeley / OHCHR — Berkeley Protocol. Framework for collecting, preserving and verifying digital open-source material. It was developed for human-rights and international investigations; using its documentation principles does not establish admissibility in a particular proceeding.
Editorial scope
Published by Internet Intelligence Service on 15 September 2026. Last content update: 29 October 2026. This educational guide describes a lawful, defensive method. It is not legal advice, an emergency service or authority instruction.