Skip to content
Damaged car photographed for a motor claim

Photo evidence verified

Verify claim photos with forensic confidence.

Available on iOS and Android.

App-first collection
Captured in app. No editing before submission.
Automatic Processing
Provenance, recapture and forensic signals analysed
Observe & confirm
View detailed forensic and origin outcome

Insurance claim evidence software

Capture in the app.
Keep editing out.

The Claimsight app is the collection point. Claimants take photos in the app and submit them directly, without the ability to edit or replace the captured image before submission.

That closes the capture-to-upload editing gap. Each photograph arrives with its available device, time and location context, ready for provenance checks, image analysis and human review.

See the app capture workflow

01 / Evidence intelligence

Look closer.
See more than pixels.

Start with controlled app capture. Then examine the source and image, and make the findings useful to the person reviewing the claim.

Explore the evidence

Illustrative motor claim photograph showing side-panel damage

Always connected to the source

One image. Several questions.

Keep the photograph alongside the context, findings and limitations that inform its review.

The source / Where did it come from?

A photograph with
its context attached.

App capture brings the photograph and its available source context into the same evidence record, without a claimant editing step before submission.

Direct app capture
Capture and submit without editing or replacing the photo.
Device & file context
Inspect available source and metadata signals.
Time & location
Compare recorded capture context where available.
Gaps & inconsistencies
See what needs explanation or fresh evidence.

The value is in the evidence behind the finding.

Follow the workflow

02 / The primary collection route

Better evidence
starts before
the upload.

Evidence collection starts in the Claimsight app - not with a file chosen for upload. The controlled capture flow keeps the photograph connected to the claim from camera to review.

Already have the photographs?

Batch analysis and the API offer a secondary route for existing files. They can examine what you already hold, but cannot add the app’s capture safeguards after the photograph has been taken.

  1. 01

    Invite

    A clear request. A simple way in.

    Send a secure capture invitation linked to the claim. Passwordless authentication with the app.

    Secure invitations Request tracking
  2. 02

    Capture

    Capture it. Submit it. No edit in between.

    The claimant takes a fresh photo inside the Claimsight app. The capture flow does not allow them to alter or replace that image before submission and retains available device, timing and location context.

    Direct app capture No pre-submission editing
  3. 03

    Examine

    Let the checks do the groundwork.

    Assess provenance and screen the photographs for manipulation and synthetic-image indicators. Surface findings and limitations for review.

    Provenance Image forensics
  4. 04

    Review

    Keep the human in the decision.

    Inspect the findings, document your assessment and carry reports and secure evidence exports into the claim file.

    Reviewer notes Reports & exports

From finding to follow-through

See what your
reviewers receive.

The photograph. The findings. The context to act. All connected to a review your team can explain.

Understand the finding.
Own the next step.

Inspect the photograph alongside origin checks, image-analysis findings and available heatmaps. Then record a separate human review outcome and the reason behind it.

See where an image needs a closer look.

Switch between the original photograph and a heatmap, and adjust the overlay opacity to inspect the highlighted regions. Read the visual evidence alongside the supporting findings and limitations.

Evidence checked. Review recorded. Ready for the next step in your claim workflow.

Evidence review

Example / Vehicle damage
Illustrative vehicle photograph showing side-panel damage

Collection route

In-app capture

No editing or replacement between capture and submission.

Origin checks
Passed
Recorded device, time and location context is consistent.
Image analysis
Passed
No manipulation indicators detected.

Human review

Cleared

“Reviewed the photograph, capture context, findings and limitations alongside the claimant’s account. No further image-evidence checks required.”

Review reason / Recorded separately

See how this works with the evidence your team handles.

Built to fit your operation

Your workflow.
A clearer view.

Collect in the Claimsight app. Manage requests and review findings in the workspace, or connect the evidence workflow to your existing claims system.

A workspace for your team

Send app capture invitations, track evidence requests, examine findings and record human review in one place. Batch analysis also supports photographs you already hold.

Connected to your claims system

Submit photos through the API, receive status notifications, retrieve findings and bring reports back into the claim file.

03 / Built for scrutiny

Confidence needs
a chain of evidence.

The way evidence is accessed, reviewed and retained matters as much as the analysis itself.

01

Controlled access

Limit evidence and results to authorised users and the teams they belong to.

02

Recorded activity

Keep access to results, reports, exports and review updates in the audit record.

03

Retention & holds

Manage the evidence lifecycle with retention controls and legal-hold support.

04

Explainable outcomes

Keep automated indicators, limitations and human decisions clearly distinguished.

Before you get started

A few things
worth knowing.

Clear answers to the questions behind a useful pilot.

Talk to our team
Can a claimant edit the photo before sending it?

Not within the Claimsight app’s capture flow. The claimant takes the photograph in the app and submits it directly, without editing it or substituting an existing image. This protects the capture-to-submission step; analysis and human review still assess what the photograph shows.

Does Claimsight decide whether a claim is fraudulent?

No. Claimsight provides evidence and indicators to support human review. Your team decides what further investigation is needed and remains responsible for decisions about fraud, liability, coverage and settlement.

Can we analyse photographs we already hold?

Yes. Batch analysis and the API provide a secondary route for evidence already collected outside the app. Those files do not gain controlled-capture protection after the fact; checks depend on the available file and source information. The Claimsight app remains the primary route for collecting new evidence.

What does the claimant need to do?

The claimant follows a secure invitation into the Claimsight app, takes the requested photographs in the app and submits them directly for review. There is no editing or file-replacement step. The invitation provides passwordless access to the capture flow.

What happens when the evidence is inconclusive?

Incomplete or inconclusive findings remain visible. Reviewers can consider the available evidence, seek additional context or request fresh photographs. An unclear result is not treated as proof of fraud.

Can results fit into our existing claims platform?

Yes. The API supports photo submission, result retrieval, reports and evidence exports. Status notifications help your systems follow an analysis through to completion.

How do we start a pilot?

Request pilot access and describe your organisation and evidence workflow. After you verify your work email, the Claimsight team reviews the application and contacts you about the proposed scope and next steps.

See it in your workflow

Bring your next
claim into focus.

Tell us how your team collects and reviews photographic evidence. Let’s build a focused pilot around the questions you need to answer.

Applications are reviewed by the Claimsight team.