Plain-language privacy information

What we collect and what we deliberately do not

This notice covers both the public research study and the signed-in Saath product preview. The study is designed to minimise personal data, while the product app stores only what is needed to provide a private account and reflection history.

Product account and sign-in

Clerk handles Google sign-in and account sessions for the product app. Saath receives the resulting Clerk user identifier but never receives your Google password. Clerk may process your Google account details as part of the sign-in flow.

Product setup and check-ins

After sign-in, we store your chosen name, broad age range, optional gender, conversation style, support goals, optional mood, and the check-ins you choose to save. These records live in a separate private Neon schema and are scoped to your verified Clerk user ID. The product app does not write this content into the research study.

AI-supported conversations

If you use “Talk with Saath,” your chosen name, broad age range, optional gender, selected mood, support preferences, a short conversation summary, and recent conversation turns are sent to OpenAI to generate and moderate a response. Saved check-ins are not automatically sent. Conversations and summaries are saved privately to your account so you can return to or delete them. OpenAI states that API data is not used to train its models by default, but API content may be retained for up to 30 days in abuse-monitoring logs unless stricter data controls apply. Do not share details you do not want processed by this service. Saath is an AI reflection companion, not a therapist, doctor, human counsellor, or emergency service.

Support usage records

To enforce monthly support limits and understand provider usage, we keep operational records linked to your Clerk user ID. They can include request and conversation IDs, model, outcome category, credits reserved or used, provider token counts, latency, context message and character totals, output length, an urgent-flow flag, provider response ID, and timestamps. These records never include prompt text, response text, journal text, mood content, or message content. They expire after 13 months, or are removed sooner when you delete your Saath data.

Unfinished drafts

We keep a same-tab draft in session storage and a 24-hour recovery draft in local storage. The recovery draft contains study answers and progress, but never optional name, contact value, or availability. If you return after reaching the contact step, you must enter those details again. Expired drafts are ignored and removed when the study next opens.

Study answers

On submission, we store age band, optional gender, city and state, broad work/study and living context, communication patterns, product reactions, and pricing choices. We do not ask for exact birth date, street address, employer, college, income, medical history, or private conversation details.

Optional contact information

If you opt in to a follow-up, the contact value and name are encrypted and stored separately from the analysis view. Researchers analysing response patterns do not need access to it.

Security and service providers

The website is hosted on Vercel. Data is stored in a Neon Postgres project selected in Singapore, the closest currently available Neon region to India. OpenAI processes support-conversation requests. We use same-origin checks, moderation, request limits, encryption, and deletion tokens to protect the service. We do not use ad pixels or session replay.

Minimal technical events

After consent, we may record that a random browser session reached a study step, encountered a validation error, or submitted successfully. These events never include answer values or contact details and expire after 30 days.

Website and app analytics

Basic Google Analytics starts automatically when it is configured for this site. It can receive the selected website or app page visited, referrer, approximate location, and basic browser or device information. We do not send support messages, profile details, check-in text, survey answers, contact details, deletion activity, under-18 exits, or completion status, and advertising storage, Google Signals, and personalisation stay disabled. Anyone can turn analytics off using “Analytics choices” in the website footer or app header; the choice is remembered in this browser and turning analytics off also removes this site's Google Analytics cookies.

Advertisements and sponsors

Saath may show a Google AdSense display advertisement only on its public Guides page. Google may process device, browser, approximate location, consent, and advertising interaction information according to your consent choices and Google's policies. Advertising code is not loaded in Saath's private Home, Talk, Reflections, Profile, onboarding, study, authentication, deletion, privacy, or urgent-help experiences. We may keep a verified Clerk user identifier in an internal ad-free allowlist. That identifier, administrative reason, and audit details are not shared with Google and remain separate from profile, check-in, conversation, and study data.

Retention

Each study response receives the configured study expiry date. Expired responses, related consent records, and contacts are deleted automatically. Content-free support usage records expire after 13 months. Backup copies may persist only for the infrastructure provider's documented backup-retention period.

Deletion

Use your response code and secret deletion token on the deletion page. The token is shown only after submission and is not stored in readable form on our server. In the product app, “Delete my Saath data” removes the profile, check-ins, support conversations, usage records, and support-limit overrides. Clerk account identity can be managed separately from the signed-in account menu. An administrative ad-free exemption is independent of all these records and remains so the account continues to receive no ads; contact us to remove that identifier too.

Questions or access requests

Email hi@siddhantkhare.com. Do not send your private story or deletion token by email.