Playing Wanted Dead Or a Wild Slot means handing over personal data https://wanteddeadorwild.uk/. This document sets forth exactly how long we keep it, the reasons, and what technical protections support each category—all built around 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 specific retention clock. Identity records are kept for five years after account closure. Financial logs are stored for seven, satisfying HMRC requirements. Gameplay data gets 24 months before anonymisation takes effect. Full card numbers never enter 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 records every edit, and we offer you 30 days’ notice before material changes are implemented. Subject access and deletion requests are handled within statutory deadlines.
Core Definitions and Range of Personal Data
We take a broad view on what counts as personal data. Direct identifiers—name, email, billing address, masked payment details—sit alongside indirect signals like hashed IP addresses, device fingerprints, browser agents, and advertising tokens. Behavioural data encompasses session length, bet sizing, spin velocity, and how often feature triggers fire. Even pseudonymised logs can re-identify 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 extend across live databases, archives, and backups without exception. Each window starts ticking from the last activity or transaction date, spelled out below. We revisit definitions every six months to keep pace with regulatory guidance.
SAR and Deletion Processes
When a subject access request arrives, we produce 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, delivered via a one-time secure link that expires in 72 hours. For deletion, we implement a cascade: immediate account suppression and token revocation, then scheduled erasure of all personal data not subject to legal hold. We generate a confirmation report specifying erased versus retained categories and their justifications. This report is maintained as auditable proof for as long as the longest surviving data category. All requests are recorded immutably for five years.
Registration Account and Verification of Identity Data
Core identity profiles—official ID scans, residence proof, biometric selfie matches—are kept for 5 years after your last session or account closure, whichever comes later. This covers contractual time limits and AML obligations. We retrieve only the key information: document ID, expiry, country of citizenship. The high-resolution image gets destroyed upon extraction. Once five years pass, all source data is purged, but a cryptographic hash of the verification result lives on for an additional two years inside an audit log. Personal identity information sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every access is logged for three years. Optional fields like place of birth are deleted at verification time to reduce the data size. Yearly audits ensure precision and proactively delete expired entries.
File Upload and Biometric Data Processing
Provide an ID through our protected portal and automated checking completes within a minute and a half. We extract the ID number, expiration date, nationality, and a confidence score, then delete the original image instantly—it never touches disk. The initial file stays in an in-memory buffer and disappears after processing. A reduced, marked preview is generated for compliance purposes and stored only for the ID lifecycle. That thumbnail lives in a write-once vault with rigorous controls and is never shown to support staff. Retrieved data are encoded and kept for the five-year plus two-year hash timeframe. All processing runs on ISO 27001 certified UK servers, and every small image access is logged permanently.
Biometric Information Details
Liveness checks record a quick video solely in memory. Video frames are analysed and removed within milliseconds of time. Only a data vector of facial landmarks remains. This numerical representation lacks any image data and cannot be reverse-engineered into a picture. It is kept for the entire identity verification process and is permanently deleted upon account closure or after five years. The vector sits in a hardware security module with automatic expiration and is never transferred. Login comparisons happen inside the HSM’s secure enclave without disclosing the raw vector. The vector is associated with a pseudonym separated from marketing data, which makes re-identification extremely difficult. Even system admins cannot see or rebuild facial features from the stored vector.
Payment Transaction and Billing Records
Deposit, withdrawal, and wager logs are kept for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised identifier. Chargeback disputes freeze the contested record until final resolution, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs verified by auditors. Tokenised card references remain valid only while your account is active and are deleted within thirty days of termination. Combined, anonymised totals endure for financial reporting without any personal information. All financial data is coded and separated from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways create vaulted tokens that associate your card to a non-sensitive identifier. We store them for the account lifetime plus a thirty-day grace interval, then issue deletion commands to the processor and erase our own reference. The only trace left behind is an anonymised transaction hash used in aggregate reports, themselves deleted after seven years. No usable credentials ever exist on our systems. We check token revocation daily and initiate incidents if deletion fails. Tokens are bound to our merchant code and cannot be used elsewhere. Weekly reconciliation verifies correctness, and tokens tied to lost or stolen cards are revoked immediately. All token operations are logged and verifiable. Aggregate reports never reveal individual transaction hashes.
Marketing Consent and Message Logs
We maintain your consent log—time-stamped, with IP address, and with capture method—for the life of our relationship plus six years after revocation, to comply with PECR requirements. Dispatch records for emails, push notifications, and SMS are kept for only thirteen months. Cancelling consent instantly blocks communications while keeping historical proof. A divided database guarantees suppression without lag, and consent logs are kept in a distinct compliance archive. Delivery logs hold metadata only—heading, time, state—not full message text. The six-year post-withdrawal timeframe mirrors the statute of limitations for regulatory inquiries. Quarterly audits confirm no expired consents trigger mailings. We never personalise offers with gameplay or financial data beyond explicit permissions.
Gaming Session and Behavioural Analytics Data
Each spin on Wanted Dead Or a Wild tracks reel positions, RNG seed, and net outcome with microsecond precision. We keep these raw logs for twenty-four months, then compress them into an anonymous statistical digest used for game design. Session behavioural profiles—average bet, spin cadence, feature buy-ins—persist for the same 24-month window and are then deleted. Feature trigger heatmaps stay for 12 months before merging into a global model. RNG seed audit trails have 36 months. Error diagnostics receive 90 days. No individual gameplay data goes into credit or marketing profiling. All logs are encrypted and off-limits to marketing teams.
- Spin-level logs: 24 months from event date, then aggregated aggregation
- Session behavioural profiles: 24 months from last session, then removed
- RNG seed audit trails: 36 months to comply with technical standards
- Feature trigger heatmaps: 12 months, then combined into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Controlled Gambling and Self-Exclusion Registers
Stake limits, reality checks, and timeout settings are kept for your account’s lifetime and never removed while it is active. If you self-exclude, your hashed identity and device fingerprints are placed into a dedicated exclusion register maintained without time limit under UKGC licence requirements. The register is coded separately, queried only at login or registration, and never employed for analytics. Entry is confined to qualified compliance staff, and all queries are recorded for three years. The register holds only identity blocks—no banking or gameplay records. We examine it annually to correct errors and remove deceased individuals. If not, it remains permanent. This retention is obligatory and excluded from deletion requests.
Reality Check and Gaming Duration Enforcement
Reality check counters use temporary session counters that reset every 24 hours, restarting from your first spin after midnight. Your preferred interval—say, 30 minutes—is kept persistently and automatically reactivates when you come back, even after a long break. Altering the interval mid-session introduces the new value right away for the next reminder. These settings are removed only upon verified 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 checkable through the same three-year access log standard. We do not analyze or market based on these settings.
Technical Infrastructure and Data Storage
All data sits 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 synchronizes every six hours. Backups are encrypted client-side and follow identical retention rules. We apply least privilege with hardware MFA for administrators, recording their sessions in an immutable three-year audit trail. Multi-factor authentication combines a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor validates automated purge schedules. Any deviation raises a Severity 1 incident, reported to our DPO within four hours. We also operate an air-gapped backup rotated weekly, subject to the same deletion policies.
Encryption Key Lifecycle Management
Master keys rotate every 90 days automatically inside an HSM. New keys are not extracted in plaintext. Rotated keys are stored for the data’s retention period plus 12 months for lawful forensic access. When a data category is purged, its key is destroyed inside the HSM, making any backups unrecoverable. We bind each key to a single data partition, avoid 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 exits the HSM boundary.
Policy Evaluation and Data Breach Protocols
We evaluate this policy every six months or upon material change to the game or regulation. Reviews are recorded 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 notify 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 hold a breach notification log audited quarterly. Post-incident reviews update controls as needed. Biannual tabletop exercises model misconfigurations and ransomware to test our response.
Document Versioning and Change Log
We keep 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 transmitted 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 check 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 reflects our commitment to accountable data governance.