On 13 November 2026, Rule 4 of the Digital Personal Data Protection Rules, 2025 came into force. That switched on the framework for consent managers. For a developer or a brokerage, the date that matters more is six months away. On 13 May 2027, Rules 3, 5 to 16, 22 and 23 come into force. Most of the Act's duties on Data Fiduciaries start the same day.

Meanwhile the sales floor isn't waiting. Anarock counted 1,00,220 homes sold across seven cities between July and September 2026, Business Standard reported. Every one of those sales left personal data in many places at once. It sits in site-visit registers, portal leads, channel partners' spreadsheets, KYC scans, loan files and allotment letters. After possession it moves into move-in forms and visitor apps.

No DPDP duty works until you know where that data sits. Rule 3 requires every notice to carry an itemised description of the personal data. Section 8(7) requires erasure, including the copies your processors hold. Rule 7 requires you to tell the Board the nature and extent of a breach. Each of these starts with data discovery.

This piece covers where buyer and tenant data hides in a real estate business, and who else sits in the file. It then covers retention after the sale and a first discovery exercise you can run before May.

Where things stand on 18 November 2026

The Rules were notified as G.S.R. 846(E) on 13 November 2025. Rule 1 sets three commencement dates. Rules 1, 2 and 17 to 21 applied on publication. Rule 4 followed a year later. Everything else, including notice, security, breach intimation, retention and rights, starts eighteen months after publication.

One provision matters more for real estate than it first appears. Rule 8(1) and the Third Schedule fix erasure periods for just three classes of business. The first is e-commerce entities with at least two crore registered users in India. The other two are online gaming intermediaries with fifty lakh users and social media intermediaries with two crore.

A developer, a brokerage or a property manager isn't on that list. No rule tells it when a buyer's purpose is deemed to be served. It has to make that call itself under Section 8(7), one record class at a time, and be ready to defend it.

Rule 8(3) adds a floor for everyone. A Data Fiduciary must keep personal data, traffic data and processing logs for at least one year from the date of processing. The purposes are listed in the Seventh Schedule. After that year the data and logs must go, unless another law requires longer retention. That covers the walk-in who never came back.

Then there's the archive. Section 5(2) of the Act covers people who consented before commencement. You must give them a notice as soon as reasonably practicable, describing the personal data and the purpose for which it was processed. A developer with fifteen years of buyers can't write that notice without knowing what each old file contains. Section 5(3) gives the buyer the option to read it in English or any Eighth Schedule language.

Where buyer data actually sits

Ask a sales head where customer data lives and the answer is usually the CRM. The CRM is the tidiest copy. It is rarely the only one.

Start with these places:

Where it startsWhere copies end upWhat it holds
Walk-in and site-visit registerPaper book, tablet app, CRMName, mobile, budget, address
Portal and partner leadsSpreadsheets, email, CRM importsContact details, source, call notes
Booking and KYCScan folders, CRM attachments, emailPAN, Aadhaar, passport, photographs
Home loan fileLoan desk folders, bank portals, chatsSalary slips, bank statements, tax returns
Allotment and agreementLegal team drives, registration copiesIdentity, address, payment schedule
Sales-office CCTVRecorder at site, security vendorFaces and movements of visitors
Possession and handoverSnag lists, move-in forms, key registersResidents, family members, vehicles
WhatsApp and personal emailSales managers' phones, partner groupsCopies of most of the above

The visitor book in a site office deserves a closer look. Section 3(a)(ii) brings personal data collected on paper inside the Act once it is digitised. A handwritten register stays outside until someone photographs a page for the CRM team. In many sales offices that happens every evening. Our piece on paper records and scanned documents works through where that line falls.

WhatsApp is the hardest source to find. Booking forms, PAN copies and payment screenshots move through groups named after projects and towers. Members include sales managers, channel partners and loan agents. Those messages live on personal phones the company doesn't manage. A server scan won't find them, so someone has to sit with the sales team and list the groups.

CCTV is easy to miss because nobody thinks of it as a customer database. The recorder in a sales office holds every visitor's face for as long as its disk allows. Find out who can export footage and how long the security vendor keeps it.

The people who never signed the form

A booking file is rarely about one person. The application names a co-applicant and often a co-owner. Many forms ask for a nominee or a family member's details. NRI buyers add a power of attorney holder. Home loan files bring in a guarantor's income papers. Leasing and property management add tenant references and emergency contacts.

Each of these people is a Data Principal in their own right. The primary buyer's signature on page six gives no notice to her brother-in-law. And unlike the GDPR, the DPDP Act offers no legitimate interests ground to fall back on.

