UnZipTool Privacy Policy
Effective date: 22 September 2026 Last updated: 22 September 2026
This is a translation of the Chinese Privacy Policy, provided for convenience.
In case of any discrepancy, the Chinese version prevails.
The short version
UnZipTool does not upload your files and does not collect any personal information. All file processing happens on your own computer.
About networking: two cases
Please read the row that matches the version you use:
| Your version | Networked | Notes |
|---|---|---|
| Downloaded from our website | Fully offline | The app contains no network code at all |
| Microsoft Store version | Fully offline | This version has no purchasing features and likewise contains no network code |
Whichever version you use, the files you extract, compress or convert never leave your computer.
1. What we do not collect
None of the following is collected. This is a design decision, not a promise:
| Category | Notes |
|---|---|
| Personal identity | No name, phone number, email, ID number or address |
| File contents | The files you extract, compress or convert never leave your computer |
| File names and paths | Not uploaded, not recorded |
| Usage behaviour | No analytics, no telemetry, no crash reports, no session tracking |
| Device information | No machine name, CPU, memory, disk serial number or network adapter address |
| Location | Not collected |
| Accounts | There are no accounts — nothing to register, nothing to sign in to |
UnZipTool has no network functionality whatsoever. The program contains no networking code and cannot send data to any server — even if we wanted to collect something, there is technically no way to do it.
2. What is read and written locally
The app reads and writes the following locations. All of it stays on your machine and is never transmitted:
2.1 Licence information
| Item | Notes |
|---|---|
| Path | %LOCALAPPDATA%\UnZipTool\license.json |
| Contents | The licence key you imported (the key itself is a digitally signed licence file) |
| Purpose | Remembers that this machine is activated, so you do not re-enter it every time |
| How to remove | The "Deactivate" button in the app, or delete the file directly |
2.2 Converter engine setting
| Item | Notes |
|---|---|
| Path | %LOCALAPPDATA%\UnZipTool\converter.json |
| Contents | The LibreOffice path you specified manually (only if you set one) |
| Purpose | Saves you from pointing at the conversion engine again each time |
| How to remove | Delete the file directly |
2.3 Temporary files
| Item | Notes |
|---|---|
| Location | The system temporary folder (%TEMP%) |
| Contents | Intermediate files produced during document conversion, and a temporary user profile folder |
| Purpose | Required to complete the conversion |
| Cleanup | Released as soon as conversion ends. Archives are written to a temporary file and renamed only on success, so a cancelled or failed run cleans up after itself and never leaves a half-written archive |
2.4 Your own files
The app reads the files you explicitly choose (to extract, compress or convert) and writes results to the location you specify. It touches nothing else.
3. About the "machine code"
Activating the full version requires giving the issuer a "machine code". Here is what that is:
3.1 What it is
It is the first 32 hexadecimal characters of a one-way SHA-256 hash of a system identifier that Windows generates at install time (MachineGuid).
It looks like: AF13-0299-5089-474F-D49F-34D4-F01A-4B30
3.2 What it is not
- It is not your hardware serial number, network adapter address or any kind of device fingerprint
- It does not contain your username, computer name, file paths or IP address
- It is irreversible: the original system identifier and any personal information cannot be recovered from the hash
- It is not fetched over the network: the system identifier is read once, locally, and hashed immediately
3.3 Why it is needed
An offline licence must be able to confirm that "this licence key was issued for this machine". That is what the machine code is for — it binds the licence key to a specific device, which removes the need for online verification and for any kind of account system.
3.4 What sharing it means
When you send it to the issuer, the issuer sees only that string of hash characters and cannot learn anything else about your device or about you.
3a. Additional notes for the Microsoft Store version
If you installed the version from the Microsoft Store, please also note:
The Store version contains no purchasing features
The Microsoft Store build is completely free. There is no purchase, in-app purchase or paid-unlock entry point anywhere in the app. This version therefore processes no payment information at all and never asks you for account details.
The Store version is equally offline
Like the website version, the Store build contains no network code:
- It makes no requests to the Microsoft Store or to any other server
- It does not query entitlement state such as "has this been purchased" (there is no need — every feature is open)
- The files you process stay on your machine throughout
The only difference
The Store version and the website version are functionally identical. The only differences are:
| Website version | Store version | |
|---|---|---|
| Extract / compress / document conversion / image conversion | All available | All available |
| Per-operation size limits | Yes | Yes |
| Buying the full version to lift the limits | Available | Not available (this build offers no such entry point) |
In other words, the Store version is a fully functional tool that is free to use indefinitely. If you need the per-operation limits lifted, use the version distributed from our website.
4. Third-party components
The app uses the following open-source components. All of them run locally and involve no data transfer:
| Component | Purpose | Licence |
|---|---|---|
| SharpCompress | Reading and writing archives | MIT |
| CommunityToolkit.Mvvm | UI architecture | MIT |
| ModernWpfUI | UI styling | MIT |
| .NET 8 Runtime | Runtime (bundled) | MIT |
External dependency for document conversion
Document conversion requires you to install one of the following yourself (the app neither bundles nor downloads them):
- Microsoft Office
- LibreOffice (free and open source)
These are provided by their respective vendors, and their data handling is governed by their own privacy policies, which this policy does not cover. UnZipTool only calls them to perform the conversion.
Image conversion requires no external software — it uses the image codecs built into Windows.
5. Children's privacy
The app is not directed at children and collects no age information or children's personal information.
6. Your rights
Because we collect and store no personal information about you, there is no data for you to access, correct or delete.
You can remove all app-related data from your machine at any time:
- Click "Deactivate" in the app to delete the licence file
- Delete the entire
%LOCALAPPDATA%\UnZipTool\folder - Uninstall the app (deleting the program files is enough — the app leaves no registry entries behind)
7. Changes to this policy
If this policy changes, we will update the "Last updated" date in this document in a new release.
Because the app does not connect to the network, we cannot notify you of policy changes — please check this document when you update to an important new version.
8. Contact
If you have any questions about this policy, please contact:
- Issuer / developer:
UnZipTool - Email:
dabangzi2026@outlook.com
Appendix: How to verify this yourself
If you have doubts about this policy, you can verify it independently:
- Disconnect test: Unplug your network connection. Every file operation (extract, compress, document conversion, image conversion) still works — the only exception is document conversion, which needs Office or LibreOffice installed on your machine.
Both versions (website and Microsoft Store) behave identically in this test: neither depends on the network.
- Packet capture: Use a tool such as Wireshark to monitor network traffic. Across extraction, compression, conversion and activation, the app makes no outbound connections.
- File monitoring: Use a tool such as Process Monitor to confirm that the app only reads and writes the locations listed in section 2.
We welcome this kind of verification — a privacy statement that survives scrutiny is the only kind worth making.