Privacy Policy

last updated — 27 august 2026

This describes, plainly and specifically, what happens to your voice and your words when you use yap. It reflects how the current version of yap is actually built, not generic boilerplate — where something isn't built yet (like rate limiting), it says so.

Accounts and sign-in

Talking to yap requires signing in with Google. We never see or store your Google password — Google handles authentication and gives yap back a verified identity token containing your email, name, and profile picture, which we use to create your account. From Google, we store your email, display name, and profile picture (you can replace this with your own uploaded photo at any time from the account menu).

Tied to that account, we also store your credit balance and a full history of transactions (purchases and call debits) and calls (which persona you talked to, when, and for how long) — this is what makes the credit system in the Refund & Cancellation Policy auditable. None of this includes what you actually said during a call; see the next section for that.

Your voice, during a call

When you start talking to a persona, your microphone audio is streamed live, over a direct WebRTC connection, to yap's backend, and from there to two third-party AI providers that generate the conversation:

One provider converts your speech to text and generates the reply text.
Another provider converts that reply text back into spoken audio.

yap's own backend does not record, save, or write your raw audio to disk or a database at any point. Once a chunk of audio has been sent onward for transcription, yap itself doesn't keep a copy of it.

Because your audio and words are processed by these third-party providers, their own privacy policies also apply to that processing.

The words you say (transcribed text)

Your transcribed speech is held in memory only for the duration of that one call, so the conversation can stay coherent turn to turn. When you end the call, close the tab, or your connection drops, that in-memory conversation is discarded. It is not written to a database, and yap does not build a profile of you across sessions — there is no cross-session memory by design.

The one exception: safety logging

yap runs a safety check on every message you send, looking for language associated with self-harm or crisis. If that check is triggered, the message that triggered it is written to yap's server-side operational logs — not a database, not sent anywhere else — solely so the people running yap can review whether the safety system is working correctly. This is the one case where something you say is kept beyond the length of the call. Everything else in this section still applies: your other messages in that same conversation are not treated any differently.

Network-level information

When you sign in, we store your IP address and browser/device information (your user agent string) against your account, refreshed on every sign-in, along with where you came from the first time you signed up (referring page). This is used for account security and understanding how people find yap — not for advertising, and not shared with or sold to anyone. We do not currently apply any rate limiting or abuse controls based on it — that's a known gap for a public deployment, not a hidden one, and it's being worked on.

Cookies and analytics

yap does not set cookies or run any analytics or advertising trackers. It does use your browser's local storage (not a cookie) to keep you signed in between visits — that's a sign-in token only, not a tracking mechanism, and it never leaves your device except to prove to yap's own server that you're signed in. If that changes in a future version, this policy will be updated to say so before it happens.

Children and age

yap is designed to be appropriate for a general, all-ages audience — every persona is built to stay platonic and to redirect away from romantic or sexual content regardless of who's asking. That said, yap has no way to verify anyone's actual age — signing in with Google confirms an email identity, not an age.

Your rights and how to reach us

Your conversations themselves are never retained (see above) — but your account (email, name, profile picture, credit balance, and purchase/call history) is, for as long as you keep using yap. You can email brandit@solidexposure.com from your registered address at any time to request a copy of the account data we hold on you, or to have your account and its data permanently deleted. Deleting your account also forfeits any unused credit balance, since there's no account left to hold it against.

India's Digital Personal Data Protection Act, 2023 requires a named Grievance Officer for services that process personal data of Indian users. That role is held by Taksh, reachable at brandit@solidexposure.com.

Changes to this policy

If how yap handles your data changes in a meaningful way, this page will be updated and the "last updated" date above will change.