How to read our pages
- Ink, set heavier marks facts and dates from the public record.
- Blue marks FlatKundli's own dated work: what we fetched and archived, and our collection runs.
- Hatching marks what a record does not show.
Facts only
- We state what a record says, when it said it and where it is.
- No scores, grades, ratings, rankings or labels for any builder or project, in words, numbers, icons or colours.
- No predictions about what a builder will do, and no advice on whether to buy.
- Simple arithmetic on filed values, such as the months between two completion dates, is shown with the formula it used and that formula's version.
- When something is not on the portal, we say so with the date we looked: "not shown on the portal as of" that date. We do not call it a failure.
- We write
Extension of 12 months granted on [date] (order no. [number]).
- We never write
The project is running late.
A source on every line
Every fact carries three things: a link to the page on the RERA portal it came from, the filing or order date, and a link to our archived copy of that page with the date we fetched it. A fact without all three is not published.
Archived copies
We keep a copy of every page and document we fetch, so anyone can see what the portal showed on the day, even after it changes. The raw copies stay private, because they hold personal data exactly as the portal published it; what you see is a version with that data removed.
"As filed by the promoter"
Much of what a RERA portal shows was filed by the builder (the promoter, in RERA terms) and has not been checked by the authority: project details, proposed completion dates, quarterly progress and units booked. We mark each such value "as filed by the promoter". Values that come from the authority itself, such as registration certificates, extension orders, complaint orders and revocations, name the authority as their source. Where a portal does not say which it is, we treat the value as filed by the promoter.
Quotes are word for word
Orders and complaint summaries are quoted exactly, with the order or complaint number, the date, the link, the archived copy and, for PDFs, the page number. Cuts are marked [...] and never change the meaning. Spelling and grammar stay as published.
How a finding is set out
Every report opens with the records it checked: the date we checked them, each list or document we examined, and what was not available to us, with the reason. It never implies that we checked a record we did not.
Every finding then has three parts, in this order:
- What the record says: the filed value or the exact quote, with its source, its date and our archived copy.
- What it does not show: the limits of that record, stated as facts about the record. Never a guess at what a missing record would show.
- Ask the builder: one neutral question that a document, a date or a status can answer.
A general order is quoted on the terms that decide which projects it covers, never summarised as covering every project. The finding on the home page shows the shape.
Complainant names and personal data
- Complainant and petitioner names are removed before anything is stored. Inside a quote, they read [complainant].
- Names, addresses and photographs of directors and signatories, PAN numbers and bank account numbers are dropped when a page is read, and never published.
- The promoter's registered name is published, because it is the registered party. A company's CIN may be published too.
Right of reply
- Anyone named on FlatKundli, builders above all, can send a reply, a correction or a takedown request to [email protected]. We answer within 7 days.
- A builder's reply can be published word for word next to the facts it addresses, with its date.
- A fact shown wrongly is corrected. Personal data published by mistake is removed at once.
- A fact that the public record still shows stays up, with any reply beside it. If a portal withdraws or changes a record, the page says so, with the date.
Corrections log
From launch, a public corrections log lists every correction: the date, the page or report affected, what changed and why. Corrections are never silent. If you hold a report whose facts change, we tell you what changed.
Coverage
- Telangana
- Collected every night since 29 September 2026, with a pause from 30 September to 4 October 2026: the Orders of Authority and the general orders by TGRERA, with their PDFs, and the authority's list of geotagged projects. Records behind the portal's CAPTCHA are not collected; we asked TG RERA for bulk access on 27 September 2026.
- Karnataka
- Our parsers for the K-RERA portal are built and tested. Collection starts once we run from a server in India, because the portal does not answer the overseas servers we use today, and nothing from K-RERA is published until the authority replies to our permission request of 27 September 2026.
- Other states
- Andhra Pradesh, Tamil Nadu, Kerala, Maharashtra, Gujarat, Odisha, West Bengal, Delhi, Haryana and Uttar Pradesh: portals assessed on 28 September 2026. Each is added once it can be collected at a polite pace and its terms allow.
Why not check the RERA portal yourself?
You can, and every line of a report shows you where to look. Start with the list of orders: most entries in it do not name the project they are about.
- Searching. The Telangana project search asks for a typed picture code on every search, and a project's records sit in separate lists: the project list, the authority's orders, its general orders, suo motu orders, orders of the adjudicating officer, revoked projects and defaulters.
- Matching. Most entries in the authority's list of orders do not name the project. A report lists the orders that name the project or its promoter in the published lists, and says plainly what that search cannot catch.
- Keeping. Portal pages change and documents are replaced. We keep a dated copy of every page and PDF we read, so a report shows what the record said on the day we checked.
- The whole promoter. A report also covers the other projects the same promoter has registered, with their status and any orders naming them.
- Asking. Every finding ends with a question to put to the builder before you pay the booking amount.
How we collect the data
- Our software reads each portal at a human pace: no more than one request every 2 seconds, in the quiet hours from 02:00 IST.
- Every request says it comes from FlatKundli and gives this site's address and our email.
- We never get around a CAPTCHA, by software or by hand. Where a portal publishes a robots.txt file, we follow it.
- If a portal blocks us, we stop and contact the authority.
Credit lines
Each authority sets its own terms for reusing what it publishes. We follow them, and reproduce records accurately, never in a misleading context.
- Telangana (TG RERA)
- Its copyright policy allows reproduction with a prominent credit. We reproduce with the credit line "Source: Telangana Real Estate Regulatory Authority, rera.telangana.gov.in", and link to its pages rather than framing them.
- Karnataka (K-RERA)
- Its copyright policy allows reproduction with permission requested by email. We requested it on 27 September 2026, and publish nothing from K-RERA until the authority replies. Credit line: "Source: Karnataka Real Estate Regulatory Authority, rera.karnataka.gov.in, reproduced with permission".
- Maharashtra (MahaRERA)
- Its copyright policy allows reproduction with a prominent credit and does not allow framing. Its project detail pages sit behind a CAPTCHA, which we do not get around.
- Andhra Pradesh and Tamil Nadu
- Both require permission before their material is reproduced. We ask each authority before we publish anything from its portal.
Review
Any change to these rules is dated on this page. Questions about any of it: [email protected]. What the pipeline has collected so far is on the data status page.