Home/DPDP guides by business/Housing societies and RWAs
DPDP guide · Housing societies, RWAs, apartment associations

Your society knows a lot about its residents. The DPDP Act now has a say.

Gate apps photograph every visitor. Committees keep tenant forms, Aadhaar copies of maids and drivers, vehicle numbers and phone numbers of every family. Most of it sits in apps, spreadsheets and WhatsApp groups. This guide explains what the DPDP Act asks of a housing society, and what a managing committee can do about it without spending much.

Does the DPDP Act apply to a housing society or RWA?

Yes. The Act applies to any "person" that decides why and how personal data is processed, and its definition of person includes an association of persons or a body of individuals, whether registered or not (Section 2(s)). A cooperative housing society, a registered RWA and an apartment owners' association all fit. The exemption for personal and domestic use covers individuals only, so it does not help a society.

From 13 May 2027 your society must give residents, tenants, staff and visitors a clear notice of what it collects, use the data only for the purposes it was collected for, keep it secure, report breaches, answer requests and delete what it no longer needs. The managing committee runs this on the society's behalf. A society does not normally need a Data Protection Officer, but it does need a named contact for privacy questions.

Last reviewed by the Decipher compliance practice.

Where a society collects personal data

Walk through one day at a large society. At 6 a.m. the domestic help and drivers check in through the gate app, which knows their names, photos and the flats they work in. A courier arrives, and the guard types his name and phone number and takes his photo. The app sends an approval request to a resident. At 10 a.m. a new tenant hands the office a rent agreement, ID proofs and a filled police verification form. At noon the secretary posts the list of maintenance defaulters, with flat numbers and amounts, in the residents' WhatsApp group of 600 people.

In the evening, children sign up for the summer camp and parents send their names, ages and photos. The CCTV in the lifts and the parking keeps recording. The office laptop holds an Excel sheet of every owner's name, phone, email and flat number going back ten years.

That is a large amount of personal data, about people who live together and see each other every day. A leak inside a society can be more harmful than a leak from a faraway company.

Member and owner register Names, flat numbers, phone numbers, emails, share certificates and sometimes copies of sale deeds.
Tenant records Rent agreements, ID proofs and police verification forms for tenants and their families.
Visitor and gate apps Visitor names, phone numbers, photos, vehicle numbers and the time of each entry and exit.
Domestic staff and drivers Names, photos, ID proofs, addresses, police verification and the list of flats each person works in.
Society employees Guards, housekeeping, plumbers and office staff: KYC, bank details, salary and attendance, often through an agency.
CCTV Cameras at gates, lifts, corridors, parking and play areas, with footage kept on a recorder or in the cloud.
WhatsApp groups Every resident's phone number visible to every member, plus photos, complaints and notices.
Maintenance and accounts Dues, payments, bank details and defaulter lists in accounting software or spreadsheets.
Amenities and events Clubhouse, gym and pool registrations, summer camps and festivals, often with children's details and photos.
Parking and vehicles Vehicle numbers linked to flats and phone numbers, sometimes printed on stickers anyone can read.

One point worth knowing: the Act covers personal data in digital form, and paper records once they are digitised (Section 3). A handwritten visitor register at the gate is outside it. The moment the guard photographs that page, or the office types it into a sheet, the digital copy is covered.

How the DPDP Act applies to a housing society

The society is the Data Fiduciary

The society, acting through its managing committee, decides why resident and visitor data is collected and how it is used. That makes the society the Data Fiduciary (Section 2(i)). Committee members change every year or two. The society's duties do not. A new committee inherits the data, and the responsibility for it, from the old one.

The gate app company, the accounting software, the security agency and the CCTV vendor are usually your Data Processors. You may use them only under a contract (Section 8(2)), and the society stays responsible for what they do with residents' data (Section 8(1)). Read your gate app's terms carefully. If the app also uses resident data for its own purposes, such as advertising to residents, then for that use the app is acting on its own account, and your residents should be told.

What a society can do without fresh consent

Many society tasks fall under the "legitimate uses" in Section 7. When a resident gives their phone number so the gate can call them about a visitor, the society can use it for that purpose (Section 7(a)). Where a law or a lawful order requires tenant or domestic staff details to be shared with the police, sharing them for that purpose is covered by the legitimate uses for meeting a legal duty to disclose information to the State and for complying with lawful orders (Sections 7(d) and 7(e)). Data of the society's own employees can be used for employment purposes (Section 7(i)).

