Handling a Visitor's Request to Delete Their Data

Published on 10/18/2026 • Updated on 10/19/2026

A visitor who came to your plant six months ago writes to say: please delete my name, number and photo from your records. Your guard has never seen such a request. The admin head is unsure whether to say yes. The email sits for two weeks.

The Digital Personal Data Protection Act, 2023 gives people the right to ask for erasure, and the DPDP Rules, 2025 set expectations for how organisations respond. This guide sets out the right, when you can and cannot delete, a simple five-step process and sample replies. It is general information, not legal advice. Confirm your approach with your legal adviser.

On this page

Section 12 of the Act gives a Data Principal the right to correction, completion, updating and erasure of personal data, subject to the Act. A Data Fiduciary must erase data on request unless retention is necessary for the purpose it was collected for or for compliance with a law.

The Rules add practical points. Rule 14 expects publication of how to make a request and a response to grievances within ninety days at most. Rule 8 sets a minimum one-year retention for certain data and logs for specified purposes, with a notice before erasure for some classes. Rule 14 and Rule 8 begin after eighteen months from publication, around mid-May 2027. Confirm the dates with your adviser.

Key idea: Erasure is not automatic in every case. It is a request you must consider and answer.

When you can keep the data

Situation Likely answer
Visitor came once, no incident, retention period over Delete
Visitor record tied to an accident investigation Keep for the investigation, explain why
Record needed by another law, such as a registered contractor entry Keep as the law requires
Logs the Rules require you to keep Keep logs, delete what you can

If you refuse in whole or in part, say so in plain words and give the reason. Silence is the worst reply.

A five-step process

Step 01

Receive

Log the request with the date, name and what was asked. Give the guard an email address to forward it to.

Step 02

Verify

Confirm the person is who they say they are, for example by replying to the phone number or email on the record.

Step 03

Search

Find every copy: the visitor system, exports, paper registers, camera clips, courier logs.

Step 04

Decide

Check retention duties and open incidents. Decide what to delete and what to keep.

Step 05

Reply

Tell the person what was deleted, what was kept and why, and the date.

Sample replies

DELETED Thank you for your request of 4 March. We have deleted your name, phone number and photo from our visitor system and from our backups cycle. Records will clear fully by 30 April. Reference: VR-0425. PARTLY KEPT We have deleted your photo. We keep your name and entry time because they relate to an open safety inquiry. We will delete them when the inquiry closes. Reference: VR-0426.

The dates and reference numbers are examples. Use your own and keep a copy of each reply.

Find a visitor record in seconds

VisitorFlow keeps one searchable record per visitor, so finding and deleting it takes minutes instead of a search through registers.

Explore Visitor Management Software

Where the data hides

  • The visitor management system and its exports.
  • Spreadsheets saved on desktops.
  • Paper registers and photographs of registers.
  • Badge printouts and envelopes.
  • CCTV footage of the visit.
  • Email and chat messages with the visitor.

A digital system with one record per visitor makes this far simpler than paper in four places. Paper registers that mix many visitors on one page cannot have a single name removed without masking the rest.

Reduce requests by deleting on schedule

The easiest erasure request is the one you never receive, because the data is already gone. Set a retention period for each type of record and delete on a schedule.

Record Suggested approach
Visitor entries with no incident Delete after a fixed period such as 90 days
Photos taken at check-in Shorter period, such as 30 days
Contractor records for registered vendors Keep while the contract runs, then a set period
Incident related entries Keep until the inquiry and any claim period ends

The periods above are assumptions for the example. Choose yours with your adviser, since other laws can set longer minimums for some records.

When a vendor holds the data

If a software vendor, a guard agency or a courier partner holds visitor data for you, your duty to the visitor does not change. You must pass the request on and make sure the data is removed there too. Put this duty into the contract: how fast the vendor must act, how it confirms deletion, and what it does with backups.

Test the route once before you need it. Ask the vendor to delete a dummy record and see how long it takes and what proof you get.

What to teach the gate team

Guards and receptionists are where requests first land. They do not need to know the law. They need three habits.

  • Never say no and never promise. Say that the request will go to the privacy owner.
  • Write down the name, phone and what was asked, and send it the same day.
  • Do not delete anything on their own, even if the visitor stands at the desk.

A laminated card at the desk with the owner's email address is enough. Check once a quarter that the address works and that someone reads it.

A worked example

Worked example (assumed) Mon Request arrives at privacy@ address. Tue Identity confirmed by phone call. Wed Record found in system and in one export. Thu Record deleted. Export file masked. CCTV clip is past retention, already gone. Fri Reply sent. Log updated.

Five working days from request to reply is well inside the ninety-day outer limit and costs about an hour of effort.

Common mistakes

Ignoring the request

Silence turns a small request into a complaint.

Deleting without checking

Check for open incidents and legal holds first.

Confirm in writing

Tell the person what was done and when.

Another mistake is deleting from the main system but not from exports and backups. Say clearly when backups clear, rather than promising instant deletion.

A third is letting guards answer. Give them one line to say, and send the request to the named owner.

A fourth is asking for more proof of identity than the original record held. If you only held a name and a phone number, a call back to that number is enough. Demanding a government ID to delete a name and number means you collect more data than you are removing.

A fifth is forgetting employees and contractors. They can make the same request about their own records, and the same five steps apply, with HR as the owner.

A one-week setup

Be ready before the first request arrives.

Step 01

Day 1: owner and address

Name the owner and set up a privacy email address.

Step 02

Days 2 to 3: map

List every place a visitor record can sit.

Step 03

Days 4 to 5: templates

Prepare reply templates and a request log.

Test it with a mock request from a colleague and time each step. Note where the request waited longest, for example for identity checks or for the vendor, and fix that step first. Repeat the test every six months and after any change of owner, system or vendor, and keep the results with your other compliance records so that you can show them if asked.

Five-minute self-check

Check your readiness against these points.

Answer yes or no

  • ☐ Is there a named owner for requests?
  • ☐ Can a visitor find the contact address?
  • ☐ Do you know every place a record sits?
  • ☐ Are reply templates ready?
  • ☐ Is there a request log?

Two or more no answers mean this is worth fixing before anything else on your list.

Reader Q&A

Can a visitor ask me to delete their data?

Yes. Section 12 of the Act gives a Data Principal the right to ask for erasure, subject to the Act.

Must I always delete?

No. You may keep data needed for the original purpose or for compliance with law, for instance during an open incident inquiry. Explain the reason.

How fast must I respond?

Rule 14 expects a grievance response within ninety days at most. Aim for days, not weeks.

Do I need to delete from backups?

Delete from live systems and say when backups cycle out. Ask your adviser about your backup setup.

How do I know the requester is genuine?

Confirm through the phone number or email already on the record before you act or share anything.

When do these duties begin?

Rules 8 and 14 begin after eighteen months from publication, around mid-May 2027. Confirm the date with your adviser.

Bottom line

An erasure request is a routine event, not an emergency. Receive, verify, search, decide and reply, and keep a record.

The more your data sits in one searchable place, the shorter the job.

Make deletion a two-minute job

VisitorFlow runs visitor, material gate pass, courier, maintenance and incident workflows on one cloud platform.

Explore Visitor Management Software See Material Gate Pass Software Book a Free Demo
Author of the Blog Post
Aadeshwar Modi
Technical Content Writer at VisitorFlow

Aadeshwar Modi is a marketing technical content writer who loves writing on technology and AI topics.

Recent Post