GDPR hardware disposal: what data controllers must know

Quick answer: GDPR hardware disposal is covered by the regulation because destroying or erasing personal data is itself processing. Controllers must dispose of servers and drives with appropriate security (Articles 5(1)(f) and 32), use decommissioning vendors bound by an Article 28 processor contract, honor erasure obligations under Article 17, and keep evidence that proves it.

When a data hall is retired, the drives inside it often still hold years of customer records, logs and backups. Under the GDPR, what happens to those drives is not an IT housekeeping task. It is a processing operation with legal obligations attached, and the controller stays accountable even after the hardware leaves the building.

This article is for data protection officers, compliance teams and infrastructure leaders at organizations that process EU personal data and are planning a decommissioning, refresh or consolidation. We cover the articles that apply to GDPR hardware disposal, what your contract with a decommissioning vendor needs to include, and the evidence file that answers a regulator’s questions.

This article is general information, not legal advice; confirm your obligations with qualified counsel.

Does GDPR apply to hardware disposal?

Yes. Article 4(2) of the GDPR defines processing as any operation performed on personal data, and it lists “erasure or destruction” in that definition. Wiping a drive, shredding it, or handing it to a vendor who will do either is processing.

GDPR hardware disposal is the set of controller and processor obligations that apply when equipment containing personal data is retired: securing it until the data is gone, choosing a compliant method, contracting properly with any vendor involved, and documenting that the data was actually made unrecoverable.

That has two consequences. First, the security principle applies until the last byte is gone, not just while systems are in production. Second, any vendor that handles your drives before the data is destroyed is, in most setups, acting as a processor on your behalf.

Which GDPR articles cover hardware disposal?

Five articles do most of the work, and one more matters if something goes wrong. The table maps each to the disposal step it affects, citing the official GDPR text on EUR-Lex.

Article

What it requires

What it means for disposal

5(1)(f)

Integrity and confidentiality: appropriate security, including protection against unauthorized processing and accidental loss

Drives stay protected from rack to destruction, including staging and transport

5(2)

Accountability: the controller must be able to demonstrate compliance

You need evidence, not just a vendor’s promise

17

Right to erasure in defined circumstances, for example when data is no longer necessary

Retired media holding data subject to erasure must actually be sanitized or destroyed

28

Controllers may only use processors that can show appropriate technical and organizational measures, bound by a contract with specified terms

Your decommissioning vendor needs a compliant data processing agreement

32

Security of processing appropriate to the risk, including a process for testing and evaluating measures

Sanitization method, verification and physical security must fit the data’s risk

33

Breach notification to the supervisory authority without undue delay and, where feasible, within 72 hours

A lost drive or pallet can be a notifiable breach

Article 30 adds a record-keeping angle: controllers’ records of processing should include, where possible, envisaged time limits for erasure. Disposal is where those time limits become real.

What Article 32 means for sanitization

Article 32 requires security appropriate to the risk, taking into account available technology, implementation costs and the nature of the processing. It doesn’t name a sanitization standard, so you need to choose one and be able to justify it.

Most organizations anchor their method to NIST SP 800-88 or an equivalent recognized standard, choosing Clear, Purge or Destroy by media type and data sensitivity. Our NIST 800-88 data sanitization guide walks through that choice.

Article 32(1)(d) also asks for a process to regularly test, assess and evaluate the effectiveness of your measures. For disposal, that translates into verification of each sanitization job and periodic review of your vendors, not a one-time due diligence file.

What your decommissioning processor contract must include

A decommissioning vendor that receives media before the data is destroyed is normally a processor, and Article 28(3) sets the minimum content of the contract. Check your agreement against this list.

  1. Processing only on your documented instructions, including instructions on transfers outside the EU (28(3)(a)).
  2. Confidentiality commitments from everyone who handles the media (28(3)(b)).
  3. All security measures required by Article 32 (28(3)(c)).
  4. No sub-processors without your prior written authorization, and the same obligations flowed down to them (28(2), 28(3)(d) and 28(4)). Downstream shredding and recycling facilities count.
  5. Assistance with your Article 32 to 36 obligations, including breach notification (28(3)(f)).
  6. Deletion or return of all personal data at the end of the service (28(3)(g)). For hardware decommissioning, this is the core deliverable.
  7. Access to the information you need to demonstrate compliance, including audits and inspections (28(3)(h)).

Two points to watch. Subcontracting is common in hardware decommissioning: a collector hands off to a sanitization facility, which hands off to a shredder. Each of those links needs to be authorized and contractually bound. And if drives holding personal data are shipped outside the EEA for processing, that movement can raise international transfer questions under Chapter V, so check the route with counsel before you sign.

