Compliance

You were never hacked, but you hold customer data you cannot account for

The question nobody in the business can answer

A customer writes to you and asks what personal details you hold about them, and whether you can delete them. Your sales head says it is “in the system”. Your accounts manager says some of it is in the billing software. Your branch in Pune says it is in a WhatsApp group and a notebook. Nobody can say, in one afternoon, where all of it sits.

Nothing has been stolen. No one has hacked you. Yet you have a problem, and it grows with every dealer, outlet or branch you add.

What it costs

Privacy exposure rarely arrives as one dramatic event. It arrives as a request you cannot answer, a complaint you cannot trace, or a partner who asks for your data-handling practice during onboarding and finds nothing to read.

Consider a hypothetical distributor with 60 dealers. Each dealer collects customer phone numbers, addresses and sometimes identity documents for warranty or credit. If each dealer keeps three separate copies (a register, a phone contact list, a spreadsheet), that is 180 places holding personal data, none under head-office control. One data request from a customer means chasing 180 places. At two hours of a manager’s time per dealer, that is 120 hours, about three working weeks, for a single request.

India’s Digital Personal Data Protection Act, 2023 places duties on businesses that decide why and how personal data is processed. The details are for your lawyer. What the owner can see without one is simpler: a business that cannot say what it holds cannot meet any rule about it.

Why it happens

Almost never carelessness. Growth does it.

At 5 outlets, the owner knows where everything is. At 50, each outlet invents its own way of recording customers, because head office never specified one. Data is collected because it might be useful, not because a process needs it. Consent, where it is sought at all, is a verbal “give me your number”. And the privacy notice, if it exists, was written once by someone who has since left and does not describe what staff actually do.

The pattern is the same as in most control problems: the rule exists on paper, practice differs by location, and nobody measures the gap.

What changes it

Start with the operating fix, before any software.

  • Decide who is accountable for personal data in the business, by name, with authority to refuse a new form or register.
  • Make a short inventory: what personal data you collect, at which step, for which purpose, and where it is stored.
  • Stop collecting what no process uses. Every field you drop is a field you need not protect.
  • Write one customer-facing notice that matches what you really do, and one internal rule for handling a request to see or delete data, with a time limit.
  • Review the inventory every quarter, in the same meeting that reviews other controls.

Then systems help. When customer details live in one place instead of 180, a request takes minutes. Consent can be recorded with a date. Access can be limited by role, so a counter salesperson cannot export the full customer list. Deletion becomes reliable, because a person no longer has to remember every copy.

What this does not fix

None of this tells you what the law requires of your particular business, and it does not replace legal advice. It will not undo past collection done without a clear purpose. And a tidy inventory goes stale within months if nobody owns it. The aim is control you can describe, not a certificate.

Compliance grows with scale in a predictable way. A handful of locations can be managed by hand, fifty is difficult, and two hundred needs a system. If you are somewhere in that range, see how DealerPlus approaches control and compliance as you grow.