What these uses do not cover is spreading data further than the purpose needs. A phone number given for gate approvals is not consent to be added to a vendor's marketing list. A police verification form collected for one tenant does not need to sit in an open folder for years after the tenant has left.

WhatsApp groups and defaulter lists

The Act does not ban WhatsApp groups. But a society group shows every member's number to every other member, and it is often the place where personal details get shared most freely. Use announcement-only groups for notices, keep complaints about individual flats out of large groups and never post ID proofs or police forms there.

Defaulter lists need care. Your bye-laws may allow the committee to notify members about unpaid dues, but publishing names, phone numbers and amounts to hundreds of people goes beyond what recovery needs. Share such details only with the people who have to act on them, in the way your bye-laws allow.

Notice, children and CCTV

Where the society asks for consent, for example for photos of events or a residents' directory, give a short notice first (Section 5 and Rule 3). It must say what you collect, why, how to withdraw consent and how to complain. Children's data, such as summer camp forms and event photos of children, needs verifiable consent from a parent (Section 9 and Rule 10).

CCTV in common areas records identifiable people, so the footage is personal data. The Act has no general "legitimate interest" ground like Europe's GDPR, so the legal basis for recording residents and visitors is not fully settled yet. Until there is guidance, put clear notices at entrances, keep cameras out of private spaces, set a short retention period and allow only a few named people to view or copy footage.

Security, breaches and deletion

Section 8(5) and Rule 6 require reasonable security. For a society, that means the office laptop has a password and is backed up, the gate app has proper logins for each guard, former committee members lose access when their term ends, and logs are kept for a year. If resident data leaks, the society must inform the affected people and the Data Protection Board (Section 8(6)). Rule 7 asks for a first report without delay and a detailed one within 72 hours.

Delete data once its purpose is over (Section 8(7)), unless a law requires you to keep it. Records the society's own laws and audit rules require, such as accounts and member registers, stay. Visitor photos from two years ago and the files of tenants who left long ago usually do not need to.

The dates

The DPDP Rules were notified in November 2025. Most duties, including notice, consent, security, breach reporting and penalties, apply from 13 May 2027. That gives a committee enough time to clean up, if it starts this year.

What can go wrong in a society

The penalty figures in the Act are maximums written for all of India. The Board will look at what actually happened and what the society did about it (Section 33(2)). A society that can show it thought about residents' data, set rules and followed them is in a very different position from one that did nothing.

The more likely problems are close to home. A resident is harassed after their number is shared in a group. A guard's phone with the gate app is lost. A tenant's police verification form is found in a dustbin. Domestic staff photos and addresses circulate on WhatsApp after a theft rumour. From May 2027 any of these can become a complaint to the Board, and inside a society the damage to trust is immediate.

Duty you could breakMaximum penaltyHow it could happen to you
Reasonable security safeguards, Section 8(5) Up to Rs 250 crore The owner register sits on an unlocked office laptop, or ex-committee members still have admin access to the gate app.
Breach intimation, Section 8(6) Up to Rs 200 crore Resident data leaks through a vendor and the committee decides to keep quiet.
Children's data, Section 9 Up to Rs 200 crore Children's photos and details from a camp are posted publicly without parents' consent.
Other duties: notice, purpose, erasure, grievances Up to Rs 50 crore Resident numbers shared with vendors for marketing, defaulter details posted widely, or a request to delete old data ignored.

These are the upper limits in the Schedule to the Act. The Board decides the actual amount after looking at how serious the breach was, how long it lasted, the type of data, whether it was repeated and what you did to limit the harm (Section 33(2)).

What a managing committee can do

Most of this costs time, not money. The steps below can be shared between two or three committee members and finished over a few monthly meetings. Record the decisions in your minutes, so that the next committee knows what was agreed and why.

1

Take stock

Sections 2(i) and 8(1)
List every place the society holds personal data: registers, tenant files, gate app, CCTV, accounts, WhatsApp groups, amenity and event forms.
Note what is collected, why, where it is stored and who can see it.
Name one committee member who looks after data protection and record it in the minutes.
2

Sort out your vendors

