Respond to driver privacy objections by identifying the processing at issue and assessing what an alternative would actually change.
Give the driver a clear contact route and have the privacy lead assess the concern. The response should address the processing being challenged, with any proposed alternative assessed against the site's operation and applicable requirements.
A parking exemption and a privacy objection are different matters. An attendant should have a way to refer the request, rather than being expected to decide the basis for collecting records.
A ticket or permit allowed a visitor to present a credential deliberately. Passive plate capture changes that interaction: a record may already exist before the driver reaches a machine, reception desk or attendant.
An objection can therefore concern collection itself, as well as later retention, searches or reuse. Removing someone from a mailing list or changing a payment setting would not address all of those concerns.
Manual assistance, another credential or a narrower capture arrangement may be worth assessing. The effect on the person matters, particularly where a visitor cannot use another entrance or access the same service by another route.
Available rights depend on the collection purpose and applicable rules. A proposed option needs an operational explanation before it is offered; describing an untested arrangement as an exemption could leave the original processing untouched.
Adding a visitor's plate to an authorised list may prevent a parking exception while still leaving a sighting. If the concern is collection, that change does not answer it. A manual route needs checking against the camera view and actual record creation.
Explain who controls the records and document whether an option changes capture, retention, access or payment. Tell the person how to seek review. Any additional identity documents should have a defined need, rather than becoming a routine hurdle for raising a concern.
Aero Ranger directs requests about deployment records to the customer organisation and describes assistance with those requests. That supports an operator-led process, because the operator determines the capture purpose for the site.
Any alternative needs confirmation with the deployment team. The privacy policy does not describe a universal driver switch to disable ANPR capture or provide an exemption, so that capability should not be assumed.
Sources were reviewed on the publication date. Check the linked material for current details.
