Real Estate: Section 12 Data Correction Template & 7-Day Response Compliance (₹200 Crore)

Applies to	Real Estate agents, property brokers, and developers storing buyer and seller personal data in India
Primary law	DPDPA 2023 · Section 12
Penalty ceiling	up to ₹200 crore
Enforcement status	Data Protection Board accepting complaints — 2026-07
Source	DPDPAReady Compliance Team

What Section 12 Requires from Real Estate Brokers

Section 12 of the DPDPA establishes a fundamental right: data principals can demand correction, completion, updating, or erasure of their personal data. The statute reads:

“A Data Principal shall have the right to correct any personal data held by a Data Fiduciary if such personal data is inaccurate, incomplete, or out-of-date in relation to the purpose for which it was collected or processed. A Data Fiduciary shall, in such cases, on the receipt of a request from the Data Principal, correct, complete, update, or erase such personal data within thirty days.”

For real estate businesses—brokers managing buyer profiles, agents storing seller documents, developers maintaining prospect lists—this creates a direct compliance obligation. When a buyer contacts you requesting deletion of their property search history, or a seller asks you to correct their property measurement data, you must act within the timeframe specified by regulation, or face penalties up to ₹200 crore.

The critical exception: you need not comply if retention is mandated by law. Property transactions governed by the Registration Act, KYC rules under anti-money laundering compliance, and tax documentation fall into this category—but only if retention is legally required, not merely “policy”.

Real Estate Data Correction Request Response Template

Use this template to standardize how your firm processes Section 12 requests. Fill in all bracketed sections before sending to the data principal.

---

[YOUR FIRM NAME] — Section 12 Data Correction/Erasure Request Response

Request Reference: [Request ID] | Date Received: [Date] | Response Date: [Date within 30 days]

Data Principal Details:

• Name: [Full name as per records]
• Email: [Contact email]
• Phone: [Contact number]
• Property/Transaction ID: [If applicable]

Request Classification (select one):

• Correction of inaccurate data
• Completion of incomplete data
• Updating of out-of-date data
• Erasure of data no longer necessary

Data Fields Identified in Request:

Data Field	Current Value in Our Records	Requested Action	Our Decision	Legal Basis for Denial (if applicable)
Example: Property Address	123 ABC Society, Mumbai	Correct to XYZ Complex	Approved	—
[Field]	[Current value]	[Action requested]	Approved/Denied	[Law requiring retention]
[Field]	[Current value]	[Action requested]	Approved/Denied	[Law requiring retention]

Compliance Decision:

• Fully Approved: All requested corrections/erasures executed by [date].
• Partially Approved: [List approved fields]. Denied fields: [List with legal basis below].
• Denied: [State legal retention requirement].

Legal Basis for Denial (check applicable laws if request denied):

• Registration Act, 1908 (property title and deed records)
• Prevention of Money Laundering Act, 2002 (KYC retention mandate: [specify retention period])
• Income Tax Act, 1961 (transaction records: [specify retention period])
• Real Estate (Regulation and Development) Act, 2016 (project records)
• Other: [Specify law and retention period]

Action Taken:

• Data corrected/completed/updated in: [List systems: CRM, website, email, partner databases, etc.]
• Data erased from: [List systems where erasure occurred]
• Third parties notified: [List any co-brokers, buyers, sellers, or portals informed of the action]
• Date action completed: [Date]

Data Principal Signature Line:

I acknowledge receipt of this response to my Section 12 request and confirm the action(s) described above.

Signature: _________________ Date: _________

Data Fiduciary Authority:

[Name], [Title] [Firm Name & Registration/License Number] [Contact Phone & Email]

---

Real Estate Section 12 Compliance Checklist

Implement these steps to handle data correction and erasure requests systematically:

1. Request Intake (Day 1)

   • Log request in a centralized register (spreadsheet or database) with timestamp
   • Verify requestor identity (match email/phone to records or request valid government ID)
   • Classify request: correction, completion, update, or erasure
   • Identify all data fields affected (name, phone, property preferences, transaction history, etc.)

2. System Audit (Days 2-5)

   • Locate all copies of data: CRM, email, spreadsheets, paper files, chat records, cloud backups
   • Document where data is stored (which employee, which system, which external vendor)
   • Check retention legality: Is this data covered by Registration Act, PMLA, Income Tax rules, or anti-money laundering obligations?
   • Distinguish: buyer/seller transactional data (often legally retained) vs. marketing/search data (may be erasable)

3. Retention Check (Days 6-10)

   • For property records: Registration Act mandates retention of title documents
   • For KYC data: PMLA requires 5 years of retention for transaction-related documents
   • For tax data: Income Tax Act requires 6 years for transaction records
   • For mortgage records: Lender’s obligation may exceed yours; coordinate with bank if applicable
   • Document the legal basis in writing

4. Approval & Execution (Days 11-25)

   • Approve correction/erasure or document denial with legal basis
   • If approved: update records, delete files, notify external parties (vendors, co-brokers)
   • If denied: prepare written explanation citing the specific law and retention period
   • Coordinate with IT: remove data from backups or mark as non-recoverable (if retention required)