Section 8(2)
Read the terms of your gate app, accounting software and CCTV cloud, and check what they do with resident data.
Make sure each vendor contract covers security, confidentiality and deletion of data when the contract ends.
Ask the security agency how it handles guard KYC and what it does with visitor data.
3

Collect less and share less

Sections 6(1), 7 and 8(7)
Stop collecting documents you do not need. Keep police verification forms only for as long as a lawful order or the purpose requires.
Move notices to announcement-only WhatsApp groups and keep ID proofs and police forms out of all groups.
Share defaulter details only with the people who need to act, as your bye-laws allow.
Remove phone numbers from vehicle stickers. A flat number or code is enough.
4

Secure what you keep

Section 8(5) · Rule 6
Password-protect the office computer and back it up.
Give every guard and staff member their own login on the gate app.
Remove access for outgoing committee members and staff on the day they leave.
Keep CCTV recorders locked, set a retention period and list who may view footage.
5

Notices and children

Sections 5 and 9 · Rules 3 and 10
Put a short notice at the gate and in the gate app explaining what visitor data is collected and why.
Use a consent form for event photos and residents' directories.
Take children's details for camps and events from parents, with their consent, and do not post children's photos publicly without it.
6

Be ready for questions and problems

Sections 8(6), 8(9), 8(10) and 13 · Rules 7 and 14
Publish the email of the society's privacy contact on the notice board and in the gate app.
Keep a simple log of requests to see, correct or delete data and close each one well inside 90 days.
Agree who will inform residents and report to the Board within 72 hours if data leaks.
Delete visitor records, old tenant files and CCTV footage on a fixed schedule.
Free · one page · printable

The DPDP checklist for housing societies.

Every step above on one printable page, with tick boxes. Pin it up in the office, or hand it to the person who looks after your data. We email you the link, and a short note when the rules change.

We use your email only to send the checklist and occasional DPDP updates. One click to unsubscribe. See our privacy policy.
DCOMPLY · CHECKLIST
DPDP Act checklist: Housing societies
6 sections, 21 tick boxes, with the section or rule behind each one.
Reviewed 18 November 2026

How dcomply can help

Most committees can work through this checklist themselves. Large townships, federations of societies and facility management companies that run many societies often want outside help, because they handle data for thousands of residents across several vendors.

In a DPDP Readiness engagement we map resident, staff and visitor data across your gate app, accounts and CCTV, write your notices and consent forms, review vendor contracts and give the committee a clear plan with owners and dates. A named practice lead works with your committee from the first meeting to sign-off.

DPDP Readiness starts at Rs 49,999 plus GST, a fixed fee for two weeks of work. See all prices.

Request a scope → Ask a free question

Questions housing societies ask us

Q 01

Is our RWA really covered? We are not a company.

Yes. The Act's definition of "person" includes an association of persons or a body of individuals, whether incorporated or not (Section 2(s)). The exemption for personal or domestic use applies to individuals, not to societies.

Q 02

Who is responsible: the society or the committee members?

The society is the Data Fiduciary. The managing committee acts on its behalf and should record decisions on data protection in its minutes, so that responsibility passes cleanly to the next committee.

Q 03

Can we still use a visitor management app?

Yes. Treat the app company as your Data Processor, read its terms, make sure the contract covers security and deletion, and tell residents and visitors what the app collects and why.

Q 04

Can we ask tenants for police verification?

Where a law or a lawful police order in your city requires it, collecting and sharing those details for that purpose is covered. Keep the forms secure and do not hold them for longer than needed.

Q 05

Can we post a list of maintenance defaulters?

Handle it carefully. Share details only with the people who need to act on them, as your bye-laws allow. Posting names, numbers and amounts to hundreds of residents goes beyond what recovering dues requires.

Q 06

Do we need a Data Protection Officer?

Almost certainly not. A DPO is needed only by Significant Data Fiduciaries notified by the government. You do need a named contact who can answer residents' questions about their data (Section 8(9)).

Q 07

When must we be ready?

Most duties apply from 13 May 2027. A committee that starts now can finish the work over a few meetings.

Where these facts come from

Primary sources, checked on 18 November 2026. This guide explains the law in plain words. It is not legal advice for your specific situation.

Last reviewed by the Decipher compliance practice.