Almost nobody asks me about this, and almost everybody thinks about it.
Sending a drive off for recovery means handing someone every file you own — tax returns, medical records, photographs, work documents, browser history, saved passwords, whatever else has accumulated over a decade. It’s a genuinely reasonable thing to be uneasy about, and the industry mostly handles it by not mentioning it.
So here’s the honest version.
Is anyone looking at my files?
Not in the way you’re imagining, but not zero either. Being straight about it:
What I necessarily see: file and folder names, sizes, dates, and directory structure. That’s the working surface of the job — verifying a recovery means confirming files exist, are the right sizes, and aren’t corrupt. I’ll see that you have a folder called Taxes 2019 and how big it is.
What I sometimes see: thumbnails and the first frames of images and video, because verifying that a recovered photo actually opens means opening it. On a photo recovery, I will see some of your photos. There’s no way around that — confirming a JPEG decodes requires decoding it.
What I don’t do: read documents, open emails, browse folders out of curiosity, or go looking at anything beyond what verifying the recovery requires. Not because of a policy poster on a wall, but because it’s a one-person operation with a queue and no time for it.
What I never do: copy anything for myself, share anything, or keep your data after the job closes.
If a lab tells you their technicians see nothing at all, they’re either automating in a way that skips verification, or they’re smoothing over how the work is done.
How long do you keep my data?
During the job: your data lives on my working drives — the sector image and the recovered files. It has to, or there’s nothing to deliver.
After delivery: I hold the recovered data for a short window after you confirm you’ve got everything, in case a file turns out to be missing or your destination drive fails in transit. Then it’s wiped.
After that: gone. Not archived, not kept “just in case,” not on a backup of my bench.
Ask any lab: how long do you retain recovered data, and how is it destroyed? A specific answer is a good sign. “We take security seriously” is not an answer.
Where does the data physically live?
Mine stays on local storage in Pittsburgh. Your files don’t go to a cloud service, don’t get processed on someone else’s infrastructure, and don’t leave the bench.
Worth asking elsewhere, particularly of services with a slick web portal — a customer-facing cloud viewer means your recovered data is sitting on a third party’s servers under their terms, not yours.
What if there’s something sensitive on it?
There often is. People have drives with medical records, legal documents, financial records, and material they’d simply rather nobody saw.
A few practical things:
You can tell me the scope. If you only need D:\Photos recovered, say so. A targeted recovery means I never touch the rest of the drive, and it’s usually faster and cheaper anyway.
You can ask me not to verify certain paths. The tradeoff is that I can’t confirm those files are intact — you’d check them yourself on delivery. Some people prefer that trade and it’s a reasonable one.
Business and legal matters should say so upfront. If you’re under HIPAA, handling client files under privilege, or dealing with anything headed for litigation, tell me at the start. Some of that needs a formal chain-of-custody process and documented handling that a one-person shop isn’t the right fit for — I’d rather point you to a lab with those procedures than improvise them.
Free evaluation. Your drive, your data, back in your hands.
What about encrypted drives?
If your drive is encrypted and you give me the key, I can work with it. If you’d rather not hand over the key, that’s a legitimate position — but understand what it means: an image of an encrypted volume is an image of noise until the key is applied, so recovery beyond raw imaging isn’t possible without it.
Some people image the drive with me and do the decryption and file-level recovery themselves. That’s a fine arrangement and I’m happy to work that way.
Questions worth asking any lab
- Who physically handles my drive, and how many people?
- Is the work done in-house, or subcontracted? A lot of “labs” ship your drive onward. That’s another building and another set of people you haven’t vetted.
- How long is recovered data retained, and how is it destroyed?
- Is my data stored on any cloud or third-party service?
- Will you sign an NDA? For business work, most legitimate labs will.
- What happens to my drive if I don’t pay or don’t respond?
The uncomfortable structural fact
There is no way to have someone recover your data without them having access to your data. That’s the shape of the transaction, and no policy changes it.
What you’re actually choosing is who to extend that access to, and how much you can verify about them. In that light, a local operation where one identifiable person handles your drive and you can turn up in person compares reasonably well against shipping it to a facility where you’ll never know how many hands touched it.
I’m not claiming that as a knockout argument — plenty of large labs handle this properly, with real procedures and staff who’ve signed real agreements. But it’s worth thinking about the question rather than not thinking about it, which is what most people do.
The bottom line
I see filenames and folder structures, and I see some of your images while verifying they open. I don’t read your documents, I don’t keep your data, and it never leaves Pittsburgh. Ask any lab you’re considering how long they retain data, whether the work is in-house, and whether anything touches a cloud service — those three questions tell you most of what you need to know.
Got a drive with something sensitive on it? Start a case and say so — we can scope the recovery to only what you need.