Skip to content
// guide · 5 min read

What POPIA means for your website

What POPIA asks of a South African website: security safeguards (section 19), breach notification (section 22), forms and cookies, and first steps.

Published · updated

// short answer

If your website collects personal information, such as names and email addresses from a contact form, POPIA expects reasonable technical safeguards to protect it (section 19) and notification if it is compromised (section 22). This is general information, not legal advice.

If you run a South African business with a website, you've probably heard of POPIA. You may also have heard a lot of confusing advice about it. This guide explains, in plain English, what the law means for a typical small business website, and what practical steps help you meet it.

What POPIA is

POPIA is the Protection of Personal Information Act 4 of 2013. It's South Africa's main data protection law. It sets out how organisations may collect, use, store and share personal information about people, and it's enforced by the Information Regulator.

"Personal information" is broad. It includes names, email addresses, phone numbers, ID numbers, physical addresses, online identifiers and much more. POPIA also protects information about existing juristic persons, such as companies, which is unusual compared with many other countries' laws.

Does it apply to my website?

If your website collects personal information, almost certainly yes. Common examples:

  • a contact form that asks for a name and email address;
  • a newsletter sign-up;
  • online bookings or appointments;
  • customer accounts and logins;
  • an online shop that takes orders and delivery addresses;
  • analytics or marketing tools that track individual visitors.

In POPIA's language, your business is usually the responsible party: the one that decides why and how personal information is processed. Your web host, email provider or developer may be an operator, processing information on your behalf. You stay responsible even when someone else does the processing for you, which is why POPIA expects written contracts with operators.

The eight conditions, briefly

POPIA sets out eight conditions for processing personal information lawfully. In short:

  1. Accountability: the responsible party must make sure the conditions are met.
  2. Processing limitation: collect only what you need, lawfully, and with a valid reason such as consent or a contract.
  3. Purpose specification: collect information for a specific, explicitly defined purpose, and don't keep it longer than necessary.
  4. Further processing limitation: don't use it later for something unrelated to the original purpose.
  5. Information quality: take reasonable steps to keep it accurate and up to date.
  6. Openness: tell people what you're collecting and why, usually through a privacy notice.
  7. Security safeguards: protect it properly (more on this below).
  8. Data subject participation: people can ask what you hold about them, and ask you to correct or delete it.

For most small business websites, conditions 2, 3, 6 and 7 are the ones that need the most thought.

Security safeguards: section 19

Section 19 is where websites come in directly. It requires a responsible party to secure the integrity and confidentiality of personal information by taking appropriate, reasonable technical and organisational measures to prevent loss, damage, unauthorised destruction, and unlawful access or processing.

The law doesn't list specific technologies. Instead, it expects you to:

  • identify reasonably foreseeable risks to the information you hold;
  • put reasonable safeguards in place against those risks;
  • check regularly that the safeguards work;
  • keep updating them as risks change.

It also says to have due regard to generally accepted information security practices. For a website, that usually means things like:

  • Encryption in transit: HTTPS on every page, with a valid SSL certificate and modern TLS.
  • Browser protections: sensible security headers that reduce the risk of attacks such as cross-site scripting.
  • Up-to-date software: your CMS, plugins and themes patched promptly.
  • Access control: strong, unique passwords, two-factor authentication, and only the people who need admin access having it.
  • Email protection: SPF, DKIM and DMARC, so criminals find it harder to impersonate you to your customers.
  • Backups: so information isn't lost if something goes wrong.
  • Collecting less: the safest personal information is the information you never collected.

"Regularly verify" is worth underlining. A one-off setup isn't enough. Checking your site from time to time, and keeping a record that you did, is part of showing that your safeguards are reasonable.

// free, passive, 30 seconds

Check the basics your website shows the world

Run the free check

When something goes wrong: section 22

Section 22 deals with security compromises. Where there are reasonable grounds to believe that personal information has been accessed or acquired by an unauthorised person, the responsible party must notify:

  • the Information Regulator; and
  • the affected people (data subjects), unless their identity can't be established.

Notification must happen as soon as reasonably possible after the compromise is discovered. It must give enough information for people to protect themselves, such as a description of what may have happened, what you're doing about it, and what they can do.

For a small business, the practical lesson is to prepare before you need it. Know who to call, keep a record of what personal information your website collects and where it's stored, and keep backups you can restore. If your site is ever hacked, our guide on what to do if your WordPress site has been hacked covers the first steps.

A practical starting list

You don't have to solve everything at once. A reasonable first pass looks like this:

  1. List what your website collects: every form, every field, every tool.
  2. Remove what you don't need. If you don't use a phone number, stop asking for it.
  3. Publish a clear privacy notice that says what you collect, why, who you share it with, and how people can contact you.
  4. Check your operators: hosting, email, form and newsletter providers. Make sure there's a written agreement and that they protect the information.
  5. Get the technical basics right: HTTPS, security headers, updates, two-factor authentication, DMARC.
  6. Check regularly, and keep a note of when you did.
  7. Write down what you'd do if personal information were compromised.

How we can help

Odesstra isn't a law firm, and we can't tell you whether you're compliant. What we can do is help with the technical side of section 19: checking what your site shows the world, explaining it in plain English, and fixing what needs fixing.

Start with the free website security check. It's passive: it only looks at what any browser can see, and nothing is attacked. If you'd like ongoing help, our website security service for South African businesses includes regular checks by a person, plain "are we affected?" answers and a monthly report, with prices available in rand. Book a short call to get started.

For a broader routine, see the website security checklist for small businesses.

Questions

Does POPIA apply to a simple contact form?

Generally yes. A name and email address are personal information, so collecting them means POPIA applies. This is general information, not legal advice.

Can a security check make my website POPIA compliant?

No check can make you compliant on its own. It can help with the technical side of section 19: finding and fixing weak spots, and showing you check regularly.

Talk to a human