Why The DPDP Act Matters For Real Estate Now
Real estate leads come from expos, cold calls, portals, and brokers, then move across multiple Developers, brokers, and PropTech platforms act as Data Fiduciaries under the DPDP Act, while portals and call centres process data on their behalf. But leads rarely come from the buyer alone or stay with one company, so whose consent do you actually hold?
Phased compliance timeline
Leads Arrive Without Proof
Ask The Vendor, Then The Buyer
One Brand, Many Companies
Consent Mapped To The Customer
Buyer Data Lives Beyond The CRM
Types of Personal Data Processed






Key Compliance & Data Governance Challenges

Buyer, seller, and landowner data is fragmented across the CRM, portal dashboards, sales spreadsheets, broker WhatsApp groups, loan-partner portals, and scanned KYC folders, with no single record of one person.

Leads arrive from portals, aggregators, and brokers with no record of the notice the buyer saw or what they agreed to, yet the developer is accountable for what it does with them.

Developers, brokers, and portals each decide what to do with the same buyer’s data, and nobody has settled whether they are a separate fiduciary, a joint fiduciary, or a processor, or written it down.

A single enquiry form is used to justify sharing buyer data with loan partners, verification agencies, telecallers and channel partners, with no purpose-specific consent and no record of what was shared.

Statutory flows such as sale-deed registration and tax reporting are either treated as consent items or used to justify keeping the entire KYC pack indefinitely.

Bought or scraped lead lists and owner databases carry no proof that the people on them ever agreed to be contacted, and cancelled-booking files and cold leads outlive the deal.
Built to Solve Every DPDP Challenge
| Real Estate / PropTech Challenge | Privy by IDfy Capability |
|---|---|
| Buyer, seller, and lead data scattered across CRM, portal dashboards, spreadsheets, broker files, and scanned KYC folders | Personal Data Discovery & Governance (Data Compass) finds and classifies personal data across structured systems, unstructured stores and endpoint devices, including documents and images such as KYC scans and agreements. |
| No view of how a buyer’s data travels between the developer, portal, broker, lender, and verification agency | Automated data lineage tracks how personal data moves across systems and vendors. |
| Leads from portals, aggregators, and brokers with no proof of how they were collected, and unwritten roles between developer, broker, and portal | Continuous Compliance & Risk Management assesses every lead source, portal, broker and channel partner, and manages data-processing agreements centrally. |
| KYC packs, cancelled-booking files, and cold leads kept indefinitely | Data Principal Rights Management automates retention schedules and erasure workflows tied to lifecycle events such as cancellation, handover, and lead age, using classification to know what to erase. |
| Sale-deed registration, tax reporting, and other statutory flows are treated as consent items | Processing registers each statutory flow to Section 7 legitimate use, so consent is not overlaid on mandatory disclosures. |
| Buyers and sellers asking for access, correction, or erasure across CRM, lender, and broker records | Data Principal Rights Management routes and fulfils access, correction, and erasure requests across connected systems. |
| Breach of KYC or lead data across the CRM, portals, and vendors | Continuous Compliance & Risk Management provides an auditable, time-stamped incident workflow for Data Protection Board notification, and discovery shows which individuals sat in the affected systems. |
| Lead scoring, pricing, and recommendation models built on buyer personal data | Data Compass classification enables masking and de-identification ahead of analytics and model use. |
| One enquiry reused for other projects, lenders, and lead resale, and tracking cookies on project microsites and portals | Consent Lifecycle Management captures purpose-specific consent per project and partner, with Cookie Manager for microsites and portals. |
| No single view of privacy posture across data, vendor, and consent risk | AI Co-pilot gives a unified view across all modules, continuously scanning for gaps. |
Buyer, seller, and lead data scattered across CRM, portal dashboards, spreadsheets, broker files, and scanned KYC folders
Personal Data Discovery & Governance (Data Compass) finds and classifies personal data across structured systems, unstructured stores and endpoint devices, including documents and images such as KYC scans and agreements.
No view of how a buyer’s data travels between the developer, portal, broker, lender, and verification agency
Automated data lineage tracks how personal data moves across systems and vendors.
Leads from portals, aggregators, and brokers with no proof of how they were collected, and unwritten roles between developer, broker, and portal
Continuous Compliance & Risk Management assesses every lead source, portal, broker and channel partner, and manages data-processing agreements centrally.
KYC packs, cancelled-booking files, and cold leads kept indefinitely
Data Principal Rights Management automates retention schedules and erasure workflows tied to lifecycle events such as cancellation, handover, and lead age, using classification to know what to erase.
Sale-deed registration, tax reporting, and other statutory flows are treated as consent items
Processing registers each statutory flow to Section 7 legitimate use, so consent is not overlaid on mandatory disclosures.
Buyers and sellers asking for access, correction, or erasure across CRM, lender, and broker records
Data Principal Rights Management routes and fulfils access, correction, and erasure requests across connected systems.
Breach of KYC or lead data across the CRM, portals, and vendors
Continuous Compliance & Risk Management provides an auditable, time-stamped incident workflow for Data Protection Board notification, and discovery shows which individuals sat in the affected systems.
Lead scoring, pricing, and recommendation models built on buyer personal data
Data Compass classification enables masking and de-identification ahead of analytics and model use.
One enquiry reused for other projects, lenders, and lead resale, and tracking cookies on project microsites and portals
Consent Lifecycle Management captures purpose-specific consent per project and partner, with Cookie Manager for microsites and portals.
No single view of privacy posture across data, vendor, and consent risk
AI Co-pilot gives a unified view across all modules, continuously scanning for gaps.
Recommended Implementation Journey
Map the Deal Data Estate
Discover and classify buyer, seller, landowner and lead data across the CRM, portal dashboards, spreadsheets, broker files, loan-partner portals and scanned KYC folders.
Audit every lead source (portals, aggregators, brokers, channel partners, purchased lists) for how data was collected and what notice the buyer saw.
Map which flows are required by law (sale-deed registration, tax reporting) and which are optional (marketing, partner sharing, lead resale), so the two are never confused.
Inventory portals, brokers, lenders, call centres, verification agencies and CRM vendors, and flag agreements missing data-processing terms.
Fix the Lead-to-Booking Journey
Set roles in writing with every broker, portal, lender and agency: separate fiduciary, joint fiduciary or processor.
Deploy purpose-specific notice and consent at enquiry, site visit and booking, with a separate choice for sharing with lenders and other projects.
Set retention and erasure triggers for cancelled bookings, cold leads and KYC packs, respecting statutory retention periods.
Build rights and breach-response workflows that reach CRM, lender and broker records.
Govern the Partner Chain Continuously
Continuously monitor portals, brokers, channel partners, lenders and vendors through the platform.
Keep discovery and classification running as new projects, lead sources and systems come online.
Run DPIAs for new PropTech features such as lead scoring, AI recommendations and lead-sharing models.
Appoint an India-based DPO and engage an independent data auditor if notified as a Significant Data Fiduciary.
Key Takeaways
Developers, brokers, and PropTech platforms are Data Fiduciaries for the buyer, seller, and landowner data they collect; call centres and CRM vendors are Data Processors.
DPDP Rules 2025 were notified on 13 November 2025, with Consent Manager registration from 13 November 2026 and major obligations effective from 13 May 2027.
Most leads reach you through someone else, so the fix has two steps: vendors supply only consented data, and you confirm the buyer’s own consent on entry.
Each project company is its own Data Fiduciary, so mapping consent to one customer ID is what lets consent and withdrawal travel across entities.
Sale-deed registration and tax reporting are legitimate uses under Section 7(d), not consent items, but they do not justify keeping the whole KYC pack forever.
Non-compliance can attract penalties of up to ₹250 crore per contravention, and a unified platform enables faster responses through discovery, consent mapping, and partner monitoring.
Why Privy by IDfy for Real Estate & PropTech
Leading real estate and PropTech companies trust Privy by IDfy to govern buyer, seller, and lead data across portals, brokers, lenders, and group companies. Our platform finds personal data wherever it sits, confirms consent as each lead enters, and maps it to the customer across entities.

