Indori ZameenIndoriZameenइंदौरीज़मीन
HomeExploreMapMaster Plan PortalBlogContact

Indori Zameen

Privacy Policy

Last updated: 11 September 2026

This policy explains what information the Indori Zameen platform handles, why, and what your choices are. It should be read together with the Terms & Conditions and the Disclaimer on that page.

1. Information about you

  • Browsing without an account. You can read the home page, the colony pages and the blog without signing in; the map needs a free account. We do not run advertising trackers. Our hosting provider (Cloudflare) processes standard technical logs — IP address, request, user agent — to serve and protect the site.
  • Signing in. You sign in with Google or with an Indian mobile number (Firebase Authentication). With Google we receive your name, email address and profile photo from your Google account. There is no password stored with us. Anyone may create a free member account; the administrator decides who gets more than that.
  • Your mobile number. Every account verifies an Indian mobile number with a one-time code sent by SMS. The code is sent and checked by our SMS provider, MSG91; we never see or store the code itself. We keep the verified number on your account, and a record of each code request — the number, the time, and a scrambled (hashed) form of your connection’s IP address — to stop abuse. Your verified number is visible to the administrator and never shown publicly or to other users.
  • If you sign up with a mobile number. You give us your first name, last name and an email address, and tell us whether you are joining as a user, a real estate agent or a developer. We use the email to contact you; we do not verify it and it is not used to sign you in. A request to join as an agent or developer is reviewed by the administrator, who sees your name, email and verified number to decide.
  • Documents you open. Each account may open a limited number of documents an hour and a day. To apply that limit we record which documents your account opens and when. Only the administrator can see this record.
  • Profile details. Members and the administrator can add profile details — display name, photo, company, address, phone numbers, social links. You can see and edit your own profile in the profile section. The administrator may also keep a short internal note about an account (for example, who invited whom and why); that note is visible only to the administrator, never to other users and never publicly.
  • Enquiries and activity. If you enquire about a colony or interact with a listed partner, the enquiry and basic activity records (such as profile views) are stored so the right people can respond and the administrator can supervise the platform.
  • On your device. We use localStorage for preferences — your theme choice and whether you have accepted the terms notice. Google Analytics sets its own cookies, described below.
  • How the site is used. Google Analytics tells us which pages are opened, roughly where in the world from, and on what kind of device — so we know which colonies people are looking for and which parts of the site are not working. What this platform sends is the address of the page you opened. Your name, your email address and which records you are entitled to see are never sent to it.
  • Google Signals, and what it adds. We have switched on a Google Analytics feature called Google Signals. For visitors who are signed in to a Google account and who have left Ads Personalisation switched on in their own Google settings, it lets Google tell us that the same person visited from a phone and then from a laptop, and lets us see reports of the estimated age range, gender and broad interest categories of our audience. Those reports reach us only as grouped totals — we are never shown, and never ask for, the age, gender, interests or identity of any individual visitor. Google performs this matching using the account and advertising data it already holds about that person, under its own policy for sites that use its services.
  • Advertising cookies, and what we do not do.Because Google Signals needs them, advertising storage, ad user data and ad personalisation are switched on by default for Google’s analytics cookies. We use this for measurement and audience reporting only. This site carries no advertising, we run no advertising campaigns, we build no remarketing or advertising audiences from it, and we do not sell or share this information with anyone.
  • How to switch it off. Turning off “Ads Personalisation” in your own Google account settings stops Signals using your account for any of the above. Google’s Analytics opt-out add-on, an ad blocker or a privacy extension will stop Analytics altogether. Nothing on this site depends on any of it, and it all keeps working with the lot switched off.

2. Information about properties and people in the records

The platform compiles information about colonies, layouts, projects, promoters, brokers and developers from public-domain portals, statutory records and market sources, as described in the Disclaimer. Where a promoter’s or professional’s details appear, they come from such sources. If information about you appears and you want it corrected or removed, write to [email protected] — takedown requests are honoured as described in the Terms.

3. How information is used

  • To operate the platform and show you the records you ask for.
  • To control access — checking whether an account is invited and what role it holds.
  • To route enquiries to the relevant partner and notify the people involved.
  • To protect the service — rate-limiting, abuse prevention, debugging.

We do not sell personal information, and we do not share it except with the service providers below, or where the law requires it.

4. Service providers

  • Google / Firebase Authentication — sign-in.
  • MSG91 — sending the one-time SMS code that verifies your mobile number, and confirming it was entered correctly. MSG91 receives your mobile number for this.
  • Google Analytics — counting page views, and, through Google Signals, cross-device and audience reporting, as described in section 1. We use it for measurement only: no advertising is carried on this site and no advertising audiences are built from it.
  • Cloudflare — hosting, storage and delivery of the site, its data and its documents.
  • Map providers — base-map tiles and place search are fetched by your browser from OpenStreetMap-based services (including CARTO tiles and Nominatim geocoding), which see the usual technical request data under their own policies.

5. Retention and deletion

Account and profile information is kept while the account exists. To have your account or profile information deleted, or to exercise any other request about your personal information, email [email protected] from the address on the account. Technical logs are retained on our providers’ standard short cycles.

6. Security

The platform runs on managed infrastructure with authentication verified on the server for every protected request. No system is perfectly secure, but access to member data is limited by role, and administrative data (such as internal notes) is restricted to the administrator.

7. Children

The platform is meant for adults dealing with land and property information and is not directed at children.

8. Changes

Updates to this policy are posted on this page with a new “last updated” date.

9. Contact

Indori Zameen
[email protected]

IndoriZameen
Indori Zameen

Indori Zameen organises Indore's real-estate information in one place — the register, the approved plans, the zoning and the paperwork behind them — so you can make an informed choice about what is, for most Indian families, the largest transaction of their lives.

An independent platform, built by architects and planners, with documents from verified sources, referenced with practising brokers. Indori Zameen is not a government body and is not affiliated with one.

Explore
HomeExplore Indori ZameenMapColonies A–ZMaster Plan PortalBlog
Company
ContactTerms & ConditionsPrivacy Policy
Get in touch
Contact us
© Indori ZameenVersion 3.02 · deployed 26 Sept 2026, 1:31 am IST