Home
Privacy
Privacy

Privacy and data handling

Usalama Voice is designed around sensitive reporting, response coordination, and protected information. This page summarizes the privacy baseline and connects into the wider trust center for data handling, role visibility, security posture, and live-versus-demo status.

Protection first

Sensitive data is treated with higher care because the platform deals with safety, harm, and survivor support.

Controlled access

Operational data should only be visible to the right people, in the right context, for the right reason.

User rights

People should understand what is collected, why it is used, and what control they have over it.

High level privacy policy

Information we collect

  • Account details such as name, email, phone number, and profile preferences
  • Gender and age information, plus sexual orientation where you choose to provide it
  • Reports, files, and other information you choose to submit
  • Location information when you actively grant permission
  • Operational and product usage data needed to keep the platform working

How the information is used

  • To provide platform access and core safety features
  • To connect people with relevant support services and response pathways
  • To maintain system integrity, prevent misuse, and improve product quality
  • To understand broad demographic patterns through anonymized analytics without exposing individual identity
  • To prepare anonymized aggregate reporting where public transparency is appropriate

Your control and rights

  • Request access to your personal information
  • Request correction where information is inaccurate
  • Request deletion where retention is not legally or operationally required
  • Manage preferences and opt out of non essential communications

Security approach

The platform is built around protected access, safer storage patterns, and restricted operational visibility.

Public data boundary

Public analytics and transparency views should use anonymized, aggregated information rather than operational case detail.

Analytics data

Gender, age, and optional orientation data may be collected to improve aggregate analytics and platform understanding. That demographic use should remain anonymized rather than tied to public identity.

Trust center

For the wider picture beyond privacy, use the trust center to review role visibility, live-versus-demo status, and the current security overview.

Policy pages

The detailed privacy and retention policy plus the consent and visibility policy now live inside the trust center.

Contact

For privacy related concerns, contact privacy@usalama.voice.

Last updated

January 2025

Understand the product before you use it

If you want the broader picture of how reporting, learning, and coordination work together, start with the product walkthrough.