Privacy Policy
Effective date: June 29, 2026
This Privacy Policy explains how ZIP Extractor (“we”, “us”, “our”) handles your information when you use the ZIP Extractor browser extension (“Extension”).
If you do not agree with this policy, please do not install or use the Extension.
What ZIP Extractor Does
ZIP Extractor is a browser extension that lets you open and extract archive files (.zip, .rar, .7z, .tar, .gz) directly in your browser. Archive files are processed entirely on your device using WebAssembly (WASM). File contents are never uploaded to our servers or any third party.
Information We Do Not Collect
We do not collect, store, or transmit:
- The contents of any archive files you open or extract.
- Your browsing history or the content of pages you visit.
- Personal identifiers such as your name, email, or IP address through the Extension.
- Cookies or tracking pixels inside the Extension.
Optional anonymous usage analytics and error reporting are described in Analytics and Error Reporting below. You can disable them at any time in Settings.
Information Stored Locally on Your Device
The Extension stores the following data in Chrome’s local extension storage (chrome.storage.local). Most of this data never leaves your device. Exceptions: files you save to Google Drive (see below) and optional anonymous analytics/error data when that feature is enabled (see Analytics and Error Reporting).
| Key | Purpose | Cleared |
|---|---|---|
displayMode | Whether the Extension opens as a tab or side panel | Persists until you change it |
activeZipExtractorTab | Chrome tab ID of the active Extension window | Cleared when the tab is closed |
pendingArchive | URL and filename of an archive opened from a page link | Cleared after the archive loads |
analytics_device_id | Random UUID used for anonymous analytics | Persists until you reset it in Settings |
analytics_opt_out | Whether you opted out of analytics and error reporting | Persists until you change it |
| Archive workspace session | Temporary state of the currently open archive | Cleared on browser startup or after extraction completes |
All locally stored data is accessible only to the Extension. Settings and workspace data are not shared with external services unless you use Google Drive or have analytics enabled.
Google Drive Integration
The Extension offers an optional feature to save extracted files directly to your Google Drive.
What we request
When you choose to connect Google Drive, the Extension requests an OAuth2 token from Google using the identity Chrome API. The requested OAuth2 scope is:
https://www.googleapis.com/auth/drive.file
This scope grants access only to files that the Extension itself creates or opens — not to your entire Google Drive.
What we do with the token
- The OAuth2 token is used solely to upload files you explicitly select for saving.
- The token is managed by the Chrome Identity API and is not stored by the Extension in
chrome.storageor sent to our servers. - You can revoke access at any time from your Google Account permissions page.
Google’s privacy practices
When you use Google Drive integration, Google’s own privacy policy applies to data handled by Google. See Google Privacy Policy.
Host Permissions and Content Script
The Extension requests access to all websites (https://*/* and http://*/*) in order to run a content script that scans page links for archive file extensions (.zip, .rar, .7z, .tar, .gz) and adds an “Extract” button next to them.
The content script:
- Only reads
hrefattributes of<a>elements to detect archive links. - Does not read, capture, or transmit page text, form data, passwords, or any other page content.
- Does not inject advertisements or modify page behavior beyond adding the Extract button UI next to recognized archive links.
Downloads Permission
The Extension uses the downloads Chrome API to save extracted files to your local Downloads folder when you choose “Save to device”. No download history or metadata is collected or transmitted.
External Websites
On first install, the Extension opens https://zipextractor.vip/welcome/ in a new browser tab. On significant version updates, it opens a changelog page at https://zipextractor.vip/changelog/.... The Extension’s UI may load content from zipextractor.vip in an embedded frame.
These pages are subject to the website’s own privacy practices. The Extension does not pass personal data or file contents to these pages.
Analytics and Error Reporting
The Extension collects optional, anonymous usage analytics and error reports to help us understand how the Extension is used and fix bugs. Analytics is enabled by default; you can turn it off at any time.
Usage Analytics (Amplitude)
The Extension sends anonymous usage events to Amplitude.
What we collect:
- A randomly generated device identifier (UUID) stored locally in
chrome.storage.local. This ID is not linked to your Google account or any personally identifiable information. - Session identifiers (timestamps) to measure session duration.
- Anonymous usage events such as: opening an archive (format and file size, no filename), extracting files (count and format), toggling display mode, switching themes, and using the content-script Extract button.
- Extension version and country (derived automatically from your IP address by Amplitude’s servers; the IP itself is not stored by us).
What we do NOT collect:
- Filenames, archive URLs, or file contents.
- Your Google account identity or OAuth tokens.
- Any personally identifiable information.
Amplitude’s privacy policy is available at https://amplitude.com/privacy.
Error Reporting (Sentry)
We use Sentry to collect anonymous crash reports and error stack traces. This helps us identify and fix bugs that affect users. Error reports include:
- JavaScript stack traces and error messages.
- Extension version.
- Approximate country (derived from IP by Sentry; IP is not stored by us).
No file contents, filenames, or personal data are included in error reports. Sentry’s privacy policy is available at https://sentry.io/privacy/.
Opting Out
You can disable both anonymous usage analytics (Amplitude) and error reporting (Sentry) at any time from the Extension Settings dialog using the Share anonymous usage data toggle. Turning the toggle off stops new data from being sent. Your preference is stored locally in chrome.storage.local and takes effect immediately, including for Sentry error reports.
Resetting Your Analytics Identifier
In Settings → Privacy, you can Reset analytics identifier to generate a new random device ID stored locally on your device. After a reset, future events are not linked to your previous anonymous profile in our analytics tools.
Requesting Data Deletion
To request deletion of data already stored on our analytics and error-reporting providers (Amplitude and Sentry), use Request data deletion in Settings → Privacy. This opens an email to delopappz@gmail.com with your current device ID pre-filled. We will process deletion requests in accordance with applicable privacy laws, including GDPR.
You may also contact us directly at delopappz@gmail.com with your analytics device ID (shown in Settings) to exercise your right to erasure or other data subject rights.
Children
The Extension is not directed at children under 13. We do not knowingly collect any personal information from children.
Changes to This Policy
We may update this policy as the Extension evolves. The “Effective date” at the top of this document will be updated accordingly. Material changes will be noted in the Extension’s changelog.
Contact
Questions or requests regarding this policy:
Email: delopappz@gmail.com