LVSR Systems — Forensic Capture

WHAT WE DO, IN PLAIN WORDS

We build a system that makes evidence impossible to fake.

When our camera takes a picture, it is encrypted and signed inside the sensor, before it is even stored. If a single pixel is changed afterwards, it shows immediately. Today, footage from war zones is dismissed as fake or AI-generated. With qXauri, a court can prove the material is genuine. The whole system is built for mobility: one operator, one drone, one laptop — deployable anywhere, no infrastructure required. Our customers are international justice bodies, national authorities, and human rights organisations.

WHY THIS EXISTS

At a conflict site, the truth is the first thing attacked.

When something happens in a war zone or at the scene of an atrocity, what actually occurred is contested almost immediately. Footage is dismissed as fake. Records are quietly altered. Witnesses are pressured, moved, or silenced. Years later, when a court finally looks at the evidence, no one can prove where it came from — and the people responsible walk free.

LVSR exists to close that gap. It captures events as they happen and seals each one with proof of where it came from, the exact moment it was taken, and the fact that nothing has been changed since. Not a claim you're asked to trust — math that anyone can check.

The aim is simple: make the truth from a conflict site impossible to deny, dismiss, or quietly rewrite — so it can stand in a courtroom and hold someone to account.

THE FILM

Watch the concept

From target selection to sealed evidence opened at the facility — the qXauri workflow in two minutes.

Drone footage in this film is AI-generated to visualise the mission concept. The console, cryptography and unlock sequence shown are the real working system. We say so plainly — building systems that make truth provable starts with telling it.

HOW IT WORKS

One operator. One drone. Court-ready evidence.

Fully mobile — no infrastructure, no base station. And two channels, deliberately: a control link that flies the aircraft, and an evidence path the control link never touches. Every hop below, from photon to courtroom.

01 · Deploy

Operator moves to the field

One person, one backpack: drone, charged batteries, laptop with the radio link. Deployable anywhere — mobility is the point.

02 · Task

Click the map — the drone flies itself

The operator marks a location; the aircraft flies the mission autonomously and documents the site from multiple angles and altitudes.

Console → agent: the command goes over an authenticated, token-protected API.

Agent → flight controller: translated to MAVLink on the 433 MHz radio. Commands, position, battery, status — kilobytes, never evidence.

Telemetry streams back live: where it is, what it is doing, when the pass is done.

03 · Capture & seal

Encrypted before it is even stored

The raw frame exists only in the device's working memory — the seal closes before anything touches disk.

Photon → sensor: light hits the camera at the incident site; the frame lives in memory only.

Hash: a SHA-256 fingerprint is computed from every bit — change one pixel and the whole value changes.

Sign: the device signs that hash with its Ed25519 identity key. GNSS position, time and fix quality are recorded with it.

Encrypt: sealed with XChaCha20-Poly1305 to the customer's X25519 public key. The drone carries only the padlock — from this instant nothing on board can read it.

Chain: appended to the hash-chained ledger — every entry locks the one before it; gaps and reordering become visible.

Store: only now does anything touch disk — sealed ciphertext. Plaintext never lands.

Why these algorithms: all primitives are open, standard and independently auditable — deliberately. In evidence, invented cryptography is a defect, not a feature.

04 · Return

The drone comes home

Mission complete — or control link lost — the aircraft returns and lands on its own. Everything on board is sealed ciphertext with a signed position-and-time trail.

05 · Extract

One cable, sealed files off

The operator connects the laptop and pulls the sealed containers with one click — ciphertext plus its signed fingerprint and chain entry.

The console verifies chain integrity on the spot — but it is deliberately key-less. The operator holds evidence they cannot open.

06 · Forward

Send over any channel

Upload, courier, USB stick — the transport needs no trust, because the security travels inside the file.

XChaCha20-Poly1305 is authenticated encryption: an intercepted copy cannot be read, and a modified copy fails authentication on arrival.

07 · Unlock & verify

Only at the customer's facility

The evidence locker. The one private key lives here on a physical USB key — and nowhere else on Earth.

The review console stays sealed until the physical key stick is inserted. The X25519 private key never leaves the facility.

Each file's SHA-256 is recomputed and compared to the fingerprint the device signed at capture. Every signature and chain link is checked.

The verdict is binary: genuine and unaltered — or visibly tampered. An attacker cannot alter a file and keep its fingerprint, and cannot sign a new one without the device's key.

IF THINGS GO WRONG

Jammed. Destroyed. Captured. Still safe.

The system assumes hostile conditions. No protection below depends on a human noticing in time.

Interference / jamming

Losing the control link does not lose evidence — the channels are separate. The aircraft flies its mission autonomously and returns home on link loss. GNSS quality is judged per capture: a degraded or spoofed fix is recorded as untrusted rather than silently accepted.

Destruction

Nothing readable is ever on board, so a downed aircraft leaks nothing. Multiple drones can seal the same scene independently — corroborating witnesses with no shared link to take down — so losing one aircraft does not erase the record.

Capture & key theft

A taken drone cannot read its own recordings — the decryption key was never on it. Its signing key is short-lived: authorised per mission, it expires on its own. A stolen device's ability to sign dies automatically, whether or not anyone is left to notice.

Silence is a signal

An aircraft that fails to check in past its window is automatically flagged and revoked — no human decision required. Every capture also sits in a signed position-and-time chain, so footage inserted after a capture must fall into a visible gap in the timeline.

