Corporate & Commercial Law

Years of Customer Data, but No Consent Records. What Now?

By Advocate Sharan Jain

Years of Customer Data, but No Consent Records. What Now?

Do not mark every old customer as "consented", and do not send a universal consent message before checking where the records came from. Existing customer data needs a record-by-record purpose and evidence review. Keep necessary transactions separate from optional campaigns, investigate uncertain sources and pause uses the company cannot explain.

Part of the legal advisory and regulatory compliance practice at S Jain & Attorneys, Bangalore.

Position checked on 18 November 2026. The ordinary DPDP processing, notice, consent and rights provisions are in the eighteen-month commencement tranche, scheduled to commence on 13 May 2027. This is preparation for that framework, alongside an assessment of the present 2011 sensitive-data Rules, contracts and relevant sector requirements. Section 5(2) provides a transition notice mechanism for qualifying earlier consent. It does not declare that every historical database was lawfully collected.

How should we audit existing customer data without disrupting the business?

Divide the records by source and current use before deciding what should happen to them. A customer may appear in accounts, a product-support system and a newsletter tool for different reasons. Deleting the whole customer profile or blessing every copy together avoids the real question: what supports each continuing use?

Create an assessment copy with access limited to the people doing the review. Preserve the original collection history and identify which system remains the authoritative transaction record. Start with high-risk or high-volume uses, such as an active campaign, an unrestricted export or an archive containing sensitive information. A company need not stop issuing receipts while it investigates an unrelated promotional list.

Record groupQuestion to resolveInitial handling
Current order and support recordsWhat service and lawful purpose require these fields?Maintain the necessary service records with appropriate access
Documented historical consentWhat purpose and notice did that permission cover?Review the future transition notice and continuing-use conditions
Marketing list with uncertain provenanceWho collected it and what permission or other basis supports contact?Pause the questioned campaign and investigate before reuse
Required retention recordsWhich provision or identified legal purpose requires retention?Restrict the retained category and record the review trigger
Unnecessary duplicate exportDoes any remaining purpose or retention duty justify this copy?Arrange controlled deletion after checking holds and dependencies

This is a triage method rather than a final legal classification. Give each group an owner who can explain the underlying operation. A column saying "old database" says nothing about whether the company may use it for a new product launch.

Where did the records come from, and why does that matter?

The source tells you which factual route must be examined. A direct purchase, an abandoned enquiry, an event registration, a referral and a bought spreadsheet do not come with the same history. Recover the collection route from the system and available records instead of relying on a colleague's recollection that "everyone agreed".

Look for original forms, account terms, campaign notices, signed documents, invoices, messages requesting a service and vendor migration records. Identify the collecting entity as well as the collecting brand. A person may have dealt with one company in a group without authorising another company to launch an unrelated campaign. A merger, agency arrangement or contractual transfer needs its own analysis, not merely a common logo.

Record source confidence separately from processing permission. You might know precisely which trade fair supplied a list while still having no evidence of permission for your proposed messaging. Conversely, a lawful transaction may be well established even though a supplementary old checkbox record has been lost. The review should make that distinction visible.

Use a short source history for each cohort: who collected it, when, through which form or channel, for what stated activity, and where it travelled afterwards. Where the company bought a third-party list, use the separate service-agreement principles to inspect promises and remedies, but do not mistake a broker's warranty for the missing factual permission.

The following categories make unknowns explicit instead of converting them into an invented answer.

Known direct source

Record the original collection route and purpose, then examine which present uses stay within that history and which require a separate assessment.

Evidence missing

Mark missing proof as missing, restrict the questioned use and assign an investigation owner rather than importing a false consent value into the CRM.

New purpose proposed

Treat a new campaign or disclosure as a new decision, even where the company has held the underlying transaction record for many years.

The evidence should connect a person or identifiable collection event to the notice and choice that actually applied. A database field carrying "Y" is not self-explanatory. Ask which process populated it, what it meant at the time and whether the value survived later system changes accurately.

A usable history may include a form version, collection date, language, purpose wording and affirmative action. An instruction from a customer can also show why particular data was supplied. Its legal significance depends on what was requested and the processing relied on. Future section 7(a), for example, is tied to the specified purpose for which the person voluntarily provided data and the absence of an indication against that use. It is not a general marketing permission.