So discovery has to tag each record by relationship. Buyer, co-applicant, nominee, guarantor, tenant and reference each need a label. Without that tag you can't send the right notice or verify the right person when a request arrives.

Rule 14(5) defines the identifiers a Data Fiduciary can ask a requester for. They include an application reference number and a customer acquisition form number. A co-applicant usually shares the main buyer's booking number. Your systems still need to separate her data from his when she writes in.

Brokers and channel partners: processor, fiduciary or both

Section 8(1) keeps the developer responsible for processing done on its behalf, whatever any agreement says. Section 8(2) lets it use a Data Processor only under a valid contract.

Channel partners don't fit neatly into one box. A partner who runs your site-visit desk, or calls your leads from your script, is processing on your behalf. A partner who brings buyers from its own database and keeps them for the next launch decides that purpose itself. For that data it is a Data Fiduciary in its own right.

Many relationships carry both flows, often in the same spreadsheet. Pull out your empanelment agreement and check what it says about personal data. Many cover commission, registration under the Real Estate (Regulation and Development) Act, 2016 (RERA) and conduct, and stop there.

Brokers also answer to a second law. Notification G.S.R. 855(E) of 29 November 2022 brought them under the Prevention of Money-laundering Act, 2002 (PMLA). It covers real estate agents as defined in RERA with annual turnover of ₹20 lakh or more. Those agents are reporting entities under the PMLA.

Section 12 of the PMLA sets their retention. Transaction records stay for five years from the date of the transaction. Identity records stay for five years after the business relationship ends or the account closes, whichever is later.

That retention is the broker's own legal duty. Section 8(7) permits it, because retention is "necessary for compliance with any law for the time being in force". SARC's guide to PMLA compliance for reporting entities covers the record-keeping side. For the contract terms, see SARC's note on third-party and vendor compliance under DPDP.

The discovery question here is short. Which lead sheets flow from partner to developer, which flow back, and who keeps a copy once the deal closes?

Retention after sale, cancellation or a rejected loan

A sale doesn't end at registration, and neither does the buyer's data.

Section 14(3) of RERA makes the promoter rectify structural and workmanship defects notified within five years of handing over possession. Until then, the buyer's contact details, the agreement and the snag history have a live purpose. In a phased project, that clock starts on a different date for each unit.

Other laws run their own clocks. Section 128(5) of the Companies Act, 2013 requires books of account and vouchers to be kept for at least eight financial years. Booking receipts, refund vouchers and commission entries carry buyer and broker names. For brokers who are PMLA reporting entities, the five-year periods run alongside.

Cancellations and rejected loans are where excess data piles up. When a booking is cancelled, the refund entry stays in the books. The PAN and Aadhaar scans, the income papers and the marketing profile each need their own decision.

Sometimes a bank rejects a loan and the buyer moves to another lender. Your copy of the salary slips and bank statements has then usually lost its purpose. The bank's own file is the bank's decision. How lenders handle that same file under DPDP is covered in our piece on the lending lifecycle.

The lifecycle below shows where the main clocks start for one buyer:

Good practice is a retention schedule built by record class. Each row names the record, the law that keeps it alive, the event that starts the clock and the systems that hold it. Discovery fills that last column. Without it, the schedule is a policy nobody can carry out.

Handover to the residents' association and facility manager

Possession starts a second data life. Move-in forms, vehicle stickers, domestic help registrations and visitor apps all collect resident data. Much of it begins while the developer or its facility manager still runs the building.

Section 17(2) of RERA requires the promoter to hand over the necessary documents and plans, including common areas, to the association of allottees. Where no local law applies, that must happen within thirty days of the occupancy certificate. The section says nothing about resident personal data.

Treat the handover date as a change of roles in your map. Before it, the facility manager usually works for you as a Data Processor. After it, the association of allottees, often run as a Resident Welfare Association (RWA), decides how resident data is used. The facility manager then answers to the RWA.

Two copies tend to survive the change. The developer's CRM still holds every resident's mobile number, and the marketing team wants it for the next launch. That use needs consent captured for that specific purpose, separate from the sale. The other copy sits with the visitor app vendor, under a contract that may still name the developer.

The handover pack should record which resident files move to the RWA and which stay with the developer. Keep what the defect liability period needs. Hand over or erase the rest on a date both sides sign.

Breach reporting depends on the map

Rule 7(2)(a) requires the Data Fiduciary to inform the Board of a breach without delay. That first intimation covers its nature, extent, timing, location and likely impact. Rule 7(2)(b) requires a detailed report within seventy-two hours. Rule 7(1) requires each affected Data Principal to be told what happened and what she can do.

