Contact ussales@ventavid.com
VentaVid

Digital evidence: what makes a photo or video hold up in a dispute

Digital evidence in a dispute: six questions a third party asks about a photo or video, from who made it to how long it was kept

In this article

The short version.

  • What holds up: a photo or video whose origin, time, integrity, handling and completeness you can show from records made at the time, and that someone outside your organisation can check without taking your word for it.
  • What does not: a file whose only history is "it was in the claim folder", however genuine the picture.
  • Who this is for: claims managers, complaints and disputes leads, and legal or compliance officers at insurers, lessors, rental companies and property managers.

A photo or video holds up in a dispute when you can answer six questions about it with records that were made at the time: who made it and when, whether it has changed since, who handled it, whether it is the whole submission, whether an outsider can check all of that, and why you still have it. The image itself answers none of them. The record around the image does.

If you lead complaints or disputes at an insurer, a lessor or a lettings business, the awkward moment comes months after the decision, when an ombudsman's investigator or the other side's solicitor asks where a photo came from and the honest answer is "an email attachment, we think". Venta Capture, a product of VentaVid, is built for that gap. Book a demo with one of your own case types if you would rather see it than read about it.

This describes how evidence gets tested. It is not legal advice, and the rules differ by country and by forum.

What does "hold up" mean for digital evidence?

Two different things get mixed together: whether a decision maker will look at the file at all, and how much they will believe it. Lawyers call the first admissibility and the second weight.

Getting the file looked at is usually the easier half. Three published examples, in general terms:

  • Civil courts in England and Wales. Under section 8 of the Civil Evidence Act 1995, a statement in a document may be proved by producing the document or a copy, "authenticated in such manner as the court may approve". The court keeps control of what it admits under rule 32.1 of the Civil Procedure Rules.
  • US federal courts. Rule 901 of the Federal Rules of Evidence asks the party relying on an item to "produce evidence sufficient to support a finding that the item is what the proponent claims it is".
  • An ombudsman. The UK's Financial Ombudsman Service describes itself as "a free, informal alternative to the courts" that decides on "the facts and evidence available in each case", and notes that "written evidence or paperwork from the time is often very helpful".

Weight is decided by the adjudicator, case by case, and no technology settles it in advance. What you control is how many of the obvious challenges your records can answer. That is what "holds up" means in the rest of this post. For the term itself, see digital evidence in our glossary.

Try it on your own phone

Want to see what a guided capture looks like?

Request a capture link and we email you one. Open it on your phone, follow the steps, and see exactly what your customer or field team would see. No app, no account.

Request a capture link →

Which questions will a third party ask about a photo or video?

Six questions cover nearly every challenge. Each has a weak answer and a strong one.

QuestionWeak answerStrong answer
Who made it, and when?The date inside the fileA recorded session plus a receipt time and an independent timestamp
Has it changed since?"Nobody here would edit it"A fingerprint taken on receipt, under a signed seal
Who handled it?Whoever had the folderAn automatic log of every access and action
Is it complete?The photos we attachedThe whole submission, sealed as one set
Can an outsider check?A statement from your IT teamA check they can run themselves
Why do you still hold it?We keep everythingA written retention period with a reason

Who made the recording, and when, and how do you know?

Start with the "when". There are three clocks, and disputes regularly confuse them.

  1. The time the phone claims. The capture date written into the file's metadata comes from the phone's own clock, which the user can set, and the field can be edited afterwards. The practice direction on electronic disclosure in England and Wales says as much in its definition: metadata "may be created automatically by a computer system or manually by a user" (Practice Direction 31B).
  2. The time your server received the file. The sender cannot set it. It is a record made by your system, which makes it stronger, but it is still your clock and your log.
  3. The time an independent authority attests. A timestamping authority, a party that is neither you nor the customer, signs a statement that a particular fingerprint existed at a particular time.

The standard behind it, RFC 3161, describes the authority's role as establishing "evidence indicating that a datum existed before a particular time". The other side can no longer suggest the case record was assembled last week, because a party with no interest in the outcome vouches for the date.

In Europe this has a legal footing. Article 41 of the eIDAS Regulation says an electronic time stamp is not to be denied admissibility only because it is electronic or not a qualified one, and that a qualified electronic time stamp "shall enjoy the presumption of the accuracy of the date and the time it indicates and the integrity of the data to which the date and time are bound".