Inspect migrations carefully. A consultant may have mapped an empty permission field to "subscribed" so a new tool would accept the import. That records a software decision, not a customer choice. Preserve the mapping document, identify the affected records and correct the operational consequence without destroying evidence of what occurred.

Separate facts from conclusions in the assessment sheet. "Customer requested a delivery update by message on this date" is a fact that a retained message may support. "Customer consented to every group company sharing the number indefinitely" is a much larger conclusion. If the evidence does not bridge that distance, do not write the conclusion into a compliance certificate or source-of-truth field.

Section 6(10)'s future proof requirement is a reason to improve this evidence now. It is not permission to backdate a notice or tell customers that an earlier screen contained wording that the company has only just written.

When is the legacy notice under section 5(2) relevant?

Section 5(2) addresses personal data for which the individual gave consent before section 5 commences on 13 May 2027, and requires the fiduciary to provide the prescribed notice as soon as reasonably practicable after that date. Section 1(2) reads a reference to the commencement of the Act as the coming into force of the provision concerned, so consent collected between now and 13 May 2027 also falls within section 5(2). Read that condition before designing a transition email. It is a route for qualifying earlier consent, not an amnesty for unidentified sources.

The notice concerns the personal data and purpose, withdrawal and grievance rights, and the route for a complaint to the Board in the operative framework. Rule 3 adds the clear, itemised and accessible presentation requirements. The company should describe what it has actually processed, rather than attach a newly expanded set of future purposes to a statement that the person already agreed.

The provision permits continuing processing unless the person withdraws consent, subject to the statute's requirements. It does not say that silence can create an earlier consent that never existed. Where the company cannot establish the premise, identify the evidential gap and analyse the available lawful route for the particular activity.

Plan delivery so the notice reaches the relevant people through an effective method connected with their accounts or dealings. Record the notice version, delivery method, failures and follow-up decisions. Do not describe a technical delivery receipt as proof that the original consent was valid. Those are different facts.

As at the date of this article, the main notice and processing tranche is still later. Do not tell recipients that a general future DPDP request is already enforceable through an ordinary Board complaint if the relevant provisions have not commenced. A carefully labelled readiness communication should also preserve whatever present contractual or sector rights apply independently.

Common mistake. A new privacy-policy link does not repair an unknown source, prove an earlier choice or authorise a new use. First establish which factual and legal question the communication is meant to answer.

No universal re-consent conclusion follows merely because a database is old. Determine what supports the relevant use, whether the evidence satisfies that route and whether a notice or fresh choice is actually needed. Blanket campaigns can create confusion by implying that necessary service records and optional promotions must stand or fall together.

Consider a hypothetical retailer with paid orders, warranty records and a seasonal advertising list. The customer asked the retailer to deliver the purchase, and the company may have separate obligations concerning accounts and service. None of that automatically authorises every promotional message. Assess the service, retention and campaign separately rather than asking a customer to "consent to all processing" to keep a purchase history.

A fresh request can be appropriate where the company wants a new consent-dependent purpose or cannot rely on the historical basis. The request must itself be lawful through the channel selected. Do not assume that buying a number creates permission to contact it solely to ask for permission. Telecom preferences, business-platform policies and other current requirements still matter.

Prepare a response path for people who decline, withdraw or ask questions. If the sending system cannot stop the proposed optional use, the company is not ready to ask for that choice. Equally, do not promise that refusal will erase a record that a specific law requires the business to preserve.

The useful practitioner distinction is between missing proof, an invalid basis and a new purpose. Each calls for a different action. Treating all three as a request to click the same button may generate a cleaner-looking spreadsheet while leaving the underlying problem untouched.

Which continuing uses need their own assessment?

Assess a use again when the purpose, recipient, collecting entity or nature of the processing materially changes. A record that remains necessary for one task is not a general asset available for every other task the company can imagine. Write the proposed change next to the original collection history.

Examples include sending a customer list to a new advertising partner, letting a supplier train its own product on support material, profiling customers using additional sources or transferring records to a different group entity for an unrelated offering. These examples are not automatically unlawful in every setting. They are decisions requiring a defined purpose, applicable basis, accurate notice and appropriate contractual and security treatment.

Ask what the recipient will actually do. "Analytics" can mean aggregate counts that do not identify anyone, or a detailed identifiable profile used to target an individual. "Vendor" can mean processing on the company's instructions, or collecting data for independent purposes. The label does not settle the role.

