What we promise, and what we don’t yet.
For IT, security and procurement teams evaluating TotalHeal business products. How we protect the home app and what it collects is on the security page.
Home users: see Trust & security.
Data residency
- The TotalHeal business SaaS runs in an India region. Organisation, device and security data is stored there and processed under India’s Digital Personal Data Protection Act, 2023.
- ZeroGate ZTNA uses a TotalHeal relay in India; our access nodes never contact third-party infrastructure.
- The Government profile sets the data-residency flag to India, keeps data for at least 180 days and switches on the CERT-In and DPDP reporting clocks.
- Retention for CERT-In: security events are kept for at least 180 days by default. For organisations in India and under the Government profile this is a floor; lowering it needs an audited administrator override with a reason, and Government cannot lower it. Remote-access and privileged-session recordings follow the same 180-day minimum.
- Update files are served worldwide from a content delivery network; they contain no personal data.
- On-premises and air-gapped deployment of the control plane is available on request.
How the platform protects your organisation.
Tamper-evident audit trail
Each organisation’s actions — policy changes, approvals, remote sessions, privileged access, WAF tuning — are written to a hash-chained audit log that can be verified and exported.
People decide, AI never does
Destructive device actions need a typed confirmation and a second human approver. AI agents and machine identities can never request, approve, reveal, rotate or open a privileged session.
Four-eyes and distinct approvers
Requesters can never approve their own remote session, just-in-time access, risk exception or privileged check-out. The Government profile adds four-eyes on policy changes.
Signed commands and policies
Device policies, edge and DNS policy bundles are signed and checked before they are applied; edge and DNS keep the last known good policy and never fail open.
Encryption where secrets live
Privileged credentials are vaulted with AES-256-GCM under a per-organisation key; recovery keys are sealed per organisation; remote file transfers are encrypted at rest and deleted after delivery.
Signed software, published keys
Desktop updates are verified in the app with pinned keys. Linux packages and the apt/yum repository are signed with the TotalHeal package signing key, fingerprint 6DA7 F53D 8AA6 7427 B4B8 B604 3DA4 475E 15A8 E5D2 (see Download). The on-premises kit is verified by its installer against a pinned release key.
Recordings encrypted at rest
RemoteLink session recordings and input logs are encrypted with a key per recording, wrapped by a per-organisation key that can be rotated; playback decrypts on the fly.
Tenant isolation, tested
Every organisation is separate. Isolation is covered by automated tests — for example on every WebShield WAF route and in the PrivilegeVault PAM vault, where a copied secret does not decrypt for another organisation.
Availability, honestly
Our SaaS runs in one India region on a single production server today, without high availability. Throughput and fleet-scale figures have not been measured for most products, so we size each deployment with you instead of quoting numbers. Each datasheet lists the product’s limits.
Certifications
TotalHeal holds no third-party security certification today, and we do not show certification marks or claim compliance with any framework. When an audit or certification is actually under way, it will be listed here with its status.
For tenders, each product’s compliance matrix marks every requirement as comply, partial or no, with an evidence reference. It is part of the procurement dossier.
Sign-in
Console users sign in with a Sttiz account over OpenID Connect. Role-based permissions separate who can read, act, approve and administer.
Report a vulnerability
Found a security issue in TotalHeal, this website or our APIs? Email security@totalhealsecurity.com. We acknowledge within 3 working days. Our security.txt has the details.