wranglify

your data never leaves your computer

Wranglify is a desktop app for Mac and Windows that reads and writes files on your own machine. There is no account, no server, no analytics, and no network request.

What we collect

Nothing. Not your files, not their names, not how often you open the app, not whether you opened it at all. There is no server for any of it to go to. This is the same answer the Mac App Store listing gives under "Data Not Collected", and it is the whole answer on Windows too.

Your files

A file you open is read from your disk into the app and worked on there. Exports are written back to a location you choose. Nothing is copied off the machine at any point, because the app has nowhere to copy it to.

The recent files list keeps a copy of what you open, in the app's own data folder on your disk - its sandbox container on macOS, %APPDATA%\com.uncsoft.wranglify on Windows - so you can reopen without hunting for the file again. You can remove any entry or clear the whole list where it is shown. Files over 256 MB are listed by name only, with no copy kept.

Folders you authorize

To run a recipe over a whole folder, the app needs lasting access to that folder. On both platforms you grant it the same way - by picking the folder in your system's ordinary open panel - and grants are listed in the app and can be removed there. What the machine does with that choice differs, and the difference is worth stating rather than smoothing over.

On macOS, the app stores an app-scoped security-scoped bookmark: the operating system's own mechanism for remembering a choice you made in a panel. The sandbox then enforces it. Nothing outside a folder you picked is reachable, including by the terminal command, because the system will not permit it.

On Windows, a packaged desktop app runs with the file permissions of the user who launched it, so there is no container drawing that line. The app records the folder you picked and confines itself to it. That is the app keeping its word rather than the system enforcing it, which is a weaker guarantee and we would rather you heard it from us. What does not change is where anything could go: the build contains no network code on either platform, so a folder's contents have nowhere to travel.

What the operating system does, on each platform

On macOS, Wranglify runs under the App Sandbox. Its complete set of entitlements is four lines, and you can read them off the installed app: 

codesign -d --entitlements :- /Applications/Wranglify.app

On Windows, the Microsoft Store build is an MSIX package that declares runFullTrust. That is how essentially every desktop application in the Store ships, and it means the app runs outside any app container, with the file access of the user who started it. So Windows is not confining it. We are telling you that instead of implying otherwise, because "sandboxed" is a word this page could easily have reused on a platform where it would not be true.

What carries the claim there is what carries it everywhere: the build ships no HTTP client and no telemetry, and its Content-Security-Policy is default-src 'none' with connections limited to the app itself. There is no auto-update. You can verify that from outside the app on either platform, which is the next section.

About that network entitlement (macOS)

An app that says it makes no network requests, carrying an entitlement called "network client", looks like a contradiction. It is not, and the reason is worth stating plainly rather than leaving for you to find.

Wranglify draws its interface in WKWebView. WKWebView routes every load through the system's Networking process, even when the content is local and compiled into the app itself. Without that entitlement the sandbox blocks the app from loading its own interface and the window never paints. Measured here on one binary signed three ways: with the sandbox and no network.client, the result is a blank grey window with a working menu bar.

So the entitlement buys the app the right to load itself. It is not used for anything else, and you do not have to take that on faith:

The command line

Wranglify can also be started from a terminal to run a saved recipe over a folder. On both platforms that is the same app, not a second program, and it can reach exactly the folders you already authorized and nothing else.

On macOS the command is a small wrapper script that executes the app's own binary inside its bundle, so it runs in the same sandbox and the same container as the window does. On Windows the Store package registers the name with the system directly, so wranglify on your PATH is the packaged app itself.

Recipes

A recipe is a plain .json file on your disk listing the steps you built, in order. It contains your method, not your data. Sharing one means sending a file, and the file has no rows in it.

Crash reports and diagnostics

The app sends none, on either platform. If macOS offers to send a crash report to Apple, or Windows offers to send diagnostic data to Microsoft, that is between you and them, and each can be declined in its own settings. Wranglify has no reporting of its own and no way to receive one.

The web version

There is also a browser version of this tool at unfckr.app. It runs entirely in the tab and has its own privacy page describing how that works, including a live test that makes the browser try to leak data and shows every route refused. The two are separate programs. This page describes the desktop app, on both Mac and Windows.

Changes and contact

If this page ever changes in a way that matters, the change will be to describe something the app does differently, and the date below will move. Questions, or something here that does not match what you observe, go to feedback.

Last updated 19 August 2026 · Wranglify 1.2.0