There is a piece of advice circulating in South African recruitment that sounds responsible and is quietly wrong: that once a role is filled, you must destroy the personal information of everyone who did not get it.
If that were true, no recruitment agency in the country could operate. The entire value of a desk is the network on it. Fortunately the Act says something more sensible, and understanding the difference is the single most useful hour a recruiter can spend on compliance.
Section 14 of the Protection of Personal Information Act sets the default: records of personal information must not be retained any longer than is necessary for achieving the purpose for which the information was collected or subsequently processed.
That is the rule people quote. What they leave out are the exceptions written into the same section. Retention beyond that point is permitted where:
Read the second and fourth of those again, because they are the ones that describe a recruitment business. Keeping a candidate on file for future roles is a lawful purpose related to your activities, and a candidate who agrees to stay on your database has consented. Neither is a loophole. Both are in the text.
The Act does not tell you to delete your database. It tells you to have a reason for keeping it, and to be able to say what that reason is.
The "destroy it when the role is filled" advice is sound for the narrow case it was written about: an employer who collected applications for one specific vacancy, kept them for nothing else, and never asked the applicants about anything further. There, the purpose really has been achieved, and the exceptions do not apply.
An agency is a different animal. Your purpose was never only that one role. But that has a condition attached: you have to have said so, at the point of collection, in language a person can understand.
When you no longer have a basis to keep a record, section 14 does not permit you to simply leave it in an old spreadsheet. The record must be destroyed, deleted or de-identified as soon as reasonably practicable, and the destruction must prevent its reconstruction in an intelligible form.
In practice that rules out a few habits worth naming: dragging a CV to the recycle bin without emptying it, "archiving" a folder that everyone can still open, and leaving a candidate's details in an exported spreadsheet on someone's laptop after they have been removed from the system.
A data subject may ask you to confirm what you hold about them and to give them a copy. They may ask you to correct information that is wrong or incomplete, and to delete information you no longer have grounds to keep. They may object to processing, and they may complain to the Information Regulator if they are not satisfied with your response.
Every responsible party must have an Information Officer, who by default is the head of the organisation. The role covers compliance, handling requests from data subjects, and dealing with the Information Regulator. Registration with the Regulator is a separate step from writing a privacy policy, and it is the one most often missed.
None of that requires a consultant. It requires an afternoon and a willingness to write down what you already do.
Consent captured at the point of collection, an audit trail on every export, and deletion that actually deletes.