Trust Center
Security and privacy are not features. They are foundations.
Zanexa platforms handle sensitive healthcare, legal and enterprise data. This page explains what we do to protect it — in plain terms, without marketing language.
PDPC Registered Data Controller
Personal Data Protection Commission, United Republic of Tanzania
Security Principles
What we do to protect your data.
These are the operating principles that govern how Zanexa builds and operates its platforms. They apply across all products and all customers.
Compliance
PDPC Data Controller
Zanexa Solutions is registered as a Data Controller under the Personal Data Protection Commission of Tanzania.
Data Localization
Customer data is stored and processed within compliant infrastructure aligned with Tanzanian data protection requirements.
Access & Identity
Role-Based Access Control
Every user operates within defined permission boundaries. Clinical, administrative and management roles are separated.
Multi-Factor Authentication
MFA is available and encouraged for all privileged accounts across Zanexa platforms.
Tenant Isolation
Each facility operates in an isolated data environment. No cross-tenant data access is permitted.
Data Protection
Data Ownership
All facility data belongs to the facility. Zanexa does not share, sell or use customer data for any purpose beyond platform operation.
Encryption
Data is encrypted in transit and at rest using industry-standard protocols.
Backup & Recovery
Automated backups with defined recovery objectives. Tested restoration procedures.
Operations
Audit Logging
All significant user actions generate immutable audit records — who did what, when, and from where.
Incident Management
Defined incident response procedures with customer notification commitments.
Secure Development
Security is incorporated into the development process. Code review, dependency auditing and vulnerability management.
Integrations
Integration Security
All third-party integrations use authenticated, encrypted channels. Credentials are never embedded in code.
Responsible AI
Any intelligence or automation features are labelled clearly, do not replace clinical judgment and operate with full auditability.
Infrastructure details are not published here
We do not publish specific cloud provider names, server configurations, IP ranges or internal architecture details in public documentation. If you require this information for a security review or enterprise procurement, contact us directly.
Security Contact
Security questions or vulnerability reports
If you have a security question, a responsible disclosure to make, or require security documentation for procurement, contact our team directly.
[email protected]