Privacy Policy
Last updated: April 15, 2026
Your archives stay in your browser.
Every archive operation — create, extract, inspect, convert, merge, split, encrypt, decrypt — runs entirely inside your browser using WebAssembly. Your files are never uploaded to a server. Not ours. Not anyone else's.
What we do not collect
We do not collect, transmit, log, or store:
- File contents — not a single byte of any file you open, create, extract, or convert
- File names — we never see what your files are called
- File sizes — we don't know how large your archives are
- File types — we don't record what formats you work with
- File counts — we don't know how many files are in your archives
- Passwords — encryption passwords exist only in your browser's memory for the duration of the operation, then are discarded when you close the tab
- Archive metadata — compression ratios, folder structures, timestamps, none of it
There is no backend. There are no API routes. There is no server that receives your files. The site is a static Next.js application hosted on Vercel. The archive processing code (JSZip for ZIP format, 7z-wasm for 7z/RAR/TAR/GZ) runs as JavaScript and WebAssembly in your browser's sandbox.
How processing works
When you drop a file onto a MakeMyZip page, this is what happens:
- Your browser reads the file from your local disk into browser memory (RAM).
- The archive library (JSZip or 7z-wasm) processes the file entirely within your browser's JavaScript/WebAssembly runtime.
- The output file is created in browser memory.
- When you click "Download," the browser saves the output file from memory to your local disk.
At no point does any data leave your machine. You can verify this yourself: open your browser's Network tab in DevTools before processing a file. You will see zero outbound requests containing file data.
What we do collect
We collect aggregate, anonymous page-view analytics. Personalized ads require your cookie consent — the ad script only loads if you opt in.
Analytics
We use Vercel Analytics, a privacy-focused analytics service that does not use cookies and does not track individual users. It records, in aggregate:
- Page URL visited (e.g., "/create-zip")
- Referrer (how you found us)
- Country-level location (derived from IP, which is not stored)
- Browser and OS type
- Screen size category (mobile, tablet, desktop)
Vercel Analytics does not set cookies on your device, does not record full IP addresses, does not use fingerprinting, and does not build user profiles. vercel.com/docs/analytics/privacy-policy
Advertising (if you consent)
We use Google AdSense to display ads. If you consent to ads, the AdSense script may set cookies and collect data according to Google's advertising policies. Ads are placed below the fold on tool pages and never interrupt the tool interface. policies.google.com/technologies/ads
Neither analytics nor ads have any access to the files you process. The archive processing code runs in an isolated WebAssembly context that does not communicate with any ad or analytics scripts.
Cookies and local storage
- Cookie consent preference — stored in localStorage so we remember your choice. Contains only "accepted" or "declined" — no personal data.
- Theme preference — stored in localStorage ("light" or "dark").
- AdSense cookies — only set if you consent to ads. Managed by Google, not by us.
We do not use session cookies, authentication cookies, tracking cookies, or any first-party cookies beyond what is listed above.
Third-party services
- Vercel — hosts and serves the website. Vercel may log IP addresses in standard web server access logs. vercel.com/legal/privacy-policy
- Vercel Analytics — cookieless. No personal data collected.
- Google AdSense — if you consent. Subject to Google's privacy policies.
None of these services receive any data about the files you process. The file processing code does not make network requests.
Data retention
We retain nothing because we receive nothing. Your files exist only in your browser's memory while you're using the tool. When you close the tab or navigate away, the browser frees that memory. There is no server-side storage to delete because there is no server-side storage.
Children's privacy
MakeMyZip does not knowingly collect personal information from anyone, including children under 13. Since we do not collect personal data at all, there is nothing to delete.
Changes to this policy
If we change this privacy policy, the updated version will be posted on this page with a new "last updated" date. The core commitment — your files never leave your browser — will not change. If it did, MakeMyZip would have no reason to exist.
Questions
If you have questions about this privacy policy, open an issue on our GitHub. github.com/File-Toolkits