← Back to Reclazz

Privacy

Reclazz collects nothing about you, your code or your machine. It makes no network requests to anywhere. This page says exactly what it does touch, because a tool that puts an agent into the JVM running your code owes you that answer.

In Plain English TL;DR

✓ No telemetry, no analytics, no crash reporting, no usage statistics
✓ No account, no sign-in, no licence check
✓ No outbound network requests of any kind, so nothing about your code leaves your machine
✓ The one socket it opens is bound to 127.0.0.1 and reachable only from your own machine
✓ The source is public, so none of this has to be taken on trust

What Reclazz reads

Only what it needs to reload your classes, and only on your own disk:

Compiled .class files in the output directories you or your build tool point it at
Java source files, when you ask it to compile changes for you
On SAP Commerce, your installation layout: extension directories, localextensions.xml and the platform properties, so it knows what to watch

All of it is read locally and used in memory. None of it is uploaded, copied off your machine or retained anywhere by us.

What Reclazz writes

~/.reclazz/agent/reclazz-agent.jar, a copy of the agent that ships inside the plugin. It lives outside the IDE installation so that upgrading your IDE cannot leave a server pointing at a jar that no longer exists.
.idea/reclazz/agent.port in your project, so the IDE can find the running agent.
On SAP Commerce, a 95-local.properties file in your optional configuration directory, containing the agent flag and nothing else. Your own local.properties is not modified, and the install verifies that it changed nothing but the agent.

The local socket

The agent opens one TCP socket so the IDE plugin can show you reload status. It is bound to the loopback address, 127.0.0.1, which means nothing outside your machine can connect to it, including other machines on your network. It carries reload events: which class was reloaded, whether it succeeded and how long it took. The IDE plugin connects to that same loopback port and to nothing else.

Third parties

There are none. Reclazz embeds no analytics or reporting library, and contacts no service of ours or anyone else’s. Your IDE and your operating system have their own privacy policies covering their own behaviour; those are between you and their vendors, and Reclazz neither adds to nor changes what they do.

Checking any of this

Reclazz is open source under the Apache License 2.0. If you would rather verify than believe, the agent’s socket setup is in StatusServer.java, and a search of the repository for outbound HTTP will come back empty. Read it at github.com/onurkat/reclazz.

Changes, and getting in touch

If this ever stops being accurate, this page changes first and the release notes will say so. Questions go to GitHub issues.

Last updated 12 August 2026.