A receipt time and an independent timestamp show that the file existed and reached you by that moment. They do not show when the dent, the leak or the stain appeared. A recording made in a session your system started, and received minutes later, leaves a small and documented gap between "made" and "received". With a file from a camera roll, the gap is unknown.

The "who" is harder than the "when". No file identifies a person. A record shows which request the material answered, which link was opened and what the person declared. Whether the policyholder or a neighbour held the phone is a question for a human reviewer.

How do you show the file has not changed since you received it?

With a fingerprint taken at receipt. A digital fingerprint is a short value calculated from the file's contents. Recalculate it a year later: if the value matches, the file is the same, bit for bit.

Courts know the idea. The committee notes to Rule 902(14) of the US Federal Rules of Evidence put it this way: "If the hash values for the original and copy are the same, it is highly improbable that the original and copy are not identical."

A fingerprint alone has a gap. If it sits in a database you administer, someone can ask whether it was replaced along with the file. Two things close that gap:

  • A signed seal. The fingerprints of every file in the submission go into a manifest, and the manifest is signed. Changing a file, or the list of files, breaks the signature. That is what tamper evident means: a change is not prevented, it shows.
  • Timing. A seal applied on receipt covers the whole life of the file in your hands. A seal applied the day the complaint arrives covers nothing before that day. The glossary entry on the sealed submission explains why "on receipt" and "on demand" are different things.

And keep the original. A compressed copy in a report or a screenshot in a decision letter is a new file with a new fingerprint.

Who handled the evidence between receipt and the hearing?

This is chain of custody, and the definition is older than smartphones. The US National Institute of Standards and Technology defines it as a process that tracks evidence "by documenting each person who handled the evidence, the date/time it was collected or transferred, and the purpose for the transfer".

For a claim or a complaint file, that means a log the system writes by itself:

  • when the request went out and who sent it
  • each time the link was opened, and when the submission arrived
  • who opened the case, who it was assigned to, and who changed its status
  • every note, retake request, download and shared view link

An audit trail written by the system as things happen carries more weight than a handling note typed up afterwards, because it was not written with the dispute in mind.

It also helps on the formal side. In civil proceedings in England and Wales, section 9 of the Civil Evidence Act 1995 allows a document "shown to form part of the records of a business" to be received without further proof, on a certificate signed by an officer of the business. A clean log makes that certificate easy to sign.

Where do chains break? At the handoffs: a photo forwarded to a contractor by messaging app, a video downloaded to a laptop, an attachment re-uploaded under a colleague's name. Each creates a copy with no history.

Is it the whole submission, or a selection?

If you declined a claim on the strength of 4 photos, the other side wants to know whether there were 12. A selection is not dishonest. It is hard to defend unless you can show what it was selected from.

Completeness comes from treating the submission as one object:

  • One manifest for everything received. Every photo, every video, every answer the person gave, sealed together, so the count is fixed at receipt.
  • Retakes kept and linked. A second attempt sits next to the first, with the stated reason, instead of replacing it.
  • Context kept with the media. The instruction the person saw before each shot, and their answers. "Show the whole wall" and "show the damage" produce different photos.
  • Gaps recorded as facts. A declined location or a skipped optional step is part of the record, stated neutrally.

When both parties hold the same record from the day it was made, a later argument about what was submitted has little room. Our post on deposit dispute evidence shows how much an adjudicator leans on a record both sides saw at the time.

Can someone outside your organisation check the evidence?

Everything above can be true and still rest on your say-so. The test is whether an investigator or an opposing expert can verify the record without logging in to your system.

That takes three things:

  1. A copy of the original files and the manifest that lists their fingerprints.
  2. A signature they can verify with a public key, so they know the manifest is the one sealed at receipt. The glossary covers public key verification in plain terms.
  3. A timestamp they can check with the authority that issued it, not with you.

Most of the time nobody runs the check. A record that can be checked is rarely challenged.

How long did you keep it, and can you justify that?

Long enough to defend the decision, and not a day longer than you can explain. Both halves get tested.

Too short, and the evidence is gone when the complaint arrives. Too long, and you hold images of people's homes and faces without a reason. The UK Information Commissioner's Office is blunt about the second: the law "does not set specific time limits", that is for you to decide and document, and "personal data held for too long will, by definition, be unnecessary" (ICO guidance on storage limitation).

