No accounts, no profiles
BhuBharati Explorer has no sign-up, login, or user account system. We do not build a profile of you, do not know who you are across visits, and do not ask for your name, email, or phone number to use the explorer, the REST API, or the MCP server.
What passes through the app
When you use the explorer in a browser:
- Your location selections (district, mandal, village) are sent to our backend so it can query the public portal on your behalf.
- Fetched land records are returned to your browser and kept in that browser's memory for searching, sorting, filtering, and export. They are not written to a database tied to you.
- CSV/JSON exports are generated entirely in your browser from data already loaded there; export files never pass back through our servers.
- Standard request metadata (IP address, user agent, timestamps) is visible to our hosting infrastructure the way it is for any web request. See Server logs below.
We do not use cookies, browser storage, or third-party analytics/advertising scripts to track visitors between sessions. See Cookies & Tracking for the current, itemized list of anything a browser stores.
About the land record data itself
The records you fetch (pattadar/owner name, father or husband's name, survey and Khata numbers, extent, classification, and similar fields) are public data already published by the Telangana government's BhuBharati portal (bhubharati.telangana.gov.in). We read that data, parse it, and display it back to you — we do not originate it, and we do not modify the source portal.
Because these records can contain another person's name and land holdings, treat exported files as personal-data-bearing documents: store and share them the way you would any document containing someone else's personal information.
The AI assistant
The /chat endpoint has two modes:
- Deterministic field-guide assistant (default, and what runs on bhubharati.dhethi.com today). It answers questions using rules and the records already loaded in your session. Nothing is sent to an external AI provider in this mode.
- Optional OpenAI-backed assistant. Self-hosted operators can enable this. When enabled, chat messages and a bounded set of already-fetched record fields (at most a few hundred rows, or a short-lived server-side cache of the current village) are sent to OpenAI to generate a response. Our production deployment explicitly disables this and does not forward an OpenAI key to the API container.
See LLMs and AI for the full breakdown of what an AI provider can and cannot see.
Server logs and infrastructure
Like most web services, our hosting and application logs can record IP address, request path, timestamp, and response status for operational purposes: debugging, abuse prevention, and uptime monitoring. We do not sell this data or use it for advertising. Logs are not linked to a user account, because none exists.
Retention
| Data | Where | Retention |
|---|---|---|
| Fetched land records for one village | Your browser's memory | Until you close/reload the tab |
| Same village result, server-side | In-process / on-disk cache | Minutes to hours, reset daily |
| District/mandal/village names and IDs | Application database | Refreshed periodically from the public portal; this is location taxonomy, not personal data |
| Request/application logs | Hosting infrastructure | Short, operational retention only |
Your rights and choices
Because we don't hold an account or profile tied to you, there is usually nothing to "delete" on our side beyond short-lived caches that expire on their own. If you believe we hold something about you that concerns you — for example, in request logs — contact us using the details below and we will look into it.
If a fetched record concerns your own land and you believe it is inaccurate, the correction has to happen at the source: the official BhuBharati portal, not here — we only mirror what it publishes.
Children
BhuBharati Explorer is a general-purpose public-records tool and is not directed at children. We do not knowingly collect information from children.
Changes to this policy
If this policy changes materially, we will update the "Last updated" date at the top of this page.
Contact
Questions about this policy can be raised through the project repository, or via the contact details published on the API documentation at /docs.