Is Unzipr Safe? Permissions and Privacy Explained
This page exists specifically so you don't have to take that reassurance on faith — every claim below is verifiable, either through Apple's own sandboxing enforcement or by checking your Mac's own network activity directly.
Before installing any app that handles your files, it's reasonable to want a clear answer to "what does this actually do with my data?" rather than a vague reassurance. Here's a transparent, specific breakdown of exactly what Unzipr accesses, why, and what happens (and doesn't happen) to your files.
Extraction and compression happen entirely locally
This is the most important thing to understand: Unzipr processes archives entirely on your Mac. When you extract a ZIP, RAR, or 7Z file, or compress files into a new archive, none of that content is transmitted anywhere — not to Unzipr's servers, not to any third party. The entire operation happens locally using your Mac's own processing power, the same way Finder's built-in Archive Utility works, just with more capability.
Why we're publishing this level of detail at all
Most apps' privacy claims live in a lengthy legal privacy policy document that few people actually read in full, and that rarely explains the specific technical reasoning behind each permission in plain language. This page exists as a more direct, readable alternative — the goal is that you finish reading this and genuinely understand what's happening, rather than skimming a legal document and hoping it's fine. If anything here seems unclear or you have a follow-up question this page doesn't address, that's worth raising directly with support rather than assuming the answer.
What Unzipr requests, and exactly why
File access (user-selected read-write): Unzipr requests permission to read and write files specifically in locations you select — the archive you choose to open, and the destination folder you choose for extraction or compression output. This is a standard macOS sandboxing permission, meaning the app only accesses files you explicitly select through a file picker or drag-and-drop, not your entire file system by default.
Network access: Unzipr requests network access for two specific, limited purposes: verifying your subscription status if you're using PRO features (through RevenueCat, a third-party subscription management service), and sending anonymized crash and performance reports (through Sentry, a third-party error-monitoring service) to help identify and fix bugs. Neither of these network calls involves your archive contents — they're limited to subscription status checks and technical diagnostic data about app performance.
What Unzipr does NOT do
- Does not upload, transmit, or store the contents of any archive you extract or create
- Does not scan or index your broader file system beyond files you explicitly select
- Does not require an account or login to use core extraction features
- Does not sell or share user data with advertisers
Mac App Store sandboxing: an additional layer of enforcement
Unzipr is distributed through the Mac App Store, which means it operates under Apple's App Sandbox — a system-level security mechanism that restricts what any App Store app is technically capable of accessing, regardless of what the app's developer intends. This isn't just a policy Unzipr's developer chooses to follow; it's an operating-system-enforced boundary that Apple's App Review process verifies before allowing any app onto the Store. Sandboxing means Unzipr genuinely cannot access files outside what you've explicitly granted through a file picker, even if it wanted to.
Why crash reporting and subscription verification need network access at all
It's fair to ask why an app that processes files entirely locally needs any network access at all. Crash reporting (via Sentry) sends anonymized technical data — what part of the app crashed, basic device information — specifically to help identify and fix bugs faster than relying purely on user-submitted bug reports, a standard practice across the vast majority of modern software. Subscription verification (via RevenueCat) confirms your PRO status against Apple's own purchase records, necessary for any app offering in-app purchases or subscriptions, regardless of what the app itself does locally.
A realistic scenario: extracting sensitive financial documents
Picture using Unzipr to extract a password-protected archive of tax documents or bank statements. The entire process — entering the password, decrypting the contents, writing the extracted files to your chosen destination — happens locally on your Mac's own processor, with the actual document contents never leaving your device. The only network activity happening around that same time would be unrelated background checks (subscription status, if applicable) that have nothing to do with the specific files you're working with.
How this compares to browser-based "online extractor" tools
It's worth contrasting this with the free "online ZIP extractor" websites that show up in search results, since the difference matters directly for privacy. Those tools, by their nature, require uploading your archive to their server for processing — meaning the actual contents of your files pass through and potentially get stored on infrastructure you don't control. A native, local app like Unzipr never has this exposure, since there's no server-side processing step involved at all.
What happens to your data if you cancel a subscription
If you're a PRO subscriber and later cancel, no archive data is affected in any way — since Unzipr never stored your archive contents anywhere to begin with, there's nothing tied to your subscription status beyond which features remain unlocked going forward. Extraction remains free and fully functional regardless of subscription status, and any archives you've already created or extracted stay exactly as they are, completely unaffected by billing changes.
Comparing this to how a typical cloud-based app handles your data
Many modern apps, particularly those built around collaboration or cross-device sync, necessarily store your content on remote servers as a core part of how they function — genuinely useful for that specific purpose, but a fundamentally different privacy model than a local-first tool. Unzipr deliberately avoids this model for archive contents specifically, since there's no legitimate reason extraction or compression needs to touch a remote server at all — the entire operation is computationally simple enough to run efficiently on-device, without any tradeoff in speed or capability from keeping it local.
What Sentry and RevenueCat can and cannot see
To be fully specific about the two third-party services Unzipr integrates with: Sentry (crash reporting) receives technical diagnostic information — what code path triggered an error, basic anonymized device and OS version information — but has no access to your file system or archive contents, since crash reports are generated from the app's own internal state, not your files. RevenueCat (subscription management) receives your App Store purchase receipt information to verify PRO status, but similarly has no visibility into what files you're extracting or compressing — its entire scope is limited to subscription and billing status.
Where to find the full legal privacy policy
This page is deliberately written in plain language to explain the reasoning behind Unzipr's data handling, but it doesn't replace the formal, legally binding privacy policy, which covers additional standard legal language around data retention, your rights as a user, and other formalities not central to the practical "is this safe" question this page focuses on. Both documents describe the same underlying reality — this page in accessible terms, the formal policy in the precise legal language required for compliance purposes.
Frequently asked questions
Does Unzipr upload my files anywhere? No — extraction and compression happen entirely locally on your Mac; archive contents are never uploaded to any server.
What permissions does Unzipr actually request? File access to let you select archives and destination folders, and network access specifically for subscription verification and crash reporting — not for transmitting your file contents.
Is Unzipr available on the Mac App Store? Yes, which means it operates under Apple's sandboxing and App Review requirements, including restrictions on what a sandboxed app can access.
Verifying network activity yourself
If you want direct proof rather than taking these claims on trust, macOS's built-in Activity Monitor (Spotlight search "Activity Monitor") includes a Network tab showing real-time data sent and received per app. Extract a large archive while watching this tab, and you'll see no meaningful network activity correlating with the extraction itself — any traffic you do observe will be limited to the periodic, small subscription-check or crash-reporting calls described above, easily distinguishable from what file-content transmission would look like given their small, infrequent size.
Our broader privacy commitment
Beyond the specific technical details covered here, the underlying design philosophy is straightforward: Unzipr is built to be a tool that respects the fact that archive contents are often genuinely private — financial documents, personal photos, business files — and treats "never touch what doesn't need to be touched" as a default, not an afterthought bolted on for marketing purposes. This is reflected directly in the architecture, not just in a privacy policy document, since local-only processing was the design decision from the start rather than a retrofit.
Try it with confidence
Download Unzipr and verify this for yourself — extraction works entirely offline if you'd like to confirm no network activity occurs during a basic extraction, with the same free tier and permissions transparency described throughout this page.