Enterprise Decision-Making · Data Privacy Compliance

DPDP Act & AI Calling in Indian Real Estate — Data Privacy Compliance for Voice AI Systems

An operational compliance framework mapping the Digital Personal Data Protection Act 2023 to real estate AI Calling — the four core obligations covering legal basis, recording consent, data retention limits, and data principal erasure rights, what must be in the vendor Data Processing Agreement, and a complete DPDP compliance checklist.

⏱ 12 min read🏢 Executive Governance & Procurement📅 7 July 2026
DPDP Act & AI Calling in Indian Real Estate — Data Privacy Compliance for Voice AI Systems
☰ On this page
Executive Governance & Procurement · Enterprise Decision-Making

DPDP Act Compliance Is Not a Checkbox Exercise

The Digital Personal Data Protection Act 2023 (DPDP Act) fundamentally changed the compliance landscape for any Indian business that collects, processes, or stores personal data of Indian residents. For real estate developers running AI Calling campaigns, the implications are specific and operationally significant: every inbound call, every outbound qualification call, and every CRM disposition record generated by an AI Calling Agent involves the personal data of prospective property buyers — their phone numbers, names, budget ranges, family size preferences, and location requirements.

The Act imposes substantive obligations on how consent is obtained before calling, how call recordings are stored, how data is shared with the AI platform vendor, and what happens when a buyer exercises their right to erasure. Developers who deployed AI Calling before the Act's operative provisions came into force — or who assumed existing RERA or telecalling compliance covered voice AI — face specific gaps that must be addressed before each campaign cycle. This article maps the DPDP Act's operative provisions to the real estate AI Calling context and provides an implementation framework for legally compliant voice AI operations in 2026.

What the DPDP Act Covers in the AI Calling Context

The DPDP Act applies to "processing of digital personal data" — and an AI Calling system processes personal data at every stage of the pipeline.

Lead Ingestion

A portal lead from 99acres, MagicBricks, or Housing.com arrives with the buyer's name, phone number, and expressed property preference. This is personal data. The portal's terms of service establish one layer of consent — the buyer agreed when submitting the inquiry form — but the developer processing this data for AI Calling qualification is a separate processing activity requiring its own legal basis.

Call Audio Recording

The AI Calling system records the full conversation, or at minimum transcribes it. A call transcript containing the buyer's name, budget, family size, and current residence location is a detailed personal profile. Call recordings of identifiable voices are treated as biometric data under emerging regulatory interpretations.

CRM Storage

The structured qualification data — name, phone, confirmed budget, BHK preference, disposition, site visit scheduled — stored in the CRM constitutes a personal data record linked to a specific individual.

Vendor Data Sharing

When the developer uses a third-party AI Calling platform, personal data of Indian buyers is shared with a third-party processor. This sharing requires a data processing agreement and potentially a disclosure in the developer's privacy policy.

The Four DPDP Obligations for AI Calling Deployments

The DPDP Act requires a legal basis for every processing activity. For real estate AI Calling, two primary bases apply.

  • Consent — the buyer explicitly agreed to be contacted; portal lead forms include consent language, but consent to "be contacted by the developer" does not automatically extend to consent for call recording, AI-generated calls, or third-party data sharing with an AI platform vendor
  • Legitimate interest — the developer has a legitimate business interest in following up on an expressed property inquiry; this requires a balancing test where the interest must not be overridden by the buyer's fundamental privacy rights, and it is easier to sustain for a fresh inquiry than for re-engagement calls to leads that are months old with no response

The first call to a fresh portal lead sits comfortably on consent or legitimate interest. Calls to leads older than 90 days with no engagement require a renewed legitimate interest assessment; calls after the buyer has requested not to be called are unlawful under both the DPDP Act and DND regulations; and calls where the AI discloses it is recording are required for transparency.

If the AI Calling system records or transcribes calls, which it must for CRM sync and transcript analysis, the buyer must be informed of the recording before it begins. The standard mechanism, at call connection and before the AI qualification script begins:

💡

"Namaste [Name], main [Project] ki taraf se Priya bol rahi hoon. Aapki quality aur service ke liye yeh call record ki ja sakti hai. Kya aap continue karna chahte hain?" — "Hello [Name], this is Priya from [Project]. This call may be recorded for quality and service purposes. Would you like to continue?"

If the buyer does not consent to recording, the platform must either continue the call without recording, or transfer to a human who continues unrecorded. Continuing a recorded call after explicit non-consent is a DPDP Act violation.

CALL OPENING RULE:
Begin EVERY call with the consent disclosure before any qualification question:
"Namaste [buyer_name]. Yeh call [project_name] ki taraf se hai aur record ki ja sakti hai
quality ke liye. Continue karein?"

If buyer says NO / "recording mat karo" / "don't record":
  -> Set session.recording_consent = False
  -> Stop all recording immediately
  -> Continue qualification call without recording
  -> At call end: dispose without transcript; use entity extraction only for CRM

