Trust, privacy, and governance in one place
Privacy, security, visibility, and public-data boundaries for Usalama Voice.
Privacy and Retention Policy
Retention periods, deletion rules, lawful basis, minor handling, breach response, and public anonymization.
Consent and Visibility Policy
Who can see what at each case stage, when consent is required, and how restrictions should work.
Data Handling
What information is collected, why it is used, and how long it should remain in the system.
Role Visibility
Who should see what, when multi-role access is allowed, and where operational boundaries sit.
Security Overview
Current security posture, access-control principles, and operational safeguards expected in the platform.
Live and Demo Status
Which parts of the product are operational today and how public data publication is governed.
Data
Protected information needs clearer rules than ordinary apps
Usalama Voice handles sensitive safety reports, referral coordination, survivor profile details, and public-safe analytics. Those layers cannot be governed with one generic policy.
Visibility
Operational access should be role-based and purpose-bound
A person or organization should only see the minimum operational detail needed to move a case forward, review closure readiness, or maintain lawful governance.
Transparency
Public trust depends on governed live publication
Mwananchi, Uwazi, public exports, and directory surfaces should state clearly how live data is rolled up, filtered, and published without exposing survivors.
Core trust areas
Privacy, security, access, and public-data boundaries.
- Data categories the platform handles across account creation, reporting, response coordination, and public-safe analytics.
- Role-visibility expectations across survivor, NGO, police, counselor, legal, medical, shelter, and admin workflows.
- Security posture at the product level, including access control, auditability, and public-data separation principles.
- A plain explanation of what is operational today and how live public publication is governed.
Data handling
Retention, lawful purpose, demographic analytics boundaries, and deletion expectations.
Role visibility
Who should see case data, when sharing expands, and when admin review becomes necessary.
Security posture
Protected access, environment separation, and audit-oriented operational discipline.
Publication boundaries
Clear separation between live operational records and the governed public rollups published from them.