Where your data lives
What WireLens stores on your device, how to clear it, and the few things that ever reach our servers.
A debugging proxy records sensitive things: tokens, cookies, personal data in request bodies. WireLens keeps all of it on the device you are debugging, and this page says exactly where.
On the Mac#
| What | Where |
|---|---|
| Captures, sessions and bodies | ~/Library/Application Support/WireLens |
| Rules and settings | ~/Library/Application Support/WireLens |
| The root certificate | ~/Library/Application Support/WireLens/ca/, with its private key in your Keychain |
| Client certificates and keys | Certificates with your settings, private keys in your Keychain |
| Team Workspace sign-in | Your Keychain |
| Crash logs | ~/Library/Application Support/WireLens/crash-logs |
Settings ▸ Storage shows how much room captures take and where. Settings ▸ Capture ▸ Body capture limit caps how much of each body is kept.
- Clear the capture: ⇧⌘K, or
wirelens clear. - Delete a session: in the Sessions window.
- Remove everything: quit WireLens and delete the folder above.
On iPhone and iPad#
Captures and settings live inside WireLens's own storage on the device. Clear them in the app. Deleting the app deletes them, and removing the WireLens profile removes the root certificate.
What reaches our servers#
Only these, and only for these reasons:
| When | What is sent |
|---|---|
| Checking or activating a Mac license, or starting the trial | Your license key or purchase email, and a one-way identifier derived on your Mac to enforce the device limit |
| Checking for a Mac update | A request for the update feed |
| Using Team Workspace | Your email to sign in, and the logs you choose to share, redacted and optionally end-to-end encrypted before they leave your Mac |
| Buying on iPhone or iPad | Handled by Apple. WireLens verifies the purchase through RevenueCat, which receives an anonymous purchase identifier, not your traffic. |
Your captured traffic is never among them. The apps contain no analytics or advertising SDKs, and crash logs stay on disk.
The license service and Team Workspace are reached over a connection that bypasses the system proxy and pins its certificates, so WireLens's own traffic never passes through a proxy, WireLens included.
A fuller Privacy Policy is being written and will live at that address. Until then, this page is the picture of what the apps store and send.
Something here is unclear, or wrong for your setup? Contact support or write to support@wirelens.app.