/** * Twenty Twenty-Five functions and definitions. * * @link https://developer.wordpress.org/themes/basics/theme-functions/ * * @package WordPress * @subpackage Twenty_Twenty_Five * @since Twenty Twenty-Five 1.0 */ // Adds theme support for post formats. if ( ! function_exists( 'twentytwentyfive_post_format_setup' ) ) : /** * Adds theme support for post formats. * * @since Twenty Twenty-Five 1.0 * * @return void */ function twentytwentyfive_post_format_setup() { add_theme_support( 'post-formats', array( 'aside', 'audio', 'chat', 'gallery', 'image', 'link', 'quote', 'status', 'video' ) ); } endif; add_action( 'after_setup_theme', 'twentytwentyfive_post_format_setup' ); // Enqueues editor-style.css in the editors. if ( ! function_exists( 'twentytwentyfive_editor_style' ) ) : /** * Enqueues editor-style.css in the editors. * * @since Twenty Twenty-Five 1.0 * * @return void */ function twentytwentyfive_editor_style() { add_editor_style( 'assets/css/editor-style.css' ); } endif; add_action( 'after_setup_theme', 'twentytwentyfive_editor_style' ); // Enqueues style.css on the front. if ( ! function_exists( 'twentytwentyfive_enqueue_styles' ) ) : /** * Enqueues style.css on the front. * * @since Twenty Twenty-Five 1.0 * * @return void */ function twentytwentyfive_enqueue_styles() { wp_enqueue_style( 'twentytwentyfive-style', get_parent_theme_file_uri( 'style.css' ), array(), wp_get_theme()->get( 'Version' ) ); } endif; add_action( 'wp_enqueue_scripts', 'twentytwentyfive_enqueue_styles' ); // Registers custom block styles. if ( ! function_exists( 'twentytwentyfive_block_styles' ) ) : /** * Registers custom block styles. * * @since Twenty Twenty-Five 1.0 * * @return void */ function twentytwentyfive_block_styles() { register_block_style( 'core/list', array( 'name' => 'checkmark-list', 'label' => __( 'Checkmark', 'twentytwentyfive' ), 'inline_style' => ' ul.is-style-checkmark-list { list-style-type: "\2713"; } ul.is-style-checkmark-list li { padding-inline-start: 1ch; }', ) ); } endif; add_action( 'init', 'twentytwentyfive_block_styles' ); // Registers pattern categories. if ( ! function_exists( 'twentytwentyfive_pattern_categories' ) ) : /** * Registers pattern categories. * * @since Twenty Twenty-Five 1.0 * * @return void */ function twentytwentyfive_pattern_categories() { register_block_pattern_category( 'twentytwentyfive_page', array( 'label' => __( 'Pages', 'twentytwentyfive' ), 'description' => __( 'A collection of full page layouts.', 'twentytwentyfive' ), ) ); register_block_pattern_category( 'twentytwentyfive_post-format', array( 'label' => __( 'Post formats', 'twentytwentyfive' ), 'description' => __( 'A collection of post format patterns.', 'twentytwentyfive' ), ) ); } endif; add_action( 'init', 'twentytwentyfive_pattern_categories' ); // Registers block binding sources. if ( ! function_exists( 'twentytwentyfive_register_block_bindings' ) ) : /** * Registers the post format block binding source. * * @since Twenty Twenty-Five 1.0 * * @return void */ function twentytwentyfive_register_block_bindings() { register_block_bindings_source( 'twentytwentyfive/format', array( 'label' => _x( 'Post format name', 'Label for the block binding placeholder in the editor', 'twentytwentyfive' ), 'get_value_callback' => 'twentytwentyfive_format_binding', ) ); } endif; add_action( 'init', 'twentytwentyfive_register_block_bindings' ); // Registers block binding callback function for the post format name. if ( ! function_exists( 'twentytwentyfive_format_binding' ) ) : /** * Callback function for the post format name block binding source. * * @since Twenty Twenty-Five 1.0 * * @return string|void Post format name, or nothing if the format is 'standard'. */ function twentytwentyfive_format_binding() { $post_format_slug = get_post_format(); if ( $post_format_slug && 'standard' !== $post_format_slug ) { return get_post_format_string( $post_format_slug ); } } endif; UKGC and GDPR: checklist for retaining promotional records – Desco Coatings of Houston