Get Your Subscriber Data Estate Audit-ready
FAQs
Yes, for the buyer, seller, and lead data it collects and uses, because it decides the purpose and means of processing. Call centres, CRM vendors, and verification agencies that process data on its behalf are Data Processors, engaged only under a valid contract (Section 8(2)). A broker who uses a lead for its own business is a Data Fiduciary in its own right, not your processor.
You are responsible for what you do with it. Where consent is the basis, the Act puts the burden on you to prove notice was given and consent obtained (Section 6(10)). Two steps close the gap: require every lead vendor to supply only consented data, with proof, and confirm the buyer’s own consent when the lead enters your journey, so nothing unconsented sits in your systems.
Often separate, sometimes joint. The Act defines a Data Fiduciary as anyone who, alone or in conjunction with other persons, decides the purpose and means of processing. Each party that decides how it uses a buyer’s data is a fiduciary for that use. Where two parties decide together, treat both as accountable and write down who handles notices, rights requests, and breach reporting.
The enquiry can generally go to the broker or developer the person chose to contact, because that is the purpose they gave it for. Passing it to other brokers, advertisers, or lenders is a different purpose and requires consent, with a notice that says who receives it. A portal that resells one enquiry to many brokers should expect each recipient to be asked for proof.
Not automatically. Each company that decides how data is used is its own Data Fiduciary, so consent given to one does not cover another. Record each consent against one customer ID once the buyer converts, so you can see which company holds what and act on a withdrawal across all of them. Group companies that want to use the same data need to be covered by the buyer’s notice and consent.
For the enquiry itself, yes. Section 7(a) lets you process data a person has voluntarily provided for a specified purpose, unless she has said she does not consent. The Act’s own example is a person who shares her details with a real estate broker to find a rental home. Marketing other projects or sharing with lenders are new purposes, so capture a separate, clear choice for each at enquiry.
Treat them as high-risk. A purchased list gives you the seller’s assurance, not the buyer’s consent, and you carry the burden of proof. Data that law requires to be made public is outside the Act, but a compiled or enriched database rarely fits that exemption cleanly. Ask the vendor for proof of consent for every record, or confirm the person’s consent as the lead enters your journey.






