We live in the first era where seeing and hearing are not believing
AI can generate a video of something that never happened, clone a voice from a few seconds of audio, invent a photograph, and stamp any of it with a location on the other side of the country. That breaks trust in two directions at once — and both directions hurt you.
Fakes get believed
A convincing forgery now takes minutes and costs nothing. Video of damage that never happened. A "before" photo generated last night. A recorded voice saying words nobody ever said. Location data pointing at an address the phone was never near. If a fake can pass for real, every real record is worth less.
Real work gets doubted
The flip side is worse for you. Once everyone knows this material can be faked, the cheapest way to attack an honest report is to suggest it was. How do we know that video wasn't edited? That the audio is really you? That you were ever actually on site? Those are now free shots at your credibility.
You should not have to argue about whether your evidence is real.
You should be able to prove it.
One file that proves itself:
the ReportBundle.zip
From the moment a report is named to the moment the first report is generated, ScribeCam is quietly building a sealed archive of everything. It arrives as a single zip file that opens on any computer — no ScribeCam software required, ever.
Think of it like an evidence bag with a tamper seal — except the seal is math, it covers every single item inside, and anyone in the world can test it for free.
Inside are your videos, your spoken words, every photo, your location and motion record, the finished report, and a certificate that explains exactly what is being certified. Every one of those files carries a digital fingerprint — the technical name is a SHA-256 cryptographic hash — computed on your phone, before anything left the device.
A fingerprint is a 64-character number produced from a file's exact contents. The same file always produces the same number. Change one pixel of one photo, one frame of one video, one word of the transcript, one coordinate of the track, and the number becomes completely different. That is the whole trick, and it is why it cannot be argued with.
Chain of custody, from the first second of recording
Nothing here happens later, in an office, on a server. The phone that captured the evidence is the thing that fingerprints it, certifies it, and seals it. It works the same way for every report on the account, whoever filed it.
You capture
Video, photos, your narration, and sensor readings — motion, compass, GPS, barometer — recorded on your device as you work.
The phone transcribes
Your spoken words become a transcript on the device itself. The sensor stream carries its own tamper-evident hash chain, written while you record.
Every file is fingerprinted
The instant your report is finished, each file is streamed through SHA-256 on the phone. The hasher self-tests against known answers first — a wrong fingerprint is worse than none.
The receipt gets its own fingerprint
All the fingerprints are written into one itemized receipt (manifest.json). That receipt is then fingerprinted itself. That number is the root fingerprint — one number for the entire bundle.
It's registered and sealed
The root fingerprint is registered with ScribeCam at that moment, an independent authority timestamps it, and the whole thing is zipped shut.
Four kinds of evidence.
One seal over all of them.
A seal that only covered photos would leave three open doors. Every stream your phone records is fingerprinted individually and bound into the same sealed archive.
Video
The full, unedited recording of every take — not a trimmed export. Highlight clips are cut later and are labeled as derived, so the original is never confused with an edit of it.
Voice
Your narration, in your own voice, inside the recording — plus the transcript the phone produced from it on the device. Both are fingerprinted, so the words can't drift from the audio.
Photos
Every photo you took, grouped by recording, each with its own fingerprint — and each bound to the words you were speaking at the moment you took it.
Location & motion
GPS, compass heading, barometric pressure and movement, recorded continuously as you work. This stream carries its own tamper-evident hash chain, written while you record — then it is fingerprinted and sealed like everything else.
Because all four are sealed together under one root fingerprint, they cannot be separated after the fact. Nobody can keep the video and quietly swap the location, or keep the photos and replace what you said about them. The set moves as one thing, or it fails as one thing.
One pixel. Completely different number.
Here is the same photo twice. The second copy has exactly one pixel altered — invisible to any human eye, and to any software that just looks at the picture. The identical test catches one altered frame of video, one edited syllable of audio, or one changed GPS coordinate.
Verify For Free: https://app.scribecam.com/verify
There is no third possibility. A file either reproduces its fingerprint or it does not. That is what "immutable" means here — not that nobody can ever change a copy, but that nobody can change one without it being provable.
Open the zip. Everything is right there.
One folder, named for your report. No proprietary format, no viewer to install, nothing that expires.
└─ Roof Inspection — 4218 Marlow Ave/ ├─ Start Here — How to Use This File.pdf ├─ Report/ the finished report + its data ├─ Media Files/ │ ├─ Videos/ full, unedited recordings │ ├─ Video Clips/ highlight clips, by recording │ └─ Photos/ every photo, by recording ├─ Recording Data/ transcripts, sensors, image labels └─ Proof of Authenticity/ ├─ Certificate of Authenticity.pdf ├─ manifest.json the itemized receipt ├─ seal.json root fingerprint + signatures └─ timestamp.tsr independent RFC 3161 token
Start Here — How to Use This File
A plain-English cover document written for the person holding the zip, not for an engineer. What it is, what it proves, how to check it, and what to do with it. No jargon left unexplained.
Certificate of Authenticity
The formal document. It states the Bundle ID, the root fingerprint, the seal time, the account and the device — then lists every single file with its individual fingerprint, and prints the exact commands anyone can run to check them.
manifest.json — the receipt
One line per file, machine-readable. This is what a forensic examiner or opposing expert will actually work from. It also records how the report was generated, so nothing about the process is hidden.
seal.json + timestamp.tsr
The cryptographic proof files: the root fingerprint, the device signature, the ScribeCam registration record, and a signed timestamp token issued by an authority that has nothing to do with ScribeCam.
"Sealed" does not mean locked
This is an ordinary zip file. Open it whenever you like. Watch the videos. Print the report. Pull out one photo and email it to a client. Opening, reading, and copying never change a file, so they never harm a fingerprint and never weaken your record.
Sealed means any change is detectable — not that the archive is closed to you. Use the parts freely; just keep one intact copy of the whole zip somewhere safe, because the complete file is what proves everything.
Four independent locks —
and not one of them is ours
Every part of the seal uses published, international standards. Nothing here is a ScribeCam invention you have to take on faith, and nothing requires ScribeCam to still exist for your evidence to hold.
The fingerprints
The U.S. federal Secure Hash Standard. Built into every Mac and Windows computer already. One command checks any file, today or in ten years.
The device signature
The root fingerprint is signed inside your phone's secure hardware, by a key that physically cannot leave the device. It ties the seal to the phone that did the recording.
The independent timestamp
At sealing, an independent public Time Stamping Authority — not ScribeCam — cryptographically signs your root fingerprint with the date and time. That token ships inside your zip.
The registration record
The moment your bundle was sealed, its ID and root fingerprint were registered with ScribeCam. One ID can never be re-registered to a different fingerprint. We keep that record permanently.
Because it is all standard, a forensic professional can verify your evidence with tools they already own — and would already trust. Our verification page is the fastest way to check a bundle.
It is never the only way.
Anyone can check it. In about a minute. For free.
A lawyer, an insurer, a judge, an opposing expert, or a client — no ScribeCam account, no login, no permission from you needed.
This fingerprint is the one registered to this Bundle ID at the moment it was sealed. The copy you are holding is byte-identical to the original.
-
Check it yourself, with no one's help
Every Mac and Windows machine ships with the tool. Compute the fingerprint of any file in the bundle and compare it to that file's line in the receipt.
shasum -a 256 "Proof of Authenticity/manifest.json"Get-FileHash "Proof of Authenticity\manifest.json" -
Check it against our registration record
Enter the Bundle ID and that fingerprint on our public verify page. It answers only MATCH or NO MATCH — it reveals no account, no file list, no information about you. Nobody can use it to go fishing.
-
Check the timestamp without us at all
The RFC 3161 token can be validated straight against the issuing authority using standard open-source tools, with ScribeCam removed from the picture entirely.
openssl ts -reply -in "Proof of Authenticity/timestamp.tsr" -text
Neither side can fake this alone. ScribeCam holds the fingerprint recorded at sealing. You hold the file that has to reproduce it. They only agree if nothing was touched.
We tell you the limits, because a limit you can see is a limit nobody can ambush you with
An overstated claim is worse than a modest one. The certificate says precisely what it covers — and precisely what it does not.
The sealed window
Captured evidence
Video, photos, transcripts and sensor records created on your device. Real camera, real phone, real moment — fingerprinted on that same phone before touching the internet. Any alteration of any file is detectable by anyone.
Derived material
The written report, its PDF, and the highlight clips. These are produced by ScribeCam from the capture. The certificate proves exactly what the report said at seal time and which captured inputs it came from — and never pretends the writing is part of the capture.
Blurring those two would be the easy sales pitch. It would also be the first thing an opposing expert took apart. The capture claim is strong enough standing on its own.
What this means legally, in plain English
Courts have long needed a way to trust digital records without calling a parade of witnesses. U.S. courts recognize a pattern for records that prove themselves through digital fingerprints rather than testimony alone — Federal Rules of Evidence 902(13) and 902(14). The certificate inside every bundle is written to that pattern.
In practice: your report does not rest on anyone simply taking your word. If the other side claims a video was edited or a photo was swapped, the fingerprints answer — recompute and compare, in front of anyone, with free tools.
No document can promise a court will admit anything; admissibility is always the court's decision. What this gives your lawyer is the technical foundation those rules ask for, prepared automatically, from the moment of capture — not reconstructed months later when someone finally asks.
You always have it. In two places.
You don't have to remember to save anything. The bundle is built, sealed and delivered without you lifting a finger.
In the ScribeCam web app
The moment the bundle is built on your phone, a copy is sent to ScribeCam. Download it any time from your Reports for as long as your plan includes storage — on any computer, no phone required.
In your own cloud — automatically
Turn on iCloud or Google Drive in the app once, and ScribeCam creates a ScribeCam folder in your cloud and drops every new sealed bundle into it. That copy belongs entirely to you — it stays yours even if the report is later deleted from ScribeCam. Opt-in only; we never place files in your personal cloud without permission.
Keep one copy safe
After your plan's storage period ends, the copy you are holding may be the only one. What ScribeCam keeps permanently, on every plan, is the registration record — so a bundle can always be confirmed against us, even long after the files themselves have left our storage.
Common questions
No. It is an ordinary zip file, and every fingerprint check uses a command that is already built into macOS, Windows and Linux. Nothing to install, nothing to buy, nothing that expires. That is deliberate — evidence that needs our software to be believed is not evidence, it is a dependency.
Your bundle still verifies. The fingerprints are an open federal standard, and the independent timestamp comes from a third-party authority, not from us. Our registration record is a convenience and a corroborating witness — it is not the thing holding your proof together.
No — and this is the part that matters. Changing the photo changes its fingerprint, which changes the receipt, which changes the receipt's own fingerprint (the root). To hide the edit you would have to consistently forge the file, the receipt, the certificate, the timestamp signed by an outside authority, and ScribeCam's registration record — the last two of which you do not control.
No. AI writes the report — the narrative interpretation of what you captured — and the bundle labels it clearly as derived material. The evidence itself (video, photos, your spoken words, sensor data) is recorded by your device's camera and microphone and is never AI-generated. The certificate keeps those two things separate on purpose.
You hand over the bundle and let them check it themselves. The video file and the audio inside it were fingerprinted on your phone at capture. If the copy they are holding reproduces that fingerprint, it is byte-for-byte the recording your device made — no edit, no splice, no re-encode, no synthesised audio. If it does not reproduce it, the file they have is not yours. You never have to win that argument by talking.
Your device records GPS, compass heading, barometric pressure and motion continuously while you capture, and that stream carries its own tamper-evident hash chain written as it is recorded. It is then sealed alongside the video, photos and transcript under the same root fingerprint. So the location record in your bundle is provably the one your device produced at the moment of capture — unchanged since, and impossible to detach from the footage it belongs to. That is a far stronger position than a photo with an EXIF tag anyone can rewrite in seconds.
A permanent reference for that one sealed archive — your report number plus a seal number, like SC-K3M9-A71-B1. It is created on the device before the first report even exists, it is printed on the certificate, and it can never be re-registered to a different fingerprint.
Never. Open it, watch it, print it, copy a photo out and send it wherever you need. Reading a file does not change it. Just keep one intact copy of the complete zip — that whole file is the thing that proves the parts.
No. It confirms or denies the two values the visitor already brought with them, and nothing else — no account, no file list, no report contents, not even whether a Bundle ID exists on its own. Someone can prove your evidence is authentic without being able to see any of it.
Evidence that argues for itself.
Walk the site. Talk it through. Hand over a report nobody can wave away.