PLXMat Privacy Notice

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.

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, and reporting service health.

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 anything to us.

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.

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.

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.

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 exactly as the browser one: your work stays on your machine, and only sign-in, license and update checks reach the network.

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 analytics script, no third-party tag and no embedded media on this site.

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.

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.

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].