BhashaWe built BhashaBadlo without accounts or logins on purpose, partly because it makes the product simpler to use, and partly because it means there's very little of your data for us to be responsible for in the first place. Here's a plain-language walkthrough of what actually happens to your information when you use the site — not a wall of legal boilerplate, just the real behavior of the app.
What we don't store
The text you type, speak, or upload is never saved to our database. When you hit translate, it's sent to our AI language-model provider (currently Groq) purely to get a result back, and Rewrite & Improve goes to that same provider. If it is ever unavailable, the request falls back to MyMemory, a free community translation service. Whichever handles it processes your text only long enough to return an answer, under their own separate privacy terms — we don't keep a copy on our end, and we don't log it anywhere ourselves. Photos are a special case: text is extracted from an uploaded image inside your own browser, so the image itself is never sent anywhere at all, and only the extracted text goes on to be translated.
What we do store
We keep a small, anonymous usage record per request — which feature was used, which provider handled it, whether it succeeded, how long it took, how many characters were involved, and an estimated cost. That's it. This exists purely so we can notice when something's broken or slow and fix it — it doesn't include your IP address or the actual text you translated, and there's no way to trace a record back to a specific person.
History and Favorites
If you use the History or Favorites features, everything is saved directly in your own browser's local storage — it never touches our servers at all. That also means it's tied to that one browser: clear your browser data, or use "Clear history" / "Clear favorites" in Settings, and it's gone for good — we have no copy to restore it from, because we never had one.
Social sharing
Connecting X to post translations directly stores your access token in an encrypted, temporary session cookie only — it's never written to our database, and it disappears the moment your browser session ends. We can't see or reuse that token after the fact.
Cookies
The only cookies BhashaBadlo sets are functional ones — your admin session (if you're staff) and the temporary X connection token above. We don't run third-party ad-tracking or analytics cookies unless Google Analytics has been explicitly enabled in the admin dashboard, in which case standard Google Analytics cookies apply under Google's own privacy terms.
Questions
If anything here is unclear, or you want to know more about how a specific feature handles your data, reach out via the Contact page — we're happy to explain.