Privacy policy

The short version: VioLens doesn't collect any data about you, and neither does this website. Nothing you capture with VioLens is sent to me or anyone else.

This policy covers the VioLens app (for Windows, macOS and Linux), VioLens Capture, violens-exec, the Violens.ProxyCore and Violens.ProxyHost.Client libraries, and this website, violens.dev. VioLens is an independent open source project, and “I” here means its maintainer.

Last updated: November 6, 2026.

The VioLens app

VioLens doesn’t collect, send or keep any information about you or how you use it.

• No telemetry, analytics or crash reporting. The app doesn’t report usage, errors or anything else to me or to any other service.
• No accounts and no sign-up. You don’t need to give anyone your name or email address to download or use it.
• One update check, which you can turn off. At start-up VioLens asks GitHub’s public releases list whether a newer version is out. That request sends nothing about you or your traffic, only what any web request does (your IP address, and the VioLens version in the User-Agent). Turn it off by unchecking Help > Check for Updates at Start-up. VioLens never downloads or installs anything itself; you download new versions yourself.
• Diagnostic info only goes where you paste it. Help > Copy Diagnostic Info copies details for a bug report to your clipboard. It leaves out your computer’s name, and nothing is sent unless you paste it somewhere yourself.
• Captured traffic stays on your computer. The requests and responses VioLens shows are kept in memory while it runs. They’re only written to disk when you save them yourself, for example with File > Save SAZ or Export HAR, and only to the place you choose. They’re never uploaded anywhere.
• The root certificate is created on your computer. The certificate and private key VioLens uses to decrypt HTTPS are generated on your machine and stay there. You can remove them at any time with Tools > Remove Root Certificate.
• violens-exec only works on your computer. Scripts send it commands over a local connection that only your own account can open. Nothing listens on the network.
• Previews don’t go online unless you ask. The WebView tab’s Preview in Browser writes a copy of the page to a folder in your temp folder that only your account can open, with scripts blocked, and deletes it after a day. Your browser only fetches the page’s images and styles if you check Load images and styles from the site.
• VioLens Capture doesn’t send anything either. It saves a capture where you choose, and that’s all. Whether to send the file to someone is up to you.
• Your identity isn’t lent out. If you let phones or other computers use VioLens, it doesn’t sign them in to your company’s proxy as you, or send them your client certificate. On Windows and Linux the same goes for programs run by other accounts on your computer. (macOS can’t tell VioLens which account a connection came from.)
• A client certificate only goes where you say. A certificate usually has your name in it, so any site that asks for one could learn who you are. Until you list the hosts it’s for, VioLens offers it to every server that asks, and shows a warning saying so.
• Settings stay on your computer. Your preferences and AutoResponder rules are saved in a local file (preferences.json). A proxy sign-in password you type in is kept only while VioLens is running and is never saved. If your organization sets VioLens’s settings by policy, VioLens reads them from your computer, not from a server.

The network connections VioLens makes

VioLens is a proxy, so it makes network connections on your behalf:

• It forwards the requests your browsers, apps and devices send through it to the servers they were meant for, directly or through the upstream proxy you’ve set.
• If your computer uses an automatic proxy configuration (PAC) script, VioLens downloads that script from the address your computer is set to use, just as a browser would.
• Unless you’ve turned it off, it checks GitHub for a newer release at start-up, or when you choose Help > Check for Updates (see above).

It makes no other connections.

Scripts and extensions you add

VioLens can run FiddlerScript files and extensions that you choose to load. They run with the same access as VioLens itself, so they can see your traffic and could send data elsewhere. The optional extensions that come with the installers don’t send data anywhere. For anything else, check what a script or extension does before you load it.

This website

violens.dev doesn’t use cookies, analytics, advertising or tracking of any kind, and it doesn’t load anything from other websites. The fonts, images and video are all served from this site.

The site is hosted on GitHub Pages. Like any web host, GitHub may record technical information, such as your IP address, when your browser requests a page, for security and to keep the service running. I can’t see or access those records. GitHub’s privacy statement explains how GitHub handles them.

Downloads, GitHub and Discord

Downloads come from the project’s releases page on GitHub. If you open an issue, start a discussion or join the Discord server, what you post is public (or visible to the server’s members) and handled under GitHub’s or Discord’s own privacy policies. I only see what you choose to post there.

Children

VioLens and this website don’t knowingly collect information from anyone, including children, because they don’t collect information at all.

Changes to this policy

If this policy ever changes, the new version will be posted on this page with a new date. The page’s full history is public in the website’s repository on GitHub.

Contact

Questions about privacy? Email security@violens.dev or open an issue on GitHub.