1. Zero file storage on our servers

JetZip does not upload, store, cache, or retain the contents of your archives or shared files on JetZip servers. ZIP tools (unzip, compress, encrypt, split/merge) run entirely inside your browser using client-side libraries. Your file bytes stay on your device unless you choose to download a result locally.

We do not operate a file-hosting backend for user content. There is no JetZip cloud locker, no server-side processing queue, and no retention of uploaded archives.

2. Peer-to-peer transfer via WebRTC

Anonymous file transfer uses WebRTC to open a direct peer-to-peer (P2P) data channel between the sender’s and receiver’s browsers. File payloads travel device-to-device over that channel. JetZip does not receive, inspect, or store the transferred file contents.

A lightweight signaling path may be used only to help browsers discover each other and establish the WebRTC session (for example, exchanging connection metadata). Signaling is not a substitute for file storage and is not used to keep copies of your files.

3. End-to-end encryption on the transfer path

WebRTC data channels are encrypted between peers using transport security provided by the WebRTC stack (DTLS-SRTP). JetZip cannot read the contents of files moving through an established peer tunnel.

Password-protected ZIP encryption is also performed in your browser before any local download. Encryption keys and passwords you enter for ZIP tools remain on your device and are not sent to JetZip servers.

4. Advertising cookies (Google AdSense / DoubleClick)

JetZip may display ads served by Google AdSense. Google and its partners—including DoubleClick—may use cookies, advertising IDs, and similar technologies to serve personalized or non-personalized ads, measure performance, and prevent fraud.

These third-party technologies can collect information such as your IP address, browser type, approximate location derived from IP, pages visited on JetZip, and interaction with ads. Google’s use of this data is governed by Google’s privacy and advertising policies. You can manage ad personalization through Google Ads Settings and, where available, your browser’s cookie controls or industry opt-out tools.

Essential site operation does not require AdSense cookies. Advertising cookies are used for advertising and related measurement on pages where ads are shown.

5. Analytics and technical logs

We may use privacy-conscious analytics or hosting provider logs (for example, request timestamps, truncated IP addresses, user-agent strings, and error rates) to keep the site reliable, understand aggregate traffic, and detect abuse. These logs are not used to reconstruct your file contents.

If analytics cookies or similar identifiers are enabled, they help us understand how visitors use JetZip in aggregate. You can limit cookies through your browser settings; see our Cookie Policy for details.

6. What we do not collect about your files

We do not ask you to create an account to use core tools. We do not require a membership profile. We do not intentionally collect the names, binary contents, or passwords of the files you process or share peer-to-peer.

Remote ZIP fetch reads ranges from a URL you provide directly from your browser to the remote host (subject to that host’s CORS and Range support). JetZip does not proxy those file bytes through a JetZip content store.

7. Your choices and contact

You can clear cookies, use browser private mode, or block third-party cookies. Blocking advertising cookies may reduce ad relevance but should not prevent local ZIP tools from working.

Privacy questions: contact us via the Contact page. We will respond as promptly as reasonably possible.