Privacy

Privacy

Effective date: August 4, 2026

unzipzapp opens archives, PDFs, images, DOCX, Markdown, and text files locally in your browser so you can sort, merge, split, rezip, and export them. The core file-processing workflow runs on your device. Your source files and generated exports are not uploaded to unzipzapp.com.

Files you process

When you choose or drop files into unzipzapp, the browser reads those files locally. The app may create temporary in-memory previews, local browser records, and downloadable output files. unzipzapp does not send file contents to a server for processing.

Optional account features

If you sign in, authentication is handled by Supabase using your email address. Signed-in use can store build history metadata such as source archive name, output name, page count, file count, output size, and quality setting. This metadata is used to provide account and history features. File contents are not stored through this account workflow.

Local browser storage

unzipzapp uses browser storage for preferences and local workflow state, including theme, navigation layout, naming rules, recent export history, prefix rules, project memory, service worker cache, and browser-authorized folder handles where supported. You can clear this data from your browser settings.

Chrome extension

The unzipzapp Chrome extension detects supported completed downloads, shows a notification, stores a short-lived local handoff record, and opens or focuses unzipzapp. The extension does not collect or upload document contents.

Network requests

The app loads the unzipzapp web bundle and optional Supabase services for sign-in, roadmap, and build-history features. The current app code does not include advertising trackers or analytics scripts.

Security reports

Security reports can be sent to gmwynnwynn@gmail.com or submitted through the GitHub security advisory form.

Changes

This policy may be updated as unzipzapp changes. The effective date above will be updated when material changes are made.