A driver sends his insurer a trimmed 18-second video of a rear-end collision. The adjuster asks for the original recording from the card. He has already formatted it. What he has left is a re-encoded clip with a start and end point he chose himself, and the other party claims he brake-checked them. Without the untouched original, he cannot show what happened in the 40 seconds before impact.
That story is the whole reason chain of custody exists. Dash cam footage is only as useful as your ability to say "this file is exactly what the camera wrote, and nobody changed it." The good news: video files from a RedTiger camera already carry a lot of built-in proof. You just have to stop destroying it.
In legal terms, chain of custody is a documented, unbroken record of who handled evidence, when, and what they did to it. For a dash cam that is much simpler than it sounds for criminal cases — you are a civilian, not a police evidence tech. In practice, insurers, claims adjusters, and small-claims judges want four things:
You can satisfy all four with about ten minutes of work, done the same day as the incident.
When something happens, the instinct is to pull the card so nothing loops over. Do not unplug the camera and do not yank the card while it is writing — that is how you corrupt the last, most important file. Instead, use the camera's own protection button or the app to lock the current clip. On RedTiger models the emergency/lock function is a dedicated button on the unit or a tap in the app; locked files are skipped by loop recording and survive a 128GB card filling up.
If you cannot lock it, power the camera down normally with the ignition, then remove the card. A clean shutdown flushes the file table and prevents the "card not readable" problem that turns a strong case into a frustrating afternoon.
Plug the card into a computer with a card reader and copy the entire DCIM folder to a folder named with the date and your initials, for example 2026-11-07-accident-JM. Copy — do not cut. Do not use the camera's WiFi app as your only transfer, because some app workflows re-encode or trim, and you lose the original bitstream and its embedded metadata.
Once the files are on the computer, mark the card as evidence. Put it in a paper envelope, write the date and time of the event on it, and do not put it back in the camera until the claim closes. A 64GB card costs less than a deductible; treat it as disposable.
This is the step almost nobody does and the one that ends arguments. A hash is a short fingerprint of a file. If one byte changes, the fingerprint changes completely. Generating one takes a single command:
Get-FileHash .\FILE.mp4 -Algorithm SHA256shasum -a 256 FILE.mp4Copy the output into a text file, save it next to the videos, and email that text file to yourself. The mail server stamps it with a date you did not set. If anyone later questions whether your clip was edited, you hand over the hash and they can run the same command on their copy. Matching fingerprints mean identical files. This is the same mechanism companies use to verify software downloads, and it is accepted far more readily than your word.
Keep it boring and factual. Five lines are enough:
| Field | Example |
|---|---|
| Camera and card | RedTiger F7N Elite, Samsung EVO 128GB, serial from the card sticker |
| Vehicle and mount position | 2019 Honda Civic, camera behind mirror, 12V socket power |
| Event date and clock | Nov 7 2026, 16:42 local; camera clock reads 16:41:38 |
| Files copied | 17 files, DCIM/Movie, 16:35–16:50 window |
| What you did to them | Copied once, hashed, no edits, no trimming |
That last line is the one that saves you. Note any clock offset. Dash cams drift a minute or two over months, and a two-minute discrepancy between your footage timestamp and the police report timestamp is the most common reason an otherwise clean clip gets challenged. If your camera clock is off, say so in the log and note the internet-synced time you actually observed.
Send a copy through a service that preserves the file — a shared drive link to the folder — rather than a messaging app that compresses video. WhatsApp and most phone messaging apps crush a 4K file until license plates become grey smudges. You have then technically preserved evidence while making it useless. If you must share by link, allow download rather than view-only, because some insurer portals cannot handle streaming playback.
When the claim settles, keep the folder and the hash file for at least as long as your jurisdiction's limitation period for injury claims, commonly two to three years. Storage is cheap; reconstructing a deleted clip is impossible.
The camera does its part well. Files are written in standard MP4 containers with the timestamp burned into the frame, and loop recording plus emergency lock means the segment around an impact is usually still on the card when you get home. A 2-channel setup recording front and rear simultaneously gives you two independent views of the same second, which is far more persuasive than one angle plus a description.
What the hardware cannot do is protect you from your own habits. The camera will not stop you from formatting the card "to free up space," from trimming a clip for social media and then sending the trimmed version to your insurer, or from leaving the card in a hot car until it fails. Those are the failure points, and they are all human.
Want footage that survives the trip from windshield to claims desk? A dual-channel RedTiger setup records front and rear at once, so one card failure never costs you the whole event.
None of this requires legal training. It requires doing it before the adrenaline wears off — which is exactly when most people delete the one file that would have settled the argument.
← Back to Blog