DPDP Compliance For Real Estate and PropTech

A buyer’s enquiry on a property portal, a broker’s KYC pack, and a lender’s sanction letter are all personal data under the DPDP Act, 2023. Trusted by Housing.com, House of Hiranandani, and 75+ enterprises.

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

Phased compliance timeline

DPDP Rules, 2025 follow a staggered rollout, with key obligations effective from 13 May 2027.
Leads Arrive Without Proof

Leads Arrive Without Proof

Expo sign-ups, cold-call lists, portals, and brokers supply most leads, each without proof of what the buyer agreed to.
Ask The Vendor, Then The Buyer

Ask The Vendor, Then The Buyer

Require vendors to supply only consented data, then confirm the buyer’s own consent when a lead enters your journey.
One Brand, Many Companies

One Brand, Many Companies

Each project company is its own Data Fiduciary, so consent given to one does not automatically cover another.
Consent Mapped To The Customer

Consent Mapped To The Customer

Mapping consent to the customer ID once a buyer converts lets a withdrawal be acted on across every company.
Buyer Data Lives Beyond The CRM

Buyer Data Lives Beyond The CRM

The same buyer also sits in broker spreadsheets, WhatsApp groups, loan-partner portals and scanned KYC folders.

Types of Personal Data Processed

Expo Sign-Ups
Expo Sign-Ups
Cold-Call Lists
Cold-Call Lists
Portal Leads
Portal Leads
Broker Leads
Broker Leads
WhatsApp Chats
WhatsApp Chats
Key Compliance & Data Governance Challenges

Key Compliance & Data Governance Challenges

  • tick

    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.

  • tick

    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.

  • tick

    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.

  • tick

    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.

  • tick

    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.

  • tick

    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

Buyer, seller, and lead data scattered across CRM, portal dashboards, spreadsheets, broker files, and scanned KYC folders

Privy by IDfy Capability

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.

Real Estate / PropTech Challenge

No view of how a buyer’s data travels between the developer, portal, broker, lender, and verification agency

Privy by IDfy Capability

Automated data lineage tracks how personal data moves across systems and vendors.

Real Estate / PropTech Challenge

Leads from portals, aggregators, and brokers with no proof of how they were collected, and unwritten roles between developer, broker, and portal

Privy by IDfy Capability

Continuous Compliance & Risk Management assesses every lead source, portal, broker and channel partner, and manages data-processing agreements centrally.

Real Estate / PropTech Challenge

KYC packs, cancelled-booking files, and cold leads kept indefinitely

Privy by IDfy Capability

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.

Real Estate / PropTech Challenge

Sale-deed registration, tax reporting, and other statutory flows are treated as consent items

Privy by IDfy Capability

Processing registers each statutory flow to Section 7 legitimate use, so consent is not overlaid on mandatory disclosures.

Real Estate / PropTech Challenge

Buyers and sellers asking for access, correction, or erasure across CRM, lender, and broker records

Privy by IDfy Capability

Data Principal Rights Management routes and fulfils access, correction, and erasure requests across connected systems.

Real Estate / PropTech Challenge

Breach of KYC or lead data across the CRM, portals, and vendors

Privy by IDfy Capability

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.

Real Estate / PropTech Challenge

Lead scoring, pricing, and recommendation models built on buyer personal data

Privy by IDfy Capability

Data Compass classification enables masking and de-identification ahead of analytics and model use.

Real Estate / PropTech Challenge

One enquiry reused for other projects, lenders, and lead resale, and tracking cookies on project microsites and portals

Privy by IDfy Capability

Consent Lifecycle Management captures purpose-specific consent per project and partner, with Cookie Manager for microsites and portals.

Real Estate / PropTech Challenge

No single view of privacy posture across data, vendor, and consent risk

Privy by IDfy Capability

AI Co-pilot gives a unified view across all modules, continuously scanning for gaps.

Recommended Implementation Journey

Now
November 2026
May 2027
2027 Onwards
Stage 1
Stage title icon

Map the Deal Data Estate

  • Checkmark iconDiscover and classify buyer, seller, landowner and lead data across the CRM, portal dashboards, spreadsheets, broker files, loan-partner portals and scanned KYC folders.
  • Checkmark iconAudit every lead source (portals, aggregators, brokers, channel partners, purchased lists) for how data was collected and what notice the buyer saw.
  • Checkmark iconMap 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.
  • Checkmark iconInventory portals, brokers, lenders, call centres, verification agencies and CRM vendors, and flag agreements missing data-processing terms.
Stage alert icon
Consent Manager registration opens: 13 November 2026
Stage 2
Stage title icon

Fix the Lead-to-Booking Journey

  • Checkmark iconSet roles in writing with every broker, portal, lender and agency: separate fiduciary, joint fiduciary or processor.
  • Checkmark iconDeploy purpose-specific notice and consent at enquiry, site visit and booking, with a separate choice for sharing with lenders and other projects.
  • Checkmark iconSet retention and erasure triggers for cancelled bookings, cold leads and KYC packs, respecting statutory retention periods.
  • Checkmark iconBuild rights and breach-response workflows that reach CRM, lender and broker records.
Stage alert icon
Core DPDP obligations become effective: 13 May 2027
Stage 3
Stage title icon

Govern the Partner Chain Continuously

  • Checkmark iconContinuously monitor portals, brokers, channel partners, lenders and vendors through the platform.
  • Checkmark iconKeep discovery and classification running as new projects, lead sources and systems come online.
  • Checkmark iconRun DPIAs for new PropTech features such as lead scoring, AI recommendations and lead-sharing models.
  • Checkmark iconAppoint an India-based DPO and engage an independent data auditor if notified as a Significant Data Fiduciary.
Stage alert icon
Every lead has a traceable source, and every deal record has a traceable legal basis.

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.

No. Registering the sale deed and reporting the transaction to the tax authorities are disclosures the law requires, which makes them legitimate uses under Section 7(d), not consent items. Treating a statutory filing as a consent item creates a withdrawal right you cannot honour. The same data cannot then be reused for marketing without its own ground.