Legal

PLXMat Privacy Notice

Last updated: 4 October 2026 · Version 2026-10-04

1. Where the Work Happens

PLXMat builds your materials on your own device, not on hetGE's servers. The description you type, the parameters read from it, the soil profile you assemble and the command log generated from them are all produced locally, in the browser or in the desktop application.

We say this plainly because it determines everything below: your engineering inputs do not leave your device when you use the application, and we could not produce them if asked (the usage statistics in §6 record only which kind of material, and for soil which model, you created, never its parameters).

2. What We Store

Nothing you create. There is no project database and no file storage behind this application; the only server endpoints it has are for signing in, checking your license, serving desktop downloads and updates, reporting service health, and, in the browser only, when the "Share usage statistics" switch on your hetGE account is on (it is on by default, so you are included unless you turn it off), relaying usage statistics to hetGE Account through PLXMat's own server, which forwards each batch with your access token and stores none of it.

Your work persists in two places, both of them yours. The materials, soil profile and unit system you have open are kept in your browser's local storage on this device, so closing the tab does not lose them. Choosing "Save" writes a JSON file to your computer, and "Load" reads a file you select; neither operation sends the file or anything in it to us. When usage statistics are on, saving and loading do each report that a project was saved or opened, and nothing about what the file contains, its name, or its path.

Clearing your browser's site data removes the stored materials. They are not backed up anywhere, so keep saved files for anything you need to retain.

3. Signing In

Access is through your hetGE account at account.hetge.com, using the standard OAuth 2.0 authorisation-code flow with PKCE. hetGE's account service handles your credentials; this application never sees your password.

In the browser, a successful sign-in sets the following cookies on this domain:

  • access_token and refresh_token, both httpOnly, which keep you signed in and let the session be renewed without asking you again;
  • user, readable by the page, which carries your display name and email so the interface can show who is signed in.

The desktop application cannot use browser cookies. It opens your system browser to sign in, receives the result back through its own plxmat:// link, and keeps the resulting tokens in the application's local storage on your machine instead.

While the application is open it re-checks the session against the account service about every 15 seconds, so that access revoked centrally, or a sign-in from another device, takes effect promptly rather than at the next reload. Signing out clears these tokens and the cached license status.

4. License Status

The application asks the account service whether your license is current, and caches the answer in local storage for up to an hour so that it is not re-asked on every screen. The cached value records whether access is valid and when it expires. It contains no payment details; purchases are handled entirely by the hetGE Marketplace and your account, not by this application.

5. The Desktop Application

The desktop build periodically asks plxmat.hetge.com whether a newer version exists, and downloads it if you choose to update. That request tells the server the platform and version you are running, which is what it needs in order to answer; it carries nothing about your materials or your project.

Otherwise the desktop application behaves as the browser one does, except that it sends no usage statistics at all: your work stays on your machine, and only sign-in, license and update checks reach the network. This may change in a future notice, but nothing about it changes today.

6. What Is Kept on Your Device

Besides your materials, the application stores these small values:

  • theme: whether you chose the light or dark appearance;
  • unit-system: whether you are working in metric or US customary units;
  • plxmat-license-status: the cached license answer described above;
  • the install-prompt flags, which record that you installed or dismissed the app so you are not asked repeatedly.

None of these are advertising or tracking identifiers, and none are sent to us. There is no third-party tag and no embedded media on this site.

When the "Share usage statistics" switch on your hetGE account is on (it is on by default, so you are included unless you turn it off, and collection is on), PLXMat reports to hetGE Account, from your browser only, that a material was created, with its type, and for a soil material its constitutive model, and whether it came from the natural-language command palette or a material's own form; that a material was duplicated; that a material's PLAXIS command log was copied to the clipboard; and that a project was saved or opened; plus how long the application was actively used, meaning visible, focused, and in use, while signed in. No content of your work is ever sent this way: no names, dimensions, coordinates, or any other free text of your materials leaves your browser. PLXMat's own server forwards each batch to hetGE Account with your access token; PLXMat's server and hetGE Account are the only recipients, and PLXMat's server stores none of it. Your IP address and browser user agent are passed along only so hetGE Account can form that day's per-browser record in its statistics service (Umami) and work out your country; neither is kept for these statistics (the ordinary logs described in "Hosting and Logs" are unaffected). See the hetGE Account Privacy Policy for how it handles what it receives.

Usage statistics set no cookies. Your browser's Global Privacy Control or Do Not Track signal stops them, and so does turning "Share usage statistics" off on your hetGE account.

7. Hosting and Logs

The application is served from hetGE's infrastructure. As with any web service, the hosting layer processes the technical information needed to deliver a page: your IP address, the request and the browser you used. This is ordinary operational data, used to run and secure the service, and it is not combined with your engineering work, which as described above never reaches us (aside from the usage statistics in §6, which record only which kind of material, and for soil which model, you created, never its parameters).

8. Your Rights

Your account details are held by hetGE as the account provider, and the rights you have over them, access, correction, export and deletion, are exercised there. Because this application stores no project data, a deletion request has nothing to remove on its side beyond the account itself; the work on your own device is removed by clearing your browser's site data, uninstalling the desktop application, or deleting the files you saved.

9. Changes and Contact

If these practices change materially, the version and date shown at the top of this page change with them. Questions about this notice can be sent to hetGE at [email protected].