Legal mode: from recording to court package

Step 1: the admissibility questionnaire

For every recording in legal mode you fill in a short admissibility questionnaire: who recorded, on what device, when and where. Your answers build the circumstances affidavit that ships in the package.

Step 2: verify and finalize the transcript

Go over the transcript in the editor, verify it against the audio, then finalize a locked version. The original file is untouched either way; it is kept bit-for-bit with a cryptographic hash, and every processing step is recorded in the audit log.

Step 3 (optional): Certified verification

A Certified order (₪9 per audio minute) opens a review queue with a deadline (an SLA of 24 to 168 hours): a qualified transcriber verifies every segment against the audio, and only when everything is verified is a "certified" version sealed, and that's what ships in the package.

Step 4: the court package

Click "Court package" and get a ZIP with the original, a court-format transcript (DOCX+PDF), a chain-of-custody annex, affidavits (including a transcriber's affidavit under Evidence Ordinance s.15) and a hash for every file.

Good to know

We provide the foundation case law requires: an unaltered original, chain of custody, affidavits and a verified transcript. Admissibility itself is the court's call. Nothing here is legal advice.

Erasure request: destroying the encryption key

Every recording is encrypted with its own key. Erasure in the system means destroying that key: the original file becomes undecipherable noise, derivatives are deleted, and every transcript and translation is blanked. What remains: the original's hash, the processing log, the audit log, and a signed erasure certificate.

How it works: an organisation admin (a person, not an API key) opens a request from the legal panel in the editor, re-authenticates with a password or a TOTP code, and a 7-day cooling-off period starts during which the request can be cancelled. At its end the system performs the erasure and issues the certificate. The erasure becomes final a further 7 days after execution; that is the key-backup window we declare.

• A recording that is locked or verified as evidence: the system asks for explicit acknowledgement that evidence will be destroyed.
• The request is refused and recorded when the organisation has marked the recording with a litigation hold (an active order/proceeding), when a certified-review order is open, and when the recording is old and not yet encrypted. The system does not know statutory retention duties by itself. Marking a hold is the organisation's responsibility.
• After erasure the record is shown as "erased"; the certificate number (hash) appears in the legal panel. The certificate is signed with the server's key (AttestVoice verifies it on request); it documents what was erased and when.