Frequently asked questions

A free, anonymous, ad-free sexual-health education library: long-form guides with cited medical sources, interactive self-check tools, and an AI-assisted conversation helper called Wingman. It works in English, Hindi and Bengali.

Free — there are no paid tiers, no ads and no card required. The catch is usage limits (for example 5 Wingman analyses per day) so one person cannot exhaust the service for everyone. Both facts are stated in our Terms of Service.

Because an account would mean an email address, a profile, and a database row linking you to every question you asked — exactly the data this site exists to avoid holding. You open the page and use it; drafts stay in your own browser.

Adults aged 18 and over. The content is adult sexual-health education, and there is no age-verification gate — see our Terms of Service for what that means for anyone supervising a shared device.

Only what you type in: submitted questions (text, language, a random anonymous handle) and anonymous Wingman metrics (tone verdict, scores, model id, latency) that are purged within 15 minutes. Rate limiting stores a salted hash of your IP, never the raw address. Full detail: our Privacy Policy.

No. There is no form on the site that asks for either, and the safety screen rejects questions containing phone numbers, emails, or "name + city" patterns before anything is stored.

Press Esc twice and the visible page is replaced instantly, localStorage and sessionStorage are wiped, and every draft the site had stored locally is gone. It does not clear the service worker cache — clear site data in your browser for that.

One cookie — NEXT_LOCALE, which stores only your language choice for a year. No ad cookies, no third-party trackers. Page views are counted by Vercel Web Analytics, which the vendor documents as cookieless. Full details: the Cookie Policy.

From your browser to our server, then transiently to Groq (the AI provider) to build the analysis. Only anonymous metrics are stored, and a purge job deletes them within 15 minutes. The conversation text itself is never written to our database or logs.

No. Wingman accepts text only — there is no upload field, no image endpoint, and on-device OCR is not enabled. If OCR ever ships, it will run entirely on your phone and say so on the page.

If the AI provider times out or fails, Wingman falls back to a local rules-based analysis that runs in your browser — no text leaves the device. Guesses are deliberately blunt (4–6 words of tone, two energy scores), and the label keeps it honest so you never mistake it for an AI read.

The AI model sits on a free tier capped at 1,000 requests per day across everyone using the site — 5 per person per day keeps that budget alive for everybody. In local development the limit is lifted entirely so testing is never blocked; production always enforces it.

They are stored for moderation but the public thread view is not live yet — nobody can browse your question today. When it launches, questions publish under the anonymous handle shown after submission, never with anything identifying you. Delete requests: email us the public ID.

The public ID (like Q-7F3K2M) identifies your question so you can ask us to delete it without revealing who you are. An edit key is a one-time secret shown only at submission — we store its hash, so even we cannot recover it if you lose it.

Wait for the window to reset — the page shows what is left (5 Wingman analyses per day, 10 questions per hour). The counter resets on a rolling window, not at midnight. If you are in local development, the limits are off by default.

Yes, as an installed PWA: the shell and guides are cached by a service worker, so the app opens with no connection and Wingman still runs its local heuristic. Anything that needs the server (submitting questions, AI analysis when the provider is reachable) waits until you are back online.

Current versions of Chrome, Edge, Firefox and Safari (desktop and mobile). Older browsers may still read the content but lose the install prompt, offline mode and some transitions.

Email anuragpanda.dev@gmail.com — for security issues, report privately first rather than publishing. Include the page URL, your locale and the browser you used. The Contact page has the full rundown.