DPDP for Digital Signature Platforms
Compliance guide for e-signature platforms handling identity docs, audit trails, and legal contracts under India's DPDP Act.
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 DPDP for Digital Signature Platforms, 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.
Managing Identity Documents and eKYC
Digital signature platforms process high-risk identity data like Aadhaar XML, PAN details, and video KYC files. Under DPDP, you must separate the data used for identity verification from the data stored in the final signed document. Once you verify a signer’s identity, you cannot keep the underlying identity documents longer than legally required by the Controller of Certifying Authorities (CCA) or other regulators.
Audit Trails as Personal Data
Every digital signature generates an audit trail containing IP addresses, timestamps, and device identifiers. This metadata is personal data because it links a specific individual to a specific action. You must map these logs in your data inventory. You need to ensure that technical logs are not shared with third-party analytics tools unless you have specific consent for that secondary use.
Data Types in Digital Signature Workflows
| Work Area | Data Processed | DPDP Risk Level |
|---|---|---|
| User Onboarding | Aadhaar, PAN, Video KYC, Phone Number | Very High |
| Signing Process | IP Address, Geolocation, Device ID | Medium |
| Contract Storage | Signer Names, Witnesses, Sensitive Terms | High |
| Support Tickets | Email, Identity Proofs, Account History | Low |
| Audit Logs | Transaction IDs, Timestamps, Signer IDs | Medium |
The Retention Conflict
Digital signature platforms face a conflict between the Indian Evidence Act and DPDP. To prove a signature in court years later, you might want to keep all verification data. However, DPDP requires you to delete personal data when the purpose is fulfilled. You must define a specific retention schedule that aligns with the limitation periods for different types of contracts, such as 3 years for simple contracts or 12 years for property documents.
This week
Identify every location where you store Aadhaar or identity document copies and check if your system automatically deletes them 30 days after a signature is successfully completed.
Need help applying this to your business? Review the consulting scope and bring the systems, teams, and data flows involved to your first call. If you already have a gap assessment, see implementation support.
Frequently asked questions
Can we keep identity documents forever to prove a signature is valid?
No. You must delete identity documents once the signature is verified and the statutory period for legal challenge ends. DPDP requires data deletion once the specific purpose of verification is served.
Are IP addresses and device IDs in audit trails personal data?
Yes. Any data in an audit trail that can identify a specific signer is personal data. You must include these technical logs in your data inventory and privacy notices.
What happens if a witness on a contract asks to delete their data?
If the data is necessary for a legal obligation or contract validity, you may have grounds to retain it. However, you must clearly document why that data is exempt from a deletion request under 'legitimate use' or legal necessity.