Record a decision for the new use before releasing the data. Where the use depends on consent, consider the necessary specific request and its withdrawal consequences. Where another statutory route is claimed, identify its conditions and the facts satisfying them. Do not replace that analysis with a paragraph saying the company has a broad commercial interest in growth.

The existing business guide explains the framework's roles and scope. The task here is narrower: apply those distinctions to the proposed change in this particular historical dataset.

What should we do when the source remains unknown?

Quarantine the questioned use while investigating, and separate that restriction from any necessary preservation of evidence or legally required record. "Quarantine" means an actual access or campaign control, not a note asking the sales team to be careful while the automation continues.

Identify the last reliable point in the chain. Check whether an external agency supplied the data, whether a departed employee imported it, or whether the same records were copied between systems. Ask for underlying collection evidence in a secure and proportionate way. Do not distribute the whole questionable list to several vendors merely to ask where they think it came from.

Set an investigation decision point and record who may authorise a future use or disposal. The company may need to retain limited evidence of the questioned processing for a complaint, inquiry or contractual dispute. That is a separate purpose to assess, with access limits. It does not mean the same records should stay active in the marketing platform.

If the necessary basis cannot be established, stop the unsupported use and decide how the unnecessary material will be removed, subject to the applicable retention analysis. A management-approved description of the uncertainty is better evidence than an invented explanation. Where the source suggests a leak or unauthorised disclosure, assess incident duties separately rather than treating the matter solely as poor database housekeeping.

How should withdrawal reach vendors and other copies?

Translate the person's choice into instructions for every system and processor involved in the affected consent-based use. Future section 6(6) requires cessation within a reasonable time, including causing processors to cease, unless continuing processing without consent is required or authorised by the applicable law. A preference change confined to the customer-facing screen will not achieve that.

Maintain a recipient and system map linked to the purpose. Identify the CRM, mailing tool, sales exports and agency platform involved in the particular activity. Distinguish a processor instructed to act for you from another fiduciary whose role and duties need separate assessment. Do not promise that a deletion button controls a party over which your contract gives no such control.

Record when the instruction was sent, acknowledged and implemented. Check the next scheduled export and campaign. A nightly integration can recreate a suppressed record if it continues to treat the older source system as an unconditional instruction to subscribe. Correct that import rule instead of manually removing the same person every week.

A limited suppression record can be a practical way to prevent unwanted re-enrolment, but identify its own purpose, basis, access and retention. Do not describe it as an unrestricted exception allowing the whole customer profile to remain forever. Explain accurately what has stopped, what remains necessary and how the person can question the decision.

Retain the category that the actual purpose or applicable law justifies, rather than every duplicate that happens to contain the customer's name. The future Act's erasure duties and section 12 must be read with lawful retention requirements. Present sensitive-data rules also address purpose and retention, so the transition is not a reason to ignore old archives.

The final DPDP Rules require particular care. Rule 8(3), in its future operative setting, contains a minimum one-year retention provision for personal data, associated traffic data and processing logs for the specified Seventh Schedule purposes, which concern use of the data by the State and the assessment of Significant Data Fiduciaries. Other provisions address security evidence and specified classes of inactive accounts. These are not interchangeable rules saying either "delete everything immediately" or "retain every database forever".

For each retained category, identify the provision, purpose, start point, review point and responsible owner. Tax and company records require their own source check before a numerical retention period is inserted. A contractual limitation or a credible existing dispute may raise further preservation questions. Those questions should be analysed without fabricating a universal retention period for all customer data.

Reduce access while information is retained for a limited purpose. A closed transaction record kept to answer an account question should not automatically remain in the promotional audience. If a backup cannot perform selective deletion immediately, document how the retained copy is controlled and how a restoration will respect subsequent deletion or restriction decisions.

These three records make the remediation decision reviewable.

Purpose register

Identify each continuing use separately so a required transaction record does not silently authorise an unrelated campaign or disclosure to another organisation.

Exception record

Name the actual retention purpose or legal provision, the affected record category and the next review point instead of writing a generic keep-forever instruction.

Implementation trail

Track changes across source systems, exports and processors, including evidence that scheduled imports cannot undo the restriction or withdrawal that has been applied.

What should the CRM cleanup and management sign-off contain?

