By organisation · Small and medium businesses

A structured start, without a dedicated privacy team

Most smaller businesses know they hold personal data and are unsure what the Act expects of them. ControlMap turns that into a list of specific things to check, each with its reference.

Your role under the Act

A Data Fiduciary, whatever the size of the business

A business that decides why and how it collects customer or employee data is a Data Fiduciary. The Act does not set a general exemption for small businesses.

Section 17(3) allows the Central Government to notify certain Data Fiduciaries or classes of them, including startups, to whom some provisions will not apply. Check whether a notification covers your business. Do not assume one does.

Guide: Data Fiduciary or Data Processor

Challenges

What makes this hard

  • No one owns privacy

    The work falls to a founder, an operations lead or an IT administrator, alongside everything else.

  • Data spread across tools

    Customer data sits in a CRM, a helpdesk, spreadsheets and payment tools that nobody has listed in one place.

  • A notice copied from elsewhere

    The privacy notice came from a template and does not describe what the business actually collects or why.

  • Vendors chosen for convenience

    Service providers handle customer data under standard terms that were never read with data protection in mind.

  • No clear first step

    The Act is short, but turning it into a work plan without help is hard.

  • Questions from larger customers

    Enterprise customers send data protection questionnaires that take days to answer from memory.

Relevant DPDP obligations

What the Act and the Rules say

These provisions apply to Data Fiduciaries generally. They are summaries; the full list is on the DPDP Act page.

Section 4

A ground for processing

Personal data may be processed only for a lawful purpose, either with the consent of the Data Principal or for one of the certain legitimate uses in Section 7.

Section 5 · Rule 3

A notice with every request for consent

The notice is to be understandable on its own and to set out, in clear and plain language, an itemised description of the personal data and the specified purpose of the processing.

Section 6

Consent that can be withdrawn

Consent is to be free, specific, informed, unconditional and unambiguous, with a clear affirmative action. Withdrawing it is to be as easy as giving it.

Section 8(5) · Rule 6

Reasonable security safeguards

Personal data is to be protected by reasonable security safeguards, including for processing carried out by a Data Processor.

Section 8(6) · Rule 7

Breach intimation

On a personal data breach, the Data Fiduciary intimates the Board and each affected Data Principal.

Section 8(9), 8(10) · Rule 9

A contact and a grievance mechanism

The business publishes the contact information of a person who can answer questions about processing, and keeps an effective mechanism to redress grievances.

These are summaries for orientation, not legal advice. Whether a provision applies to you depends on your facts. The DPDP Act page sets out the provisions more fully, says when each comes into force and links to the official text.

Typical workflow

How the work usually runs

A sequence that works for a small team with limited time.

  1. List what you hold

    Record each dataset, the system it sits in and who looks after it. The coverage score shows how much is still unknown.

  2. Write down why

    Give each dataset a purpose, a processing basis and a retention period.

  3. Review what people see

    Check the notice against Section 5 and Rule 3, and record how consent is asked for and withdrawn.

  4. Work through the controls

    Answer the catalogue's questions one module at a time and note what evidence exists.

  5. Track what is open

    Give each finding an owner and a due date, and close it when the work is done.

Data Discovery and Inventory summary: an inventory coverage score, the number of known and scanned systems, and counts of records with unclassified data or with no owner, purpose or retention period.
Product screenshot. The organisation and records shown are sample data that ships with ControlMap.

Implementation approach

Three phases, in your own time

The order matters more than the pace. How long each phase takes depends on how many systems you have and who is available to do the work.

  1. First

    Know what you hold

    Build the inventory for the systems that hold customer and employee data, and name an owner for each.

  2. Next

    Fix what Data Principals see

    Bring the notice, the consent request, the published contact and the grievance route into line with the Act.

  3. Ongoing

    Assess and maintain

    Work through the remaining controls, record evidence, and review the record when systems or vendors change.

Benefits

What you have at the end

ControlMap supports the work of governance. Meeting the Act's requirements remains the responsibility of your organisation.

  • A defined place to start, and an order in which to continue.
  • Each question carries its section or rule, so you can read the source yourself.
  • Work is split into small items that can be assigned and closed.
  • A current record to answer from when a customer or partner asks how you handle personal data.

See where a smaller business would begin.

We will walk through the modules on this page with the product's sample data and answer what they do and do not cover.