Point of view
A destruction record should be built to forensic standard
Because the day you need it is the day of an incident. An attestation and a spreadsheet won't give an investigator — or a CISO whose job is on the line — any confidence.
Where it comes from
Digital forensics: never alter the original, prove its integrity, keep everything verifiable. We've seen evidence fail an audit because a screenshot had no date and time.
What it does today
- Picks the right serial on 97.7% of legible labels, in under a second
- Checks every serial against your client's asset list
- Every record is shown and can be corrected before certifying
- A certificate of destruction, and a certificate-of-sanitization label for every device
- The tablet works fully offline
97.7%: our lab, 241 real drive labels, five-fold cross-validation, within one character (87.4% exact). Under a second: our bench, capture to identified serial.
What we're building
- The original capture of every device, kept unaltered
- Where it was, and the machine that made it
- A hash on every record, so anyone can check it
- Every change of state and location, from the rack to the shredder
- Offline scanning on the phone
Who it's for
Teams that destroy devices at volume for regulated clients, and have to prove every one. Not unregulated work, or resale of drives already erased.
What we're up against
The manual record. It depends on a person getting every step right, and the only thing left to audit is a signature.
What we hold ourselves to
- Transparent: the evidence behind the certificate is visible.
- Verifiable: a record checked against its capture. We're building it.
- Effortless: quick in the session, quick to find a device later.
- Knowledgeable: built by people who know forensics and audit.
- Purpose-built: made for how ITAD and data center teams work.
What we won't build
- A plain barcode scanner for the shredder.
- A record no operator sees.