Company Data on Rented Laptops: Wipe It Before Return

Summary
How to secure company data before a rented laptop goes back: revoke access and MDM, wipe according to data category, and keep evidence for every unit.
Before a rented laptop goes back, company data needs to be secured in five steps: inventory the units and their data category, move the files that are still needed, revoke account and device access, wipe the data with a suitable method, then keep evidence for every unit. This responsibility stays with your company, even though the laptop belongs to the rental provider.
The end of a contract is usually treated as a logistics job: units are counted, packed and collected. The part most often missed is the riskiest one, namely what is still stored on the device when it leaves the office. IT and admin teams can adopt this guide as a standing procedure. Pickup scheduling, accessories and the collection record are covered separately in our article on collecting units at the end of a contract.
What Is Left on a Laptop After Months of Use?
A device used every day holds far more than the Documents folder. The layers most often forgotten:
- Local copies of cloud storage, such as OneDrive, Google Drive or Dropbox folders synced to the disk.
- Browser credentials, including saved passwords, session cookies and autofill data.
- Application tokens, such as chat, email and collaboration sessions that stay signed in without a password.
- Network profiles and certificates, including office Wi-Fi and the VPN client.
- Email caches and attachments that were once opened, often containing financial documents or employee data.
- Temporary files and downloads that were never moved to official storage.
That is why "we deleted the work folder" is not the same as "the data is safe".
Who Is Responsible: Your Company or the Rental Provider?
In Indonesia, the Personal Data Protection Law (UU PDP), Law No. 27 of 2022, places your company in the role of personal data controller, obliged to keep the data it processes secure. That obligation does not move just because the device is rented. A rental provider can help, for example by wiping returned units again before preparing them for the next customer, but that is a second layer, not a substitute for the procedure on your side.
The division of tasks should be written into the contract or the rental agreement (SPS): who wipes the data, by which method, and what evidence is handed over. Broader compliance is covered in our article on UU PDP for company laptops.
Step 1: Inventory the Units and Set Their Data Category
Start with a list of units and everyone who used them during the contract. For each unit, set a category, because the category determines how strict the treatment must be.
| Category | Example units | Risk | Minimum treatment | Evidence to keep |
|---|---|---|---|---|
| Light | Reception, kiosk and data-entry terminals that only access central systems | Low | Sign out of every account, then factory reset | Per-unit reset log |
| Standard | General work laptops holding operational documents | Medium | Revoke access, destroy the encryption key, factory reset | Per-unit evidence sheet |
| Sensitive | HR, finance, legal, or client projects under confidentiality | High | A purge-level method agreed with the provider, with a witness | Evidence sheet, witness signature, provider confirmation |
Ideally the category is set when the unit is issued, not just before it goes back. Setting it at the end means relying on memory of everything done on that device over many months. If your company already has an inventory SOP, add a data-category column to it. An example SOP is in our article on managing employee laptop inventory.
Step 2: Move the Files That Are Still Needed
Make sure work files that still matter are in company storage, not only on the laptop's disk. Watch for documents kept outside synced folders, such as the desktop, the downloads folder, or project folders inside application directories.
Do not forget the things that are not documents: user-made templates, application settings, software licence keys that need transferring, and local databases for accounting or design applications. Losing these is rarely fatal, but it is disruptive when the user moves to a new unit.
Give users a deadline to confirm their files are safe, then lock their access to the old unit once the deadline passes.
Step 3: Revoke Account, Device and Network Access
Deleting files does not revoke access. A device still registered in company systems can keep receiving email, syncing data or applying security policies after it has left the office. This is also the part that most often causes trouble for the next customer if it is skipped.
- Remove it from MDM. In Microsoft Intune, use the wipe or retire action, then delete the device record once the action completes.
- Deregister it from Windows Autopilot. A unit still registered in your company's Autopilot will be steered into your company's setup screens every time it is reset and set up again. For a rental unit, that means the next customer gets stuck at another company's sign-in.
- Delete it from the directory. Remove the device from Active Directory or Entra ID; the background is in our AD and Azure AD glossary entry.
- For MacBooks, turn off Activation Lock. Sign out of the Apple ID and turn off Find My, or release the device from Apple Business Manager if it was enrolled there. A MacBook that is still locked cannot be reused by the provider.
- Revoke sessions on the server side. Remove the device from the trusted device lists of email accounts, collaboration platforms and password managers, rather than just closing the apps on the laptop.
- Remove network profiles and certificates, including office Wi-Fi and the VPN client.
Step 4: Wipe According to the Data Category
The wiping method depends on the data category and on whether the device is encrypted. The general framework follows the NIST 800-88 standard, which divides sanitisation into clear, purge and destroy.
| Method | How it works | Enough for | Notes |
|---|---|---|---|
| Delete files and empty the recycle bin | Only marks disk space as free | Not enough for any category | Data can still be recovered with common tools |
| Factory reset on an unencrypted disk | Reinstalls the operating system | Light category only | Old data can remain in storage cells |
| Destroy the encryption key, then factory reset | Encrypted data becomes unreadable without the key | Light and standard categories | Only effective if encryption was on from the start |
| SSD firmware sanitize or secure erase command | The SSD controller erases every cell | Sensitive category | Needs tools and permissions; agree it with the provider |
| Physical destruction | The media is destroyed | Not applicable to rental units | The unit belongs to the provider; discuss options at the start of the contract |
On Windows, disk encryption usually means BitLocker; on a Mac it is FileVault, and storage on Macs with Apple Silicon is always encrypted. Modern Macs also offer Erase All Content and Settings, which destroys the encryption keys in one step. The difference between clear, purge and destroy is explained in detail in our article on NIST 800-88 for rental laptops.
Step 5: Keep Evidence for Every Unit
Evidence is the part most often missing, yet it is the part most needed when an audit or a question comes up months later. A useful evidence sheet has one line per unit with these columns:
- Serial number and asset tag, not just brand and model.
- Last user and data category.
- Date, wiping method, who performed it and who witnessed it.
- Confirmation of access revocation: MDM, Autopilot or Apple Business Manager, directory and accounts.
- The provider's collection record number, so the two documents can be matched.
Keep this sheet with the original handover BAST. A tidy handover documentation routine is covered in our rental unit handover article.
Special Cases That Often Slip Through
Units that will not power on
A completely dead device still holds data on its storage. First revoke all of its access in MDM, the directory and accounts, because that can be done without touching the hardware. Then tell the provider about its condition in writing and agree how it will be handled. Record that agreement on the evidence sheet.
Units lost mid-contract
Treat this as a security incident, not merely a lost asset. Revoke its access immediately, send a remote wipe command if the device is still connected, then report it to the provider. If the unit held personal data and a data protection failure occurs, Article 46 of UU PDP requires the data controller to give written notice within 3 × 24 hours to the data subjects and the relevant authority. The steps for reporting it to the provider are explained in our article on damaged or lost rental units.
Units held by remote employees
Wipe the data remotely through MDM before the unit is shipped back, not after it reaches the office. A unit travelling with company data still on it is an easily avoided risk. How to prepare devices for remote employees from the start of the contract, including MDM enrolment, is covered in our article on laptop rental for remote and WFH employees.
Start on Day One: Encryption and a Standard Configuration
How complicated the return will be is decided when the unit is first prepared. If encryption is on from the start and the recovery key is recorded in the management system, wiping at the end of the contract is just a matter of destroying the key and resetting the device. If encryption is only switched on shortly before the return, data already written unencrypted does not automatically become protected.
Build encryption, MDM enrolment and standard accounts into the system image installed before the units ship. The process is known as pre-imaging. For companies that want more centralised device management throughout the contract, see also our DaaS laptop rental service.
Common Mistakes
- Leaving everything to users. Users know their documents, but not the network profiles, certificates or tokens stored inside applications.
- Only checking senior managers' units. Sensitive data often sits on the units of operational staff who process documents every day.
- Forgetting Autopilot or Activation Lock, so the unit gets stuck at the provider and raises questions after the contract has ended.
- Logging by group instead of by serial number, so nobody can say which unit has not been wiped.
Frequently Asked Questions
Is a factory reset enough before returning a rented laptop?
For a device encrypted from the start, a factory reset after destroying the encryption key is generally adequate for ordinary business needs. For an unencrypted disk or sensitive-category data, a factory reset alone is not enough; agree a stricter method with the provider at the start of the contract.
Who is responsible for the data on a rented laptop?
Your company, as the data controller. The rental provider can help with wiping, but the obligation to protect personal data does not pass to the provider. Write the division of tasks into the contract so nobody relies on assumptions.
What about a rented laptop lost mid-contract?
Revoke all of its access immediately, send a remote wipe if possible, then report it to the provider. If personal data is involved, remember the obligation under UU PDP to give notice within 3 × 24 hours.
What should be done to a rented MacBook before it goes back?
Sign out of the Apple ID and turn off Find My so Activation Lock is disabled, release the device from MDM or Apple Business Manager, then run Erase All Content and Settings. Record the serial number and date on the evidence sheet.
Does a laptop need to be removed from Intune and Autopilot?
Yes. Otherwise the unit stays linked to your company's tenant and the next customer may be steered into your company's setup. Run a wipe or retire in Intune, deregister it from Autopilot, then delete the device record from the directory.
References & Sources
Data sanitisation methods, including cryptographic key deletion, follow NIST SP 800-88 Rev. 2 — Guidelines for Media Sanitization (accessed 8 November 2026). In Indonesia, the duty to protect personal data is set out in Law No. 27 of 2022 on Personal Data Protection (accessed 8 November 2026).