What a regulator wants to see is a data retention period per case type, written down with its reason (the complaint window, the limitation period, a regulatory duty), and a system that deletes on that rule.

Our post on photo evidence for inspections covers retention floors and ceilings in detail.

What does a sealed, timestamped file still not settle?

  • Whether the scene is what it appears to be. A genuine recording can show a staged situation, older damage or a different object of the same model. Integrity tells you the file is the one you received. It says nothing about what happened before the camera started.
  • Whether an uploaded image was ever a photograph. Sealing a file that arrived as an upload fixes it from that moment. If it was generated or edited before it reached you, the seal preserves the edit. A recording made in a session you started is worth more than a file someone already had, as set out under upload versus capture.
  • The outcome. A strong record can support the wrong decision. The adjudicator weighs the evidence.

For what to ask customers for in the first place, see photo evidence for insurance claims.

How do you test one of your own closed cases?

Pick a case from 9 to 12 months ago where a photo or video drove the decision. Answer in writing, from records only:

  1. Which exact file did the decision rest on? Can you produce the original, not a copy in a report?
  2. When did it reach you, and what besides the file's own date says so?
  3. Can you show it is unchanged since that day?
  4. Who opened, forwarded, downloaded or commented on it, and when?
  5. Was it everything the customer sent? Where is the rest?
  6. Could the other side's expert confirm points 2 and 3 without your help?
  7. Under which retention rule is it still here?

Points 2, 3, 5 and 6 are where a file usually goes quiet, and all four are decided at the moment of receipt. You cannot add them later.

Where does Venta Capture fit, and where does it not?

With Venta Capture you send a secure, personal capture link, the customer records photos and video in the phone's browser by following your workflow, and the submission arrives as one case. How that case is built answers several of the six questions.

  • When. The server records the receipt time, and every case gets a timestamp from an independent timestamping authority, which can be a qualified one. Photos and video recorded in the session carry a visible stamp with date, time and seal. The file's own metadata is shown as unverified.
  • Changed since. The case is sealed on receipt: a fingerprint per file and a signed seal over the submission.
  • Who handled it. An activity timeline records the link being created and opened, the submission, assignment, notes and retakes. A reviewer marks each deviation as handled or as a genuine deviation, with name and time.
  • Complete. The seal counts the files it covers, videos included. A retake becomes a linked case with the stated reason. Gallery uploads, where a workflow allows them, are labelled "Provenance: Not verified".
  • Outside check. A reviewer prints a proof of seal: one sheet that names who stands behind each link in the chain and leads to a verification page.
  • Retention. Retention and automatic purging are configurable.

With the session record, that comes to more than 25 control points per submission: observations for a reviewer, who decides.

Where it does not fit:

  • Evidence you already hold. It seals new submissions from the moment they arrive. It cannot give last year's email attachments a history.
  • Identity. It records the session and the device. It does not establish who the person is.
  • A ruling. No software decides admissibility or weight.

Per desk: remote claim inspection and property.

Frequently asked questions

What is digital evidence in a dispute?

Any information held as data that a decision maker may rely on: photos, video, messages, system logs and the metadata around them. In a claim or complaint it is usually the customer's photos and video plus your own records of how they arrived and what was done with them.

Are photos and videos from a phone admissible as evidence?

In general terms, yes, provided someone can show the material is what it is said to be. The rules differ by country and forum, and the decision maker decides the weight. Ask your own legal adviser about a specific case.

What does an independent timestamp add?

A party outside your organisation attests that a specific fingerprint existed at a specific time. It stops the argument that the record was created or rearranged later, and under the eIDAS Regulation a qualified time stamp carries a presumption of accuracy.

Does a seal show that a photo is real?

No. A seal shows the file has not changed since it was sealed. Whether the scene was genuine, staged or generated before it reached you is a separate question, which is why recordings made in a session you started are stronger than uploaded files.

Start with the next case, not the old ones

You cannot repair the record on a closed file. You can decide that from next month one case type arrives sealed, timestamped and complete.

The free plan is enough to try that, with no credit card: start for free and send the first link to your own phone. Or book a demo and bring the case type that produces the most complaints. We will build the workflow for it on the call.

Turn any smartphone into your eyes on site

Guided video and photo capture. No app, no account, sealed on receipt.