The endgame

The roadmap closes the last door: a hardware secure element generates the signing key inside a tamper-resistant chip that never releases it. At that point, physically capturing the aircraft yields nothing at all.

PROGRESS

Built, not promised

What exists today, verified by our own hands — and what comes next.

✓

Capture-and-seal on real hardware — imagery sealed, signed and hash-verified on the device at capture

Working

✓

Facility review console — evidence stays locked until a physical USB key is inserted; tamper detection live

Working

✓

Autonomous survey flight — waypoint missions with multi-angle, multi-altitude documentation, proven in simulation

Working

✓

Concept film — the full workflow, published

Live

◐

Field aircraft assembled — drone built; motor tests and first flight underway

Now

›

First sealed capture in real flight — the same pipeline, airborne

◐

Security hardening — short-lived device keys and automatic revocation on silence in development; hardware secure element on the roadmap

Building

WHY IT'S BUILT THIS WAY

Designed against four adversaries

The field is assumed hostile — the radio is tapped, the drone may be seized, and not everyone in the loop is trusted. Each design decision answers a specific attacker.

Interception

The radio is tapped.

Comms are assumed compromised end to end. Because data is sealed at the sensor, a captured stream is ciphertext keyed to a facility the attacker can't reach.

Seal-at-sensor, end-to-end encryption

Tampering

The footage gets edited.

Every capture is hashed and signed in hardware the moment it's recorded. Alter a single byte and verification fails at the facility — silently editing evidence is impossible.

Hardware signing + hash-chained ledger

Device capture

The drone is seized.

A captured or hacked drone yields nothing readable. It never holds the private key and never stores plaintext — past captures stay sealed.

No private key on device · no plaintext at rest

Insider

Someone in the loop turns.

No operator, integrator, or LVSR employee can decrypt anything. The private key lives only with the customer's facility — trust is removed from people and placed in math.

Customer-held keys · zero vendor access

HOW THE PROOF WORKS

The technical spine, in plain terms

You don't have to take any of this on faith — that's the point. It's built from standard, well-understood cryptography that an independent expert can inspect and verify. Here's what each piece does.

Locking the image

Every capture is encrypted the moment it's recorded, using a key only the customer's facility can open. Even we can't read it. (XChaCha20-Poly1305 per capture, sealed to the customer's X25519 public key.)

Proving the source

Each device signs its own footage with its own identity key — so you can prove exactly which device recorded what. (Per-device Ed25519 signing key; software-protected today, migration into a hardware secure element is on the roadmap.)

Protecting the timeline

Every event — captured, moved, received — is logged in a chain where each entry locks the one before it. Change anything earlier and the chain visibly breaks. (SHA-256 hash-chained custody log.)

Opening it safely

The only key that can unlock the footage lives with the customer's facility — never on the drone, never with us. The review console stays sealed until a physical key is inserted. (Facility private key carried on a provisioned physical USB key; HSM integration on the roadmap.)

Checking the work

Anyone — a court, a defence team, an auditor — can re-run the checks and confirm the evidence is genuine and untouched, without holding any key. (Exportable, independently verifiable chain of custody.)

WHO IT'S FOR

For anyone who refuses to let the truth disappear

From a lone journalist in the field to a national ministry — LVSR is built for the people and institutions that put the truth first, and need a record no one can wave away.

[ 01 ]

Individuals prioritizing truth

Journalists, field investigators, and frontline witnesses documenting what others would bury — so their record can't be dismissed as hearsay.

[ 02 ]

Accountability orgs

Human-rights monitors gathering proof of what happened, in a form no party can dismiss as fabricated.

[ 03 ]

International courts

Tribunals and bodies such as the ICC — capture chains attributable and independently verifiable across jurisdictions.

[ 04 ]

Democracies & ministries

Lawful documentation of incidents and operations, with evidence that survives legal challenge.

THE COMPANY

One person, accountable for every line

No layers, no committee. The technology people rely on is built and answered for by the person who made it.

Axel Mikkonen Larsson

Founder · Sole developer · Livsro Group AB

LVSR Systems is the work of one person — from the capture firmware to the cryptography behind an audit. The people who depend on this technology deal directly with the person who built it.

LVSR is built by Livsro Group AB, a registered Swedish company. Full company background, ownership and transparency live on the parent-company site → livsroab.se ↗

PARTNERS

We can't build this alone — and we're not trying to

LVSR is one person with a mission far larger than one person. Getting there means working with others who want the same thing: a world where the truth can't be erased. We're actively looking for three kinds of partner.

Investors

Fuel the build

We're open to investment to fund continuous development — the verification platform now, capture hardware next. If you back technology built for accountability and truth, we'd like to talk.

Drone & hardware

Bring the platform

We'd rather integrate with excellent drone and sensor makers than reinvent them. Your airframes and hardware, our encryption and chain of custody — a natural fit. Let's explore a cooperation.

Open source

Solve the hard problems

The core system is proprietary — but the hardest problems shouldn't be solved in isolation. On specific, well-defined challenges we open the door to the open-source community, and credit every contribution. If you're drawn to difficult cryptography and provenance work, there's a place for you here.

SECURE CHANNEL

Request a briefing

Vetted operators only. Briefings cover deployment, key custody, and the admissibility model for your jurisdiction.