Privacy choices

Analytics are enabled by default when configured. I use PostHog US Cloud for anonymous traffic and engagement analytics. Browser identities stay separate on each site origin. PostHog receives technical device information, page paths, referrer hostname, and fixed interaction categories, without query strings or URL fragments.

Session replay is enabled by default when configured. 20% of eligible sessions are sampled. Inputs are masked; Ask, inquiry and booking regions and iframes are blocked. Console logs, network headers and bodies are excluded. Messages, responses, chat IDs, inquiry contents, email addresses and provider errors are never sent as analytics events.

Analytics use browser-local storage for anonymous identities. Blocking ingestion never prevents site interactions.

Ask requires your name and email before you can ask a question. These details are emailed to Animesh through Resend when you submit them. Every valid, rate-limit-accepted question is also emailed with your name, email, submission time and selected storage setting. Your email is used as the reply address. Question emails do not contain the answer, previous conversation, IP address, chat ID or session token. These emails may remain in Resend and Animesh’s inbox according to their retention settings, even if you choose not to save chat history.

Ask’s separate choice controls chat-history storage: saved chats use Redis for 30 days, while no-save history stays only in the current browser tab. Your name and email are kept in browser storage with the same duration: up to 30 days for saved chats or for the current tab in no-save mode. Deleting a saved chat also removes its browser contact details. Contact details are not included in chat transcripts sent to OpenAI or saved in Redis. Analytics do not change this choice. Chat requests are processed by OpenAI, with response storage disabled.

Analytics measure clicks and browser-observed API acceptance, rather than completed downloads or bookings. This disclosure describes the optional integration; capture also requires explicit environment configuration.