Privacy first. Share what matters, not what identifies you.

SAAKHA is designed to be useful without asking for more personal information than necessary. Begin with the situation; you do not need to lay out your identity or your whole life.

Starting does not require an account. Saving will: when Save is offered, SAAKHA will use a SAAKHA ID and PIN so you can return to what you kept.

Your choices stay separate

A conversation is not automatically a memory. Save and Memory are separate choices: one keeps a conversation; the other keeps selected context for later use. Our principle is that a “yes”, “haan”, “maybe”, a click or accepting a suggestion must not silently become a permanent personal fact.

An unsaved conversation may disappear after refresh or if browser data is cleared, so do not rely on it as a permanent record.

Anything you choose to save should also have a way to delete it. Save will not be treated as complete without deletion controls.

How SAAKHA protects your space

  • Talk first

    No mandatory personal profile before you begin.

  • Less identifying data

    SAAKHA is designed not to need identifying details to help with most situations.

  • You choose what is kept

    Saving and Memory are separate choices.

  • Protection grows with you

    The more you choose to keep, the stronger the protection around it.

These are guiding principles; private Save, Memory and their added protections are being introduced progressively, not claimed as fully live.

Privacy is protected in layers

Our privacy architecture is designed around independent layers: secure web connections (HTTPS/TLS), server-side access controls, separate account, saved-conversation and memory data, and encrypted private storage. These describe the architecture direction, not a universal live guarantee.

Security without extra setup at the start

You should be able to begin without complex setup. Stronger authentication, recovery and private-memory controls can be introduced as private account features are released.

On a shared device, clear the screen when you finish and avoid leaving identifying details in the conversation. Clearing the screen does not confirm deletion from service systems. Stronger Lock/Exit controls will come with private account features.

Minimise what leaves SAAKHA

SAAKHA does not need your identity to help you think. Our design goal is data minimisation: send only relevant context, filter unnecessary identifiers locally where practical, and limit memory access to the context needed. SAAKHA still processes messages through its systems and AI services to reply.

If you choose to use the microphone, its audio is sent through SAAKHA to Google only for transcription. SAAKHA does not persist the raw audio. If transcription fails, only that current clip may remain temporarily in this page's memory when “Try transcription again” is available. A successful transcription, “Record again”, dismissing the error, or leaving the voice flow discards that clip. The resulting text stays editable and is not sent as a message until you choose Send.

What you should not share

Share the situation, not the details that identify you or someone else.

  • Phone number, email, full address or exact date of birth.
  • Aadhaar, PAN or other government identity numbers.
  • Passwords, PINs, OTPs, security answers or bank/card/account details.
  • Another person’s identifying information unless it is genuinely necessary.

AI and safety

SAAKHA uses AI and can make mistakes. Please verify important information.

Privacy is not the same as safety. SAAKHA is not a doctor, therapist or emergency service. Read What SAAKHA can and cannot do for safety and professional-help limits.

We describe a privacy or security protection as live only after it is actually enforced and tested.

This is a plain-language product privacy explanation, not a statutory Privacy Policy. Formal legal/privacy policy claims require separate legal and compliance review.