Why deleting and reformatting are not enough
When you delete a file, the operating system usually removes only the pointer to it. The data remains on the disk until something overwrites it, and freely available recovery tools can read it back. A quick format behaves the same way. This is why a laptop that “looks wiped” can still hand a stranger a client list, payroll data or saved credentials.
Solid-state drives add another wrinkle. Wear levelling and over-provisioned memory mean an SSD can hold copies of data in locations that ordinary overwriting never touches. A method that is acceptable for a spinning hard drive may be unacceptable for flash storage. That is why the right approach depends on the media, not just on the policy statement.
The consequence of getting this wrong is not abstract. A recovered drive can trigger breach notification duties, regulator attention, contractual penalties and reputational damage that far outweighs the cost of doing the job properly.
Clear, purge and destroy: choosing the right method
NIST Special Publication 800-88 describes three levels of media sanitization. Westmark uses that framework because it gives security teams a common language and gives auditors something to check against.
- Clear: logical techniques such as overwriting to protect against simple recovery. Suitable for lower-sensitivity devices that will be reused
- Purge: stronger techniques, such as cryptographic erase or firmware-level secure erase where the device supports it, that make recovery infeasible even with laboratory methods
- Destroy: physical destruction of the media so that it cannot be reused or read. Required when drives are failed, unsupported, or covered by a policy that mandates it
Matching the method to the device
A policy that says “all drives are shredded” is simple but expensive, and it throws away resale value from devices that could have been safely purged and reused. A policy that says “all drives are wiped” is cheaper but fails on damaged media. Most organizations land on a tiered approach: highly sensitive systems and failed drives are destroyed, standard fleet devices are purged and resold, and low-risk peripherals are cleared.
Different media need different handling. Hard disk drives can be overwritten or destroyed. SSDs and NVMe modules need purge methods the device itself supports, or destruction that reaches the memory chips. Backup tapes, optical discs, USB sticks and SD cards each have their own approach. Mobile phones and tablets need factory reset plus encryption checks, or destruction if the policy requires it. Multifunction printers and copiers often hold hard drives that store scanned documents, and they are routinely forgotten.
If you are unsure how your devices should be classified, send us the inventory and your existing policy. We will propose a tiered plan and explain where each method applies.
Chain of custody from your door to final disposition
Sanitization is only half of the assurance. The other half is knowing where the device was between your site and the process. Westmark captures serial numbers when equipment is collected, seals containers where required and tracks the load through to processing. Each handoff is recorded, which means a missing device is noticed immediately instead of being discovered months later in an audit.
You can also request witnessed handling. If your policy requires that your own staff observe destruction, tell us during scoping so we can plan the location and timing, and confirm in the written quote how that will work.
What a certificate of destruction should contain
A certificate is only as useful as the detail behind it. A one-line statement saying “data destroyed” will not satisfy a serious auditor. Westmark’s certificates list the serial numbers of the devices that were wiped or destroyed, the method applied to each, and the dates of processing. They are issued alongside your project close-out report so everything is filed together.
For organizations that must prove destruction to their own clients, a serial-level certificate can be passed straight through. For internal audit, it reconciles directly to the asset register. If your security team has a required template or additional fields, send it with the inventory and we will align the report to it.
Compliance context for Canadian organizations
PIPEDA requires organizations to protect personal information with safeguards proportionate to its sensitivity, and that duty continues through disposal. Ontario health-care custodians have additional obligations under PHIPA. Public-sector bodies and regulated financial institutions typically add their own retention and disposal rules. Contracts with enterprise clients often specify destruction standards by name.
Data destruction is one control among several, and your privacy or legal team owns the interpretation of the rules that apply to you. What we provide is the operational side: a method that matches your policy, a record that stands up to review and a process that does not depend on anyone remembering to wipe a laptop.
Preparing devices for collection
Preparation is straightforward. Gather devices in a secure, access-controlled room. Do not strip or reimage them unless your policy requires it. Provide an inventory with counts by device type and, if you have them, asset tags. Flag anything with unusually sensitive content, any failed drives and any equipment that is leased or under legal hold, since those items follow different rules.
We serve Toronto, the wider GTA, Windsor, Moncton, Fredericton and Halifax, and can arrange evening or weekend collection where building rules require it.
How a project runs
- 1
Classify the media
List devices by type and sensitivity, and share any internal data policy.
- 2
Choose methods
We propose clear, purge or destroy for each category and confirm it in the quote.
- 3
Collect under custody
Serial numbers are recorded and equipment is moved in tracked, secured containers.
- 4
Sanitize or destroy
Each device is processed by the agreed method and the outcome is logged.
- 5
Issue the certificate
You receive serial-level records tied to your close-out report.
Service areas
We serve businesses across Ontario, New Brunswick and Nova Scotia. Select your city for local access notes and what to prepare.
Ontario: Toronto, Mississauga, Oakville, Brampton, Vaughan, Markham, Windsor
Atlantic Canada: Moncton, Fredericton, Halifax
Frequently asked questions
Is wiping a drive as secure as destroying it?
A correctly performed purge on a device that supports it can make data recovery infeasible, and the drive can then be reused or resold. Destruction is the only option for failed drives or where your policy demands it. The right choice depends on media type, sensitivity and your internal rules.
Can you provide certificates of destruction?
Yes, for any device that undergoes physical destruction or certified data wipe. Certificates list serial numbers and the destruction method, and are issued alongside your project close-out report.
How do you handle SSDs differently from hard drives?
Overwriting is unreliable on flash storage because of wear levelling and spare capacity. For SSDs we use purge methods the device supports, such as cryptographic or firmware-level erase, or destroy the drive so the memory chips cannot be read.
What about copiers, printers and phones?
Multifunction printers and copiers frequently contain drives that store scanned documents. Phones and tablets store credentials and corporate email. Include them in your inventory and we will assign the appropriate method to each.
Can our team witness the destruction?
If your policy requires witnessed destruction, tell us during scoping. We confirm in the written quote how and where it will take place so your team can plan to attend.
Do we need to wipe devices before you collect them?
No. Leave devices intact unless your policy says otherwise, so serial numbers and asset tags stay linked to the machine. We handle sanitization as part of the project.
How are failed or damaged drives handled?
Drives that cannot be wiped, such as those that no longer spin up, are routed to physical destruction. List them separately if you know which ones they are.

