Skip to main content

Who writes on Save My Disk

Our team: who we are, what we test, and why we take consumer data recovery seriously.

EG

Eric Gerard

Editor · Data recovery and backup specialist

Independent editor for 12 years, former network admin at an industrial SMB. I've spent years testing data recovery software on SATA, NVMe, SD and USB drives to check in the field what vendors claim on their spec sheets. On this site, every recommendation comes from hands-on use, not a product brochure.

My career started in 2010 as a network admin for a French industrial SMB: three sites, fifty workstations, and responsibility for local backups on LTO tapes and Synology NAS. That's where I first saw what a botched RAID 5 crash could cost a factory floor — and since then, I've known data recovery isn't a marketing product; it's a discipline with hard physical rules (don't write to the failing disk, image first with dd, work on the copy). After 2014 I switched to affiliate tech publishing, keeping the same hands-on discipline: I buy every license myself as a normal customer, I run the tools on real drives, and I lean on documented capabilities and public consensus rather than invented figures. I'm self-taught — no degree in data forensics, but 12 years of operational practice on HDD, SSD, NVMe, SD cards, USB drives, plus continuous reading of NIST SP 800-88 (sanitization) and professional forums (HDDSurgery, Ace Lab). I publish under my full name and personally answer technical questions sent through the contact form.

12+ years in tech publishing and affiliate marketing

Have a question about a recovery case or a tool we tested? Email me directly at contact@save-my-disk.com — I answer personally.

Areas of coverage

  • File recovery on HDD, SSD, NVMe and SD cards
  • Lost partition, RAW and MFT corruption diagnosis
  • Comparative tests of EaseUS, Recuva, Disk Drill, R-Studio, PhotoRec
  • 3-2-1 backup strategies and local encryption
  • GDPR audit and CJ Affiliate compliance

Our extended team

Beyond Eric, our technical articles go through a review loop by external consultants, anonymised at their request. They are not co-authors: they are reviewers paid on a per-article basis to verify technical claims before publication.

  • Technical reviewer #1 — Storage forensics

    14 years of experience in professional data recovery (private recovery lab), expert in HDD platters, PCB swaps, clean-room reads on dead mechanical drives. Verifies our claims on SMART failure scenarios, BAD CTX, SSD controller death before publication. Average review time: 5 business days.

  • Technical reviewer #2 — Enterprise backup strategies

    11 years in sysadmin / SMB IT (50-500 endpoints), expert on Synology and QNAP NAS, off-site backups (LTO, encrypted cloud), DR/BC plans. Verifies our 3-2-1 recommendations, restore drills, ZFS/Btrfs snapshots. Average review time: 7 business days.

Editorial standards

Every article published on Save My Disk follows the process below, with no exceptions or shortcuts.

  • Technical peer review before publication

    Every article containing measurable technical claims (recovery rates, scan times, TRIM behavior) is reviewed by one of our two technical reviewers. Unverifiable claims are removed.

  • Editorial transparency

    This is an editorial comparison, not a private lab study. We don't publish invented per-scenario percentages — capability ratings are qualitative (High / Medium / Low) and the software version covered is noted on each product page.

  • Maximum revision cycle of 90 days

    No article stays published longer than 90 days without a review of its technical content. The frontmatter date (datePublished / dateModified) reflects the last real verification, not a cosmetic CI build.

  • Public correction policy

    If a factual error is reported, we correct it within 48 business hours and add a dated note at the bottom of the article explaining the change. No silent corrections.

  • Conflicts of interest declared on every page

    Pages containing affiliate links carry a disclaimer at the top: persistent banner + rel="sponsored nofollow" HTML attribute on every commercial link. No exceptions.

See our testing process in detail

Read the full methodology