Security
What we hold, and what we do not.
The short version: your simulation work never leaves your machine, and the worst thing we could lose about you is your email address and which licence you bought.
| Where your simulations live | On your machine. Cases, geometry, meshes and results never leave it. The application talks to us only to check a licence, and that exchange contains a licence key and a hashed device fingerprint — nothing about your work. |
|---|---|
| What we store about you | Your email and name, your organisation if you have one, your licence and subscription state, and a hashed fingerprint per activated device. Card details we never see — Paddle handles payment as merchant of record. |
| Device fingerprints | Hashed on your machine before they are sent. We never hold raw volume serials, MAC addresses or CPU IDs, and fingerprints are shown as a short prefix in every screen, never in full. |
| Passwords | Argon2id. A minimum of 12 characters, checked against a breached-password list. No composition rules and no forced expiry — both make passwords worse. |
| Sessions | Stored server-side and revocable immediately. "Sign me out everywhere" takes effect at once rather than when a token happens to expire. |
| Two-factor authentication | Authenticator apps and hardware security keys (WebAuthn/FIDO2), several per account. Optional for customers and mandatory for every member of SHD Systems staff with administrative access. No exceptions and no grace period. |
| Staff access to your account | Support can look at your licences and devices. Impersonating your account requires a stated reason and re-authentication, is time-boxed, is read-only, and is recorded where you can see it happened. |
| Installers | Published with a SHA-256 checksum on the download page, so you can verify the file you received is the file we built. The licence file carries an Ed25519 signature the application checks independently. |
| Transport | TLS everywhere, certificates from Let’s Encrypt. The desktop client does not pin certificates — a renewal that bricked activation for every install would be a worse outcome than the attack pinning prevents. Integrity comes from the licence file’s Ed25519 signature, which does not depend on TLS. |
| Backups | Nightly, encrypted, off the application host, with restores rehearsed rather than assumed. |
| Code signing | Installers are Authenticode-signed by SHD SYSTEMS LTD via Azure Trusted Signing, and the signature is timestamped so it outlives the certificate. SmartScreen reputation is separate and accrues with downloads, so a warning can still appear on a new release — the SHA-256 published beside each download is the check that does not depend on reputation. |
What we have not done
Listed because you would otherwise have to ask, and because a vendor this size claiming a full compliance stack has usually bought a badge.
| SOC 2 / ISO 27001 | Neither. Enterprise procurement will eventually ask; there are not yet enterprise customers to justify the cost. |
|---|---|
| Penetration test | Not done. Planned trigger: the first Enterprise customer who asks, or £50k ARR. |
| Bug bounty | No paid programme. A published contact and a commitment to respond is the proportionate version at this size. |
| SSO / SAML | Not built. It is the first thing on the list when an Enterprise prospect names it. |
Reporting something
security@shd-sim.com
If you have found a vulnerability, email security@shd-sim.com. We will acknowledge within two working days and tell you what we intend to do about it.
We will not threaten you, and we will credit you if you want to be credited. Please give us a reasonable window before publishing, and please do not test against other people’s accounts or data.