1. Capture
Take a photo or video in the mobile app. The device-side capture time is kept as part of the record context.
Cloud proof record
How proof records work
Evidence Camera does not leave important photos and videos as loose files on a device. It saves them as cloud proof records that are easier to explain later.
It does not guarantee acceptance or outcomes in court, insurance, platforms, or disputes. It does preserve useful material for explaining when the file reached the server and whether a later file matches the saved one.
SHA-256
SHA-256 is a mathematical fingerprint for a file.
SHA-256 produces a 64-character hash from the contents of a photo or video. If the file is edited or tampered with, the hash normally changes completely.
Example SHA-256
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824The same file produces the same hash.
If one pixel, frame, or byte changes, the hash changes.
Comparing a later file against the saved hash makes it easier to check whether it is the same file.
Preservation flow
After capture, the record is also preserved server-side.
Instead of relying only on a local camera roll file, Evidence Camera keeps capture time, server receipt time, and a file hash together so the record has more context later.
2. Upload to cloud
After capture, the file is uploaded to the server instead of remaining only as a local file.
3. Record receipt time
The server records when it received the file. This is separate from the device clock.
4. Store the hash
A SHA-256 hash is generated from the file and stored with the proof receipt.
Why this is stronger than a loose photo
The record separates two questions: when the file existed, and whether it is the same file.
A normal photo often leaves you explaining only a file stored on your device. Evidence Camera connects the file to server-side records that are harder to explain away as a fresh local edit.
Server-side time is preserved
Instead of relying only on the camera roll, Kiroku keeps the time its server received the file. That helps explain that the file existed on the server at that point.
The file fingerprint is preserved
A SHA-256 hash acts like a fingerprint for the file. If a photo or video is edited later, the hash changes, making it easier to check whether it is still the same file.
The time and file are tied together
Kiroku keeps both the receipt time and the hash of the file received at that time. This lets you explain not only when a file arrived, but which file it was.
What you can review later
The record view and proof receipt keep the media file together with the metadata needed to explain it.
Capture time
The time recorded on the device when the media was captured.
Server receipt time
The time Kiroku's server received the uploaded file.
SHA-256 hash
A 64-character value that helps check file identity.
Proof receipt
A readable summary of receipt time, hash data, and record details.
What this helps answer
It gives you a technical answer to “you made this later.”
A normal camera roll photo can be questioned. Evidence Camera keeps server-side material that can help you respond.
You just created that photo now.
The server receipt time helps show that Kiroku's server had received the file at that earlier point.
You edited it after the fact.
If the saved hash and the later file's hash match, it is easier to show that the file is the same as the saved one.
You changed the device clock.
The record does not rely only on the device capture time; it also keeps the server-side receipt time.
What it does and does not do
Kiroku is a tool for making records easier to explain. The limits are explicit so the record is not oversold.
It does not guarantee that the contents of a photo or video are true.
It does not guarantee acceptance by a court, insurer, platform, or counterparty.
It does not automatically prove everything that happened before capture or outside the frame.
Wide context shots, close-ups, continuous video, and notes make the record easier to explain.
Move from loose photos to explainable records.
The point is not to search for evidence after a dispute starts. It is to preserve important moments in a form you can explain before the argument begins.
Get the appDoes SHA-256 prove a file was not tampered with?
SHA-256 helps verify file identity. If the saved hash and the hash of a later file match, it is easier to explain that the file is the same. It does not guarantee the truth of the content or a legal outcome.
Why does server receipt time matter?
It gives you material to explain that Kiroku's server had received the file at that point in time, which can help respond to claims that the file was created later.