Privacy Policy

Last updated: June 5, 2026

SautiSafe is designed for safety situations involving women and children. We collect only the data needed to create accounts, notify trusted contacts, share live location during alerts, support safety check-ins, and store evidence submitted by the user.

Information We Collect

• Account information such as name, email, phone number, password hash, consent status, and verification status.
• Eligibility and responder-verification metadata, such as attestation, phone verification, approved responder status, review source, and review timestamp. SautiSafe should not store raw ID documents or selfie images unless a separate verified identity workflow and retention policy is enabled.
• Emergency contact information chosen by the user, including contact names, phone numbers, relationship labels, and optional Telegram IDs.
• SOS event details such as time, alert type, battery percentage, location coordinates, map links, delivery status, acknowledgement status, and responder actions.
• Opt-in community responder presence, when enabled by an approved responder, used to show anonymous nearby responder bubbles.
• Evidence files uploaded by the user, stored encrypted at rest.
• Operational logs needed for fraud prevention, auditability, safety response, debugging, and delivery reliability.

How We Use Information

We use data to deliver emergency alerts, provide live location links, coordinate trusted-contact acknowledgements, operate the command center, maintain audit trails, and improve reliability. We do not sell personal data.

Nearby community responder data is used only for opt-in safety coordination. Nearby lists are anonymous and do not show names, emails, or phone numbers. Exact victim location is shared with an approved responder only after an active SOS invitation is accepted with safety acknowledgement.

Security

Passwords are stored as bcrypt hashes. Sensitive fields such as phone numbers, emergency contact details, Telegram IDs, wake phrases, and evidence metadata are encrypted at rest where implemented. Transport uses HTTPS on the public service.

Microphone and Voice Trigger

SautiSafe is designed so voice-trigger setup and wake-phrase matching happen on the user's device. The service does not continuously stream or listen to everyday conversations on the server. Audio evidence should be recorded only when the user starts evidence capture or an emergency workflow requires it with device permissions.

Sharing

Emergency details are shared only with the trusted contacts and partner organizations selected or configured by the user, plus service providers needed to deliver SMS, Telegram, hosting, database, and infrastructure services.

User Control

Users can update their profile, contacts, safe locations, wake phrase, partner selections, and may delete their account from the app. For support with data deletion, use the instructions on the Data Deletion page.

Contact

For privacy questions, contact [email protected].