5. Response Communication (By Day 30)

   • Send written response using the template above
   • Include proof of action (updated record, deletion confirmation, third-party notifications)
   • If denied, clearly state the law requiring retention and the retention period
   • Provide escalation contact and grievance procedure

6. Record Keeping (Ongoing)

   • Maintain audit trail of all Section 12 requests and responses for 3 years
   • Monthly review: are denial reasons defensible?
   • Quarterly training: brief all staff (sales, admin, IT) on Section 12 scope and real estate exceptions

Common Section 12 Scenarios in Real Estate

Scenario 1: Buyer Requests Erasure of Search History (6 Months Post-Purchase)

A buyer contacts your firm requesting deletion of all property search data. Section 12 permits erasure unless you have a legal retention obligation.

• If data is pure marketing records (no financial transaction, no mortgage, no regulatory filing): Erasure is required.
• If purchase involved a bank mortgage: Those records fall under financial regulation (RBI guidelines) and cannot be erased.
• Your response: “Your property search history and marketing preferences will be erased by [date]. However, your property transaction documents and purchase agreement will be retained per the Registration Act, 1908.”

Scenario 2: Seller Requests Correction of Property Details

A seller notices your listing states “2,500 sq. ft.” but the original deed says “2,300 sq. ft.” The seller requests correction. You must comply per Section 12 and update all copies.

• Update: your website listing, agent databases, shared portals, any buyer communications
• Notify: all buyers who received the incorrect information
• Document: the correction request and your response
• Your response deadline: 30 days from request

Scenario 3: Applicant Requests Erasure of Incomplete KYC Documents

A buyer started the application process, provided partial KYC documents (Aadhaar copy but no income proof), then withdrew. Later, they request erasure of all submitted KYC data. You must comply unless the data is subject to AML retention.

• If no transaction occurred: KYC data can be erased (Section 12 permits erasure of incomplete data no longer necessary).
• If transaction occurred but buyer wants records erased post-completion: Deny. PMLA mandates 5-year retention of transaction-related KYC.
• Your response: “Your KYC documents submitted during the [property name] transaction will be retained until [date] per the Prevention of Money Laundering Act, 2002.”

Scenario 4: Denial Based on Mandatory Retention

A buyer requests full erasure of their property transaction, including deed, payment receipts, and title transfer documents. You must deny this if the property is registered under the Registration Act, 1908 (virtually all Indian properties).

• Your denial statement: “Section 12 requests cannot override the Registration Act’s retention requirements. Your property deed and title transfer documents are retained permanently per law. Other discretionary records will be erased upon request.”

Frequently Asked Questions

Q: If a buyer asks me to delete their data within 30 days of a property purchase, must I erase their transaction records immediately?

A: Not if the transaction involved a bank loan, title registration, or tax filing. These are legally mandated retentions. However, you must erase any discretionary data—browsing history, preference profiles, marketing tags—unless there is a specific legal retention mandate. If you deny the erasure request, your written response must cite the specific law requiring retention and the retention period. A blanket “we keep all records” is not a valid Section 12 denial.

Q: What if we use a third-party property management or CRM platform—can we delay a Section 12 request while we wait for the vendor to delete the data?

A: You remain the Data Fiduciary under Section 12. The 30-day compliance clock starts when you receive the request, not when your vendor responds. If you cannot meet the 30-day deadline due to vendor delays, you must still respond within 30 days explaining the status and providing an updated timeline—not exceeding an additional 30 days without justified cause. Establish vendor SLAs in your contracts to ensure deletion happens within your compliance window. Do not use vendor delays as a reason to ignore Section 12 deadlines.

Q: Does Section 12 allow us to refuse erasure if the buyer “might” contact us again in the future for new property searches?

A: No. Section 12 protects erasure of data “no longer necessary for the stated purpose.” If the original purpose (property purchase, property search) is complete, you cannot retain the data on speculative future use. If you wish to retain contact information for new marketing, you must obtain fresh consent under Section 5. Refusing erasure because “we might send them listings later” violates Section 12; speculative future contact is not a legal retention basis.

Q: Can we delay a Section 12 correction request if we are verifying the accuracy of the new data with the buyer?

A: Brief, reasonable verification is acceptable if the correction is ambiguous (e.g., buyer reports a name change without supporting ID). However, you cannot indefinitely delay. If the buyer provides reasonable proof of their requested correction, update the records within 30 days. If genuine verification is required beyond 30 days, respond with a status update and estimated completion date (generally no more than 60 days total). Document your verification process to justify the timeline.

Q: Our firm stores buyer property preferences (budget, location, size) to match with future listings. If a buyer requests erasure, must we delete these preferences even though they help us serve them better?

A: Yes, if the original purpose for collecting preferences has ended and you lack a new legal basis for retention. If the buyer searched for properties and has now completed their purchase, the original purpose is fulfilled. The preferences are no longer necessary for that purpose under Section 12. You must erase them upon request. If you want to retain them for future marketing with independent consent, you must separately obtain consent under Section 5 (consent-based processing). Do not assume ongoing consent for new purposes; Section 12 erasure requests are an explicit signal that the original consent has been withdrawn.