UKGC and GDPR: checklist for retaining promotional records

Promotional records are the part of a casino’s data estate that compliance teams most often get wrong, because they sit across two regulatory regimes at once. The UK Gambling Commission wants to see what you offered, to whom, and on what terms, for years after the fact. The Information Commissioner’s Office wants you to hold no more personal data than you need, for no longer than necessary. A retention checklist that satisfies both is not a nice-to-have. It is the difference between a clean audit and a section 116 licence review with awkward questions about deleted logs. The five-point framework below is the one I would apply to any operator running a Lady Luckmore-style promotions programme, and it is deliberately narrow: consent, bonus issuance, wagering progress, redemption evidence, and identity verification.

Why promotional records sit across two regulatory regimes

Lady Luckmore is operated by Grace Media (Gibraltar) Limited and holds UK Gambling Commission licence 057869-R-334655-008. That licence brings with it the Gambling Commission’s record-keeping expectations under the Licence Conditions and Codes of Practice, which in practice means an operator must be able to reconstruct a customer’s promotional history on demand. Separately, the UK GDPR and the Data Protection Act 2018 require a lawful basis for processing, a defined retention period, and secure deletion once that period ends. The tension is real: gambling regulation pushes towards keeping more, data protection pushes towards keeping less, and the resolution is a documented schedule that names each record type, its purpose, its retention period, and its deletion method.

The five-year floor is the anchor. Five years from the end of the customer relationship is the working assumption most UK operators apply to promotional and transactional records, because it covers the limitation period for most contractual claims and aligns with the Gambling Commission’s expectation that records remain available for compliance review. Anything shorter needs a written justification. Anything longer needs a documented legal or regulatory reason, not a vague “we might need it”.

There is a practical wrinkle that catches operators out. Promotional data is not one dataset. It is scattered across the CRM, the bonus engine, the payments ledger, the KYC provider, and the affiliate platform. A retention policy that exists only as a paragraph in a privacy notice, with no mapping to actual systems, is a policy that will fail on the first subject access request or the first audit sample.

The five-point retention checklist for promotional records

This is the core of the article, and it is worth stating plainly: a data retention checklist for promotional records must include player consent records, bonus issuance logs, wagering progress, redemption evidence, and identity verification checks, all retained for a minimum of five years per UKGC and GDPR requirements, with secure deletion after that period. Each of the five points below maps to a specific system and a specific failure mode.

Point one: player consent records. Every marketing communication needs a provable opt-in, with a timestamp, the channel, the wording the customer saw, and the source. Consent for promotional emails is not the same as consent for SMS, and neither is the same as acceptance of bonus terms at the point of deposit. Store the consent state as an immutable log entry, not an overwritable field. If a customer withdraws consent, record the withdrawal with equal care, because the audit question is always “show me the state at the time of the send”.

Point two: bonus issuance logs. This is where the Lady Luckmore promotions programme generates most of its record volume. The welcome package is hidden until registration, which means the terms a player accepts are only visible after account creation, so the issuance log must capture the exact terms version presented at that moment. Weekly Rewards awards 10 free spins for a £25 deposit and wager and 20 free spins for a £50 deposit and wager, and Weekly Rewards spins are credited by 17:00 every Monday. Each credit needs a record: player ID, promotion ID, terms version, credit timestamp, and the triggering deposit reference. Promo code MEGA grants 10 spins for a £10 slots wager, and seasonal codes such as BOOST50 and SANTA need the same treatment, including the code expiry window. Full details of the programme are set out at https://ladyluckmore-casino.uk/promotions/ for reference.

Point three: wagering progress. The 25 percent max bet rule applies to bonus play, and proving compliance after the fact depends entirely on the wagering ledger. Record each qualifying wager against the bonus, the stake, the game, the timestamp, and the running contribution toward the wagering requirement. If a player breaches the max bet rule and the bonus is voided, the void decision and its evidential basis must be retained alongside the wagering record. Without this, a complaint about a confiscated bonus becomes unwinnable.

