Registration at an online casino now routinely asks for a selfie, a short head-turn video, or both. The facial matching that follows produces a biometric template, and the moment that template is stored, the operator is processing special category data under UK GDPR. The question that tends to get buried in onboarding design is not whether the check is lawful, but how long the resulting biometric record should survive. Operators working under a Curaçao Gaming Authority licence, such as GALAKTIKA N.V. (licence OGL/2024/169/0146), face two retention schedules pulling in different directions: identity records they must keep for the regulator, and biometric templates that have no equivalent statutory shelf life. This piece treats those as separate decisions, because they are. It also looks at where a Lex Casino promo code such as WELCOME2026 fits into the flow, and why claiming a Lex Casino welcome package should never require the player to hand over more biometric data than verification already captured.
The analytical trap is to assume that because a licence requires identity records to be retained, the biometric template used to confirm that identity can be kept for the same period. That collapses a licensing obligation into a data protection one. A document scan proves who someone is and can be re-inspected; a facial template proves a match at a point in time and can be regenerated only by asking the player to repeat the check. Retention of the template is therefore a GDPR necessity and proportionality judgement, not an administrative convention, and the 30 day completion window attached to a Lex Casino bonus has nothing to do with it. The two clocks run independently, and conflating them is where most redemption troubleshooting and most regulatory exposure begin.
The sections below work from the registration flow outwards: where liveness sits, why the output is Article 9 data, which lawful basis holds up, and how to set a deletion trigger that survives scrutiny. Promotional mechanics, including how a Lex Casino bonus code interacts with a verified account, come later, since the bonus directory and cashier interface should sit downstream of a completed, proportionate KYC process rather than alongside it.
How liveness checks fit into casino registration and KYC onboarding
Registration at a licensed online casino has become a sequence of checks rather than a single form. Before a player can deposit or claim a Lex Casino promo code, the operator typically runs an email and phone verification step, a document upload stage, and, increasingly, a liveness check that captures a short video or a burst of frames from the device camera. That capture is matched against the photo page of an identity document, and the result feeds a decision engine that either passes the account, flags it for manual review, or rejects it outright.
The order matters. Most operators place liveness detection after the basic data capture but before the first withdrawal, because that is the point where the cost of a false identity becomes real money. Document verification alone confirms that a plausible ID exists. Facial matching confirms that the person presenting it is the person named on it. Age assurance depends on both: a forged or borrowed passport defeats a document-only check, while a liveness pass against a genuine document makes underage registration substantially harder.
Operators running under GALAKTIKA N.V. sit within a framework supervised by the Curaçao Gaming Authority under licence OGL/2024/169/0146. That licence does not prescribe a specific liveness vendor, but it does require the operator to know its customer and to keep records that demonstrate the check happened. In practice this pushes operators toward automated liveness rather than manual review, because automation produces an auditable timestamp, a confidence score and a stored decision that a manual reviewer would have to reconstruct from notes.
The typical flow looks like this:
- Account creation with name, date of birth, address and contact details.
- Email and mobile verification, sometimes with a one-time code.
- Identity document capture, front and back, with checks on format and tampering.
- Liveness capture: a short selfie video or frame sequence with a prompted action such as turning the head or blinking.
- Facial comparison between the live capture and the document portrait, scored against a threshold.
- Decision routing: automatic approval, manual review queue, or rejection with a reason code.
Each of those steps generates a different category of data with a different legal character. The document image is ordinary personal data. The liveness video, once it is processed to extract a facial template for the purpose of unique identification, is not. That distinction is where the retention argument starts, and it is the reason a single „keep everything for five years“ policy is difficult to defend. The account record, the document image and the biometric template may all relate to the same person, but they are not the same processing operation, and they should not share a deletion date by default.
Players notice the friction. A failed liveness check during registration can block access to the cashier and therefore to any bonus activation, including a Lex Casino welcome package tied to a specific code. Operators that explain the step in advance, and that offer a fallback such as a manual video call, see fewer abandoned registrations. The trade-off is real: stricter capture reduces fraud, but every additional prompt adds a drop-off point.
Why liveness verification output is special category biometric data under UK GDPR
Most casino onboarding flows treat a liveness check as a routine step: the player turns their head, reads a phrase, blinks, and the session moves on to the next screen. The legal classification of what that check produces is anything but routine. Under UK GDPR, biometric data is personal data resulting from specific technical processing relating to the physical or physiological characteristics of a person, which allows or confirms unique identification. Article 9(1) then lists it among the special categories of data whose processing is prohibited unless a condition in Article 9(2) applies. Recital 51 draws the line that matters here: photographs as such are not automatically biometric data, and processing becomes biometric only when the purpose is uniquely identifying a person.
That distinction is not cosmetic. A passport scan, a selfie and a short video clip are ordinary personal data when used to check that a name matches a face and that the document is not forged. The same footage becomes Article 9 data the moment the system converts facial geometry into a template and compares it against the document photo to confirm that this person is that applicant. The test is functional, not technical: purpose plus means. A passive liveness model that only scores „live versus spoof“ and discards the frame may sit outside Article 9. A facial matching engine that retains a mathematical template almost certainly sits inside it.
The practical consequence is that consent to a privacy notice is not enough on its own to carry the processing. Article 9(2)(a) requires explicit consent, and Article 9(2)(g) requires a substantial public interest basis backed by a documented policy and, in the UK, an appropriate policy document under the Data Protection Act 2018. Both routes impose obligations that flow downstream: a lawful basis statement, a record of processing activity, and a data protection impact assessment proportionate to the risk of misidentification or template leakage. The Article 9 classification also sharpens the retention analysis, because a biometric template kept „for the duration of the account“ is processing for a purpose that must be separately justified from the identity record the template was matched against.
The classification also affects the operator chain. Where a brand such as GALAKTIKA N.V. runs verification through a third-party vendor, the vendor is a processor of special category data, and the contract must reflect that. The Curaçao Gaming Authority, which issued licence OGL/2024/169/0146, sets identity and age assurance expectations, but it does not authorise indefinite biometric storage. UK GDPR does not care that the operator is offshore either: if the check is offered to UK residents, the Article 9 analysis applies. Treating liveness output as ordinary verification footage is the most common error in the flow, and it is the one that costs most when a supervisory authority asks what template was stored, for how long, and on what basis.
Choosing a lawful basis: explicit consent versus substantial public interest
Two Article 9 conditions are realistically available for KYC liveness checks in a gambling context: explicit consent under Article 9(2)(a), or substantial public interest under Article 9(2)(g) read with the DPA 2018 Schedule 1, Part 2, paragraph 10 (preventing or detecting unlawful acts). Most operators reach for consent first because it looks simpler. It usually is not.
Consent under UK GDPR must be freely given, specific, informed and unambiguous, signalled by a clear affirmative act. Gambling onboarding strains every one of those limbs. A player cannot complete registration, cannot deposit, and cannot claim a welcome offer without passing the liveness check. Where refusal blocks the entire service, the ICO’s position is that consent is rarely free. Add the imbalance of the relationship (a commercial operator setting the condition) and the fact that Article 9(2)(a) consent can be withdrawn at any time, and you have a basis that is fragile exactly when you need it to be durable: at the point a regulator or a customer disputes the processing.
Withdrawal is the practical killer. If a player withdraws consent mid-relationship, the operator must stop processing the template. But the account is already open, the identity check has already been performed, and the Curaçao-licensed entity still carries ongoing AML obligations. Consent creates a stop switch the operator cannot honour without either closing the account or arguing the processing was never really consent-based. That contradiction is difficult to defend in a complaint file.
The substantial public interest route is harder to set up and easier to live with. It requires an appropriate policy document, a documented assessment of why the processing is necessary, retention specifics, and a record that the condition applies. Paragraph 10 covers processing for the prevention or detection of unlawful acts, which maps onto AML and age-assurance checks. The condition does not depend on the player’s ongoing permission, so withdrawal is not a live risk. The trade-off is evidential: the operator must be able to show necessity and proportionality, and must publish the policy document or make it available on request.
A workable pattern is to rely on substantial public interest for the liveness check and template comparison, and reserve consent for anything genuinely optional, such as reusing a stored template for faster future logins. Mixing the two without labelling which basis covers which step is where files fall apart.
| Factor | Explicit consent (9(2)(a)) | Substantial public interest (9(2)(g) + DPA para 10) |
|---|---|---|
| Withdrawal | Available at any time; halts processing | Not applicable |
| Freely given test | Weak where access is conditional | Not engaged |
| Documentation | Consent record and granular notice | Appropriate policy document, necessity assessment |
| Fit for AML KYC | Poor, because of the stop switch | Strong |
Whichever route is chosen, the decision belongs in the DPIA and the record of processing, not in a paragraph of marketing copy.
The retention question: separating biometric templates from Curaçao-mandated identity records
This is where most compliance write-ups blur two separate questions. The retention period for a facial biometric template and the retention period for a passport scan look like the same housekeeping task. They are not. One is set by a regulator’s record-keeping rule and the other is a data protection decision that has to be justified from first principles, and treating them as a single schedule is how operators end up holding templates for years with no lawful reason.
Start with the identity records. Lex Casino operates under GALAKTIKA N.V., and GALAKTIKA N.V. is regulated by the Curaçao Gaming Authority under licence OGL/2024/169/0146. That licence framework requires the operator to be able to demonstrate who each customer is, and to produce evidence on request during the life of the account and for a defined period afterwards. Keeping a copy of the ID document, a dated note of when verification completed, and the audit trail for the decision is a licensing obligation. It is processed under a legal obligation basis and the retention clock is driven by the regulator, not by the operator’s preference.
The biometric template is a different animal. It exists for one purpose: to answer the question „is the person in front of the camera the person on this document“ at the moment of onboarding. Once that answer has been recorded as a pass or fail, the template has served its purpose. Under UK GDPR the template is special category data, and the proportionality test for keeping it past the verification event is hard to meet. A stored template is a stored identifier that can be breached, reused for re-authentication the customer never agreed to, or repurposed for fraud analytics. None of those uses is covered by the consent or public interest condition that justified the original check.
So the deletion triggers diverge:
- Biometric template: deleted on verification completion, or within a short documented window (hours, not months) where a manual review queue requires it to be held. Vendors should be contractually bound to the same trigger, with a deletion certificate or API confirmation.
- Liveness video clip: if the vendor retains footage rather than a template, the same logic applies. A few days for dispute resolution is defensible; indefinite storage is not.
- Identity documents: retained for the period the Curaçao licence requires, then deleted or anonymised. Access should be role-restricted to compliance staff.
- Decision record: a pass/fail result, timestamp, and the verification method, kept for the licensing period without the underlying biometric.
The practical test is whether the operator can answer, for any given account, „where is the template now, and what is the date it will be destroyed.“ If the answer is „in the KYC file, same as the passport,“ the two schedules have been merged by accident. The guide does not handle user accounts or transaction processing, but it can say this much: a retention policy that cannot name a deletion date for the template is not a policy, it is a hope.
Promotional mechanics: Lex Casino promo code WELCOME2026 and the welcome package
What WELCOME2026 actually unlocks
The Lex Casino promo code WELCOME2026 is a single voucher code that triggers the Lex Casino welcome package: 225% up to €900 plus 400 free spins. You can find details of the offer at https://lv-lex-casino.com/en/promo-code/ and the code is entered in the cashier interface before or alongside the qualifying deposit, with a minimum entry threshold of €20. Anything below that does not activate the package, and a deposit made without the code in place will not retroactively attach it.
Mechanically, this is a bonus activation step, not a registration step. The account can exist, and even be funded, before the Lex Casino bonus code is applied. What the code does is flag the deposit as qualifying, which then releases the matched percentage and the free spins in the amounts set out in the promotional terms. The 400 free spins are typically staged rather than credited in one block, so players should read the schedule in the bonus directory attached to the offer.
The obligations that come with it are the usual ones. The Lex Casino welcome package requires a 40x wagering obligation on bonus funds, and the wagering requirement has a completion window of 30 days from credit. Miss the window and the balance is removed. The 225% up to €900 ceiling means the match is proportional to the deposit, so a €100 deposit yields €225 bonus, not the full €900.
How bonus code entry interacts with a verified account
Here is where the KYC thread from earlier sections meets the marketing thread. A code can be entered and accepted on an unverified account, but withdrawal of anything won from the Lex Casino free spins or the matched bonus will stall at the first cash-out request until identity verification clears. In practice, operators front-load verification at registration precisely to avoid that friction later.
That matters for the biometric question. A player who completes a liveness check at sign-up, then claims a Lex Casino bonus code weeks later, is not re-verified for the bonus itself. The verification record already exists; the bonus system simply checks its status flag. If the flag reads verified, the promotion proceeds. If it reads pending or expired, the cashier will block the withdrawal path, not the deposit path.
Two practical points follow. First, the code is case-sensitive in most cashier implementations, so WELCOME2026 should be pasted rather than typed. Second, redemption troubleshooting almost always traces back to one of three things: deposit below €20, code entered after the deposit settled, or an account that has previously claimed a welcome offer. Lex Casino, like most operators under GALAKTIKA N.V., restricts the Lex Casino welcome package to first-time depositors only.
Beyond the welcome offer, Lex Casino offers ongoing promotions such as cashback and free-spin drops. Those sit outside the WELCOME2026 code and carry their own terms, so the code should not be assumed to stack with them.
Compliance checklist for operators and player-facing transparency
The practical test for any operator running liveness checks is whether the paperwork matches the pipeline. A DPIA that describes „identity verification“ in general terms while the vendor stores a facial template for 90 days is not a DPIA, it is a placeholder. Article 35(3)(b) and (c) of the UK GDPR push large-scale special category processing into DPIA territory, and a casino onboarding flow at scale qualifies. The assessment should name the vendor, the template format, the matching threshold, the retention period for both the template and any source images, and the transfer mechanism if matching happens outside the UK or EEA. If the vendor cannot supply those facts in writing, that is a finding, not an inconvenience.
Records of processing under Article 30 need the same specificity. List biometric verification as a separate processing activity from document verification, with its own lawful basis, its own retention entry, and its own recipient list. GALAKTIKA N.V. is regulated by the Curaçao Gaming Authority under licence OGL/2024/169/0146, and Curaçao rules on identity record retention do not automatically extend to the biometric template. Keep the two schedules apart in the record. A common failure is a single „KYC records: 5 years“ line that quietly swallows the template, which is exactly the conflation that causes trouble when a deletion request arrives.
Template deletion should be automated and evidenced, not left to a quarterly tidy-up. Set the trigger at the point the match decision is recorded, keep the decision and the audit trail, and purge the template and raw frames within a defined window. Log the deletion with a timestamp and a job identifier so you can answer a subject access request or an ICO query without guesswork. Test the job: run a sample account through the full cycle and confirm the template is actually gone from the vendor’s environment as well as your own.
Privacy notice wording needs to be plain and specific. Say that a live image is captured, that it is compared against the document photo, that the resulting template is biometric data under Article 9, how long each artefact is kept, and how to object or complain. Vague phrases such as „we may use biometric technology to protect you“ fail the transparency test in Articles 13 and 14.
On the player side, verification gates the promotional layer. A Lex Casino promo code such as WELCOME2026 unlocks 225% up to €900 plus 400 free spins, but bonus activation only completes against a verified account, and the qualifying deposit minimum is €20. The welcome package carries a 40x wagering obligation with a 30 day completion window, so a liveness check that stalls for a week eats into the clock. Players should expect the cashier interface to show bonus status only after KYC clears, and should keep the voucher code confirmation until the free spins appear. Where a Lex Casino bonus code fails to apply, redemption troubleshooting starts with verification status, not with support.
If you are the operator, the next step is to open the processing record for your liveness vendor and check one field: the retention period attached to the biometric template, not the identity record. If that field mirrors the document retention schedule required under Curaçao licence OGL/2024/169/0146, you have a proportionality gap to close before the next audit. If it is blank, treat it as an unlawful indefinite hold and set a deletion trigger today. Document the DPIA outcome, the Article 9 condition relied on, and the template deletion date in the same file, because a regulator will ask for all three together and a vendor contract alone will not answer the question.
If you are a player, the practical test is simpler. Ask support, in writing, how long the biometric template from your liveness check is held and whether it is deleted once the facial match is confirmed. A compliant operator should answer without redirecting you to a generic privacy page. Note that Lex Casino operates under GALAKTIKA N.V., regulated by the Curaçao Gaming Authority, and holds no local licence in Latvia, Germany, Austria and Lithuania, so your practical remedies sit with the Curaçao regulator rather than a national gambling authority. Keep the reply, keep your verification timestamp, and treat any refusal to name a retention period as a data protection complaint in waiting. The same discipline applies to promotions: before you enter the Lex Casino promo code WELCOME2026 to unlock 225% up to €900 plus 400 free spins, confirm your account is fully verified, because the Lex Casino welcome package requires a qualifying deposit of at least €20 and carries a 40x wagering obligation with a 30 day completion window. A Lex Casino bonus code claimed on an unverified account is the most common source of redemption troubleshooting, and no amount of free spins compensates for a template held without a deletion date.