Exporting records (CSV / JSON)
After you fetch a village's records:
- Use the search box, land-type filter, or sort dropdown above the results table to narrow or order what you're looking at.
- Select JSON to download the original fetched records as-is, or Export CSV to download a UTF-8 spreadsheet-friendly file.
- The export is built entirely in your browser from records already loaded there — nothing is sent back to our servers to generate the file, and no copy of the export is retained by us.
Exported files can contain another person's name and land details, because the underlying records are public ownership data. Store and share export files the way you would any document containing someone else's personal information.
Account settings
There is no account to configure. BhuBharati Explorer has no sign-up, login, password, or profile — every visit starts fresh. If you're looking for a "settings" page, it doesn't exist, and nothing about your usage carries over between visits.
Privacy controls
Because there are no cookies, accounts, or trackers to opt out of (see Cookies & Tracking), the main privacy control you have is simply: close the tab. That clears everything the explorer held in memory. If you used the optional AI assistant on a self-hosted instance where an operator enabled OpenAI, see AI for what was sent and to whom.
Requesting deletion
Since we don't retain a record tied to an individual visitor, there is typically nothing to delete on request. If you believe our request logs or server-side caches contain something specific that concerns you, contact us (see Get help) and we will investigate and remove it if appropriate. To correct or remove data about your own land as it appears on the government portal, you must go through the official BhuBharati portal — we only mirror what it publishes.
Security basics for exports
- Treat CSV/JSON exports as sensitive files if they include other people's ownership data — avoid posting them publicly.
- Prefer HTTPS when accessing the explorer or API (the production site is served over HTTPS).
- If you build automation against the REST API or MCP server, keep in mind the endpoints are read-only and currently unauthenticated by default — don't rely on them as an access control boundary for sensitive downstream systems.
Troubleshooting
| Symptom | Likely cause / fix |
|---|---|
| Mandal or village dropdown stays empty | Select the level above it first (District → Mandal → Village); each level loads only after its parent is chosen. |
| Fetch seems stuck | Large villages can have many surveys; watch the progress bar for live survey/record counts, or select Cancel fetch and try again. |
| "API offline" status | The backend or the upstream government portal may be temporarily unavailable; retry after a few minutes. |
| A record looks wrong or incomplete | We display what the source portal reports; verify against the official portal or your current documents before relying on it. |
Get help
For anything not covered here, see the Help Center for concept explanations, or reach us through the project repository or the API documentation at /docs.