/// Security
What L3git does with your data: nothing.
L3git is a desktop application, not a hosted service. The short version is that your tests, the systems they exercise, and the credentials they use never reach us. This page states what we can show you how to verify, and says plainly where something is a business commitment rather than a technical guarantee.
Data handling
Your tests, the systems they exercise, your credentials, and the code L3git generates stay on your machine. We never receive them. There is no test-results cloud, no hosted execution grid you are required to use, and no account needed to run the product.
Everywhere the application can make a network call
For completeness, rather than a reassuring summary — the full outbound list:
- Our license endpoint — detailed in the next section.
- Our update check — whether a newer version exists.
- Your AI provider — only if you switch on the optional AI authoring features, and only using an API key you supply. Prompts go directly to that provider, never through us. If you do not enable AI features, this call never happens.
- Browser-driver downloads — the Chrome and Firefox WebDriver binaries, from their official public sources, when a driver is needed.
On an offline key, every one of these is suppressed — including the update check.
Licensing and activation
License enforcement is the only thing the application talks to us about, so here is exactly what it sends, how often, and what it keeps.
What is transmitted
Over TLS to our license endpoint, the client sends: the license key, a client-generated instance ID (a random GUID, not derived from your hardware), a truncated machine fingerprint (the first 12 characters of a SHA-256 hash — one-way and not reversible to anything about the machine), and the machine hostname. That is the complete list.
The client does not transmit an IP address. It also never sends your tests, the systems they exercise, your credentials, or any generated code — none of that is part of any licensing payload.
How often
A standard online key re-validates once each time the application starts — not once at purchase. Floating seats additionally heartbeat about every five minutes to hold the lease. If our server is unreachable, the application continues to work for a 14-day grace period and then warns rather than locking you out.
The update check sends only the edition name and the app version. We count those requests — with a hashed, daily-rotated visitor id, never a raw IP — as our installed-base metric, and we count installer downloads the same way. That is the whole of our product analytics: no third-party trackers, no cookies, nothing per person.
Keys issued with the offline flag make no outbound calls at all — activation, heartbeat, and the update check are all suppressed. See regulated & air-gapped.
What is stored on your machine
Beside the executable, the app keeps a hash of the license key, the full machine fingerprint hash (only 12 characters of which are ever transmitted), the instance ID, and activation timestamps. Your license key file itself is stored in cleartext, as with most desktop software — treat it with the same care as any other credential on that machine. These files persist until you deactivate or uninstall.
What our server keeps
Per activated machine, the license server stores: a SHA-256 hash of the key (never the key itself), the instance ID, the truncated fingerprint, the hostname, the source IP of the activation call as seen by the web server (the client never sends one, but any HTTPS server observes it), and created / last-seen timestamps. Nothing else is received, so nothing else is stored.
Retention: a node-locked activation record lives exactly as long as the seat is held. Deactivating deletes the row — it does not merely free the seat. Floating-seat records whose lease lapses are deleted automatically the next time that key is seen. Keys issued with the offline flag never create a record at all.
The AI assistant
Optional and authoring-time only. With the cloud provider, the app sends your
plain-English description and a trimmed snapshot of the current page's interactive elements
(password field values are dropped before capture) to the Anthropic API under your own
key; we operate no proxy and see none of it. With the local provider, the
same request goes only to the Ollama host you configure — typically localhost
— and nothing leaves the machine. Generated tests never call a model; CI stays deterministic.
Hard daily and monthly call caps are enforced locally so a loop cannot run up a bill.
What runs on the machine
The desktop app runs on the PowerShell that already ships with Windows — no Python, Node, or additional runtime is installed. The installer is digitally signed. Running the tests it generates needs JDK 17 or later and Maven, like any Java project.
For browser tests, L3git drives the Microsoft Edge already installed and managed on the machine; it never downloads a browser of its own. The only companion it needs is Edge's WebDriver, which air-gapped builds bundle and online builds fetch from Microsoft only after announcing the exact URL — and which you can supply by hand instead.
Dependencies and supply chain
Generated projects are standard Maven, so every dependency is declared in a pom.xml
you control and can scan with your existing tooling.
An opt-in checkbox adds a Maven Enforcer rule to the generated build that bans log4j: if it ever
enters the dependency tree, the build fails loudly rather than shipping quietly. Because the rule
lives in the pom.xml you own, your team can confirm it is present and enforced.
pom.xml, read the maven-enforcer-plugin configuration,
and try adding a log4j dependency — the build should refuse it.
When a CVE lands
Two kinds of dependency, two answers. Libraries in the generated project
(Selenium, REST Assured, Cucumber, Allure, and the optional WebSocket / Kafka / gRPC / Pact
clients) are ordinary versions in a pom.xml you own: bump them the day a fix ships,
with no wait on us and no tool update required. Libraries bundled in the app itself
(axe-core for the accessibility check, the Edge WebDriver runtime) are pinned per release; a
disclosed vulnerability in one of them gets a point release that bumps the pin, announced through
the in-app update check and the download page. We do not patch silently — every release lists
what changed.
Verifying our claims
Everything above is checkable without taking our word for it: the generated project is ordinary Java you can read, the dependency list is a file you own, and the application's network behaviour can be observed directly. If a claim on this page cannot be verified, we would rather hear about it.
Reporting a vulnerability
Email [email protected]. It is a monitored mailbox, not a ticket queue. We acknowledge every report within 3 business days, tell you what we found, and credit you in the release notes if you want it. Please include steps to reproduce and the app version from the About tab. If you need to send something sensitive, say so in a first message and we will arrange a channel before you send details.
Certifications
L3git Development holds no security certifications — not SOC 2, not FedRAMP, not HIPAA, and nothing else. We are not going to imply otherwise, and you should be wary of vendors who do.
Where a compliance programme requires evidence, the architecture is the argument: the product does not receive your data, so a large part of the questionnaire is answered by what it never does. We also make no formal support commitment for STIG-hardened or FIPS-mode hosts — see regulated & air-gapped for what that does and doesn't mean.