WitnessView
You hold the phone. It holds the proof.
Records an encounter and seals each segment as it is captured, so later alteration is detectable — and so anyone can check that for themselves without taking our word for it.
Most phone video is easy to doubt.
A file can be trimmed, re-encoded, or re-dated, and there is often no way to show that what you are playing is what the phone actually captured.
That doubt does the most damage to the person with the least support — someone holding a phone during an encounter they did not choose, with no expert to call and nobody to vouch for them afterwards.
Four screens, in the order you would meet them.
The counter is not a progress bar. Each segment is hashed and sealed the moment it is written, so the count is the number of pieces already committed to the chain.
Every segment still matches the chain sealed at capture. The app recomputes this on your phone rather than asking a server, so the answer does not depend on us.
This is the screen the whole design exists to produce. It names which part failed, and it tells you not to delete the recording — the portion that still verifies is still worth something.
Every recording carries its verification result on its face, so the state of your evidence is something you can see at a glance rather than something you have to go and test.
A chain, not a pile of files.
WitnessView records in short segments and hashes each one as it is sealed. Every hash includes the one before it, so the segments form a chain rather than a pile of independent files. Alter any part afterward and the chain no longer matches, which is visible to anyone who checks.
Nothing about that depends on us being trustworthy, available, or still in business. The chain is arithmetic over the bytes you hold.
Evidence anyone can check themselves.
Export an incident and you get the segments, the manifest, and the full chain. Anyone can recompute it from our published specification, in an ordinary browser, offline, with no account and no connection to us — opposing counsel, an expert, a clerk.
Evidence you must trust a vendor to validate is weaker than evidence anyone can check themselves. That is the whole design.
- Tamper-evident
- Verify independently
- Stays on your phone
- No account
Two decisions worth explaining.
Face ID is more convenient and it is the wrong choice here. Recording never asks for the password at all — only viewing saved evidence does, so the gate never stands between you and the moment you need to record.
Recording law is not uniform, and a tool that stays quiet about it is not being neutral. The app names the rule and its exceptions up front rather than leaving you to find out afterwards.
The specifics.
- Platform
- iPhone
- Price
- Free
- Account
- None. Nothing to sign up for.
- Where recordings live
- On your phone, until you choose to export them.
- Verification
- Published specification; recomputable offline in a browser.
- Status
- On TestFlight, preparing App Store submission.
The line we will not cross.
WitnessView is built to support authentication of a recording — whether a record is what it claims to be. Whether a court admits it is a separate question that depends on facts and law no app controls. It makes alteration detectable, not impossible, and it does not provide legal advice.