DPDP Compliance for Stockbrokers and Wealth Firms: Investor Data Under DPDP and SEBI Rules

    A practical guide to DPDP compliance for stockbrokers and wealth firms, covering investor consent, KYC retention, SEBI obligations and data workflows.

    OneConsentBlog
    8 min read
    Thursday, 5 November 2026
    Investor data flow across onboarding, advisory, trading and retention with separate consent and SEBI compliance controls.

    DPDP compliance for stockbrokers requires a purpose-by-purpose review of investor data, consent, security and retention alongside SEBI obligations. DPDP compliance for wealth management also depends on whether the business operates as an investment adviser, portfolio manager, distributor or another regulated intermediary. A useful implementation plan connects each investor journey to its legal basis, responsible entity and evidence trail.

    For compliance heads, privacy teams and technology leaders, the central decision is how to support investor choice while preserving records required for market supervision and dispute resolution. This article explains that decision across onboarding, advisory interactions, partner sharing and account closure.

    When do DPDP requirements apply to stockbrokers and wealth firms?

    As at 2 November 2026, the core DPDP processing obligations are scheduled to commence on 13 May 2027. These include notice, consent, Data Fiduciary duties, children's data safeguards and Data Principal Rights. The Consent Manager registration framework is scheduled for 13 November 2026. Existing securities and other applicable obligations continue during this transition.

    The Digital Personal Data Protection Act, 2023 covers personal data collected digitally and information collected offline that is subsequently digitized. A scanned account-opening form, an identifiable call recording and an investor profile in a relationship manager's CRM can therefore enter its scope. The Data Fiduciary is the entity deciding the purpose and means of processing. A service provider acting on its behalf may be a Data Processor.

    Your DPDP readiness review should follow legal entities and regulated activities. A group brand can contain separate broking, advisory and distribution businesses. Common ownership alone provides an incomplete basis for sharing investor data across them.

    For current securities references, account for the SEBI Stock Brokers Regulations, 2026 and the Investment Advisers Master Circular dated 6 February 2026. Applying an older regulatory framework without checking subsequent changes can distort the review.

    Which investor data should the compliance review cover?

    Investor data protection extends from the first enquiry to records retained after closure. Map PAN and identity documents, bank details, beneficial ownership information, income and risk profiles, holdings, transaction instructions, nominee information and communications.

    Different records support different activities. A stockbroker processes order instructions and transaction records. An investment adviser may also maintain suitability assessments, financial goals and advice-related interactions. A portfolio manager has a separate mandate and regulatory perimeter. The term wealth firm describes a business category; it does not identify a single SEBI license.

    You should include exports and working copies in the inventory: onboarding uploads, document-verification tools, adviser email, recorded calls, CRM notes, messaging channels and support attachments. You should identify which systems hold original records, which contain duplicates and which permit staff to download investor files.

    Your processing register should record the legal entity, investor identifier, data category, purpose, lawful basis, recipients, system owner, retention trigger and deletion restriction. Maintaining such a register supports investor data protection. DPDP does not impose a universally named RoPA document on every firm.

    How should DPDP compliance for stockbrokers separate consent from statutory duties?

    Each processing activity needs an applicable basis under the DPDP framework. Section 4 provides for consent or specified legitimate uses under Section 7. The Act does not contain a general-purpose legitimate-interests ground equivalent to the GDPR.

    Legal teams should distinguish account servicing, statutory reporting, optional marketing and partner referrals. Section 7(d) addresses legally required disclosures to the State or its instrumentalities. Its wording should be assessed against the particular disclosure; describing every financial-services activity as a legal obligation overstates its scope.

    For consent-based activity, Section 6 requires a free, specific, informed, unconditional and unambiguous indication through clear affirmative action. Rule 3 requires a standalone, understandable notice identifying the personal data and specified purposes, with routes for withdrawal, rights and complaints.

    Your investor consent management design can separate optional promotional contact from account operations. For example, a request to open a trading account should have its own documented purpose and basis. Sharing the investor's profile with a group insurance distributor for a sales campaign requires a separate assessment and an appropriate consent mechanism where applicable.

    An onboarding acknowledgement, a trade instruction, an advisory mandate and a marketing permission each prove something different. Investor consent management should preserve those distinctions in the consent management platform.

    How do SEBI data retention requirements affect investor records?

    Retention follows the record category and applicable legal requirement. SEBI's AML framework requires specified transaction records to be maintained for five years from the transaction date. Identification records, account files and business correspondence have a different trigger: five years after the relationship ends or the account closes, whichever is later.

    For investment advisers, the February 2026 Master Circular requires preservation of specified advice-related interactions, including interactions with prospective clients. It provides a five-year retention period for these records, with extended preservation where a dispute remains unresolved or SEBI requires it. Telephone consent for implementation or execution also has specific recording and timestamp requirements.

    DPDP Section 8(7) recognizes retention necessary for compliance with law. The final Rules also contain a minimum one-year retention requirement for personal data, associated traffic data and processing logs for the purposes specified in the Seventh Schedule. These requirements need to be reflected when the relevant provisions commence.

    You can implement this through record-level retention rules: record class, legal reference, start event, minimum period, hold reason, approver and review date. A single five-year expiry across the entire investor database would overlook different triggers and preservation duties.

    Where an investor withdraws optional marketing consent, stop that processing and instruct relevant processors within the applicable reasonable time. Preserve records that remain lawfully required in a restricted archive. Retention for supervision provides no automatic permission to reuse the archive for cross-selling.

    How should wealth firms manage sharing with partners and AI providers?

    You should assign a role to each recipient before designing the data flow. Depositories, KYC Registration Agencies, exchanges, banks, cloud hosts, verification providers and marketing agencies operate under different arrangements. A recipient that determines its own purposes requires a different assessment from a processor following the firm's instructions.

    Section 8 places responsibility on the Data Fiduciary for processing undertaken on its behalf. A valid processor contract is required where a processor is engaged to process personal data in connection with offering goods or services. Appropriate contractual security provisions also feature in Rule 6.

    Your vendor review should cover permitted fields, sub-processors, access locations, breach escalation, return or deletion, and evidence of completion. Contracts should explain how withdrawals reach operational systems and how statutory holds affect erasure.

    AI adds an industry-specific control. SEBI's February 2026 adviser circular addresses responsibility for client data and advice when an adviser uses AI tools. It also requires disclosure to clients of the extent of AI use in providing investment advice.

    An adviser using an AI meeting assistant should assess recording, transcription, hosting, access and any provider reuse of the material for training. A disclosure about AI-assisted advice and a lawful basis for personal-data processing address separate obligations.

    The related OneConsent article on customer data and AI examines the purpose question in more detail.

    What should an investor rights and incident workflow include?

    Investor rights management should connect authenticated requests to the correct accounts, legal entities and records. Sections 11 to 14 address access to information, correction and erasure, grievance redressal and nomination, subject to their terms.

    Account closure, an instruction to stop promotional calls and a request to correct a PAN entry need different workflows. You should verify identity using proportionate checks, preserve the request history and explain any legally required retention. For nominee or representative requests, verify authority before releasing information.

    Your firm should publish the grievance response period required by Rule 14, within its maximum of 90 days. Keep this distinct from SEBI investor grievance procedures and their applicable timelines. The 90-day provision addresses grievances; treating it as one universal deadline for every privacy operation would be inaccurate.

    For incidents, the scheduled DPDP regime requires notification to affected individuals and initial intimation to the Board without delay, followed by detailed information to the Board within 72 hours, subject to an allowed extension. Securities firms should separately assess applicable SEBI cybersecurity and incident-reporting requirements.

    Your incident exercise should include a compromised relationship-manager account, an exposed onboarding document store and a vendor leak. Assign owners for technical containment, investor communication, regulatory assessment and evidence preservation.

    How can firms implement DPDP compliance for stockbrokers?

    You can start DPDP compliance for stockbrokers with a complete onboarding-to-closure walkthrough. Then test the same investor's preferences across the trading app, adviser CRM, support platform and marketing systems.

    For a first implementation cycle:

    ·         Inventory regulated entities, investor journeys and recipients.

    ·         Map consent-based processing and other applicable grounds with Legal.

    ·         Configure notice versions, purpose records and withdrawal routes.

    ·         Apply retention schedules and restricted preservation holds.

    ·         Test rights requests and incident escalation across vendors.

    ·         Review evidence with Compliance, Information Security and Operations.

    DPDP compliance solutions provide value where these decisions become repeatable workflows. Evaluate DPDP consent management software using a live investor example, including a failed synchronization and a record that must remain under a legal hold.

    OneConsent lists consent and preference management, Data Principal Rights, consent audit trails and data discovery among its platform modules. These capabilities can support an investor consent management program; the implementation should be evaluated against the firm's systems and approved retention rules.

    The DPDPA readiness guide can help your team organize the wider implementation review.

    Book a demo to discuss the investor journeys and evidence requirements your firm needs to support.

    Tiya Grover
    Marketing Associate

    Tiya Grover is a Marketing and Economics graduate from FLAME University and a Marketing Associate at Easyrewardz. She contributes to OneConsent’s growth through product marketing, content strategy, and digital marketing, with expertise in SEO and AEO. Her writing spans OneConsent’s products and capabilities, industry-specific applications of the Digital Personal Data Protection Act (DPDPA), and educational content on data privacy and consent management. She translates legal concepts and product features into clear, practical insights, helping businesses understand their obligations, evaluate consent solutions, and build customer trust.

    See all articles by Tiya Grover

    Frequently Asked Questions

    Have more questions?

    Search our full DPDP knowledge base for more answers.

    See it live

    See OneConsent in action

    Get a personalised walkthrough of how OneConsent helps your teams stay DPDPA compliant.

    • 30-minute walkthrough
    • DPDPA-ready by design
    • Tailored to your stack