How Visual Java (the desktop app and the Online Editor) and jter handle account data, published projects, team/company publishing, and payments — and which cookies this site uses.
This page is built from the rules you use in practice. One placeholder still needs a real value before publishing: the legal entity/registered address of the data controller (jter). The contact email for privacy requests is already in place — see Contact.
When you create an account on visualjava.jter.eu (needed for the Online Editor and community features), we automatically store your account data — your username, email address, password (hashed, never stored in plain text), and any profile details you add, such as your bio and avatar — in a dedicated database, separate from the rest of the site.
Visual Java staff do not access this data in the normal course of operating the service. Access happens only when necessary — in practice, when investigating a serious violation of the rules described on this page.
Account data is kept for as long as the account exists, and normally for as long as needed to resolve any open issue involving it. If an account is deleted following a rule violation, its associated data is deleted with it, except where we're required or allowed to keep specific records (for example, payment logs — see Billing information).
There are two situations that lead Visual Java to access or act on your account data:
| Situation | What happens |
|---|---|
| The account has published one or more projects that break the community's content rules (see below). | We review the account and the reported project(s); depending on severity this can lead to a project or account suspension or deletion, as described in the next section. |
| The account is identified as a bot. | The account is deleted and enters a 7-day suspension window. If a real person doesn't come forward to claim the account within those 7 days, it is permanently deleted once the window expires. |
Outside of these cases, your account data is not accessed or reviewed by anyone at Visual Java.
The Online Editor lets you build limited 2D/3D projects using visual block-based programming and the JVL system. You can publish a finished project to the community in different ways:
Separately, you decide whether to also publish the project's source code — if you do, other users can create their own copy of it.
When you publish a project to the community (public or link-only), it must follow these rules:
Breaking any of these rules can lead to one or more of the following, depending on severity:
| Consequence | What it means |
|---|---|
| Project suspended | No longer visible to the public; can be restored once resolved. |
| Project deleted | You have 7 days to reclaim it; if you don't, it's permanently deleted once that period ends. |
| Account suspended | You can't access your account for a set period; your data and projects are preserved. |
| Account deleted (extreme cases) | The account enters a 7-day ban, during which you can download a copy of your projects. After 7 days, everything is permanently deleted. |
Publishing an exported, standalone application is deliberately restricted. As an individual user, you cannot export or publish a project as a real application under any circumstances.
Starting from Visual Java 1.9, companies and groups can create a paid Team to unlock this. Indicative pricing (subject to change):
A Team is fully customizable — roles, staff, projects, and data can all be configured — and gets access to official plugins that aren't otherwise available, plus the ability to export projects as real .exe applications or jpackage bundles.
Publishing a Team's app runs for a 7-day window, during which Visual Java is notified and reviews the project if it contains: plain-Java code (functions outside of JVL), public APIs (e.g. multiplayer), local file read/write (saving or reading files on the user's PC), or command execution (running terminal commands on the user's machine). This review checks for risks to the people who will use or interact with the app. Visual Java can also require the development team to publish clear, easily accessible disclosure documents (privacy notice / disclaimer) for the app.
A published Team application must not:
If one of these four rules is broken, the project is suspended and its publication is cancelled until the development team resolves the issue.
If a program is explicitly built as a tool for malware, viruses, doxxing, attacks (e.g. DDoS), cheat clients, or similar: the project is suspended and deleted, and the development team is suspended and sanctioned — this can mean losing access to specific extensions, having to pay a fee, and facing stricter publishing terms — or the team itself can be suspended and removed. In extreme cases, all data belonging to the team and everyone who was part of or interacted with the project is preserved, and the matter is reported to the relevant authorities (e.g. postal/cybercrime police).
Outside of these situations, Visual Java does not normally exercise a right to access user/company data — that right is reserved for the extreme cases described above.
Visual Java is run by jter, which operates primarily in Europe. As a result, all transactions are processed in euros (EUR). Where a payment processor applies transaction fees, jter factors that percentage into the price you're charged.
Every transaction is recorded in our database logs. If you have a billing issue, these logs can be reviewed together with a staff member within 7 days of the transaction.
Some quick facts about the Windows installer, gathered in one place so you can decide with confidence before you run it.
Visualvisualjava.jter.eu. Don't download it from anywhere else.The installer isn't code-signed by a major Certificate Authority yet. Windows SmartScreen and some antivirus engines flag unsigned or low-reputation installers by default, regardless of what the program actually does — this is a reputation heuristic, not a detection of malicious behaviour. Code signing is on our roadmap and will be added as soon as it's practical for a small, independent publisher.
Verify your download with SHA-256. After downloading, you can compute the installer's hash yourself (e.g. with certutil -hashfile VisualJava-Setup.exe SHA256 on Windows) and compare it to the value published here for the current version:
VisualJava-Setup.exe
SHA-256:
<published with each release — see the Changelog>If the hash you compute doesn't match the one published for that version, don't run the file, and get in touch using the Contact details below.
This site uses a minimal set of cookies and browser storage, all needed to make the site and Online Editor work — no advertising or tracking cookies, and no analytics, are currently in use.
| Name | Type | Purpose | Duration |
|---|---|---|---|
PHPSESSID | Strictly necessary cookie | Keeps you logged in and identifies your session to the API. Set as HttpOnly and Secure. | Up to 30 days, or until you log out |
vj-lang | Local storage (not a cookie) | Remembers whether you last chose English or Italian. | Until cleared |
| Project drafts | Local storage (not a cookie) | Temporarily keeps in-progress Online Editor work in your browser. | Until cleared or overwritten |
This site loads typefaces from Google Fonts (fonts.googleapis.com). Loading them causes your browser to contact Google's servers directly, which involves sharing your IP address with Google under Google's own privacy policy. No cookie is set by us for this.
Because none of the above are used for tracking or advertising, we don't currently show a cookie-consent banner. If that changes — for example, if analytics are added in the future — this page and the site's consent mechanism will be updated accordingly.
If you're in the EU/EEA (or another region with similar protections), you generally have the right to:
To exercise any of these rights, use the contact details in Contact.
We may update this page as Visual Java's features or rules evolve. Meaningful changes will be reflected here with an updated date; for major changes affecting how your data is handled, we'll try to give notice through the site or Discord ahead of time.
For privacy requests, billing questions, or to report a violation, reach us directly at:
visualjava@jter.euYou can also reach us via Discord for general questions.