Playing Wanted Dead Or a Wild Slot game means providing personal data wanteddeadorwild.uk. This document details exactly how long we keep it, the rationale, and what technical protections support each category—all built around 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 unique retention clock. Identity records are retained for five years after account closure. Financial logs remain for seven, meeting HMRC requirements. Gameplay data gets 24 months before anonymisation kicks in. Full card numbers never touch our systems—only tokenised aliases—and every byte is protected. Independent auditors verify our automated deletion routines, and any schedule slip activates a full incident response. A version-controlled policy log records every edit, and we provide you 30 days’ notice before material changes take effect. Subject access and deletion requests are handled within statutory deadlines.
Essential Definitions and Extent of Personal Data
We adopt a comprehensive approach on what qualifies as personal data. Direct identifiers—name, email, billing address, masked payment details—are accompanied by 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 link back to 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 revisit definitions every six months to remain compliant with regulatory guidance.
SAR and Deletion Processes
When an SAR lands, we generate a structured JSON/CSV export of all non-purged data within one month, expandable 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 batched erasure of all personal data not subject to legal hold. We generate a confirmation report outlining 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 recorded immutably for five years.
Registration Account and ID Verification Data
Main identity data—official ID scans, address verification, biometric selfie verifications—are kept for a five-year period after your final session or account termination, whichever is later. This encompasses contractual time limits and anti-money laundering responsibilities. We extract only the key information: document ID, expiration date, country of citizenship. The high-resolution image gets shredded upon extraction. Once five years pass, all source data is erased, but a encrypted hash of the verification data lives on for another two years inside an audit trail. Identity data sits stored encrypted with AES-256-GCM, isolated from analytics, and every data access is logged for 3 years. Optional fields like place of birth are discarded at the time of verification to shrink the data volume. Yearly reviews confirm precision and actively purge expired entries.
File Upload and Biometric Processing
Submit an ID through our secure portal and automatic verification wraps up within 90 seconds. We extract the ID number, expiration date, nationality, and a trust score, then shred the full-resolution image instantly—it never reaches storage. The initial file stays in an memory buffer and is removed after handling. A compressed, marked small image is generated for auditing purposes and retained only for the identity verification period. That preview lives in a write-once vault with rigorous controls and is never shared to client support. Retrieved data are encrypted and saved for the five-year plus two-year hash timeframe. All operations runs on ISO 27001 certified UK servers, and every thumbnail access is logged permanently.
Biometric Data Specifics
Liveness checks capture a quick video solely in memory. Frames are processed and removed within milliseconds. Only a numerical vector of facial landmarks remains. This data set lacks any image data and cannot be turned back into a facial image. It remains for the duration of identity verification and is irreversibly removed upon account termination or after five years. The numerical representation sits in a hardware security module with automatic expiration and is never exported. Login verifications happen inside the HSM’s protected enclave without exposing the original vector. The data set is bound to a pseudonym separated from advertising profiles, which makes re-identifying very hard. Even system administrators cannot view or reconstruct face characteristics from the saved data.
Payment Transaction and Settlement Records
Deposit, withdrawal, and wager records are maintained 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 operates cleanly, with monthly deletion runs audited by auditors. Tokenised card references are valid only while your account is live and are wiped within thirty days of closing. Summarised, anonymised totals persist for financial reporting without any personal details. All financial data is coded and quarantined from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways create vaulted tokens that link your card to a non-sensitive reference. We hold them for the account lifetime plus a thirty-day grace interval, then transmit deletion commands to the processor and erase our own mapping. The only evidence 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 trigger incidents if deletion fails. Tokens are linked to our merchant code and cannot be used elsewhere. Weekly reconciliation validates authenticity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are logged and auditable. Aggregate reports never expose individual transaction hashes.
Controlled Gambling and Voluntary Exclusion Registers
Deposit limits, session reminders, and timeout settings are saved for your account’s entire duration and never deleted while it remains active. If you choose to ban yourself, your hashed identity and device fingerprints are added to a specific exclusion register maintained without time limit under UKGC licence requirements. The register is secured separately, accessed only at login or registration, and never used for analytics. Access is restricted to educated compliance staff, and all lookups are logged for three years. The register stores only identity blocks—no monetary or gameplay records. We review it annually to rectify errors and remove deceased individuals. Apart from that, it is kept indefinite. This retention is obligatory and free from deletion requests.
Time Check and Gaming Duration Enforcement
Reality check timers use short-lived session counters that clear every 24 hours, restarting from your first spin after midnight. Your chosen interval—say, 30 minutes—is saved persistently and routinely reactivates when you visit again, even after a long break. Changing the interval mid-session applies the new value instantly for the next reminder. These settings are purged only upon validated 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 accuracy. All timer configurations are checkable through the same three-year access log standard. We at no time categorize or promote based on these settings.
Gaming Session and Analytics of Behavior Data
Each spin on Wanted Dead Or a Wild records reel positions, RNG seed, and net outcome with microsecond precision. We keep these raw logs for twenty-four months, then condense them into an anonymous statistical digest utilized for game design. Session behavioural profiles—average bet, spin cadence, feature buy-ins—stay for the same 24-month window and are then deleted. Feature trigger heatmaps remain 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 flows 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 cycled out
Marketing Consent and Message Logs
We store your consent document—timestamped, IP-stamped, and with capture method—for the duration of our partnership plus six years after revocation, to comply with PECR obligations. Delivery logs for e-mails, push messages, and SMS are kept for only thirteen months. Cancelling consent immediately suppresses communications while preserving historical proof. A partitioned database ensures suppression without latency, and consent logs are kept in a distinct compliance archive. Dispatch records include metadata only—heading, time, state—not full message text. The six-year post-withdrawal period matches the statute of limitations for regulatory probes. Quarterly audits verify no expired consents trigger mailings. We never tailor offers with gameplay or financial data beyond explicit authorisations.
Technical Infrastructure and Data Residency
All data resides in UK-based ISO 27001 Tier III+ data centres, not copied outside the UK. A hot disaster recovery site in a separate UK zone synchronizes every six hours. Backups are encrypted client-side and adhere to 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 uses a hardware token and biometric check. Penetration tests are conducted quarterly, and an independent auditor verifies automated purge schedules. Any deviation generates a Severity 1 incident, alerted to our DPO within four hours. We also operate an air-gapped backup rotated weekly, following the same deletion policies.
Management of Encryption Keys
Master keys change every 90 days automatically inside an HSM. New keys are kept internal 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 deleted inside the HSM, making any backups unrecoverable. We bind each key to a single data partition, do not reuse, and conduct quarterly witnessed key ceremonies logged immutably for five years. The offline archive of old keys demands dual control and is stored on write-once media in a fireproof safe. Annual recovery drills confirm forensic decryption works when needed. No plaintext key material ever leaves the HSM boundary.
Policy Evaluation and Data Breach Protocols
We review 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 displayed 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 model misconfigurations and ransomware to test our response.
Document Versioning and Revision History
We preserve a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log specifies 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 communicated 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 view the full change log through a link in our privacy centre at any time. This transparent approach shows our commitment to accountable data governance.