Proof basics
What a Tamper-Evident Proof Bundle Means
Tamper-evident proof sounds heavier than it is. The basic idea is simple: if someone changes an exported file after the fact, verification should notice.
What goes into a Kept bundle
A Kept export can include the tab recording, screenshots, a structured event log, a readable offline summary, artifact hashes, and verification metadata. Those pieces are meant to travel together so the session can be reviewed later.
How hashes help
A hash is a short fingerprint of a file or record. If the file changes, the hash changes. By hashing artifacts and chaining session records together, Kept can flag when exported contents no longer match the original bundle metadata.
This does not prove every fact about the outside world. It helps answer a narrower question: has this exported bundle been modified since it was created?
What tamper-evident does not mean
- It does not certify that a website was authentic.
- It does not guarantee a company will accept the proof.
- It does not make a recording court-certified evidence.
- It does not replace careful redaction before sharing.
Why the distinction matters
Overclaiming proof can backfire. Kept is designed for practical personal records: clearer support escalations, better chargeback documentation, and fewer arguments from memory.
Frequently asked questions
Can a verifier detect edited exported files?
That is the goal. The verifier checks whether exported artifacts still match the bundle metadata and hash chain.
Is tamper-evident the same as tamper-proof?
No. Tamper-evident means changes should be detectable. It does not mean impossible to alter.