Playing Wanted Dead Or a Wild Slot game means providing personal data. This document lays out exactly how long we retain it, the reasons, 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 stay for seven, satisfying HMRC requirements. Gameplay data undergoes 24 months before anonymisation takes effect. Full card numbers never reach our systems—only tokenised aliases—and every byte is secured. Independent auditors verify our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log records every edit, and we give you 30 days’ notice before material changes take effect. Subject access and deletion requests are handled within statutory deadlines.

Monetary Transaction and Settlement Records

Funding, withdrawal, and wager histories are maintained for seven years from the transaction date, per HMRC and FCA rules https://wanteddeadorwild.uk/. We seldom store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised reference. Chargeback disputes freeze the contested record until final outcome, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs checked by auditors. Tokenised card references stay valid only while your account is open and are deleted 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 hold them for the account lifetime plus a thirty-day grace period, then send deletion commands to the processor and wipe our own mapping. The only evidence left behind is an anonymised transaction hash used in aggregate summaries, themselves purged after seven years. No usable credentials ever exist on our systems. We track token revocation daily and raise incidents if deletion does not work. Tokens are bound to our merchant code and cannot be used other places. Weekly reconciliation validates correctness, and tokens tied to lost or stolen cards are revoked immediately. All token operations are logged and checked. Aggregate reports never expose individual transaction hashes.

Marketing Approval and Correspondence Records

We maintain your consent document—with time stamp, with IP address, and with capture method—for the duration of our association plus six years after cancellation, to meet PECR rules. Send logs for emails, push messages, and SMS are kept for only thirteen months. Withdrawing consent instantly suppresses communications while preserving historical proof. A partitioned database ensures suppression without latency, and consent logs are stored in a dedicated compliance archive. Delivery logs hold metadata only—subject, timestamp, state—not full message content. The six-year post-withdrawal period mirrors the statute of limitations for regulatory probes. Quarterly audits confirm no expired consents trigger mailings. We never personalise offers with gameplay or financial data beyond explicit authorisations.

Session Gameplay and Behavioural Analytics Data

Every spin 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 used 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 persist for 12 months before merging into a global model. RNG seed audit trails have 36 months. Error diagnostics get 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 deleted
• 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

Controlled Gambling and Voluntary Exclusion Registers

Deposit limits, time checks, and timeout settings are saved for your account’s whole period and never deleted while it is active. If you self-exclude, your hashed identity and device fingerprints are placed into a dedicated exclusion register held indefinitely under UKGC licence requirements. The register is secured separately, queried only at login or registration, and never used for analytics. Access is restricted to trained compliance staff, and all searches are logged for three years. The register holds only identity blocks—no financial or gameplay records. We check it annually to rectify errors and remove deceased individuals. If not, it remains everlasting. This retention is required and excluded from deletion requests.

Session Awareness and Session Limit Enforcement

Reality check counters use short-lived session counters that reset every 24 hours, restarting from your first spin after midnight. Your preferred interval—say, 30 minutes—is saved persistently and instantly reactivates when you visit again, even after a long break. Changing the interval mid-session introduces the new value immediately for the next reminder. These settings are deleted only upon confirmed account deletion. Session timer data sits in a specific, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for accuracy. All timer configurations are auditable through the same three-year access log standard. We do not profile or advertise based on these settings.

Essential Definitions and Range of Personal Data

We take a broad view on what constitutes 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 link back to 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 cover live databases, archives, and backups without exception. Each window commences from the last activity or transaction date, spelled out below. We review definitions every six months to keep pace with regulatory guidance.

Data Subject Access Request and Deletion Workflows

Upon receiving an SAR, we produce a formatted JSON/CSV export of all non-purged data within one month, expandable by two months for complex cases. The export covers live databases, encrypted archives, and processor tokens, provided via a one-time secure link that expires in 72 hours. For deletion, we proceed sequentially: immediate account suppression and token revocation, then batched erasure of all personal data not subject to legal hold. We produce a confirmation report outlining 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 documented immutably for five years.

User Account and Identity Verification Data

Core identity profiles—government ID scans, residence proof, selfie biometric matches—are kept for a five-year period after your last session or account closure, whichever comes later. This encompasses contractual limitation periods and anti-money laundering duties. We extract only the essentials: ID number, validity, citizenship. The high-resolution image gets deleted right after extraction. Once the five-year period pass, all raw data is purged, but a cryptographic hash of the verification result remains for two more years inside an audit log. Personal identity information sits encrypted in storage with AES-256-GCM, isolated from analytics, and every retrieval is logged for three years. Unnecessary fields like birth location are removed at the time of verification to shrink the data footprint. Yearly reviews ensure accuracy and proactively delete outdated records.

Document Upload and Biometric Handling

Submit an ID through our protected portal and automated checking finishes within a minute and a half. We extract the ID number, expiration date, citizenship, and a trust score, then shred the full-resolution image right away—it never touches disk. The initial file stays in an in-memory buffer and vanishes after analysis. A compacted, watermarked small image is generated for audit purposes and stored only for the identity lifecycle. That small image lives in a write-once vault with tight controls and is never shown to support staff. Collected information are encrypted and kept for the 5-year-plus-2-year hash period. All operations runs on UK-based ISO 27001 servers, and every small image access is recorded immutably.

Biometric Data Specifics

Liveness verifications capture a short video stream completely in memory. Images are analyzed and discarded within milliseconds. Only a numerical vector of facial landmarks persists. This data set has no image data and cannot be turned back into a facial image. It stays for the entire identity verification process and is purged irrevocably upon closure of account or after a five-year period. The vector sits in a hardware security module with self-expiry and is never transferred. Login comparisons happen inside the HSM’s safe environment without disclosing the original vector. The numerical representation is bound to a pseudonym separated from marketing profiles, which makes re-identification extremely difficult. Even IT admins are unable to view or recreate face characteristics from the stored vector.

Infrastructure Setup and Data Location

All data is stored in UK-based ISO 27001 Tier III+ data centres, never replicated outside the UK. A hot disaster recovery site in a separate UK zone syncs every six hours. Backups are encrypted client-side and adhere to identical retention rules. We enforce least privilege with hardware MFA for administrators, recording their sessions in an immutable three-year audit trail. Multi-factor authentication integrates 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 keep an air-gapped backup rotated weekly, subject to the same deletion policies.

Key Lifecycle Administration

Master keys are renewed every 90 days automatically inside an HSM. New keys are not extracted in plaintext. Rotated keys are retained 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, 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 departs the HSM boundary.

Policy Evaluation and Breach Notification Protocols

We assess 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 emailed 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, submit with the ICO, and post a transparency notice. Third-party processor breaches must follow the same protocol. We keep a breach notification log audited quarterly. Post-incident reviews revise controls as needed. Biannual tabletop exercises simulate misconfigurations and ransomware to test our response.

Document Versioning and Change Log

We preserve 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 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 retrieve the full change log through a link in our privacy centre at any time. This transparent approach demonstrates our commitment to accountable data governance.