Different work · Different data · Different risks

DPDP compliance looks different across industries

A school, a clinic and an online store do not collect the same information, serve the same people or rely on the same systems. The DPDP Act provides a shared framework, but the actual compliance work depends on each organisation’s purposes, data flows, role, scale and other laws that apply.

Start with the way your organisation works. A generic checklist can miss the point where a sector-specific rule, child-data safeguard, vendor relationship or retention duty changes the answer.

01 · The context matters

Same Act, different data journeys

Organisations have common responsibilities under the Act, but how they meet them depends on the data they process and why. A useful assessment follows a person’s data from collection through use, sharing, retention and deletion.

  • People and age: a school or edtech platform may process children’s data; an employer handles candidate and staff information; a housing society deals with residents, visitors and domestic workers.
  • Purpose and context: a hospital supports care; a lender evaluates and services credit; a hotel manages reservations, identity checks and guest services.
  • Vendors and roles: SaaS businesses may act as processors for customers and as Data Fiduciaries for their own accounts, billing and support.
  • Other rules: sector regulations may impose additional safeguards, records or retention periods alongside DPDP duties.
  • Scale and designation: some duties depend on whether an organisation is notified as a Significant Data Fiduciary or falls into a class named in the Rules.

The DPDP Act does not create a simple list of “regulated” and “unregulated” industries. Map each activity, role and applicable exception before deciding what controls are needed.

02 · A few practical differences

What changes from one sector to another?

These examples show why teams should tailor the work. They are starting points, not exhaustive sector legal advice.

Education and healthcare

Children, students and patients

Schools and edtech providers should examine parent verification, age-appropriate journeys and limited child-data exemptions. Healthcare teams need to map care, appointments, reports, referrals and access among providers.

Finance and commerce

Identity, transactions and records

NBFCs and insurers connect data to onboarding, eligibility, servicing and claims. Retailers handle checkout, marketing choices, customer support and account erasure alongside transaction records.

Workplaces and platforms

Multiple roles and many systems

HR teams coordinate candidate and employee data across hiring, payroll and benefits. SaaS providers must distinguish customer processing from their own product, billing and support uses.

03 · Explore the sectors

All industry-specific DPDP guides

Choose the guide closest to your organisation. Many businesses work across more than one category.

Schools

Student records, parent consent, learning apps, transport and school communications.

Read the schools guide →

Colleges and universities

Admissions, student services, alumni, placements, research systems and campus vendors.

Read the colleges guide →

Coaching institutes

Enrolment, exam preparation, minors, parent communication and online classes.

Read the coaching guide →

Edtech platforms

Accounts, learning analytics, age checks, child safeguards and education partners.

Read the edtech guide →

Hospitals

Patient journeys, clinical systems, appointments, care teams, insurers and processors.

Read the hospitals guide →

Clinics and doctors

Consultations, appointment reminders, patient communications and practice tools.

Read the clinics guide →

Diagnostic laboratories

Test bookings, sample tracking, reports, referrals and result delivery.

Read the diagnostic labs guide →

E-commerce and D2C

Checkout, fulfilment, marketing, support, loyalty data and inactive accounts.

Read the e-commerce guide →

Real estate

Lead forms, site visits, buyer records, tenant services and broker sharing.

Read the real estate guide →

NBFCs and fintech

Borrower onboarding, credit journeys, servicing, recovery and financial-sector duties.

Read the NBFC guide →

Insurance

Proposals, policy administration, claims, agents, health details and service partners.

Read the insurance guide →

Hotels and travel

Reservations, guest identity, preferences, payments and booking channels.

Read the hotels guide →

HR and recruitment

Applicant pipelines, background checks, employee systems and benefits.

Read the HR guide →

SaaS and IT services

Processor commitments, product telemetry, customer support and sub-processors.

Read the SaaS guide →

Gyms and fitness studios

Memberships, attendance, wellness programmes, payments and member communications.

Read the gyms guide →

Housing societies and RWAs

Resident directories, visitor logs, CCTV, facility access and community apps.

Read the housing guide →

NGOs, trusts and nonprofits

Beneficiaries, donors, volunteers, field teams and programme partners.

Read the nonprofit guide →

Restaurants and cafés

Reservations, delivery, loyalty, payment systems and guest feedback.

Read the restaurant guide →

04 · A practical first pass

Start with your own data map

Pick one customer or service journey and document what information is collected, the purpose, who can access it, which providers receive it and when it should be reviewed or erased.

Use the common foundation

Review notices, consent, safeguards, rights, grievance handling, retention and processor arrangements with a named owner.

Add sector-specific checks

Layer in child-data rules, industry records, existing regulations, contractual duties and the actual systems your teams use.

Continue with the DPDP compliance checklist, Rules guide or website readiness check.

Find the guide that matches your work

Explore your sector’s data flows, then turn the common requirements into an owned plan.