Why the difference matters on a South African website
Many business owners treat consent and notice as if they are one and the same. They are not. A notice tells people what you are doing with their information, while consent is a permission you ask for in specific situations. If you blur the two, your forms can become confusing and your records can be difficult to defend later.
In South Africa, this matters because POPIA expects responsible handling of personal information, not just a generic pop-up with a tick box. A clear notice helps customers understand what happens to their data, and consent is only needed where you are relying on permission rather than another lawful ground. The point is to be honest, specific, and practical about how you collect, store, and use information.
What a proper notice should tell people up front
A notice is the plain explanation you give before or at the point of collection. It should be short enough to read on a phone, but detailed enough for someone to understand what will happen next. For a Cape Town business taking online enquiries, that usually means telling users why the information is needed, who will use it, and how long it will be kept.
- What personal information you collect, such as names, contact details, addresses or ID numbers
- The reason for collecting it, such as quotes, bookings, delivery or account management
- Who may receive it, including internal staff or third-party service providers
- Whether the information is sent outside South Africa
- How long you keep it, and what happens when it is no longer needed
A notice is not there to hide behind legal jargon. It should answer the customer’s first question: what are you doing with my details, and why?
When consent is the better route
Consent is needed when you want someone to actively agree to a specific use of their information. A marketing opt-in is the clearest example. If you want to send newsletters, promotions, or follow-up offers, you should ask clearly and leave the choice open. Pre-ticked boxes and bundled wording create problems and usually do not give you a strong position.
Consent is also important where the processing is not obvious from the main service. For example, a booking form for a salon in Gardens may need a notice for the appointment itself, but a separate consent line for promotional WhatsApp messages. That distinction keeps the record clean and makes it easier to prove what the client agreed to.
- Use a separate tick box for marketing, never bundle it with service terms
- Explain exactly what the person will receive and by which channel
- Keep a record of when and how consent was given
- Make it easy to withdraw consent later
How the two work together on forms and checkout pages
Most websites need both. A contact form needs a notice so the visitor understands why their details are being collected. An ecommerce checkout may also need consent for optional extras, such as promotions or reminders that are not required to complete the sale. The trick is to separate the must-have information from the optional permissions.
For example, a Paarl business selling subscription boxes can explain in the notice that details are used to process orders, deliveries and support queries. Then, if the business wants to send monthly offers, it asks for consent in a separate field. That way the customer can buy the product without being forced into marketing. It sounds simple, but this is where many sites get it wrong.
Keep the wording close to the action. If a button says “Get quote”, the notice beside the form should make it clear what data is needed for that quote and how long it will be kept. If the page asks for consent, the wording should not leave room for doubt.
A local example from Cape Town Gardens
Picture a small business in Gardens that takes online bookings for after-hours support. The booking form asks for a name, mobile number, email address and service notes. A notice should tell the client that the details are needed to confirm the booking, manage the appointment, and contact them if the technician is delayed because of load-shedding or traffic around the city bowl.
If the same business also wants to send future service reminders or promotions, it needs a separate consent choice. The reminder can be useful, but it should not be hidden inside the notice or included automatically. Customers in Sea Point, Bellville or Stellenbosch should be able to see what is required for service and what is optional for marketing.
That separation is especially important where information is shared across teams or stored in cloud systems. The user should understand the practical flow of their data, not just see a broad privacy statement in fine print.
Practical checks before you publish or update your policy
A good policy does not just sound legal. It matches what the business actually does. Before launch, review every form, booking flow, checkout page and popup against the wording in your notice and consent fields. If the site collects more data than the policy describes, or asks for consent where notice would be enough, the documents need attention.
- Check every enquiry form, lead form and checkout step
- Match the policy wording to the data fields on the page
- Separate service notices from marketing permissions
- Make sure opt-outs and withdrawal steps are simple
- Review updates when your tools, suppliers or processes change
For businesses in Cape Town CBD, Claremont, Bellville or nationwide, the safest approach is to keep records current. A policy written two years ago may no longer reflect your current systems, and that can become a problem when a customer asks how their details were used. Clear wording now saves time later, and it reduces disputes when someone questions what they agreed to.
Consent is an active yes. Notice is a clear explanation. A compliant website usually needs both, but for different reasons.
