Testimonies
An account written within the hour is worth much more than a memory pieced together weeks later. ripoux.fr attaches it to the session, encrypts it like the footage, and has it signed and timestamped: you can prove it existed at that time, with that content.
From the account
In a session, the Testimonies section offers Write a testimony. The form asks for:
- the account, the only required field: the facts, in order, with times when you have them;
- the start and end of the events (prefilled with the session times);
- the place;
- the people and officers: descriptions, uniforms, ID numbers, vehicle numbers;
- injuries, witnesses, and other details.
Say what you saw yourself, and point out what was reported to you.
The session owner and their read and modify contacts can write a testimony. Read-only contacts read it without being able to add one.
From the field phone
On the phone's end screen, Tell what happened opens a short form: account, place, people. The text is encrypted on the phone with the session public key, then sent.
The phone can write it but cannot read it back: once sent, it keeps nothing. You find it in the account. Without a network, the encrypted text waits in memory and leaves as soon as possible, as long as the page stays open. This is possible up to 48 hours after the recording window ends.
Correcting without erasing
A testimony is never deleted or edited. Correct adds a new version, shown instead of the previous one; earlier versions stay visible under earlier versions, each with its time of reception. An honest correction, visible and dated, is worth more than a text altered without a trace.
What the server sees
Nothing of the content: the text is encrypted in your browser or on the phone. The server also receives the text's hash, signs it with the time of reception and the author (the account or "the field phone"), and has it timestamped by a third-party authority. If the decrypted text no longer matches that hash, the session shows it.
In the export
The legal export holds, for each testimony, the decrypted text (testimonies/<n>.json), the receipt signed by the server (.receipt.json, .receipt.sig) and its timestamp (.receipt.tsr). A third party checks the receipt signature with the server public key, then that the text's hash is the one in the receipt.