Digital Shredder & Verifiable Certificate of Destruction
A local-first data sanitization tool for anyone who needs a defensible audit trail. It overwrites the in-browser working copy of up to 50 files with multi-pass patterns, confirms every buffer is all-zero, and issues one signed Certificate of Destruction laid out like the NIST SP 800-88 Rev. 2 Certificate of Sanitization. All work happens in a Web Worker on your device: no upload.
How the destruction runs
- Pre-hash: SHA-256 of each file records its pre-destruction digest.
- Multi-pass overwrite: fixed patterns, complements and CSPRNG entropy are written in place, one file at a time, chunked so large files never freeze the page.
- Zeroization: a final
.fill(0)pass makes each buffer deterministic. - Verification: a linear scan proves zero residual bytes, and each post digest equals SHA-256 of an all-zero buffer of that size.
- Manifest: the file records are bound into one Merkle root, so the list cannot be edited without breaking the signature.
- Signing: the canonical certificate is signed with Ed25519 (or ECDSA P-256) via WebCrypto, with the public key embedded.
- Teardown: buffers are zeroed and detached. File contents are never stored; the optional log keeps only certificate summaries in this browser.
Standards
- NIST SP 800-88 Rev. 2 (Clear pattern): one CSPRNG pass. Rev. 2 (September 2025) replaced Rev. 1.
- DoD 5220.22-M (E):
0x00→0xFF→ random, three passes. - Paranoid (7-pass):
0x00 · 0xFF · 0xAA · 0x55plus three CSPRNG passes.
What the certificate claims
It attests that the in-browser working copy of each listed file was overwritten with the stated sequence, verified all-zero and signed. A web page cannot reach the storage controller, so it does not claim firmware Secure-Erase or a purge of spare blocks. When you let it delete originals (Chrome and Edge), each one is removed from its folder only after its bytes match, and the certificate records that the disk blocks were not overwritten. For NIST Purge on physical media, add device-level tooling.
Verifying a certificate
The certificate is canonicalized (key-sorted, minimal JSON, orilami-jcs-v1) before signing, so anyone can rebuild the signed bytes and check them with the embedded JWK public key. The Verify tab does this offline from the PDF itself or its JSON: it recomputes every zero digest and the manifest root, checks an RFC 3161 timestamp against its authority's certificate, and checks each validator's concurrence. The QR on the PDF opens Verify with the certificate's id and fingerprint.
How to shred files with a certificate of destruction
Step 1: Add the files
Drop the files or the folder to destroy. Each one is fingerprinted with SHA-256 before anything is overwritten.
Step 2: Choose the standard and fill in the record
Pick NIST SP 800-88 Rev. 2, DoD 5220.22-M or the 7-pass sequence, a compliance template such as HIPAA or GDPR, and who performed the sanitization.
Step 3: Preview & Shred for free
The working copies are overwritten and checked as all zeroes, and the certificate is drafted for you to read.
Step 4: Download the certificate
Download the signed PDF and JSON. A validator can add a countersignature, and anyone can check the certificate in the Verify tab.
When to use the Digital Shredder
- Ending a client engagement
- Show the client that their files were destroyed when the work ended, with a certificate listing each one.
- Files at the end of their retention period
- Record the destruction with the rule cited on the certificate, so the decision can be traced later.
- Preparing for an ISO 27001 or SOC 2 audit
- Hand the auditor a signed record they can check, instead of an email saying the files were deleted.
- Disposing of applicant and HR files
- Document that CVs and interview notes were destroyed once they were no longer needed.
Common mistakes
Forgetting the other copies
Backups, cloud sync, email attachments and the Downloads folder all hold copies. Destroy those too, or note them on the certificate.
Leaving the record fields empty
A certificate that does not say who did it, under which rule and why is weak evidence. Fill in the performer, the template and the notes.
Filing the certificate with the files
Once the files are gone, the certificate is the only proof left. Keep it with your compliance records, not in the folder you emptied.
Digital Shredder compared with other ways to destroy files
| Digital Shredder | Deleting the file | Disk-wiping software | Shredding services | |
|---|---|---|---|---|
| Where your files go | Stay on your device | Stay on your device | Stay on your device | Collected by the company |
| What is overwritten | The working copy loaded in the browser | Nothing, the space is only marked free | Free space or the whole drive | Physical media |
| Proof | A signed certificate anyone can verify | None | Some produce a report | A certificate from the company |
| Compliance templates | HIPAA, GDPR, ISO 27001, SOC 2 and more | No | Varies | Usually |
| Cost | Pay per file with tokens, preview free | Free | Free or a licence | Per box or device |
Frequently asked questions
Does this securely erase a file from my hard drive?
Why do multi-pass overwrites exist if one pass is enough?
What is on the Certificate of Destruction?
Can someone else verify my certificate?
Is the file uploaded to be shredded?
Which signature algorithms are used?
Is the PDF a PDF/A archive?
What changed in NIST SP 800-88 Rev. 2?
Does a Certificate of Destruction satisfy HIPAA?
Can I use it to document GDPR erasure, or PIPEDA and APP 11 destruction?
How does one certificate cover 50 files?
What does the trusted timestamp add, and what is sent?
Digital Shredder at a glance
| Where it runs | Entirely in your browser. Files are never uploaded. |
|---|---|
| Cost | 90 tokens per file (about $0.90 at the base rate); larger batches cost less per file: 6–10 take 10% off the total, rising to 30% off at 41–50 |
| Accepts | Up to 50 files of any type, or a folder |
| Produces | Overwritten working copies verified as all zeroes, and one Certificate of Destruction for the batch, laid out like the NIST SP 800-88 Rev. 2 Certificate of Sanitization and signed with Ed25519 or ECDSA, as PDF (English or Arabic) and JSON. |
| Batch | Up to 50 files per run. |
| Account needed | Only to spend tokens. Browsing and previewing are free. |
| What it does not do | It overwrites the copy loaded into your browser. It cannot overwrite the original bytes on your disk, your SSD's spare blocks, or a backup. In Chrome and Edge it can delete the originals from a folder you pick, which removes them but does not overwrite their disk blocks. |
Destroy the files and keep the proof
90 tokens per file · Preview free, nothing uploaded
Shred my files