A certification such as R2v3, e-Stewards or NAID AAA can support your assessment of a vendor. It does not replace the Article 28 contract. Our guide on how to choose a decommissioning vendor covers the rest of the selection process.

What evidence should a controller keep?

Keep enough to show, for any drive, where it was, who held it, what was done to it and when. Under Article 5(2), the burden is yours.

  • A serial-level inventory of in-scope assets and drives, frozen before de-install.
  • Chain-of-custody records for every handoff, with seal numbers and signatures.
  • The sanitization or destruction method per device, with verification results.
  • Serial-level certificates of sanitization or destruction from the vendor.
  • The signed processor agreement and sub-processor authorizations.
  • Records of vendor audits or reviews.

Our articles on chain of custody in hardware decommissioning and on certificates of destruction explain what good records look like.

Where GDPR hardware disposal goes wrong

The failures we see are rarely about the shredder. They happen earlier.

  • Drives are pulled and left in open boxes in a shared corridor for days while the pickup is rescheduled.
  • The vendor’s pickup manifest lists pallets and weights, not serials, so nothing can be reconciled.
  • A regional office ships old servers to a local recycler with no contract at all.
  • Failed drives from RMA workflows are returned to manufacturers without sanitization or a documented exception.

Each of these is a potential Article 32 and Article 5(1)(f) problem, and a lost drive can trigger the Article 33 breach assessment. The fix is procedural: seal at the rack, scan every handoff, and never let custody go undocumented.

Does encryption change your disposal obligations?

It changes the risk, not the obligation. Encrypted media still holds personal data, so disposal remains processing and the Article 28 and 32 duties still apply. What encryption changes is the consequence of a loss.

Under Article 34(3)(a), communication to data subjects is not required when the controller has applied measures that make the data unintelligible to anyone not authorized to access it, such as encryption. That only holds if the keys were never exposed. Self-encrypting drives also open a faster sanitization route: a cryptographic erase that destroys the media encryption key is a recognized Purge technique when the drive’s implementation can be trusted. Record which drives were encrypted, how keys were managed and when they were destroyed. Without that record, you can’t rely on encryption after the fact.

How Hype Telecom helps

Hype Telecom delivers the on-site part of decommissioning where most GDPR exposure sits: serial-level inventory, de-install, drive removal, sealing at the rack and chain-of-custody documentation through to the downstream facility. We work with certified downstream facilities for sanitization and destruction and structure the documentation so it maps to your evidence file. Our coordination team reconciles serials at every handoff, and our vetted teams are OSHA 10/30 trained and Avetta registered. We support projects where rules differ by country, including Brazil, which our LGPD IT asset disposal guide covers. For scope and process, see our data center decommissioning guide.

If you are preparing a decommissioning project with EU personal data in scope, request the Decommissioning Compliance & Chain-of-Custody Toolkit and use it to check your processor contract and evidence file before the first drive leaves the rack.

Request the Decommissioning Compliance & Chain-of-Custody ToolkitCheck your vendor contract, custody process and evidence file before the first drive leaves the rack.Request the Toolkit →
24/7/365 coordinationHistorical sub-4-hour emergency response95% first-visit resolution

Frequently asked questions

GDPR doesn’t prescribe a method. It requires security appropriate to the risk and proof of compliance. Shredding can be appropriate, but you still need to secure the drive until it is destroyed, use a properly contracted processor, and keep serial-level evidence. For higher-sensitivity data, many organizations purge drives before physical destruction.

Usually yes, if it receives media that still contains personal data and handles it on your instructions. Destruction and erasure are processing under Article 4(2). That means you need an Article 28 contract covering instructions, confidentiality, security, sub-processors, deletion at the end of service and audit rights. If media is fully sanitized before handover, the analysis can change.

Article 17 applies to personal data wherever it is stored, including backups and drives in storage. If a data subject’s data must be erased, copies on retired media are in scope. In practice, a sanitization or destruction process with serial-level evidence is how controllers show that retired media no longer holds data that should have been erased.

If a drive containing personal data is lost or stolen during disposal, that is a personal data breach. Under Article 33, the controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours, unless the breach is unlikely to result in a risk to individuals. Strong encryption can affect that risk assessment.

At minimum: the serial number of each device, media type, the method used, the date and location of sanitization or destruction, the facility that performed it and a signature from a responsible person. A lot-level certificate that lists only weights or pallet counts makes it hard to demonstrate accountability under Article 5(2).

Share this :

One Response

Leave a Reply

Your email address will not be published. Required fields are marked *