Limited intake
The public form asks for contact, device, symptom, and service information—not passwords or sensitive file contents.
Data security
A data-recovery provider may encounter the most private information a customer owns. Our workflow is designed to collect only what is needed, restrict internal case access, separate public intake from private operations, and avoid unnecessary exposure.
Privacy controls
The public form asks for contact, device, symptom, and service information—not passwords or sensitive file contents.
The operational case dashboard is sign-in protected and checks an explicit server-side owner allowlist before customer data is shown or changed.
Files are accessed only as needed for evaluation, recovery, targeted verification, and preparing the authorized return.
Case details are tied to a unique number, and updates are handled through authorized contacts recorded for the case.
Secure handling
Where the case permits, recovery proceeds from a controlled image or working copy instead of changing the original device.
Customer priorities guide file checks so unnecessary browsing is avoided.
Recovered files are prepared on agreed storage and shipped or handed off using the case’s authorized method.
Original devices, temporary copies, and recovered media follow the service terms and the customer’s documented decisions.
A clear next step
Use the case form for symptoms and priorities. Do not include passwords, passcodes, recovery keys, financial details, or examples of sensitive file contents.
Start with a case reviewQuestions, answered
The route requires ChatGPT sign-in and a server-side allowlist match. A signed-in account that is not authorized receives no customer case data.
No. Recovery may require valid customer-provided credentials. NEPFOSYS does not bypass account security or encryption controls.
No. Email is used as an alert. The private dashboard remains the operational source for full case management and should be used for sensitive internal notes.
DFW local · Nationwide mail-in