FAQ – data recovery and safety

Standard diagnosis is free. If the case requires non-standard analysis or preparation, we explain that before any paid recovery work begins.

After diagnosis, you receive a quote and a description of the realistic recovery scope. Paid work starts only after approval.

We can give a general range after hearing the symptoms, but the final quote depends on the media type, damage and recovery procedure.

Data recovery often requires diagnosis, safe imaging, logical analysis or laboratory preparation of the device. The goal is working files, not a single technical operation.

Yes. We issue invoices and can handle company cases with formal intake confirmation.

Simple logical cases may be faster, while unstable HDDs, RAID/NAS arrays, encrypted media and damaged SSDs require more careful work. We explain the expected timeline after diagnosis.

If the case is time-sensitive, tell us immediately. We will explain whether a faster path is possible without increasing the risk to the device.

Yes. We provide updates after diagnosis and at key decision points, especially in business cases.

You receive the recovered data in the agreed form and information about the recovered scope so you can verify the result.

Data are handled confidentially. Access is limited to the people working on the case, and business clients can request NDA handling.

Yes. If an NDA is needed, tell us before delivery or before the case is accepted.

If the device is unstable or the case requires it, we create an image or sector-by-sector copy and continue analysis on the copy. The original is then less exposed to additional wear.

By default, we keep recovered data for a limited time after the case is completed so you can collect and verify it. Details are agreed when we hand over the result.

Disconnect the device and do not make further attempts to write, format or repair it. Describe the symptoms by phone or through the form and we will suggest the safest first step.

No. Chances depend on the device type, damage type and what happened after the failure. That is why we diagnose first instead of promising a result without checking the device.

We do not recommend it if the data matter. Software launched on the same device may write data, deepen logical damage or make later diagnosis harder.

It should not if it is performed safely. We avoid aggressive scans on the original and match the procedure to the symptoms and condition of the device.

It depends on the case. If intervention in the device is needed, the manufacturer may refuse warranty coverage. If the device is under warranty, tell us before we accept the case.

An HDD may have mechanical or surface damage, while SSD/NVMe recovery depends on the controller, NAND memory, firmware, TRIM and encryption. That is why the procedure for SSD/NVMe differs from a classic spinning drive.

TRIM can remove information about deleted data and make recovery harder. After file loss on SSD/NVMe, it is best to shut down the computer immediately and not boot the system from that device again.

Yes. We work with RAID/NAS arrays, file servers and business environments. It is important not to perform a rushed rebuild, initialization or disk order change.

The safest option is to deliver the full drive set and information about order and configuration. If you have clones or images, we can determine whether they are enough for analysis.

Yes. We handle USB flash drives, external USB drives, SD/microSD cards, CFexpress, CFast and other flash media. After an error, do not write new data to them.

Stop using the card and do not take more photos or videos. Every write may overwrite material that could still be recovered.

Yes, but the scope depends on the recorder, recording system, disk condition and possible overwriting. First we secure the device and check which time ranges are realistic to recover.

Yes. We handle SQL Server, Access, Płatnik, Optima, Subiekt and accounting or warehouse databases. It is best to prepare database files, logs, backups and a description of the last correct operation.

Collect database files, application or SQL logs, error messages, software version, the latest backup and a description of events. Do not run repairs on the only production copy.

Yes. We analyze virtual machines, VMDK/VHDX files, PST/OST mail and file servers. In these cases, dependencies between files, snapshots and environment configuration matter.

Disconnect infected devices from the network, do not install cleaning tools on the same device and do not overwrite data. In a company, secure logs, backups and a timeline of the incident.

First stop actions that could change the state of the data. Then set priorities: key folders, databases, users or date ranges. This helps make decisions faster after diagnosis.

Call us or send the form with a short description of the device, symptoms and the data that matter most. You do not need to know the exact device model for the first conversation.

Yes. We accept shipped cases from all over Poland. After contact, we will tell you how to prepare the package safely and what to include with the case.

It is best to call first or send a case form. That lets us confirm availability and tell you what not to do with the device before delivery.

The laboratory is in Warsaw, Białołęka: Jana Kowalczyka 1, unit 8, 2nd floor. Address details are also in the page footer.

Protect the device from shocks and electrostatic discharge. Use a rigid box, padding, and include a note with contact details and a symptom description.

We do not recommend it. Continuing to use an unstable drive, card or USB flash drive may increase damage or overwrite data.

Do not force it to start again, do not scan it with repair programs and do not open the enclosure. With mechanical symptoms, every further attempt can make the drive condition worse.

Do not rebuild blindly, initialize the volume or change disk order. Save messages, drive order and recent administrative actions.

Do not repair the only production copy and do not overwrite logs. The safest approach is to secure database files, logs, backups and an event description, then analyze a copy.