Privacy statement
Effective: August 25, 2026. Last updated: August 31, 2026.
ZiFile is published by ZiCode and is an open-source Windows archive utility licensed under the MIT License. This statement applies to the ZiFile desktop app, command-line tool, isolated Worker, and File Explorer extension.
Data we do not collect
Section titled “Data we do not collect”ZiFile requires no account and contains no advertising, analytics SDK, default telemetry, cloud synchronization, or automatic crash upload. The app does not send file names, paths, file contents, archive contents, passwords, or usage activity to ZiCode or third-party services.
Local processing
Section titled “Local processing”Files and archives that the user selects or drops are processed only on the device. Input files, created archives, and extracted results remain in locations selected by the user on the local file system. ZiCode does not receive this content and sets no remote retention period for it.
ZIP and 7z passwords are passed and used locally and are not written to settings, logs, or command-line arguments. The CLI reads passwords from standard input. After a create request is accepted for execution or queuing, the desktop immediately clears the create-form password. A password used to open an encrypted archive remains only for that archive session so subsequent test or extract operations can reuse it, and is released when another archive is opened or the app exits. Queued request snapshots release their passwords after completion, clearing, or exit. As with any desktop process, data can exist briefly in memory while the process is running.
ZiFile stores interface language, theme, and up to eight local archive paths that the Worker opened successfully in %LOCALAPPDATA%\ZiFile\settings.conf. These paths power the home-page recent list. Failed open requests are not recorded, and passwords and archive contents are not written to this file. Paths use hexadecimal field encoding to protect the configuration structure, not encryption; anyone who can read the current Windows user’s profile can recover them.
Users can remove one recent entry, clear all recent history, or delete settings.conf after closing ZiFile. An entry remains until displaced by a newer item, removed or cleared by the user, or removed with the settings file. Removing history does not delete the referenced file. Whether uninstall or Windows app reset removes a settings file in an ordinary desktop path depends on deployment behavior, so this statement does not promise automatic removal.
Network and third parties
Section titled “Network and third parties”The current MSIX declares only the full-trust desktop capability and does not declare the Internet client capability. ZiFile provides no in-app network service. Microsoft Store, GitHub, or WinGet may process network and account data under their own privacy terms when users download or update the app; that activity is separate from data collection by ZiFile itself.
ZiFile does not sell, rent, or share personal data because the app does not collect that data for ZiCode. Open-source dependencies and their licenses are recorded in the project repository and release materials.
Children, changes, and contact
Section titled “Children, changes, and contact”ZiFile is a general-purpose file utility, is not directed to children, and does not knowingly collect children’s data.
If a future optional feature requires networking or data collection, this statement will be updated before that feature is released and will describe its purpose, scope, retention, and controls. The revision date will remain visible at the top of this page.
For privacy questions or deletion requests, contact ZiCode through ZiFile GitHub Issues. Because the current app does not upload user files or personal data to ZiCode, ZiCode normally holds no app data that it can delete on a user’s behalf.