Picture a channel partner's laptop stolen from a car outside a sales office. On it are a lead sheet and a folder of booking-form scans. If the partner was acting as your processor, the intimation is yours to make. If your map shows which projects that partner handled and which fields its sheets carried, you can state the extent on day one. If it doesn't, you're estimating in a document that goes to a regulator.

CERT-In adds a shorter clock. Its directions of 28 April 2022 require covered entities to report specified cyber incidents within six hours of noticing them. Khaitan & Co's summary of the directions notes that data breaches and data leaks are on that list. Your CERT-In compliance process and your DPDP intimation should draw on the same map.

The Schedule to the Act sets the stakes. Failing to take reasonable security safeguards under Section 8(5) can attract a penalty of up to ₹250 crore. Failing to notify a breach under Section 8(6) can attract up to ₹200 crore.

A first discovery exercise across sites and sales offices

Start smaller than you think. One live project and one sales office will teach you more in four weeks than a company-wide questionnaire will in four months.

Run the pilot in this order:

StepWhat to doWhat you have at the end
1. Pick the pilotOne live project with its sales and site officesA scope the team can finish
2. List every intake pointWalk-in desk, website, portals, partner uploads, eventsEvery route by which data enters
3. Talk to the floorSales managers, CRM admin, loan desk, accounts, facility teamThe WhatsApp groups and private sheets
4. Scan the systemsCRM, file shares, mailboxes, scan folders, CCTV recorderWhere identity and income papers really sit
5. Tag by personBuyer, co-applicant, nominee, guarantor, tenant, booking numberRecords you can match to a request
6. Set the clocksLegal basis and start event for each record classA retention schedule tied to locations
7. Fix partner contractsSection 8(2) terms for processors, sharing terms for independent partnersA written list of who holds what

Step 4 gives you an inventory. Data mapping turns that inventory into flows between the CRM, the loan desk, partners and the RWA. Those flows are what you'll need when a process changes or a partner leaves.

Step 5 is what lets you answer rights requests from buyers and tenants. Rule 14(3) sets ninety days as the outer limit for responding to grievances. A request you can't match to a record won't close in time.

Put the open items on the weekly sales review agenda, where the sales heads already sit. Then take the pilot to the next three sites. The second project usually moves faster, because the sources repeat.

The buyer file outlives the sale

In real estate, a buyer's file has legal reasons to exist for years after the keys change hands. Every DPDP duty depends on knowing where each copy sits and which law, if any, keeps it alive. A developer that can answer that by May 2027 can erase on schedule and report a breach with facts. One that can't will learn where its data was from the incident report.

This article is general information on the law as it stands on 18 November 2026. It isn't legal advice for any specific transaction.

Sources

  1. Ministry of Electronics and Information Technology, "Digital Personal Data Protection Rules, 2025, G.S.R. 846(E), Gazette of India copy", 13 November 2025. Link
  2. DPDP Wiki, MYND Integrated Solutions, "Section 3: Application of Act, official text reproduced", 9 September 2026. Link
  3. DPDP Wiki, MYND Integrated Solutions, "Section 5: Notice, official text reproduced", 9 September 2026. Link
  4. DPDP Wiki, MYND Integrated Solutions, "Section 8: General obligations of Data Fiduciary, official text reproduced", 9 September 2026. Link
  5. DPDP Wiki, MYND Integrated Solutions, "The Schedule: penalties under the DPDP Act", 9 September 2026. Link
  6. Business Standard, Press Trust of India, "Housing sales in top 7 cities up 3% in Jul-Sep at 100,000 units: Anarock", 28 September 2026. Link
  7. Taxmann, "Govt. notifies 'Real Estate Agents' defined under RERA as a 'person carrying on designated business' under PMLA", 1 December 2022. Link
  8. Indian Kanoon, "Section 12 in The Prevention of Money-Laundering Act, 2002", accessed 18 November 2026. Link
  9. Indian Kanoon, "Section 14 in Real Estate (Regulation And Development) Act, 2016", accessed 18 November 2026. Link
  10. Indian Kanoon, "Section 17(2) in Real Estate (Regulation And Development) Act, 2016", accessed 18 November 2026. Link
  11. Income Tax Department, "Section 128, Companies Act, 2013: Books of account, etc., to be kept by company", accessed 18 November 2026. Link
  12. Khaitan & Co, "Indian Computer Emergency Response Team Direction: Paradigm Shift in Cyber Incident Reporting", 30 April 2022. Link