The whole discipline comes down to one rule: never work on the original. We take a read-only copy of your failed drive, then do every bit of the rebuilding on the copy. Here’s what actually happens from drive to recovered files — and, since everyone wonders, a straight answer to whether anyone can see what’s on it.
A failing drive gets worse every time it’s used, so the original is imaged once, read-only, and then set aside. Everything after that happens to the copy — which is why good recovery can’t make things worse.
Work on a copy, never the patient.
Whatever has gone wrong, the first move is always the same: take a sector-by-sector, read-only image of the drive onto healthy storage, using hardware that can read the drive but is physically prevented from writing to it. From that point the original is left untouched and every attempt at reconstruction happens on the image.
There are two good reasons. First, a failing drive degrades a little more every time it spins — so you get one clean read, not dozens of risky ones. Second, if a first approach doesn’t work, we simply take a fresh copy of the image and try another, without ever having altered your data. It’s the opposite of running repair software on the drive itself, which writes to the very thing you’re trying to save.
Almost every job is one of these two, and they’re solved differently.
Logical failures mean the drive works but the data is scrambled — deleted files, a formatted or corrupt file system, a lost partition. The disk is healthy, so we image it and then rebuild the file system, or, where its structure is gone, carve the files straight out of the raw data by recognising each format’s signature. Our guides on recovering deleted files cover the DIY end of this.
Physical failures mean the hardware itself is broken — failed read/write heads, a burnt circuit board, corrupt firmware, fire or water damage. Software can’t touch a drive the computer can’t even read, so this is bench work first: a matched donor part, board or head-stack, or a firmware repair, just to get the drive to a state where it can be imaged — and only then does the logical side begin. Our lab and tools page shows the equipment that makes that possible.
1. Diagnose. The drive is examined read-only — its health data, heads and service area checked, the file system inspected — to find exactly what’s failed. That’s the free diagnostic, and it’s what your fixed quote is based on.
2. Image. A read-only, sector-by-sector copy is taken, working around any bad areas and returning to them last, so the most data comes off before a weak drive tires.
3. Rebuild. On the copy, we rebuild the file system, reassemble a RAID array from its members, or carve files by signature — whatever the failure calls for.
4. Verify. Recovered files are validated — opened, checked against their own internal structure, compared by checksum — so what comes back genuinely opens rather than reproducing the damage.
5. Return. Your data comes back on fresh encrypted media or a secure download, and once it’s safely with you the working copy is securely wiped. The full journey is on our process page.
Recovery touches the structure of your files. It doesn’t mean anyone reads them.
Here’s the honest version. Rebuilding a file system inevitably means the recovery software — and the engineer — sees folder names and file names, because that’s the structure being repaired. Confirming the recovery worked means opening a small sample of files to check they’re intact. Beyond that, nobody trawls through your content; there’s no reason to, and a serious lab doesn’t.
What protects you is method rather than a promise: a single engineer handles your job from start to finish, the work is done in-house and never outsourced or sent abroad, we’ll sign an NDA at no charge, and once your data is returned the working copy is securely wiped — a verified overwrite, not a simple delete — with no copies kept. It all stays within UK jurisdiction. There’s more on our data security page.
Done properly, no — and knowing why tells you what to avoid.
Proper recovery works on a read-only image, so the original can’t come out worse than it went in — there’s simply nothing being written to it. The real danger is the opposite approach: DIY software scanning a failing drive for hours, a controller rebuilding a degraded RAID, or a “repair” that writes over the very data you need. That’s how recoverable data becomes lost data.
So when you’re choosing anyone, look for the signs of a lab that works this way: a real premises you could visit, a written quote before any work, plain no-fix-no-fee terms, and a straight answer that they image read-only. If a drive is clicking, undetected, dropped or flooded, the safest thing is to stop using it and get an honest diagnostic.
An engineer takes a read-only, sector-by-sector copy of the failed drive — repairing physical or firmware faults first where needed to make it readable — then does all the reconstruction on that copy: rebuilding the file system, reassembling a RAID array, or carving files by signature. The results are verified so they genuinely open, then returned to you. The original is never written to.
Rebuilding a file system means the software and the engineer see folder and file names, and checking the recovery worked means opening a small sample — but nobody reads through your content. A single engineer handles your job in-house, we’ll sign an NDA at no charge, and the working copy is securely wiped once your data is returned.
Not when it’s done properly. Professional recovery works on a read-only image, so the original can’t be altered. What does overwrite data is running repair or recovery software on the drive itself, or letting a RAID rebuild — both write to the drive. If the data matters, image first and work on the copy.
A reputable lab is both. The safeguard is method: the drive is imaged read-only so nothing degrades, one engineer handles the job in-house and never outsources it, an NDA is available at no charge, and your data stays within the UK and is wiped after return. Look for a real premises, a written quote and no-fix-no-fee terms.
Logical recovery is for a healthy drive with scrambled data — deleted, formatted or corrupt — and is solved by rebuilding the file system or carving files out. Physical recovery is for a broken drive — failed heads, a dead board, corrupt firmware — and needs clean-room and firmware work to make the drive readable before the data can be imaged.
No. Once your recovered data is back with you — on encrypted media or by secure download — the working copy on our systems is securely wiped with a verified overwrite, not a simple delete, and no copies are kept.
Send the drive in or drop it off — we’ll diagnose it read-only, tell you honestly what can be recovered, and give you a fixed written quote before any money changes hands.