I never thought of having a checklist for this before but I think it's useful and there's probably some sort of standard best practice.
I'm interested in what are people's responses for different platforms and is there any sort of Open source script that will handle this for you like a "nuke script"... I mean obviously the point is not to Nuke it you want to bring it back later but.... you want to handle if someone somehow has privileged access to everything you want them to have his little surface area of anything valuable as possible.
Second, if we're talking about my laptop.. I use Linux and a fairly open hardware device so I simply order replacement parts online and fix it myself. I can't imagine sending my laptop away to get it fixed.
If I can't fix it.. I remove all working parts and toss in a supply box. I toss the device carcass in a pile in my garage in hopes of finding a use some day, and order a new laptop.
You can get an impression of how much by searching for "forensic artifacts." Here's a taste: https://docs.google.com/spreadsheets/d/1X2Hu0NE2ptdRj023OVWI...
That's not even a complete list. For example, I think it's missing the QuickLook cache that contains thumbnails of all the things you've previewed recently.
So the checklist is simple:
1. Backup your drive.
2. If FileVault wasn't turned on, turn it on and wait for it to finish encrypting the disk.
3. Erase the disk and reinstall the operating system.
EDIT: Forgot that not everyone has FileVault turned on. Turn on FileVault, everyone!
Whatever Apple employee is performing service on your machine doesn't have the time or possibly even the ability to do much of anything with your system. Apple's going to be using automated diagnostic tools and has a general interest in getting your repair done as quickly as possible.
That Apple employee is being watched by cameras and monitoring tools while they do their job and they're not going to sacrifice their performance metrics or potentially get fired/prosecuted over a desire to rummage through your system. Put yourself in their shoes: if you were repairing 20 laptops per day as your job, how much would you care about fucking around on any of those particular systems? File this one under "the cashier doesn't care that you're buying condoms."
If Apple did something with your stuff it could be very detectable, and Apple is a massive lawsuit target. They have every motivation to be extremely careful about how they handle data. They also handle repairs for business customers.
If you've really got some sensitive data, you still don't need to be talking about nuke scripts and other time-wasting complexities. Skip all that and just do a local Time Machine backup, wipe the system, then send it in for repair. Then when you get it back you restore the whole thing as a single piece. But honestly I've never bothered with that.
1. Power off computer.
If I don’t trust my disk encryption:
1. Fix it myself or buy a new computer.
Wipe the LUKS header (`cryptsetup erase Run the default NixOS setup. When I get the machine back, reformat & re-install. Copy back the config, reboot to my working old system. I've got an "erase your darlings" style setup, so everything outside /home and /persist gets erased every boot anyway, and I test my backups so "just wipe it and restore once it's back" is pretty low risk.
If that isn't possible, I usually make a backup and restore system to defaults. Easier for support to determine the issue if software is in any way involved.
I believe some manufacturers explicitly tell you that you cannot expect your data getting returned if you ship your device to them. You get it back in most cases, but not if you get the whole device replaced for example.
When I get the laptop back, I restore the disk.
If you want to be more secure, in case you worry that someone might do a file recovery to grab data, just overwrite all the data with 0x00 using a program. and your data will be secure and unrecoverable unless someone will try really hard to sniff your data.
2. unscrew all screws
3. replace everything non-functional
4. screw all screws, use blue fixator
5. power on
6. notice that one of bus ribbons was forgotten or misplaced
7. redo steps 1-5
8. get a final result, power on
Our company uses VMs for everything sensitive now, so hopefully no one needs this checklist!