Sohbat
Privacy Policy
Last updated 16 September 2026
This is a draft MVP policy for Google OAuth Testing. It describes how Sohbat currently works. It is not legal advice and is not a substitute for counsel.
Who we are
Sohbat is an AI rehearsal product for high-stakes conversations. You practice sales, founder, and executive meetings against AI stakeholders in the browser.
Questions, access requests, or deletion requests: elamonoov@gmail.com.
What we collect
Depending on how you use Sohbat, we may process:
- Account data if you sign in (email, Google account identifiers, and authentication records).
- Rehearsal data: briefs, objectives, uploaded decks, personas, transcripts, scores, and debriefs.
- Voice audio when you use spoken turns, which is transcribed before the meeting continues.
- Session cookies used to keep you signed in or to hold a guest rehearsal.
Where rehearsal and auth data are stored
Signed-in rehearsals and authentication data are stored in Supabase (hosted Postgres and Auth). Guest rehearsals may live in encrypted browser cookies and, when configured, a short-lived cache or Redis store.
OpenAI processing
Sohbat sends rehearsal text (and, for voice, audio) to OpenAI so stakeholders can reply, speech can be transcribed, spoken replies can be synthesized, and debriefs can be scored. Do not put secrets in a brief that you would not send to those processors.
Cookies and sessions
We use cookies and similar session storage to keep a signed-in session (Supabase Auth cookies) and, for guests, to persist a rehearsal in httpOnly cookies until it expires. These are needed for the product to work; they are not advertising cookies.
How to request deletion
Email elamonoov@gmail.com from the address on your account and ask us to delete your Sohbat account and stored rehearsals. We will remove what we control in Supabase. Copies already sent to processors such as OpenAI follow those providers' retention rules.
Related
Use of Sohbat is also described in the Terms of Use.