Point four: redemption evidence. When free spins are played and winnings converted, the redemption event needs a record linking the spin batch to the resulting credit, the withdrawal cap applied, and the payout method. Sweetest Slots offers prize drops on selected slots, and those prize drop awards need the same redemption trail as a standard free spin conversion, including the draw reference and the award notification. Payment method matters here: PayPal and Google Pay transactions carry their own reference numbers, and the promotional record should store that reference so the finance ledger and the bonus ledger can be reconciled.

Point five: identity verification checks. Promotional records are personal data, and the link between a bonus and a verified identity is what makes the whole chain auditable. Store the KYC outcome, the verification timestamp, the document type, and the check reference, not the document images themselves. Images belong in the KYC provider’s vault with their own retention schedule. The promotional record needs only enough to prove the identity was verified before the bonus was credited and before any withdrawal was processed.

How long each record type should actually be kept

Five years from the end of the customer relationship is the default, but the clock start differs by record type. Consent records run from the date consent was given or withdrawn, whichever is later. Bonus issuance and wagering records run from the date of the promotion’s final settlement, which for a reload bonus or a seasonal code is usually the expiry of the wagering window. Redemption evidence runs from the date of the withdrawal. Identity verification records run from the end of the relationship, and where anti-money-laundering rules apply, the five-year clock starts at the end of the relationship rather than the date of the check.

The deletion step is where most schedules quietly fail. Secure deletion means the record is gone from production, from backups within the backup rotation window, and from any analytics warehouse that ingested it. A retention policy that deletes from the primary database but leaves a five-year-old copy in a data lake is not compliance, it is a breach waiting for a subject access request to expose it. Document the deletion method, the date, and the person who authorised it.

Operational controls that make the checklist survive an audit

A checklist on paper is worth nothing if the underlying systems cannot produce the records on request. The first operational control is a data map that names, for each of the five record types, the system of record, the retention period, the deletion owner, and the retrieval method. Keep it current. When a new promotion mechanic launches, the data map gets updated before the mechanic goes live, not after.

The second control is version control on terms. Lady Luckmore hides the welcome package until registration, and Sweetest Slots prize drops run on selected slot games with their own rules. Every terms document needs a version number and an effective date, and every promotional record needs to reference the version the player actually saw. When a complaint arrives about a term that changed three months ago, the version reference is what settles it.

The third control is access discipline. Promotional records contain personal data, so access should be role-based and logged. Customer support needs read access to resolve queries. Compliance needs read access for audits. Marketing needs aggregated access, not row-level access to individual wagering histories. Every access event should be logged and retained for the same five-year period, because the audit trail for who looked at a record is itself a record.

The fourth control is the subject access request workflow. A player can ask for a copy of their promotional records at any time, and the response must be complete and within one month. Test the workflow quarterly with a synthetic request. If assembling the five record types takes more than a few days, the data map is wrong and the retention schedule is theoretical rather than operational.

Responsible gambling data and the deletion boundary

Responsible gambling records sit at the edge of the promotional dataset and need their own handling. Interactions flagged through GamStop, GamCare, BeGambleAware, or Gamblers Anonymous referrals are not promotional records, but they often sit in the same CRM and get caught in the same deletion sweep. Exclude them explicitly. Self-exclusion and responsible gambling interaction records carry their own retention obligations, and deleting them alongside expired bonus logs is a serious error.

The deletion boundary also matters for the UKGC licence relationship. Lady Luckmore does not publish no deposit bonuses, which removes one common record type from the schedule, but the absence of a record type is itself something to document. An auditor who asks “where are your no deposit bonus records” should find a written note explaining that the operator does not offer them, not a blank space that looks like a deletion gap.

The final piece is the annual review. Retention schedules drift because promotions change, systems get replaced, and new codes appear. Once a year, walk the five points against the live promotion calendar, confirm the deletion jobs ran, spot-check a sample of records for completeness, and sign off. The sign-off document is short, but it is the artefact that turns a checklist into evidence of a functioning control environment.

Build the schedule around the five record types, name a system of record for each, set the five-year clock correctly per record type, and prove the deletion actually happens. That combination is what a UKGC reviewer and an ICO case officer both want to see, and it is achievable without turning the compliance team into a records-management department. Start with the data map, version the terms, test the subject access workflow, and keep responsible gambling records out of the promotional deletion sweep. The rest follows from those four moves.