Privacy Policy
BharatCode collects only what we need to operate accounts, route model requests, improve reliability, prevent abuse, and understand whether the product is helping students and builders.
Information we collect
We receive account details from Supabase Auth, such as your email address, provider identity, display name, and sign-in timestamps. If you submit profile, phone, leaderboard, project, hackathon, or community forms, we store the information you provide.
BharatCode logs usage data for model requests, including timestamps, request status, token counts, latency, and message counts. Outside the paid Pro policy below, private prompt/response logs may be retained for debugging, abuse review and product quality. They are not placed in public buckets.
Paid Pro: Zero Data Retention for prompt/response logs
From 13 October 2026, BharatCode does not save new model-request prompts or responses in its proxy logs while your account has active paid Pro access, across CLI, Desktop, API and Chat requests. Complimentary and referral-earned Pro access alone do not include ZDR. Usage counts, timings, classified errors, account and billing records remain available; they do not contain your prompt or response text.
Historical logs collected before this change remain retained. ZDR does not delete your saved conversations: BharatCode Chat keeps conversation history so you can reopen it, and you can delete it using Chat's controls. Local CLI and Desktop history also remains on your device. This policy does not erase content from those stores.
How we use data
We use this data to authenticate you, provide access to the shared model endpoint, show usage and leaderboard views, review submitted projects or hackathon registrations, detect misuse, troubleshoot failures, and plan BharatCode capacity.
Third-party partners
BharatCode works with third-party partners to provide inference. Prompts and related content you send are processed by these partners under agreements covering Zero Data Retention. Some processing may occur outside India, while we are working out partnerships with Indian providers.
These partner terms are separate from BharatCode's Pro logging policy above. Account, billing and content-free operational records are not prompt/response logs.
Where data lives
Supabase currently handles authentication. BharatCode account and usage data lives in our internal application database, and private raw logs or proof uploads may be stored in private cloud storage buckets. Access is restricted to operational and admin use. Prompts and related content are additionally processed by the partners described above.
Your choices
You can sign out from the account page, choose whether to submit optional profile fields, and avoid public project leaderboard submissions if you do not want project details reviewed. For account or data questions, contact the BharatCode team through the community channels linked on this site.