Before contacting support
Confirm that every numbered Takeout part was selected, the output is outside the source tree and the destination has enough free space. Check the JSON or CSV report for the source path, matching result and verification status of the affected item.
Record the Takeout Rescue version, operating system, source type, organization mode and the exact error text. Do not delete the original ZIPs while troubleshooting.
Download and launch issues
For macOS, verify that the application is the signed and notarized universal build. The current Windows 0.3.10 ZIP is unsigned, so verify its HTTPS source and compare the release SHA-256 checksum with the published value.
If the download was interrupted, discard the incomplete file and download the current artifact again rather than attempting repair with a partial installer or archive.
Repair and matching questions
A useful report excerpt includes the affected source path, detected format, sidecar match class and failure message. Remove or replace personal filenames if they are not necessary to reproduce the problem.
If support needs a sample, start with synthetic filenames and metadata or the smallest non-sensitive file you control. Do not send an irreplaceable private photo unless support has explained why it is necessary and you explicitly agree.
License and purchase help
Use the purchase email address when requesting a license restore or billing correction. Include the plan and approximate purchase time, but never send card numbers, authentication codes or private keys.
Support can help identify entitlement state; payment details remain with the payment provider.
Contact
Email support@takeoutrescue.ukilabs.com. Include a concise subject such as “0.3.10 macOS — ZIP integrity failure” or “license restore — purchase email” so the request can be routed quickly.
Support responses can explain published behavior and investigate reproducible defects, but cannot recreate information that is absent from both the media and Google sidecar.