POPIA and your business software: questions to ask before you build

The Protection of Personal Information Act (POPIA) applies to almost every business system that stores names, ID numbers, contact details, payroll records or client files. Responsibility for that information stays with your organisation — so the software you commission should make compliance easier, not harder.

These are the questions we believe every business should ask before a system is built. (This article is general guidance, not legal advice.)

1. What personal information will the system collect — and why?

Good design collects only what the purpose requires. If a field is “nice to have”, it should be questioned before it is built.

2. Who can see what?

Role-based permissions should limit each user to the information their job needs. A receptionist and a payroll administrator should not see the same records.

3. Is each client’s data kept separate?

For multi-company or multi-branch systems, strict data isolation prevents one client’s records from ever appearing in another’s view or report.

4. Is there an audit trail?

You should be able to show who accessed or changed personal information, and when.

5. How is information secured in transit and at rest?

Encrypted HTTPS connections, secure sign-in, backups and security updates are baseline expectations, not extras.

6. Can you correct, export or delete records?

Individuals may ask for access to, or correction of, their information. The system should make those requests straightforward to handle.

7. Who owns the data, and what happens if you leave?

Your agreement should state clearly that the data belongs to you and how it will be exported at the end of the relationship.

How we approach it

At Think Mybiz Tech, POPIA-aligned handling is part of our engineering standards: least-privilege permissions, per-client data separation, audit logs and clear data-ownership terms in every engagement. You can export your data at any time.

Building a system that will hold personal information? Let’s discuss how to design it responsibly from day one.