DPDP Compliance for Real Estate Platforms: Broker Data and Site Visit Tracking

Real estate portals routinely sell or route the same buyer lead — name, phone number, budget, preferred locality — to several brokers or builder sales teams simultaneously, each of whom then calls the buyer independently. That fan-out is a disclosure to multiple third parties that needs to be clearly stated in the notice at the point the buyer submits their contact details, not discovered when four different brokers call within an hour.

Because the buyer rarely has a direct relationship with each broker who receives the lead, the portal carries the practical burden of making sure every downstream broker is bound by a processor agreement or, where the broker is independently deciding how to use the lead for their own marketing, understood as a separate fiduciary who needs their own lawful basis to keep contacting the buyer.

Gated communities and commercial developments frequently require visitors to show ID and sign a physical or digital register before a site visit, sometimes paired with a photograph taken at the security desk. That register is personal data collection outside the portal's own systems, run by the property's security provider, and the notice a buyer receives before a site visit should mention that a security check-in will occur, since it is a distinct collection point from anything the portal itself gathers online.

Where site-visit registers are digitised and centralised across a builder's projects, that consolidated database becomes a valuable target and a retention question in its own right — a builder holding years of visitor logs across dozens of projects should have a defined reason for keeping each entry beyond the visit itself, tied to legitimate purposes like safety incident investigation.

Broker and builder CRMs accumulate leads that went cold years ago, often re-surfaced periodically for fresh marketing campaigns without any renewed consent. A lead who declined interest, asked to be removed, or simply never responded should be treated as having withdrawn engagement, and Section 6's requirement that withdrawal be as easy as giving consent means an unsubscribe or “stop contacting me” request needs to actually stop the calls across every broker who received that lead, not just the portal's own outreach.

Property preference data — budget, locality, family size implied from unit-size searches — can reveal a good deal about a household's financial situation, which is reason enough to keep CRM access tightly scoped to the sales team actually working a lead rather than broadly visible across an entire brokerage.

The Personal Data Inventory is a good fit for real estate platforms specifically because leads move through so many hands — use it to map every party who receives a buyer's contact details once a lead form is submitted. The Consent Notice Builder can help draft language that discloses the multi-broker fan-out clearly, upfront, rather than after the calls start.