Obligation 3: Data Minimization and Retention Limits

The DPDP Act requires that personal data is retained only as long as necessary for the purpose for which it was collected.

  • Call recordings — purpose is quality review and dispute resolution; retention of 90 days maximum during a project's active sales period, 30 days after possession or project closure
  • Call transcripts — purpose is CRM data population and qualification verification; retention typically matches the lead record lifecycle in the CRM, generally project lifecycle plus one year
  • Raw call audio, pre-transcription — the highest sensitivity data; retention of 30 days maximum, then auto-delete, since the transcription already serves the operational purpose and raw audio retention beyond 30 days serves no business purpose that outweighs the privacy risk
async def enforce_data_retention():
    """
    Daily job: enforce data retention policy across all tenant data.
    Run at 2:00 AM IST — off-peak, minimal operational impact.
    """
    retention_policies = {
        "call_audio_raw": 30,       # days
        "call_transcripts": 365,    # days (CRM lifecycle)
        "call_recordings": 90,      # days
        "session_data_redis": 7,    # days (Redis TTL)
    }

    for data_type, max_days in retention_policies.items():
        cutoff_date = datetime.utcnow() - timedelta(days=max_days)

        # Delete expired records from data store
        deleted_count = await data_store.delete_before(
            data_type=data_type,
            before_date=cutoff_date
        )

        # Log deletion for audit trail (DPDP requires demonstrable compliance)
        await audit_log.write({
            "action": "data_retention_deletion",
            "data_type": data_type,
            "cutoff_date": cutoff_date.isoformat(),
            "records_deleted": deleted_count,
            "timestamp": datetime.utcnow().isoformat()
        })

Obligation 4: Data Principal Rights — Erasure and Access Requests

The DPDP Act grants data principals (buyers) three operative rights relevant to AI Calling.

  • Right to erasure — a buyer can request deletion of all their personal data held by the developer; complete deletion within a reasonable timeframe, with 30 days emerging as the standard pending Rules notification
  • Right to access — a buyer can request confirmation of what data the developer holds about them, with a summary of data held provided within a reasonable timeframe
  • Right to correction — a buyer can request correction of inaccurate data; for example, if the AI transcription misheard the buyer's budget and recorded ₹80L when the buyer said ₹1.8Cr, the buyer can request correction of the CRM record
async def handle_erasure_request(buyer_phone: str, requestor_verification: dict):
    """
    DPDP Act erasure request: delete all personal data for a buyer.
    """
    # Step 1: Verify requestor identity (same number, OTP verification)
    if not await verify_requestor(buyer_phone, requestor_verification):
        return ErasureResult(status="rejected", reason="Identity verification failed")

    # Step 2: Locate all data records
    records = await data_store.find_all_by_phone(buyer_phone)

    # Step 3: Delete in sequence with audit trail
    deletion_log = []

    for record in records:
        if record.audio_url:
            await storage_client.delete(record.audio_url)
            deletion_log.append(f"Deleted audio: {record.call_id}")

        if record.transcript:
            await data_store.delete_transcript(record.call_id)
            deletion_log.append(f"Deleted transcript: {record.call_id}")

        # Anonymize CRM record (cannot delete if part of active sales contract)
        await crm_client.anonymize_lead(
            lead_id=record.crm_lead_id,
            retain_disposition=True,  # Business record integrity
            anonymize_pii=True        # Replace name, phone with [DELETED]
        )
        deletion_log.append(f"Anonymized CRM lead: {record.crm_lead_id}")

    # Step 4: Confirm erasure to requestor
    await notification_service.send_erasure_confirmation(
        phone=buyer_phone,
        deletion_log=deletion_log,
        timestamp=datetime.utcnow()
    )

    return ErasureResult(status="completed", records_processed=len(records))

Vendor Data Processing Agreement: What Must Be in the DPA

When the developer uses a third-party AI Calling platform, personal data is shared with a data processor. The DPDP Act requires a contractual framework that governs this relationship.

What the DPA Must Specify

  • What data the processor receives — lead list fields, call recordings
  • The purpose for which the processor may use the data — only for providing the calling service, not for platform training
  • Data retention limits matching the developer's own policy
  • Security standards the processor must maintain
  • The processor's obligation to return or delete data on contract termination
  • The processor's obligation to notify the developer of any data breach within 72 hours

What the DPA Must Prohibit

The processor using developer customer data for any purpose beyond service delivery — including model training, benchmark development, or aggregated analytics shared with third parties without explicit consent.

Verification

Request evidence of the processor's security controls annually — a SOC 2 report or equivalent — and include audit rights in the DPA that allow the developer to request evidence of compliance at any time.

The DPDP Compliance Checklist for AI Calling