The sign-off should describe completed decisions and their evidence, not certify that every historical entry is lawful simply because an audit was attempted. Record the dataset reviewed, the period covered, the sources examined, limitations, actions taken and matters awaiting a decision. Keep a useful before-and-after account of substantive changes.

  1. Freeze unsupported optional uses and preserve the relevant history.
  2. Group records by source, purpose, system and recipient.
  3. Assess the evidence and applicable present or future legal route.
  4. Prepare any appropriate notices or specific new choices.
  5. Implement restrictions, corrections and retention decisions across the systems.
  6. Test integrations, vendor instructions and exception handling.
  7. Give management a decision record and named follow-up owners.

Keep the status vocabulary honest: "source verified", "consent evidence missing", "marketing stopped", "invoice retained under identified duty" and "vendor confirmation outstanding" are different results. Do not collapse them into a single green compliance score. A subsequent reviewer should be able to understand what the company actually did without interviewing everyone who attended the cleanup meeting.

Use the broader startup documents checklist to keep customer-facing terms and supplier arrangements aligned with the remediated process. The lasting improvement is not the one-off spreadsheet. It is a collection process that records the necessary facts when the next customer arrives.

Key takeaway. Historical data calls for a defensible source-and-purpose decision. Preserve evidence, stop unsupported uses, distinguish retention from marketing and build a process that does not manufacture yesterday's consent today.

How do we test a migrated database before restarting campaigns?

Test the permission history as well as the contact details. A migration can preserve the customer's name accurately while losing the distinction between a service record, a newsletter choice and an unknown historical status. That is a different problem from a misspelled address, and ordinary deduplication will not repair it.

Select a small, explained set of records from each material source and trace them from the original form or transaction through the old system, export and new CRM. Include a person who declined marketing, one who withdrew, a record with no recorded choice and a contact imported by a vendor. This is an operational test, not a claim that a particular sample size proves legal compliance. Document what the test can and cannot establish.

Check whether joining records changed the meaning of a field. Two people may share a family telephone number, and one employee's work address may later be reassigned. A permission given by one person should not silently become permission for every profile linked to that number or address. Likewise, merging an opted-out profile into an active customer account should not reactivate the promotional route simply because the surviving account has an open invoice.

Restart only the uses for which the reviewed records and channel rules support the decision. Keep unresolved groups segregated, preserve the import mapping and make the suppression test part of future migrations. This creates a useful evidence trail without pretending that a software cleanup generated consent the customer never gave.

Frequently Asked Questions

Does every old customer need to consent again?

Not automatically. Establish the original basis, evidence, continuing purpose and applicable transition before deciding whether a fresh request is required.

Can a legacy notice repair a bought list?

Section 5(2) is conditional on qualifying earlier consent. It does not establish the source or permission for an otherwise unsupported third-party database.

Should we delete the whole CRM immediately?

No blanket deletion instruction fits every company. Distinguish necessary services, legal retention, disputed records and unsupported optional uses.

Can a sale count as permission for every future promotion?

A transaction and a broad marketing campaign are different purposes. Channel-specific requirements also need separate assessment.

What if our software automatically marked missing values as consent?

Preserve the import history, identify the affected records and stop treating the generated value as proof of a customer choice.

Does withdrawing marketing consent erase an invoice?

Not necessarily. Assess the record-specific purpose and applicable retention duty separately from the promotional use.

Are the future DPDP deletion rules unconditional?

No. The Act and final Rules include retention conditions and specific minimum-period provisions that require reading in their operative setting.

What is the first useful management decision?

Assign owners to the highest-risk uses and stop relying on unknown permission fields while the original sources are investigated.

This article is for general informational purposes only and does not constitute legal advice. Consult a qualified advocate for advice on your specific situation.

Related Legal Services

Dealing with a matter like this? Our Bangalore advocates can help. Explore the relevant practice areas:

SJ

About the Author

Advocate Sharan Jain

Advocate based in Bangalore, practising before the Karnataka High Court and District, Sessions, Consumer and Family courts. Writes on civil, criminal, corporate, family and constitutional law to make Indian law more accessible.

S Jain & Attorneys · Legal Consultation

Have a Legal Question? We're Here to Help.

Our experienced lawyers in Bangalore offer confidential consultations tailored to your specific legal needs.

All matters handled with complete confidentiality and legal discretion.