Compliance
DPDP and Your Visitor Register: What Offices and Plants Must Change Before May 2027
By VizTrak Team · 15 October 2026 · 11 min read
Walk up to the security cabin of almost any office or factory in India and you will find it. A thick register with a green or maroon cover, a pen tied to it with string, and columns for name, mobile number, company, whom to meet, time in, time out and signature. Many sites also ask for an ID number. Some ask the guard to keep a photocopy of the visitor's Aadhaar, "just in case".
That register has worked for decades because nobody asked hard questions about it. The Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025 are now asking them. Every line in that book is personal data, and the organisation that owns the premises is answerable for it.
This guide is for admin heads, security managers, plant HR and compliance teams who want a plain answer to two questions: what has to change at the gate and the reception desk, and by when.
The short version
The DPDP duties that matter at the front desk (notice, security safeguards, breach reporting and data principal rights) apply from May 2027. The Rules were notified in November 2025.
Your organisation is responsible for visitor data, even when an outside security agency runs the gate.
An open paper register falls short on notice, minimisation, security and retention.
Most sites collect far more than they need. Full ID numbers, home addresses and ID photocopies can usually go.
Pick a retention period, write it down and delete on schedule.
Where the DPDP timeline stands today
The Act was passed in August 2023 but stayed largely on paper until the Ministry of Electronics and IT notified the DPDP Rules in November 2025. The Rules come into force in three stages:
StageWhenWhat it coversImmediateNovember 2025Data Protection Board of India set up, definitions and Board procedures in force12 monthsNovember 2026Registration framework for consent managers18 monthsMay 2027Notice, reasonable security safeguards, breach reporting, data principal rights, children's data and most other operational duties
The 18-month stage is the one that reaches your front desk. It sounds like plenty of time until you count the work involved. A company with 30 branches usually has 30 slightly different registers, guards from two or three agencies, and a reception team that has done things the same way for years. Changing forms, rewriting agency contracts and retraining people at every site takes most of a year on its own.
Why your visitor register is in scope
The DPDP Act applies to personal data collected in digital form, and to data collected on paper that is digitised later. So is a purely paper register covered? Strictly, a register that is never scanned, typed up or photographed sits in a grey zone.
In practice, very few registers stay purely on paper. Pages get scanned for audits. Entries get typed into Excel for the monthly MIS. Someone asks "who came to see the plant head last Tuesday?" and a guard photographs the page and sends it on WhatsApp. Visitor photos get clicked on the guard's phone. The moment any of that happens, the data is digitised and the Act applies in full. And if you are moving to a tablet or an app, as most organisations are, it applies from the first check-in.
Under the Act, the organisation that decides why and how visitor data is collected is the data fiduciary. That is you, not the security agency. If an agency's guards run your gate, they act as a data processor on your behalf, and you remain responsible for what they do with the data.
Five places a paper register falls short
1. Every visitor can read the page
When a courier signs in at 4 pm, the page in front of him shows the names, phone numbers and companies of everyone who came in since morning. Some of those people may be candidates who came for a confidential interview, or a competitor's vendor. An open register shares one person's details with the next by design, and that is hard to square with the Act's security and purpose principles.
2. Nobody is told why their data is collected
Rule 3 of the DPDP Rules sets out what a notice must contain: an itemised list of the personal data being collected, the specific purpose, and how the person can exercise their rights or complain to the Data Protection Board. A register with a column heading that says "Mobile No." tells the visitor none of this. The Act also lets you give the notice in English or any language listed in the Eighth Schedule of the Constitution, which matters at a gate where visitors may be more comfortable reading Hindi, Marathi or Tamil.
3. It collects far more than it needs
Ask why the register has a column for home address and the usual answer is "it was always there". The Act expects you to collect only what the stated purpose needs. For most offices, that purpose is simple: know who is on site, who they are meeting, and when they left. A full Aadhaar number or a photocopy of a PAN card does not serve that purpose, but it does create a serious problem if the register goes missing.
4. It never gets thrown away
Many facilities have a cupboard or a corner of the godown with every register since the building opened. Under DPDP, personal data should be erased once the purpose is served, unless another law requires you to keep it. Ten years of visitor phone numbers sitting in a storeroom is the opposite of that.
5. There is no trail when something goes wrong
Rule 6 asks for reasonable security safeguards, including access controls and logs that let you detect and investigate unauthorised access. Rule 7 requires a detailed breach report to the Data Protection Board within 72 hours of becoming aware of a breach. If a register disappears from the cabin during a night shift, you will struggle to say who had it, what was in it, or when it went missing. The Act provides for penalties of up to ₹250 crore where a data fiduciary fails to take reasonable security safeguards.
Consent or legitimate use? Settle the legal basis first
Before you redesign any form, decide on what legal basis you are collecting visitor data. The Act gives you two broad routes.
The first is consent, backed by a notice that meets Rule 3. The visitor sees a short statement of what is collected and why, and agrees before check-in.
The second is a legitimate use under Section 7 of the Act. One of these covers situations where a person voluntarily provides their data for a specified purpose and has not objected. A visitor who gives their name at the gate in order to get in may well fit here.
Lawyers are still debating where visitor check-in sits, and different organisations will reach different answers. Many legal teams are choosing a short notice with a tick-box consent anyway, because it costs almost nothing at a digital check-in and it puts the purpose in writing. Whichever route you choose, the rules on minimisation, security and retention still apply. Make the decision with your counsel and record it in your visitor policy, so every site follows the same approach.
What a DPDP-ready visitor form looks like
Here is a field-by-field view of a typical register, and what most organisations can do with each field. Your own risk profile may justify more at some sites, such as a data centre, a pharma plant or a bank's cash area. The point is to have a reason for every field you keep.
FieldKeep it?NotesFull nameYesNeeded to know who is on siteMobile numberYesUsed for OTP verification and host alerts. Never visible to other visitorsCompany or organisationYesHelps the host and security confirm the visitPerson to meetYesDrives approval and host notificationPurpose of visitYes, kept shortDecides access areas and retentionTime in and time outYesCore to evacuation and incident reviewPhotoOnly where risk justifies itPlants, data centres, restricted zonesID type and last four digitsUsually enoughSight the ID, record the minimumFull Aadhaar or ID numberAvoidRarely needed. UIDAI encourages masked AadhaarID photocopyAvoidThe single biggest liability at most gatesHome addressAvoidAlmost never needed for a visitVehicle numberOnly at vehicle gatesBetter handled through a gate passSignatureReplaceA digital acknowledgement of the notice does the job
If you pre-register visitors, much of this can be collected before they arrive. A host sends an invitation, the visitor fills in their own details on their phone and sees the notice there, and the guard only has to verify. VizTrak's visitor pre-registration and QR-based contactless check-in work this way.
Retention: choose a period you can defend
The Act says personal data should be erased once its purpose is served, unless a law requires you to retain it. At the same time, Rule 6 asks data fiduciaries to keep logs and related personal data for at least one year so that breaches can be detected and investigated.
Put those two together and a practical pattern appears. Many organisations are settling on about twelve months for routine visitor logs, then deleting automatically. Some records will need longer. Contractor entry records may support labour law compliance, and records linked to a safety incident or a police complaint should be held until that matter is closed. Write these exceptions into your policy so the decision isn't left to whoever happens to be on shift.
And deal with the old registers. Count them, decide what genuinely needs to be kept, and shred the rest under supervision. A cupboard full of old visitor books is exactly the kind of risk this law was written for.
Your security agency is now part of your compliance
Most Indian sites outsource gate security, and the agency's guards are the people who actually handle visitor data. Under DPDP, their mistakes are your problem. When agency contracts come up for renewal, check that they cover a few basics:
Visitor data is used only for gate and security purposes, and only as you instruct.
No photographing register pages or screens, and no sharing visitor details on personal WhatsApp groups.
Any lost register, stolen device or suspected leak is reported to you immediately, so you can meet the 72-hour reporting window.
Guards are trained on the new process, in a language they are comfortable with.
Any visitor data the agency holds is returned or deleted when the contract ends.
A digital system helps here too. When check-in happens on a device with role-based access, a guard sees what they need for the shift and nothing more, and every view is logged.
Sites that need extra care
Schools and colleges. The Act and Rules set tighter conditions for processing children's data, including verifiable parental consent. Your visitor process mostly deals with adults, such as parents, vendors and guest faculty, but any record that links a visitor to a specific child (an authorised pick-up list, for example) needs careful handling. See visitor management for schools.
Hospitals. A visitor form that records which patient someone is visiting can reveal health information about that patient. Keep patient details off the visitor record where you can, and restrict who can see them where you can't. See visitor management for healthcare.
Bank and NBFC branches. Branches often run separate registers for customers, vendors and auditors, each with its own habits. A central policy and a single system across branches keeps the approach consistent. See visitor management for BFSI.
Factories and warehouses. The same principles apply to the drivers, contractors and material movements logged at the plant gate. If your gate pass book records driver licence numbers and phone numbers, it needs the same review as the visitor register. See gate pass management.
A practical plan for the months ahead
If you start now, this is very manageable. Here is the sequence we see working for multi-site organisations:
Find every register. Main gate, reception, the back gate, the loading bay, the guest house. The registers nobody remembers are usually the riskiest.
Decide the legal basis with your counsel and draft a short notice in English and the local language.
Cut the form down using the table above. Every field should have a reason you could explain to the Data Protection Board.
Set a retention period, schedule deletion, and dispose of old registers securely.
Update agency contracts and train guards and receptionists.
Move check-in to a digital system with access controls and logs, then run a simple drill: can you say who viewed visitor data at a given site last month?
Aim to finish by early 2027. That leaves a few months of buffer before May for the sites that turn out to be harder than expected.
Where VizTrak fits
Software does not make an organisation compliant on its own. The decisions above about legal basis, fields and retention are yours to make. What a good system does is make the right behaviour the default at every gate, every day.
VizTrak was built with this in mind. It shows the notice and captures consent at check-in, lets you configure exactly which fields each site collects, applies retention rules with automatic deletion, restricts access by role and keeps audit-ready logs. You can run it on your own servers or as SaaS on AWS in the Mumbai region, so you decide where visitor data lives. It is priced per location with no limit on users, which helps when you are rolling it out across every branch at once.
For the detail, see DPDP-compliant visitor management, VizTrak for India and our security and compliance page. Reporting and audit trails are covered under visitor tracking and reporting.
Frequently asked questions
Is a paper visitor register illegal under the DPDP Act?
Not automatically. The Act covers personal data collected digitally, or collected on paper and digitised later. A register that is never scanned, typed up or photographed sits in a grey zone, but very few registers stay that way. Once entries are scanned, typed into Excel or shared on WhatsApp, the Act applies, and an open register fails on notice, minimisation, security and retention.
When do the DPDP Rules apply to visitor management?
The DPDP Rules were notified in November 2025 and roll out in stages. The duties that matter most at the front desk, such as notice, security safeguards, breach reporting and data principal rights, apply from May 2027.
Do we need visitor consent at the gate?
You need a lawful basis. That can be consent backed by a clear notice, or a legitimate use under Section 7 of the Act, such as a visitor voluntarily sharing details to enter the premises. Many legal teams still choose a short notice and consent at check-in because it makes the purpose explicit. Decide this with your counsel and record it in your visitor policy.
How long can we keep visitor records under DPDP?
Only as long as the purpose needs, unless another law requires longer. Rule 6 of the DPDP Rules asks for logs and related data to be kept for at least one year for breach investigation, so many organisations are settling on about twelve months for routine visitor logs, with deletion on a fixed schedule.
Can we keep photocopies of visitors' Aadhaar cards?
It is best avoided. Most sites only need to sight an ID and record its type and the last four digits. UIDAI encourages the use of masked Aadhaar, and full Aadhaar numbers carry their own legal restrictions. A stack of ID photocopies is one of the biggest data risks at any gate.
Who is responsible if our security agency leaks visitor data?
Your organisation. Under DPDP the company that decides why visitor data is collected is the data fiduciary, and an outsourced security agency acts as a data processor on its behalf. Your contract with the agency should require proper safeguards, prompt incident reporting and deletion of data when the contract ends.
This article is a practical guide, not legal advice. DPDP interpretation is still developing, so please confirm decisions on legal basis and retention with your own legal counsel.
See a DPDP-ready front desk in action
Book a 20-minute demo and we will walk through consent capture, retention settings and audit logs on a setup that matches your sites.