Eight layers of protection
Every component of Tracka is designed with security as a first-class requirement, not an afterthought. From the database to the API, patient data is protected at every step.
End-to-End Encryption
All data in transit is encrypted using TLS 1.3. Data at rest is encrypted with AES-256. Database connections are routed through PGBouncer with SSL enforcement, ensuring patient data is never exposed in plaintext.
Role-Based Access Control
Four distinct roles — super admin, product admin, field agent, and external monitor — each with precisely scoped permissions. Product admins are region-scoped, and external monitors always see anonymized data.
Two-Factor Authentication
All user accounts support two-factor authentication via authenticator apps. 2FA is mandatory for super admin and product admin roles accessing sensitive patient data or administrative functions.
Immutable Audit Trails
Every data modification is recorded in an append-only audit log that can never be altered or deleted. Track who changed what, when, from which device, and what the previous value was.
Data Anonymization
External monitors access fully anonymized patient data by default. The Data API serves only aggregated, de-identified data. No individual patient records are ever exposed through external interfaces.
Consent Management
Built-in consent workflows track patient consent for data collection, storage, and sharing. Consent records include scope, expiration dates, and withdrawal mechanisms compliant with local data protection regulations.
Strong Password Policy
All accounts require passwords of 12 or more characters with a mix of uppercase, lowercase, numbers, and special characters. Passwords are hashed using bcrypt with adaptive cost factors.
Session Management
Sessions are managed through Redis with configurable timeouts. Inactive sessions are automatically terminated. Concurrent session limits prevent unauthorized shared access to accounts.
Meeting the highest standards
Tracka is designed to comply with healthcare data regulations across Africa and aligns with international security standards.
Nigeria Data Protection Regulation (NDPR)
Tracka complies with the Nigeria Data Protection Regulation, including lawful data processing, data subject rights, breach notification requirements, and cross-border data transfer safeguards.
International Digital Health Guidelines
The platform follows international guidelines for digital health interventions, including data quality standards, interoperability requirements, and ethical considerations for health data systems.
HIPAA-Aligned Controls
While operating primarily in Africa, Tracka implements security controls aligned with HIPAA standards including access controls, audit logging, encryption, and administrative safeguards.
OWASP Security Standards
Our development practices follow OWASP guidelines for secure application development, including protection against the OWASP Top 10 vulnerabilities, regular security testing, and secure coding practices.
Secure by architecture
Database Security
PostgreSQL 16 with dedicated database users for each access pattern: tracka_app for application DML operations, tracka_migration for schema changes, and tracka_readonly for reporting queries. All connections routed through PGBouncer with SSL enforcement on port 6432.
Caching and Session Isolation
Redis instances are segregated by function: DB 0 for sessions, DB 1 for rate limiting, DB 2 for Socket.IO real-time events, DB 3 for BullMQ job queues, and DB 4 for application cache. This isolation prevents cross-contamination and enables independent scaling of each subsystem.
API Authentication
Internal routes between the main app and API use Bearer token authentication with short-lived JWTs. The external Data API uses X-API-Key header authentication with rate limiting enforced per key. All API traffic is encrypted over TLS 1.3.