BlogCompliance guide

Why an accept-only cookie banner is not enough

Give visitors a real choice, then make the scripts follow it

Tawthiq team8 November 20263 min read

A browser window with two equal choice buttons and a hand selecting one

Start with the processing behind the button

Open your website in a fresh browser session and leave the banner untouched. If an advertising pixel already sends a page view, the banner has not prevented that processing. Adding a button changes the interface, not the script that runs behind it.

The PDPL generally requires consent for processing personal data, subject to its exceptions (article 5). Those exceptions need their own assessment (article 6). A cookie name alone does not establish the lawful basis, and not every cookie requires consent simply because it is a cookie.

List each tool, its purpose, what it sends and who receives it. Separate functions needed for a requested service from optional measurement or advertising. This is practical implementation guidance, not legal advice.

Make refusal visible

A message that says “By continuing, you accept” does not record a clear affirmative choice. Neither does a banner with only an acceptance button and no way to decline optional processing. Closing the banner should not silently grant permission.

Consent must be freely given, informed by clear purposes and documented. Each processing purpose needs separate consent under the Implementing Regulations (article 11 of the Regulations). Do not combine analytics, personalised advertising and unrelated marketing into one compulsory switch.

Place “Reject optional” beside “Accept all” on the first layer. Give both readable labels, similar size and comparable contrast. This is a practical design recommendation for a real choice, not a claim that the PDPL prescribes those exact words or button dimensions.

Keep a preferences option for visitors who want one purpose but not another. Do not preselect optional categories. Explain necessary functions without presenting them as optional permissions that visitors can switch off when they cannot.

Find every route that loads a vendor. Check direct scripts, tag-manager containers, plugins and embedded widgets. Blocking a tag in one container does nothing if the same vendor also loads from the page template.

Where processing relies on consent, do not start it while waiting for an answer. Apply the saved choice before optional tools initialise on later visits. A timeout, scroll or page change should not turn an unanswered request into acceptance.

Do not make an unrelated service depend on agreeing to optional processing. The law restricts making consent a condition of a service or benefit, with an exception where the service or benefit directly relates to that processing (article 7).

Make withdrawal work

Add a persistent “Privacy choices” link in the footer. It should reopen the same controls without requiring an account, a support email or a search through policy pages.

Withdrawal must be as easy as giving consent, or easier (article 12 of the Regulations). When someone switches a purpose off, stop the processing that depends on that consent without undue delay. Withdrawal does not undo earlier lawful processing or automatically resolve every data-retention question.

Keep enough evidence to establish what the person chose, when and against which notice version. Do not turn the consent record into a new source of unnecessary visitor data.

Test the choices separately

Check a fresh visit, rejection, partial acceptance, full acceptance and later withdrawal. In each case, inspect browser storage and network requests, then navigate to another page and reload.

Try the same checks on mobile. If a visitor cannot reach the reject control without scrolling past a fixed overlay, fix the layout. For the policy and data inventory that support these controls, use the website preparation guide.

References

  1. Personal Data Protection Lawsdaia.gov.sa
  2. PDPL Implementing Regulationsdgp.sdaia.gov.sa
  3. Five steps for your websiteBlog