Every South African driver knows the ritual. Window down, licence out, and somewhere between the boom and the visitor book your identity number, cell number and signature end up in a place you’ll never see again. For years that ritual passed as “security procedure.” Under POPIA — and especially under the Information Regulator’s code of conduct for gated accesses — much of it is now a compliance problem wearing a reflective vest.

So what may the person at the gate actually ask for?

The short version

A guard may collect what the estate’s stated security purpose actually requires — and nothing more. The guard is acting on behalf of the estate (in POPIA terms, an operator processing for the responsible party), which means the estate owns the obligation: it must be able to justify every field the guard captures, secure it, and delete it on schedule.

In practice, a defensible gate process looks like:

  • Verified identification — looking at a licence or ID to confirm a name is materially different from copying it. Verification leaves nothing behind; harvesting does.
  • Destination — which unit or resident the visitor is going to, so the visit can be confirmed.
  • Vehicle registration — defensible where vehicle-level control is genuinely part of the security design, not as a reflex.

What crosses the line

The same practices come up in every assessment of gate compliance:

  • Scanning the licence barcode. That barcode carries far more than a name — the full identity number among it. Captured for a thirty-minute visit, it’s the textbook over-collection the code was written to end.
  • Photographing documents or the visitor themselves as a routine condition of entry.
  • Biometrics for a once-off visit — a fingerprint for a pizza delivery is not a proportionate trade.
  • The eternal visitor book. Paper registers that anyone at the gate can page through fail the code’s storage requirements on sight — and they never get deleted, only filled.
  • “Phone number, for the register.” If nobody can say what the number is for, it shouldn’t be asked.

Visitors, for their part, may ask what is being collected and why — and estates should expect that question more often, not less. An estate can still control entry on its own property; what it can’t do is make disproportionate data collection the toll.

The better answer: make the question disappear

The cleanest way through isn’t a better visitor book — it’s removing the data conversation from the gate entirely. When a resident pre-authorises a visitor with a time-limited pass, identity was established by the invitation itself: the resident knows who they invited. At the boom, the guard verifies a PIN or QR code and waves the visitor through. Nothing is written down, nothing is scanned off a licence, and the estate still gets what security actually needs — a timestamped, revocable record that this specific authorised visit happened.

That’s the model QRXS is built on: passes carry their own time window, the gate verification carries no personal-data capture, and the audit trail assembles itself with the minimum the law asks anyone to hold. The guard’s job gets simpler, the visitor’s wait gets shorter, and the trustees’ compliance file gets thinner — in the good way.

Sources: Information Regulator (South Africa); Protection of Personal Information Act, 2013; TTK Surveillance — The new rules for access control to residential and business estates (19 May 2026). See also our overview of the gated-access code of conduct.

This article is general information, not legal advice. For a compliance opinion on your estate’s specific setup, consult your attorney.