D-Secure Autopilot Detection identifies Windows Autopilot and Intune-enrolled devices during ITAD processing, verifying cloud unenrollment before resale to prevent re-enrollment loops. Even after a complete drive wipe, Autopilot enrollment persists at the cloud level, causing resold devices to automatically re-lock to the previous owner's Microsoft tenant. This tool detects enrollment via bootable USB, verifies unenrollment directly through the Azure/Intune API, and generates a tamper-evident.
Been thinking about this a lot lately most teams either rely on OS-level deletion or full-drive wipe tools, but neither really covers targeted cleanup (specific files, cloud drive residue, browser traces) for GDPR/HIPAA-style audits. Curious how others handle this in practice is it a tooling gap, or more of a "nobody owns this process" problem in most orgs?
Hey everyone we launched D-Secure File Eraser on Product Hunt today.
The problem we kept running into: most data erasure tools focus on wiping an entire drive, but a lot of real compliance work (offboarding an employee's laptop, cleaning shared drives, clearing cloud residue) needs to target specific files and folders without touching the rest of the machine. Regular deletion also isn't enough, since the data is technically still recoverable.
File Eraser overwrites the targeted files/folders/free space beyond forensic recovery and generates a tamper-proof, digitally signed certificate useful for GDPR/HIPAA/DPDPA audit trails.
Curious how others here handle this do you use dedicated erasure tools, or rely on OS-level deletion/reformatting? And for anyone who's built compliance-facing tools, what's been the hardest part to get right the erasure itself, or the reporting/audit side?
