A casino marketing screen needs to show both what and how

Find the choice behind the switch

A single switch labelled “Offers” cannot, by itself, tell a reader which gambling products or contact channels it controls. The relevant Gambling Commission provision requires covered remote operators to offer marketing choices by product and by channel. For an interface reader, the first task is therefore to find two kinds of information: what the messages concern and how they arrive.

This is a document-based inspection method for adult readers. No casino account was opened, no preferences were changed and no number of clicks at a named operator was measured. The examples below are deliberately fictional.

They show how to read the information architecture of a settings screen without treating an attractive switch as evidence of a complete choice.

The focus is the screen’s labels, grouping and confirmation language. It is not an assessment of whether a particular operator has lawfully processed someone’s data. That would require the relevant account record and circumstances.

A useful interface observation can nevertheless be precise: identify the choice that is visible, the relationship that is unclear and the text needed to resolve it.

Sources: 5.1.12 Direct marketing preferences.

Read the provision before designing a checklist

Social responsibility code provision 5.1.12 covers the specified remote casino, bingo and betting licences, with listed exceptions. It describes options set to opt-out by default, available at registration and updateable later. Its named channels include calls, email and SMS where applicable; its product categories include betting, casino and bingo where applicable.

Operators must explain which products fall under their categories.

That last point turns a category label into a design question. Suppose a fictional menu says “Games”. A reader cannot assume that it means casino only, or that bingo is included.

The inspection should record the label and look for its explanation. It should not silently translate an ambiguous word into the category the reviewer expected to find.

Likewise, a channel headed “Mobile” leaves an unresolved question if its description does not distinguish a call from a text. This is a hypothetical example of ambiguity, not a finding against an operator. The method begins with the wording that is actually visible and asks what choice that wording allows a person to make.

It does not assign a numerical quality score merely because one design uses more switches than another.

Sources: 5.1.12 Direct marketing preferences.

Use a matrix to expose an ambiguous relationship

Imagine a fictional screen with three product rows and three contact columns. All nine cells begin off. The rows are casino, betting and bingo; the columns are email, SMS and phone call.

A reader wants every marketing choice to remain off. In this example the intended result is simple: nine off states, followed by a confirmation that preserves them.

The matrix is our analysis tool, not a statutory demand for nine physical switches. Another interface might express choices through two grouped lists. The question is whether the resulting permissions are understandable, not whether the page resembles our drawing.

If the screen groups products separately from channels, its explanation must be read before inferring which combinations follow.

Now consider a second fictional request: permit casino email only. That changes one cell of our example matrix and leaves eight off. We use this solely to test whether a screen can express a specific choice, not to encourage marketing subscriptions.

If the interface cannot explain whether selecting email also selects every product, the inspection has found an unanswered relationship. The honest result is “scope unclear”, not an invented account setting.

The original figure shows the all-off matrix. Its labels illustrate the two axes of the choice. It contains no live controls, operator branding or claim that an account has been configured.

The confirmation page is part of the interface

Provision 5.1.12 also addresses an additional confirmation step. Where an operator uses one, the text and structure should ask for confirmation of the chosen preferences with one click to proceed, without encouraging a change of selection. That rule concerns this particular step; it is not a one-click limit for finding every settings page.

Compare two invented confirmations. “Save these choices” followed by a neutral accept or decline option gives a reviewer a clear task to examine. “Are you sure you want to miss our offers?” adds an attempt to reconsider the choice.

The example is a reading exercise, not an observed screen or a legal ruling on a named business.

A record of the first page alone would miss this difference. The proposed inspection follows the displayed choices into the confirmation language, noting whether the same product and channel scope remains visible. It also records what has not been observed.

A public help article may describe a process without displaying its final screen; that is a documented route, not a completed account inspection. Keep those evidence types separate.

Sources: 5.1.12 Direct marketing preferences.

Consent should remain separate from the contract

The Information Commissioner’s Office describes consent as an affirmative choice and says pre-ticked opt-in boxes do not meet that standard. Its guidance also distinguishes consent from general terms and conditions. These principles explain why proximity matters: a box accepting account terms should not be casually read as the same thing as a marketing preference.

In a fictional registration panel, place “I accept the account terms” above “Email me casino promotions”. Those sentences concern different decisions even if the designer aligns them in one column. A reviewer should copy both labels into the evidence record and note the grouping.

Do not assume that separate rows necessarily mean separate choices if a single control governs them.

The ICO’s detailed consent guidance recommends concise language, consistent methods and avoidance of confusing double negatives. A switch labelled “Do not stop sending messages” is consequently a poor sentence to interpret at speed. Our editorial preference is to write the intended state in plain words before discussing the control: “email marketing off”.

That is a proposed clarity technique, not a quotation from the regulator.

The ICO pages carried a notice that guidance was under review following the Data (Use and Access) Act. The record here reflects the pages retrieved on 19 September 2026; a later review should recheck them.

Sources: Consent; How should we obtain, record and manage consent?.

Follow the route back out

The Commission’s electronic-marketing consent provision requires an opportunity to withdraw consent when a consumer is contacted. It says the licensee must stop electronic marketing as soon as practicable after withdrawal unless the consumer consents again, and must be able to evidence consent. It does not supply a universal number of minutes in which every downstream message will cease.

That distinction prevents a settings observation becoming an unsupported delivery claim. A screen may display “saved”, but our inspection has not thereby established what every mailing system holds or when a queued message was prepared. Record the visible confirmation and its time separately from any message later received.

The two records can support a clear query without pretending to reveal the operator’s internal processing.

The ICO’s management guidance says withdrawal should be as easy as giving consent. Read that alongside the route actually documented: where the setting is named, whether the explanation identifies the relevant organisation, and how the person is told to change it. Do not create an account or subscribe to promotions merely to complete a comparison.

A missing public view remains a limitation.

Turning off marketing is also a different task from changing account access or gambling limits. This inspection makes no claim that an off switch blocks gambling. Its purpose is to understand communications choices.

Sources: 5.1.11 Direct electronic marketing consent; How should we obtain, record and manage consent?.

Write a finding another reader can reproduce

A useful observation sheet contains six fields: the page or document inspected, the observation date, the exact control label, the stated product scope, the stated channel scope and the confirmation text. Add a final field for uncertainty. In a real private account review, account identifiers should stay out of a public report.

Here is an invented completed entry. The help document describes an account menu called “Communication choices”. It names email and SMS but uses “Games” without explaining whether that includes bingo.

It says changes can be saved, but does not reproduce the confirmation page. The resulting finding is narrow: the public document describes a route and two channels, while product coverage and the final screen remain unverified.

It would be inaccurate to turn that record into “the operator hides settings” or “the operator sends unwanted bingo emails”. Neither event was observed. The next useful question is simply which products “Games” covers and where the confirmation wording can be inspected.

This is where information architecture becomes a consumer problem. A preference is useful only when its scope can be understood. Product, channel, state and confirmation belong in the same reading, even when the interface distributes them across several panels.

Our method gives the reader a way to describe an ambiguity without inventing a test result or mistaking a marketing control for a broader safety measure.