DPDP for housing societies and RWAs
A society is not a business, but it holds a great deal of personal data: owners, tenants and their families, visitors, domestic staff and vendors. The Act’s exclusion for personal or domestic use covers individuals, not associations. And the people responsible change every time a new committee is elected.
Not every society holds the same data
A ten-flat building with a paper register and one watchman is very different from a gated township with a gate app, number-plate cameras, a clubhouse and a facility management company. This guide marks the parts that apply only where the society does that thing.
The Act applies to personal data in digital form, and to paper records once they are digitised (s. 3). A paper visitor book is outside it until someone photographs or types it up. Most societies now have at least a WhatsApp group and a spreadsheet, which are digital from the start.
- Every society
- The resident register, maintenance dues and the committee’s hand-over.
- Where the society runs WhatsApp or other groups, or employs or registers staff
- Group membership and what is posted; staff ID copies and their deletion.
- Where the society uses a gate or visitor app
- Visitor photographs and logs, guards’ devices, and the app provider’s terms.
- Where CCTV or number-plate cameras are installed
- Signage, named viewers, overwrite periods and requests for footage.
- Where biometric entry or staff attendance is used
- Templates rather than images, and an alternative for those who decline.
- Where a facility management company or security agency is engaged
- Written data terms and hand-back of registers when they are replaced.
The society is the fiduciary, not the secretary
When the register lives in a committee member’s personal email, phone or spreadsheet, the society loses control of it at every election. Keep registers, app administration, CCTV access and group admin rights in accounts the society owns, with a hand-over checklist: new office-bearers get access, outgoing ones lose it, and the change is recorded.
Collecting dues is a legitimate purpose. Posting defaulters’ names in groups or on notice boards goes well beyond what collecting dues needs, and it is a frequent cause of complaints.
Members often have rights under the society’s bye-laws and state co-operative or apartment ownership laws to inspect certain records. Give access to what those rules allow, and no more. Under legal review: Members’ inspection rights depend on the state law and bye-laws that apply to each society.
- Hand over
- Register files, app admin rights, CCTV passwords, group admin, billing software.
- Remove
- Outgoing members’ access the same day, and copies on personal devices.
The three roles, in a worked case
The Act gives three roles. The Data Principal is the person the data is about. The Data Fiduciary decides why and how it is used, and carries the duties. A Data Processor handles it on the fiduciary’s behalf, under a contract. The same business can be a fiduciary for some data and a processor for other data.
The case
Mr Iyer rents a flat in a gated society. His cook enters daily through the gate app, which photographs her. The society employs a security agency through a facility management company and pays a software company for the gate app.
| Role under the Act | In this case |
|---|---|
| Data Principal | Mr Iyer, his family members, and his cook. Each is a Data Principal for their own data. The flat’s owner is a Data Principal too, for the owner records. |
| Data Fiduciary | The housing society, acting through its managing committee. |
| Data Processor | The gate-app company, the facility management company and the security agency, each acting on the society’s instructions. |
If the gate-app company used visitor data to sell services to residents, it would be deciding its own purpose and become a fiduciary for that use. A smaller society without a gate app has no such provider: its guards and paper register are its own.
What a housing society holds, and where it goes
| Kind of data | Examples |
|---|---|
| Owners, tenants and families | Names, flat numbers, phone numbers, family members including children, vehicle numbers, rent agreements |
| Financial | Maintenance dues, payment records, bank details for collections |
| Visitors and deliveries | Names, phone numbers, photographs, vehicle numbers, purpose of visit |
| Domestic staff, drivers and vendors | Names, photographs, ID copies, police verification, attendance |
| Visual and biometric | CCTV, number-plate camera records, fingerprint or face templates |
| Committee records | Minutes, complaints, notices, correspondence with members |
Where it comes in
- Move-in, tenant and staff registration forms
- Maintenance billing and payment collection
- Society WhatsApp groups and notice boards
- Gate and visitor-management apps (where used)
- CCTV and number-plate cameras (where installed)
- Biometric entry or attendance devices (where used)
Where it goes
| From | To | What and why |
|---|---|---|
| Resident | Society office or committee | Move-in form, family and vehicle details |
| Visitor | Gate app provider | Name, number and photograph at entry |
| Society | Facility manager and security agency | Resident list and staff details for gate checks |
| Committee | WhatsApp group | Notices, sometimes dues and defaulter names |
| Society | Police | Tenant and staff verification |
| Society | Billing software and bank | Dues, receipts and payment records |
Where housing societies are most exposed
| Severity | Risk | Why it matters |
|---|---|---|
| High | Defaulter lists posted in groups or on notice boards | Shames individuals and goes well beyond what collecting dues needs. |
| High | Register held in a member’s personal account | The society cannot recover or secure it after the committee changes. |
| High | Gate app with no written terms | Visitor photographs and logs held by a provider bound by nothing. Applies where a gate app is used. |
| Medium | Staff ID copies kept after they leave | Identity documents of people no longer working in the society. |
| Medium | CCTV footage viewed and forwarded freely | Clips shared in groups without control. Applies where CCTV is installed. |
| Medium | Resident lists given to vendors and builders | Numbers passed on for sales calls the residents never agreed to. |
Who else handles the data
You answer for what your processors do with the data (s. 8(1)), and you need a valid contract with each (s. 8(2)). Some vendors are fiduciaries in their own right; the table says where that is common.
| Vendor | Data they handle | What the contract should cover |
|---|---|---|
| Gate and visitor-management app | Residents, visitors, staff, photographs | Written data terms; visitor log retention; who sees what |
| Facility management company and security agency | Resident lists, visitor entries, CCTV | Confidentiality; no copies on guards’ phones; hand-back when replaced |
| Accounting and billing software | Dues, payments, contact details | Access for office-bearers only; hand-over at elections |
| CCTV and biometric system contractors | Footage, templates and system access | Access only for repairs; no copying |
43 controls written for housing societies, on top of 66 common ones
Alongside the common controls, the housing society assessment asks about the register and the committee first, then about the systems around them: CCTV, service providers, staff records, WhatsApp groups and dues. It asks early on whether the society has CCTV, uses outside providers such as a facility manager or security agency, or uses a gate app, biometric devices or number-plate cameras; for anything the society does not have, the questions about it are not asked and do not count.
| Module | What is checked |
|---|---|
| Organisation and role mapping |
|
| Data inventory and purpose |
|
| Notice and transparency |
|
| Consent and lawful basis |
|
| Data Principal rights |
|
| Children and guardians |
|
| Data quality |
|
| Retention and deletion |
|
| Security safeguards |
|
| Breach response |
|
| Processors and vendors |
|
| Data sharing and disclosure |
|
| Transfer and storage location |
|
| Records and evidence |
|
| Access control |
|
| Incident testing |
|
| Policy and training |
|
Six of the questions you will be asked
Questions ask what you actually do, not whether you have a policy. Each answer maps to one control.
-
RWA-01 Critical
Is the resident register kept in the society's own accounts, with a set process to hand it to the next committee and remove it from outgoing members' devices?
Why it is asked: Data on personal devices of outgoing members leaves the society's control.
-
RWA-02 High
Do you avoid sharing lists of defaulters or dues in group chats and on notice boards?
Why it is asked: Publishing dues goes beyond the purpose of collecting them and can harm the resident.
-
RWA-03 High
Is your gate or visitor-management app provider bound by written data terms, including how long visitor records are kept?
Why it is asked: The app provider processes residents' and visitors' data for the society.
-
RWA-04 Medium
Are there CCTV notices at entrances, with footage viewable only by named people and overwritten after a set period?
Why it is asked: Footage of residents, staff and visitors is personal data; it must be protected and kept only as long as needed.
-
RWA-05 High
Are domestic staff and driver ID documents stored securely and deleted when they stop working in the society?
Why it is asked: Staff ID copies are rarely protected and often kept long after the person has left.
-
RWA-30 High
Do you refuse to share resident lists or numbers with vendors, builders, service providers or campaigners for their own use without residents' consent?
Why it is asked: Each recipient using the data for its own purposes needs a basis.
All 43 questions written for housing societies
- RWA-08 Have you agreed in writing with your facility management company, security agency and community app provider who decides how residents' data is used, and that they act only for the society?
- RWA-09 Have you identified every group whose data the society holds: owners, tenants, family members including children, domestic staff, drivers, visitors, delivery workers and vendors' staff?
- RWA-10 Do move-in, tenant and domestic-staff forms ask only for what the society needs, without religion, full family histories, or ID copies of every family member unless a local order requires them?
- RWA-11 Do you know where old society data sits: previous committees' spreadsheets and phones, old visitor books, paper registers and old email accounts?
- RWA-07 Have residents been given a short notice explaining what data the society holds, why, and whom to ask about it?
- RWA-04 Are there CCTV notices at entrances, with footage viewable only by named people and overwritten after a set period?
- RWA-12 Are visitors and delivery workers told, at the gate, what is recorded (name, number, photograph, vehicle) and why?
- RWA-06 Do residents know that their number is visible to every member of society WhatsApp groups, and can they join without exposing it?
- RWA-13 Are residents listed in a printed or app directory only if they agreed, with the choice of what to show?
- RWA-14 Are photographs from society events shared on groups or social media only where those shown agreed, with a way to ask for removal?
- RWA-15 Can residents, staff and visitors ask to see, correct or delete their data, with requests tracked so they are not lost when the committee changes?
- RWA-17 Are children's details (names, photographs, school timings, who may collect them) kept to what safety needs and seen only by security staff who need them?
- RWA-18 Before charging penalties or restricting facilities for unpaid dues, do you check the records and give the resident a chance to correct errors?
- RWA-19 When residents move out or details change, are the gate app, guards' lists and facility manager updated?
- RWA-20 After residents or tenants move out and dues are settled, is their data deleted except what society records must keep?
- RWA-05 Are domestic staff and driver ID documents stored securely and deleted when they stop working in the society?
- RWA-21 Are visitor records in gate registers and apps deleted after a set short period?
- RWA-22 Are CCTV recorders, gate tablets and committee laptops wiped before disposal, return or repair?
- RWA-23 Are resident and staff records kept in password-protected, encrypted storage, with identity numbers masked?
- RWA-24 Is the CCTV recorder in a locked place, with its default password changed and remote viewing limited to named people?
- RWA-25 Are lost access cards deactivated at once, cards of departed residents and staff cancelled, and entry logs protected?
- RWA-43 Is biometric data used only for attendance or entry, stored as templates by the device, with an alternative offered, and deleted when people leave?
- RWA-44 Are vehicle numbers and number-plate camera records used only for parking and entry, visible only to security, and deleted after a set period?
- RWA-26 If CCTV footage, the resident register or staff records are shared without authority, is it logged and notified to the Board and the people affected?
- RWA-27 Are your facility management company, security agency and billing software provider bound by written data terms?
- RWA-28 Do contracts require providers to report breaches at once and, when replaced, hand back visitor registers, staff records and footage and delete their copies?
- RWA-29 Before appointing a provider who will see residents' data, does the committee check how it protects data and who will access it?
- RWA-03 Is your gate or visitor-management app provider bound by written data terms, including how long visitor records are kept?
- RWA-42 Are the guards' gate devices locked with a PIN, with guards able to see only visitor entries and not residents' full profiles?
- RWA-02 Do you avoid sharing lists of defaulters or dues in group chats and on notice boards?
- RWA-30 Do you refuse to share resident lists or numbers with vendors, builders, service providers or campaigners for their own use without residents' consent?
- RWA-31 Does the society record when residents' or staff data is given to outside parties, such as the police, municipal bodies or providers?
- RWA-32 Are requests for residents', staff or visitors' data, or footage, from police and municipal bodies made in writing, checked by a named office-bearer, limited and logged?
- RWA-16 When members ask to inspect society registers or records, do you give access only to what the bye-laws allow, without exposing other residents' personal details beyond that?
- RWA-33 Do you know where the society's app, billing software, email and cloud storage keep data?
- RWA-34 Where society tools store data outside India, has the country been checked against any government restriction?
- RWA-35 Are residents' consents, the disclosure log and committee decisions about data kept in society accounts and handed to each new committee?
- RWA-01 Is the resident register kept in the society's own accounts, with a set process to hand it to the next committee and remove it from outgoing members' devices?
- RWA-36 Can each office-bearer, the manager and guards see only the records their role needs (for example, the treasurer billing, guards visitor entries)?
- RWA-37 Is two-step sign-in turned on for the society email, app admin and billing accounts?
- RWA-38 Is access to society accounts, the app and CCTV reviewed when the committee changes and at least yearly?
- RWA-39 Is there a written policy covering groups, footage, registers, staff records and requests from residents?
- RWA-40 Are guards, managers and helpdesk staff briefed not to give residents' details, flat numbers or movements to callers and visitors?
Evidence that may be asked for
A “yes” is self-declared until something shows it. These are the documents and records that usually do. Your own result lists what each control needs.
- A short privacy notice given to residents and displayed at the gate
- Register held in a society-owned account, with the access list
- Hand-over checklist from the last election
- Data terms with the gate-app provider, facility manager and security agency
- CCTV signage, named viewers and the overwrite period
- Rule for deleting domestic staff records after they leave
- Committee resolution adopting these practices
What makes evidence good enough · How the Evidence Room keeps it
First actions, in the order they usually make sense
Stop posting defaulter names in groups and on boards
Move the register, app admin and billing to society-owned accounts
Sign data terms with the gate app, facility manager and security agency
Display CCTV notices and name who may view footage
Give residents a one-page privacy notice
Run the hand-over checklist at every election
Your own result orders these by your answers and the law’s dates. How to plan remediation.
The reports a housing society usually needs
A society’s result is read by the managing committee and, often, by members at the general body meeting.
| Report | Who reads it | What it shows |
|---|---|---|
| Executive and Board Summary | The managing committee and the general body | A one-page view of where the society stands, suitable for the AGM, without naming any resident. |
| Remediation Report | The secretary, treasurer and facility manager | Each gap as a task with an owner, carried across committees through the hand-over. |
| Free Readiness Report | A committee deciding whether to act | The free result, printed, for a first discussion. |
Start the housing society readiness check
The 43 questions above, plus the common ones, answered in your browser. You see your gaps, their severity and your first actions straight away. It is free and needs no account.
The law behind the housing society controls
Every section of the Act and rule of the Rules that the housing society controls rely on. Read them in plain language in the DPDP Act and the DPDP Rules guides, or in the official text linked from those pages.
Digital Personal Data Protection Act, 2023
| Section | About | Parts cited |
|---|---|---|
| s. 2 | Definitions | s. 2(i) s. 2(j) s. 2(k) |
| s. 4 | Grounds for processing | s. 4(1) |
| s. 5 | Notice | s. 5(1) s. 5(1)(i) s. 5(2) |
| s. 6 | Consent | s. 6(1) s. 6(4) s. 6(10) |
| s. 7 | Certain legitimate uses | s. 7(d) s. 7(e) |
| s. 8 | General duties of the Data Fiduciary | s. 8(1) s. 8(2) s. 8(3)(a) s. 8(3)(b) s. 8(4) s. 8(5) s. 8(6) s. 8(7)(a) s. 8(7)(b) |
| s. 9 | Children's data | s. 9(2) |
| s. 11 | Right to information | s. 11(1) s. 11(1)(b) |
| s. 12 | Right to correction and erasure | s. 12(1) |
| s. 16 | Transfer outside India | s. 16(1) s. 16(2) |
| s. 17 | Exemptions | s. 17(1)(c) |
Digital Personal Data Protection Rules, 2025
| Rule | About | Parts cited |
|---|---|---|
| r. 3 | Notice | r. 3 |
| r. 6 | Reasonable security safeguards | r. 6(1)(a) r. 6(1)(b) r. 6(1)(c) r. 6(1)(f) r. 6(1)(g) |
| r. 7 | Breach intimation | r. 7(1) r. 7(2) r. 7(2)(b) |
| r. 14 | Rights of Data Principals | r. 14(1) r. 14(3) |
| r. 15 | Transfer outside India | r. 15 |