Board Resolutions for DPDP Compliance
Get a practical DPDP board-resolution guide for governance, oversight and data protection accountability.
Discuss this page with an LLM
DPDP Action Sheet
Use this before your next workflow goes live. It keeps the useful parts visible and turns DPDP into checks your team can actually answer.
For Board Resolutions for DPDP Compliance, the DPDP question is how personal data enters the workflow, where it is stored, which tools touch it, what purpose was explained, and how deletion or withdrawal will work.
1. Lead Forms
Check:
- What data are you collecting?
- Is the purpose clear at the point of collection?
- Is marketing consent separate from service communication?
- Can the user withdraw consent later?
Common mistake: one checkbox that silently covers newsletters, sales calls, partner sharing and remarketing.
2. Email and WhatsApp
Check:
- Who is on the list?
- Where did consent come from?
- Is the list imported from a vendor, event, webinar, scrape or old CRM?
- Can you prove the source of consent?
Common mistake: treating every lead as permanently marketable.
3. Ads and Retargeting
Check:
- Are pixels or ad platforms receiving identifiable user behavior?
- Are audiences built from customer lists?
- Are lookalike or remarketing audiences using personal data?
Common mistake: assuming "the ad platform handles it" means your company has no DPDP responsibility.
4. Website Analytics
Check:
- Which tools run on the site?
- Are IP address, device identifiers, session IDs or form fields being captured?
- Is analytics used only for measurement, or also for profiling and targeting?
Common mistake: installing tools first and asking privacy questions later.
5. Vendor List
Make a quick list:
- CRM
- Email platform
- WhatsApp provider
- Analytics
- Ad pixels
- Form tool
- Landing page builder
- Webinar tool
For each vendor, answer: what data goes there, why, who can access it and how deletion works.
6. This Week's Action
Map one campaign from first click to final follow-up. Mark every place personal data is collected, enriched, shared, uploaded or used for targeting.
If your team cannot answer where the data came from and where it goes next, start with a data flow map before rewriting policy copy.
Book a DPDP clarity callWant all of this handled, end to end? Sanctum is the all-in-one DPDP compliance programme behind this site: legal position, data map, gap analysis, implementation, tooling, training, readiness opinion, and breach cover under one accountable owner. How all-in-one DPDP compliance works or see the Sanctum programme.
Documenting the Data Protection Officer Appointment
The Board of Directors must formally designate a Data Protection Officer (DPO) through a signed resolution to meet DPDP requirements. This document links a specific individual’s name, professional address, and contact details to the legal liability of the firm. Unlike standard administrative shifts, this resolution serves as the primary evidence for the Data Protection Board of India that your leadership has established a clear chain of command for data grievances.
Balancing Permanent Records and Data Minimization
The Companies Act requires board minutes to be kept permanently, but the DPDP Act mandates deleting personal data once its purpose ends. Your resolutions must now include specific clauses that justify the continued storage of director identification numbers (DIN) and signatures as a statutory necessity. This prevents a conflict where a former director exercises their “right to erasure” for data contained within historical board records.
Board-Level Data Workflows
| Workflow | Personal Data Involved | DPDP Risk |
|---|---|---|
| Director Onboarding | PAN, DIN, and residential addresses | Internal exposure to staff outside the Company Secretarial team. |
| Virtual Board Meetings | IP addresses and video recordings | Storing biometric or behavioral data on third-party servers without a processing deal. |
| Remuneration Filing | Bank account details and tax brackets | Data leaks during the circulation of unencrypted board packs via email. |
| Conflict Disclosures | Names of family members and their holdings | Processing “third-party” data without a clear “legitimate use” justification. |
This week
Review your board portal’s access logs. Remove any former employees or IT vendors who still have “viewer” access to past resolutions containing the PAN or home addresses of your directors.
Now think about your work. Where does personal data enter your workflows? Where does it sit? Who else touches it?
Frequently asked questions
Does a director’s "right to erasure" allow them to demand their name be removed from old board resolutions?
No, because the Companies Act requires these records to be maintained permanently. The DPDP Act allows for continued processing when it is necessary to comply with any law currently in force.
Should the board resolution specifically name the third-party data processors we use?
Yes, the resolution should authorize the engagement of specific cloud providers or consultants. This creates a formal record that the Board has performed due diligence on how those vendors handle personal data.
Can we use a single resolution to cover all group companies?
Each legal entity acting as a Data Fiduciary must pass its own resolution. A parent company resolution does not automatically fulfill the compliance obligations of a subsidiary under the DPDP Act.