Software Development
Asking Customers for an ID Number? What POPIA Expects First
Asking for an ID number is often the right call, but POPIA sets conditions before you collect one. Here is what to check first, and how to design the form and the database so the number does less harm if something goes wrong.
Yes, a South African business can ask customers for their ID number, but only with a lawful reason, for a purpose you tell them about, and only when that purpose needs it. POPIA treats an ID number as personal information. Reusing it to link your records with other companies' records can need the Information Regulator's approval first.
Is an ID number personal information under POPIA?
An ID number is personal information under POPIA, and it says more than most owners think. Section 1 of the Act lists "any identifying number" as personal information. And a South African ID number is not a random string. Under the Identification Act regulations, the 13 digits carry your date of birth, your gender and whether you are a citizen.
So the useful question is what you need it for. Section 10 says personal information may only be processed if, for its purpose, it is "adequate, relevant and not excessive". If you only need to know a customer is over 18, the full number is more than you need. If you must match a person to a credit bureau record, it is probably the right field.
POPIA also gives you more than one lawful basis. Section 11 allows consent, but also processing that is necessary for a contract, or required by law.
Where do businesses get ID numbers wrong?
Most problems with ID numbers come from what happens after collection, not from asking. The number goes into a spreadsheet, a CRM export and three email threads. Then someone shows it on a public page or reuses it for something nobody agreed to. The Information Regulator received 2 374 security compromise notifications in the 2024/25 financial year, about 198 a month, and 284 a month from April 2025, which it called a 40% increase, according to ITWeb's November 2025 report of its briefing. A customer can change a leaked password. They cannot change their date of birth.
Take a made-up example, not one of our projects. A loyalty app wants to stop people opening a second account to claim a second welcome voucher. The first question is whether it needs the ID number at all. A verified cell number may be enough, with far less harm if it leaks. If the owner decides only the ID number will do, the app asks for it as a separate step and says why. It keeps the full number in one place and shows only the last few digits on the member's profile, on receipts and on staff screens. Only the duplicate-account check can read the whole value. When a member closes their account and the record is no longer needed, it is deleted or de-identified. We wrote separately about privacy in loyalty programmes, which covers the rest of the member data.
The second trap is reuse. Section 57 of POPIA requires prior authorisation from the Regulator before you process unique identifiers for a purpose other than the one they were collected for, with the aim of linking them to information other responsible parties hold. Matching your customer list with a partner's list by ID number is the kind of plan to check with a lawyer first.
How should you collect and store ID numbers?
Collect an ID number only on the screen where it is needed, and tell the person why on that screen. Section 18 expects you to tell people what you collect, why, and whether giving it is voluntary or mandatory, before you collect it. One plain sentence under the field does this better than a link to a privacy policy.
Then design the storage so the number is hard to see by accident:
- Mask it everywhere a person does not need the full number: lists, emails, receipts, exports.
- Restrict who and what can read the full value. Put that rule in the database itself, not only on the app screen.
- Decide how long you keep it. Section 14 says records must not be kept longer than the purpose needs, unless the law or a contract requires it.
We built the access rule into a recruitment site for a holding group with six subsidiaries. Role-based access control gives each subsidiary its own secure area, and applications go straight to that subsidiary's HR team. Job applications are different data from ID numbers, but the rule carries over.
If you are scoping a new system, this is part of the custom software work we would cost upfront rather than add later, the same way we approach compliance by design in South African software. If the ID number feeds a credit decision, read our notes on NCR registration for a credit app too.
Ask for the ID number when the business needs it, then treat it like cash in the till. I would not put an ID field on any form until someone can say in one sentence what it is for.
Questions about POPIA and ID numbers
Can a business ask for my ID number in South Africa?
Yes, if it has a lawful reason and the purpose needs it. POPIA allows processing with consent, for a contract, or to meet a legal duty, among other grounds. Matching a customer to a credit bureau record is one purpose that needs it. Collecting it "just in case" fails the minimality test in section 10.
Is an ID number personal information under POPIA?
Yes. Section 1 of POPIA lists any identifying number as personal information. A South African ID number also encodes date of birth, gender and citizenship in its 13 digits, so it reveals more than it looks. Treat it as one of the most sensitive fields in your customer database.
Do I need consent to collect an ID number?
Not always. Consent is one of several lawful grounds in section 11 of POPIA. Processing needed for a contract, or required by law, qualifies too. You still have to tell people what you collect and why, before you collect it.
How should a website store ID numbers?
Store the full number in one place, restrict who can read it, and mask it everywhere else. Put the access rule in the database itself, not only on the app screen. Lists, emails and exports should never carry the full number unless the task needs it.
How long can a business keep an ID number?
No longer than the purpose needs, under section 14 of POPIA, unless a law, a contract or the person's consent allows longer. When the purpose ends, delete, destroy or de-identify the record so it cannot be reconstructed. Decide the retention period when you design the system, not after.
When do you need prior authorisation for ID numbers under POPIA?
Section 57 requires prior authorisation from the Information Regulator before you process unique identifiers for a purpose other than the one they were collected for, with the aim of linking them to information other responsible parties process. Matching your list against a partner's by ID number is the kind of plan to check first.
Arnaud Brunel
Founder, Brunel Studios
Arnaud Brunel is the founder of Brunel Studios, a software product studio based in Cape Town. He has spent the last 8 years building digital products for founders and SMEs across South Africa and Africa, working across mobile, web and AI-native platforms.
LinkedIn ↗