Playing wanted dead or a wild code Slot game means handing over personal data. This document details exactly how long we store it, why, and what technical protections underpin each category—all aligned with UK GDPR, the Data Protection Act 2018, and PCI DSS. We handle identity documents, financial transactions, gameplay telemetry, responsible gambling markers, and marketing consents, each with its unique retention clock. Identity records are kept for five years after account closure. Financial logs are stored for seven, meeting HMRC requirements. Gameplay data receives 24 months before anonymisation takes effect. Full card numbers never reach our systems—only tokenised aliases—and every byte is encrypted. Independent auditors review our automated deletion routines, and any schedule slip activates a full incident response. A version-controlled policy log documents every edit, and we offer you 30 days’ notice before material changes become effective. Subject access and deletion requests are managed within statutory deadlines.
Technology Framework and Data Residency
All data is stored in UK-based ISO 27001 Tier III+ data centres, with no replication outside the UK. A hot disaster recovery site in a separate UK zone updates every six hours. Backups are encrypted client-side and follow identical retention rules. We apply least privilege with hardware MFA for administrators, logging their sessions in an immutable three-year audit trail. Multi-factor authentication integrates a hardware token and biometric check. Penetration tests run quarterly, and an independent auditor validates automated purge schedules. Any deviation generates a Severity 1 incident, alerted to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, under the same deletion policies.
Encryption Key Lifecycle Management
Master keys change every 90 days automatically inside an HSM. New keys are not extracted in plaintext. Rotated keys are archived for the data’s retention period plus 12 months for lawful forensic access. When a data category is purged, its key is removed inside the HSM, making any backups unrecoverable. We link each key to a single data partition, never reuse, and conduct quarterly witnessed key ceremonies logged immutably for five years. The offline archive of old keys requires dual control and is stored on write-once media in a fireproof safe. Annual recovery drills ensure forensic decryption works when needed. No plaintext key material ever leaves the HSM boundary.
Financial Transaction and Payment Records
Deposit, withdrawal, and wager logs are kept for seven years from the transaction date, per HMRC and FCA rules. We do not store full PANs or CVVs. We collect only the BIN, last four digits, and a tokenised identifier. Chargeback disputes halt the contested record until final settlement, after which the seven-year clock continues. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs audited by auditors. Tokenised card references remain valid only while your account is open and are erased within thirty days of closing. Combined, anonymised totals endure for financial reporting without any personal identifiers. All financial data is encrypted and isolated from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways create vaulted tokens that associate your card to a non-sensitive alias. We keep them for the account lifetime plus a thirty-day grace period, then transmit deletion commands to the processor and erase our own mapping. The only remnant left behind is an anonymised transaction hash used in aggregate statements, themselves purged after seven years. No usable credentials ever exist on our systems. We check token revocation daily and raise incidents if deletion is unsuccessful. Tokens are bound to our merchant code and cannot be used other places. Weekly reconciliation verifies authenticity, and tokens tied to lost or stolen cards are revoked immediately. All token operations are documented and checked. Aggregate reports never disclose individual transaction hashes.
Session Gameplay and Analytics of Behavior Data
All spins on Wanted Dead Or a Wild logs reel positions, RNG seed, and net outcome with microsecond precision. We keep these raw logs for twenty-four months, then compact them into an anonymous statistical digest employed for game design. Session behavioural profiles—average bet, spin cadence, feature buy-ins—remain for the same 24-month window and are then deleted. Feature trigger heatmaps persist for 12 months before merging into a global model. RNG seed audit trails receive 36 months. Error diagnostics get 90 days. No individual gameplay data feeds into credit or marketing profiling. All logs are encrypted and off-limits to marketing teams.
- Spin-level logs: 24 months from event date, then anonymised aggregation
- Session behavioural profiles: 24 months from last session, then deleted
- RNG seed audit trails: 36 months to meet technical standards
- Feature trigger heatmaps: 12 months, then integrated into global model
- Error and crash diagnostic logs: 90 days, then removed
Controlled Gambling and Voluntary Exclusion Registers
Stake limits, time checks, and timeout settings are saved for your account’s lifetime and never deleted while it stays active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a specialized exclusion register held permanently under UKGC licence requirements. The register is secured separately, checked only at login or registration, and never employed for analytics. Access is limited to trained compliance staff, and all lookups are tracked for three years. The register stores only identity blocks—no monetary or gameplay records. We examine it annually to fix errors and remove deceased individuals. Apart from that, it remains everlasting. This retention is mandatory and free from deletion requests.
Session Awareness and Session Limit Enforcement
Reality check counters use transient session counters that reset every 24 hours, starting anew from your first spin after midnight. Your preferred interval—say, 30 minutes—is saved persistently and automatically reactivates when you visit again, even after a long break. Changing the interval mid-session sets the new value immediately for the next reminder. These settings are removed only upon confirmed account deletion. Session timer data lies in a dedicated, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for correctness. All timer configurations are verifiable through the same three-year access log standard. We never profile or market based on these settings.
Policy Review and Breach Notification Protocols
We evaluate this policy every six months or upon material change to the game or regulation. Reviews are minuted with DPO, CISO, and legal counsel. A public summary is posted in our privacy centre, minus confidential details. Material changes are sent 30 days ahead. Minor edits are silently recorded. If a breach occurs affecting data under this policy, we inform affected individuals within 72 hours if high risk, file with the ICO, and publish a transparency notice. Third-party processor breaches must follow the same protocol. We maintain a breach notification log audited quarterly. Post-incident reviews adjust controls as needed. Biannual tabletop exercises model misconfigurations and ransomware to test our response.
Policy Version Control and Update Log
We maintain a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log outlines exactly which sections changed and why. Previous versions remain accessible for comparison, so you can see precisely what was added or removed. Material modifications affecting your rights are conveyed via email at least thirty days in advance. Minor typographical fixes are deployed silently but still recorded. Each entry is cryptographically signed to prove integrity, and annual independent audits verify the log’s accuracy. The log is a living document reflecting our evolving data practices. You can access the full change log through a link in our privacy centre at any time. This transparent approach shows our commitment to accountable data governance.
Registration Account and Verification of Identity Data
Core identity profiles—official ID scans, residence proof, biometric selfie verifications—are kept for 5 years after your last session or account closure, whichever is later. This covers contractual time limits and AML obligations. We obtain only the necessary details: document ID, validity, citizenship. The original image gets deleted upon extraction. Once 5 years pass, all raw data is removed, but a cryptographic hash of the verification outcome remains for another two years inside an logging system. Identity data sits encrypted at rest with AES-256-GCM, stored away from analytics, and every data access is recorded for 3 years. Non-essential fields like place of birth are discarded at verification stage to minimize the data size. Annual reviews verify accuracy and automatically remove expired data.
Document Upload and Biometric Handling
Provide an ID through our protected portal and automatic verification completes within a minute and a half. We pull the document number, expiry, citizenship, and a confidence score, then shred the original image right away—it is never stored on disk. The initial file stays in an in-memory buffer and vanishes after processing. A compressed, stamped small image is generated for audit purposes and retained only for the identity verification period. That thumbnail lives in a immutable vault with tight controls and is never shown to support staff. Collected information are encrypted and stored for the five-year-plus-two hash window. All operations runs on ISO 27001 certified UK servers, and every preview retrieval is recorded immutably.
Specifics of Biometric Data
Liveness checks record a quick video completely in memory. Images are processed and discarded within milliseconds of time. Only a numerical vector of facial landmarks survives. This data set lacks any image data and cannot be reverse-engineered into a face. It is kept for the time of identity verification and is permanently deleted upon account termination or after five years. The numerical representation sits in a dedicated HSM with automatic expiration and is never transferred. Authentication checks happen inside the HSM’s protected enclave without exposing the original vector. The numerical representation is linked to a pseudonymous identifier unlinked from marketing profiles, which makes re-identifying highly challenging. Even system administrators are unable to view or rebuild facial attributes from the stored vector.
Access Request and Erasure Workflows
When an SAR lands, we compile a organized JSON/CSV export of all non-purged data within one month, extendable by two months for complex cases. The export includes live databases, encrypted archives, and processor tokens, sent via a one-time secure link that expires in 72 hours. For deletion, we implement a cascade: immediate account suppression and token revocation, then batched erasure of all personal data not subject to legal hold. We produce a confirmation report specifying erased versus retained categories and their justifications. This report is kept as auditable proof for as long as the longest surviving data category. All requests are recorded immutably for five years.
Fundamental Definitions and Range of Personal Data
We adopt a comprehensive approach on what counts as personal data. Direct identifiers—name, email, billing address, masked payment details—coexist with indirect signals like hashed IP addresses, device fingerprints, browser agents, and advertising tokens. Behavioural data includes session length, bet sizing, spin velocity, and how often feature triggers fire. Even pseudonymised logs can identify again a person when stitched together, so we handle them as personal. Our lawful bases are contractual necessity, legitimate interest for fraud prevention, and explicit consent for game-related marketing. Full card numbers get tokenised before storage. We never collect special category data. Encryption and access controls apply uniformly, and retention rules cover live databases, archives, and backups without exception. Each window commences from the last activity or transaction date, spelled out below. We reassess definitions every six months to stay aligned with regulatory guidance.
Marketing Consent and Correspondence Records
We store your consent record—with time stamp, IP-marked, and method-recorded—for the duration of our partnership plus six years after revocation, to satisfy PECR rules. Delivery logs for e-mails, push messages, and SMS are retained for only thirteen months. Withdrawing consent right away halts communications while retaining historical proof. A segmented database guarantees suppression without lag, and consent logs are stored in a separate compliance archive. Dispatch records contain metadata only—topic, time stamp, condition—not full message body. The six-year post-withdrawal timeframe reflects the statute of limitations for regulatory investigations. Quarterly audits verify no expired consents trigger mailings. We never tailor offers with gameplay or financial data beyond explicit authorisations.