RequirementImplementationStatus Check
Consent disclosure at call startTTS script opens with recording noticeEvery call, every tenant
Recording non-consent handlingSession flag stops recording; no transcriptTest monthly
DND/NCPR exclusionPre-call scrubbing via telephony providerEvery campaign batch
Raw audio auto-deletion at 30 daysAutomated retention jobDaily audit log
Transcript retention at 365 daysData store TTL configurationMonthly audit
Erasure request handlingProcess + response within 30 daysQuarterly drill
Vendor DPA executedSigned agreement with AI Calling platformPre-go-live
Privacy policy updatedDiscloses AI calling and third-party processorPre-go-live
Consent audit trailAll consent decisions logged with timestampContinuous
Data breach response plan72-hour notification protocol definedAnnual review

Frequently Asked Questions

Portal consent covers the developer contacting the buyer about their specific inquiry — that contact basis is established. What portal consent does not automatically cover: AI-generated calls, since some legal interpretations require disclosure that the calling party is an AI when the buyer explicitly asks; call recording by the developer or their vendor, which requires the developer's own consent disclosure; and data sharing with the AI Calling platform vendor, which requires disclosure in the developer's privacy policy. The practical guidance is to layer your own consent disclosure at call start on top of the portal's consent, and ensure your privacy policy is updated to disclose AI Calling and vendor data sharing.

The DPDP Act does not yet have specific provisions on AI disclosure. Consumer Protection (E-Commerce) Rules and sector-specific guidance from Real Estate Regulatory Authorities (HARERA, MahaRERA, and others) do not currently mandate upfront AI disclosure for commercial calling. The practical and ethically sound standard is to disclose truthfully when the buyer directly asks whether they are speaking with a robot or AI — the system should never actively claim to be human when sincerely asked. Voluntary upfront AI disclosure is increasingly considered best practice and eliminates the trust damage of a buyer discovering they were misled mid-conversation.

Yes. An inbound call answered by the AI, regardless of whether the buyer initiated it, is a new processing event. The recording consent disclosure should play at the start of every call session, inbound or outbound. Configure the inbound call handler with the same consent disclosure script used for the outbound opener. Inbound calls from buyers who are actively engaged and calling back after an AI call represent high-intent leads, so the consent disclosure should be brief and warm rather than bureaucratic.

Retention should map to the purpose the data serves. Raw call audio serves only a short-term quality and dispute-resolution purpose, so 30 days maximum is appropriate before auto-deletion. Call recordings retained for review purposes can extend to 90 days during a project's active sales period and 30 days after project closure. Transcripts and CRM disposition records serve the ongoing sales-pipeline purpose, so retention typically matches the lead record lifecycle in the CRM — project lifecycle plus one year is a defensible standard. Retaining any of this data indefinitely without a documented purpose is the most common DPDP compliance gap in real estate AI Calling deployments.

The developer is the data fiduciary and bears primary legal responsibility for DPDP Act compliance, regardless of which vendor's platform processes the calls. The AI Calling platform vendor is a data processor acting under the developer's instructions, and their obligations are defined contractually through the Data Processing Agreement (DPA) rather than directly under the Act in the same way. This means the developer cannot outsource compliance risk by simply choosing a vendor — the developer must independently verify the vendor's security controls, execute a proper DPA, and maintain their own consent and retention practices regardless of platform-level features the vendor provides.

Final Verdict: Compliance Is the Developer's Responsibility

The DPDP Act does not treat AI Calling as a special case — it treats it as what it is: a system that processes the personal data of thousands of prospective buyers at scale, continuously. The obligations in this article are not optional add-ons layered onto a working AI Calling deployment; they are the difference between a legally defensible operation and one carrying unquantified regulatory exposure. The developer, as data fiduciary, cannot transfer this responsibility to the AI Calling platform vendor by contract alone — a properly executed DPA reduces risk, but consent design, retention enforcement, and erasure handling remain the developer's operational responsibility. Build these into the deployment from day one rather than retrofitting them after a campaign has already generated thousands of call records.

Disclaimer: This article provides an operational interpretation of the Digital Personal Data Protection Act 2023 as it applies to AI Calling systems in Indian real estate as of Q2 2026. It does not constitute legal advice. The DPDP Act's Rules and operative provisions are subject to ongoing notification by the Government of India — requirements may change after publication of this article. Real estate developers deploying AI Calling systems should obtain specific legal advice from qualified data protection counsel before deployment. All compliance obligations remain the responsibility of the data fiduciary (the developer), not the AI Calling platform vendor.

Related Reading

Z

Written by

Zappio Team

AI & Real Estate Experts — building AI voice agents that qualify real-estate leads in minutes, not days.

See more Zappio insights in Google Search — add us as a preferred source.

Add as preferred source
Start Free — ₹10,000 Credits

Ready to stop losing leads?

Join 200+ real-estate consultants using Zappio. Go live in 2 hours.