What our certificates say — and what they don't.
In data erasure, trust is built on precision. This page explains exactly what happens to a device processed with WipeProof, which standards apply, and what every field on the certificate means. No claims we cannot back with a record.
Methods and standards
| Device type | Method | Standard alignment |
|---|---|---|
| HDDs (laptops, desktops, servers, loose drives) | Overwrite with verification | |
| SSDs / NVMe | Firmware-level secure erase / sanitize with verification | |
| Smartphones & tablets | Full device erasure + diagnostics |
The evidence chain
The erasure is executed by a certified erasure engine (independently evaluated; methods aligned with NIST 800-88).
The engine produces a digitally signed report for every device — pass or fail.
WipeProof preserves that signed report and generates a numbered, branded certificate linked to the asset, the job and the customer.
Every action is logged in an audit trail: who, what, when, on which serial.
Is WipeProof itself "certified"?
The certifications belong to the erasure engine we operate — that's where they matter. WipeProof's role is orchestration: making sure the certified wipe happens on the right device, and that the proof is preserved, linked and retrievable. On every certificate, the engine and its signed report reference are stated explicitly.
Read one before you buy anything.
Every field annotated: device, serial, method, standard, date, operator, engine report reference, certificate number.
Field detail
Device
The make and model of the unit processed, as read from the device itself.
GDPR posture
- Service operated with EU-hosted infrastructure; erasure records and certificates stored in the EU.
- WipeProof acts as a processor for the device data handled during erasure; a Data Processing Agreement is available on request.
- Certificates and audit records are retained per your instruction and exportable at any time in standard formats.
FAQ
Can a wiped drive's data be recovered?
The methods used are designed to make data unrecoverable, and each erasure is verified by the engine before a certificate is issued. If verification fails, no certificate is issued and the device is routed to physical destruction.
Do you erase SSDs properly?
Yes — SSDs and NVMe drives are processed with firmware-level secure-erase/sanitize commands with verification, not just overwriting.
What about devices that can't be wiped?
They're flagged as failed, tracked into your physical-destruction workflow, and documented to their final outcome. You are never billed for them.
Who owns the certificates and records?
You do. Export everything, any time, in standard formats.
Can our own clients verify a certificate?
Each certificate carries a unique number and the signed engine report reference; verification against the stored record is part of the service.
Do you support other standards or specific wipe policies?
Erasure policies are configured at setup — talk to us about your specific compliance requirements.