Playing Wanted Dead Or a Wild Slot means submitting personal data wanteddeadorwild.uk. This document details exactly how long we store it, the rationale, and what technical protections sit behind each category—all aligned with UK GDPR, the Data Protection Act 2018, and PCI DSS. We manage 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 stay for seven, meeting HMRC requirements. Gameplay data gets 24 months before anonymisation takes effect. Full card numbers never reach our systems—only tokenised aliases—and every byte is encrypted. Independent auditors verify our automated deletion routines, and any schedule slip triggers a full incident response. A version-controlled policy log records every edit, and we offer you 30 days’ notice before material changes take effect. Subject access and deletion requests are managed within statutory deadlines.
Technical Infrastructure and Data Residency
All data is stored in UK-based ISO 27001 Tier III+ data centres, not copied outside the UK. A hot disaster recovery site in a separate UK zone syncs every six hours. Backups are encrypted client-side and follow identical retention rules. We enforce least privilege with hardware MFA for administrators, capturing 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, alerted to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, following 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 stored 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 assign 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 departs the HSM boundary.
Marketing Approval and Correspondence Records
We store your consent log—with time stamp, IP-marked, and method-recorded—for the entirety of our association plus six years after cancellation, to meet PECR requirements. Send logs for emails, push alerts, and SMS are kept for only thirteen months. Revoking consent instantly suppresses communications while keeping historical proof. A partitioned database ensures suppression without lag, and consent logs are kept in a dedicated compliance archive. Send logs include metadata only—subject, time, state—not full message content. The six-year post-withdrawal window mirrors the statute of limitations for regulatory inquiries. Quarterly audits verify no expired consents initiate mailings. We never personalise offers with gameplay or financial data beyond explicit authorisations.
Session Gameplay and Behavioural Analytics Data
Each spin on Wanted Dead Or a Wild logs reel positions, RNG seed, and net outcome with microsecond precision. We retain these raw logs for twenty-four months, then compress 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 stay for 12 months before merging into a global model. RNG seed audit trails get 36 months. Error diagnostics receive 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 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 cycled out
User Account and ID Verification Data
Primary identity records—government ID scans, address verification, biometric selfie verifications—are held for 5 years after your last session or closure of account, whichever is later. This covers contractual time limits and anti-money laundering responsibilities. We extract only the key information: document number, expiration date, citizenship. The original image gets deleted immediately after extraction. Once five years pass, all raw data is purged, but a cryptographic hash of the verification result remains for two more years inside an logging system. Personal identity information sits encrypted in storage with AES-256-GCM, isolated from analytics, and every access is tracked for 3 years. Optional fields like birthplace are discarded at the time of verification to shrink the data footprint. Annual reviews verify correctness and proactively delete expired entries.
Document Upload and Biometric Data Processing
Provide an ID through our protected portal and automatic verification wraps up within 90 seconds. We retrieve the document ID, expiration date, citizenship, and a confidence score, then destroy the original image right away—it is never stored on disk. The source file stays in an in-memory buffer and vanishes after handling. A compressed, marked preview is generated for auditing purposes and kept only for the ID lifecycle. That small image lives in a immutable vault with strict controls and is never exposed to client support. Retrieved data are encrypted and kept for the five-year-plus-two hash window. All handling runs on UK-based ISO 27001 servers, and every thumbnail access is stored unchangeably.
Specifics of Biometric Data
Liveness verifications capture a quick video completely in memory. Images are processed and removed within a few milliseconds. Only a mathematical vector of face features remains. This data set contains no image data and cannot be reverse-engineered into a facial image. It is kept for the duration of identity verification and is permanently deleted upon closure of account or after a five-year period. The vector sits in a hardware security module with automatic expiration and is never exported. Login verifications happen inside the HSM’s safe environment without disclosing the raw vector. The vector is linked to a anonymous identifier separated from marketing profiles, which makes re-identifying highly challenging. Even IT admins are unable to view or reconstruct facial features from the kept numerical representation.
SAR and Deletion Processes
When a subject access request arrives, we generate a structured JSON/CSV export of all non-purged data within one month, extendable by two months for complex cases. The export spans 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 scheduled erasure of all personal data not subject to legal hold. We generate a confirmation report detailing erased versus retained categories and their justifications. This report is retained as auditable proof for as long as the longest surviving data category. All requests are documented immutably for five years.
Fundamental Definitions and Range of Personal Data
We cast a wide net 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 covers 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 regard 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 commences from the last activity or transaction date, spelled out below. We reassess definitions every six months to stay aligned with regulatory guidance.
Controlled Gambling and Self-Exclusion Registers
Betting limits, time checks, and timeout settings are saved for your account’s lifetime and never deleted while it remains active. If you choose to ban yourself, your hashed identity and device fingerprints are placed into a dedicated exclusion register kept without time limit under UKGC licence requirements. The register is coded separately, accessed only at login or registration, and never utilized for analytics. Entry is confined to qualified compliance staff, and all queries are tracked for three years. The register holds only identity blocks—no banking or gameplay records. We review it annually to correct errors and remove deceased individuals. Apart from that, it is kept permanent. This retention is mandatory and exempt from deletion requests.
Reality Check and Gaming Duration Enforcement
Reality check timers use transient session counters that clear every 24 hours, restarting from your first spin after midnight. Your selected interval—say, 30 minutes—is saved persistently and automatically reactivates when you return, even after a long break. Changing the interval mid-session applies the new value instantly for the next reminder. These settings are deleted only upon verified account deletion. Session timer data sits in a dedicated, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for precision. All timer configurations are auditable through the same three-year access log standard. We do not analyze or market based on these settings.
Financial 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 collect only the BIN, last four digits, and a tokenised reference. Chargeback disputes halt the contested record until final resolution, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs checked by auditors. Tokenised card references remain valid only while your account is active and are wiped within thirty days of closing. Aggregated, anonymised totals persist for financial reporting without any personal details. All financial data is coded and separated from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways generate vaulted tokens that associate your card to a non-sensitive reference. We hold them for the account lifetime plus a thirty-day grace period, then transmit deletion commands to the processor and wipe our own link. The only evidence left behind is an anonymised transaction hash used in aggregate summaries, themselves removed after seven years. No usable credentials ever exist on our systems. We track token revocation daily and initiate incidents if deletion fails. Tokens are linked 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 reveal individual transaction hashes.
Policy Evaluation and Breach Notification 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 alert affected individuals within 72 hours if high risk, report with the ICO, and publish a transparency notice. Third-party processor breaches must follow the same protocol. We keep a breach notification log audited quarterly. Post-incident reviews adjust controls as needed. Biannual tabletop exercises simulate misconfigurations and ransomware to test our response.
Document Versioning and Revision History
We keep a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log details 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 confirm 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.