Patient data deserves more than a password
SonoTez is built in layers, so each protection still holds if another one fails.
| Encryption | TLS for every connection; uploaded images and PDFs encrypted at rest with AES-256-GCM. |
|---|---|
| Sign-in | Individual accounts, strong password hashing, optional two-factor authentication, account lockout and short idle sessions. |
| Permissions | Role-based access for every action, scoped to the user's centre and branches. |
| Abuse protection | Rate limiting at the proxy and application, bot checks on sign-in and sign-up, and automatic blocking of vulnerability scanners. |
| Browser protection | Strict Content-Security-Policy, framing blocked, cross-site requests refused. |
| Audit | Every registration, report, amendment, payment and setting change is logged with identifiers only. |
| Report integrity | Finalized reports are frozen with a content hash; QR verification shows whether a report is genuine and current. |
| Patient sharing | Patient links are protected by a PIN and expire; verification pages never show clinical content. |
Running SonoTez on your own server? The deployment guide covers TLS, the reverse proxy, firewall rules and backups. Ask us for it.
Write your next report in SonoTez
Set up your centre in minutes. Your first 15 days are free, and every template can be adapted to your own wording.