Playing Wanted Dead Or a Wild Slot game means submitting personal data https://wanteddeadorwild.uk/. This document sets forth exactly how long we keep it, why, and what technical protections support 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 kicks in. Full card numbers never enter our systems—only tokenised aliases—and every byte is protected. Independent auditors check 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 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 maintain 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 integrates a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor validates automated purge schedules. Any deviation triggers a Severity 1 incident, notified to our DPO within four hours. We also operate an air-gapped backup rotated weekly, under the same deletion policies.

Encryption Key Lifecycle Management

Master keys rotate every 90 days automatically inside an HSM. New keys are never exported 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 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 needs 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.

Responsible Gambling and Voluntary Exclusion Registers

Betting limits, time checks, and timeout settings are kept for your account’s entire duration and never removed while it is active. If you choose to ban yourself, your hashed identity and device fingerprints enter a specific exclusion register held indefinitely under UKGC licence requirements. The register is encrypted separately, queried only at login or registration, and never utilized for analytics. Entry is limited to trained 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 rectify errors and remove deceased individuals. Otherwise, it remains indefinite. This retention is required and exempt from deletion requests.

Time Check and Gaming Duration Enforcement

Reality check timers use short-lived session counters that reset every 24 hours, beginning again from your first spin after midnight. Your chosen interval—say, 30 minutes—is saved persistently and instantly reactivates when you come back, even after a long break. Modifying the interval mid-session applies the new value immediately for the next reminder. These settings are deleted only upon validated account deletion. Session timer data sits in a specialized, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for correctness. All timer configurations are auditable through the same three-year access log standard. We at no time categorize or market based on these settings.

Payment Transaction and Billing Records

Funding, withdrawal, and wager histories are kept for seven years from the transaction date, per HMRC and FCA rules. We seldom 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 resolution, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs verified by auditors. Tokenised card references are valid only while your account is open and are deleted within thirty days of closure. Aggregated, anonymised totals remain for financial reporting without any personal information. All financial data is secured and isolated from marketing systems.

Tokenised Payment Instruments and Processor References

Payment gateways produce vaulted tokens that map your card to a non-sensitive alias. We keep them for the account lifetime plus a thirty-day grace window, then issue deletion commands to the processor and erase our own reference. The only evidence left behind is an anonymised transaction hash used in aggregate statements, themselves deleted after seven years. No usable credentials ever sit on our systems. We track token revocation daily and trigger incidents if deletion fails. Tokens are linked to our merchant code and cannot be used in other contexts. Weekly reconciliation validates validity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are documented and auditable. Aggregate reports never disclose individual transaction hashes.

Marketing Approval and Correspondence Records

We store your consent log—with time stamp, IP-marked, and with capture method—for the entirety of our partnership plus six years after withdrawal, to satisfy PECR requirements. Dispatch records for e-mails, push messages, and SMS are held for only thirteen months. Revoking consent instantly halts communications while keeping historical proof. A segmented database ensures suppression without delay, and consent logs are stored in a distinct compliance archive. Send logs include metadata only—heading, timestamp, status—not full message content. The six-year post-withdrawal window matches the statute of limitations for regulatory probes. Quarterly audits verify no expired consents initiate mailings. We never tailor offers with gameplay or financial data beyond explicit authorisations.

User Account and ID Verification Data

Core identity profiles—scans of government IDs, residence proof, biometric selfie matches—are retained for five years after your final session or closure of account, whichever is later. This includes statutory limitation periods and anti-money laundering duties. We obtain only the necessary details: ID number, validity, country of citizenship. The original image gets destroyed immediately after extraction. Once the five-year period pass, all raw data is erased, but a hash of the verification result persists for another two years inside an audit trail. Identity data sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every retrieval is tracked for three years. Unnecessary fields like birthplace are discarded at verification time to minimize the data footprint. Yearly audits verify correctness and proactively delete outdated records.

Uploading Documents and Biometric Data Processing

Provide an ID through our protected portal and automated validation finishes within a minute and a half. We extract the document ID, expiry, nationality, and a trust score, then shred the full-resolution image instantly—it never reaches storage. The source file stays in an in-memory buffer and disappears after processing. A reduced, watermarked thumbnail is produced for compliance purposes and stored only for the identity verification period. That small image lives in a write-once vault with strict controls and is never exposed to client support. Extracted fields are encrypted and kept for the five-year-plus-two hash window. All operations runs on UK-based ISO 27001 servers, and every thumbnail access is stored unchangeably.

Biometric Data Specifics

Live detection checks capture a short video stream solely in memory. Frames are analyzed and removed within a few milliseconds. Only a mathematical vector of face features persists. This vector lacks any image data and cannot be turned back into a face. It stays for the duration of identity verification and is permanently deleted upon account closure or after a five-year period. The vector sits in a specialized HSM with auto-expiry and is never sent out. Login comparisons happen inside the HSM’s secure enclave without disclosing the raw vector. The vector is bound to a pseudonym separated from marketing profiles, which makes reidentification extremely difficult. Even system admins cannot see or rebuild face characteristics from the saved data.

Gameplay Session and Behavioral Analytics 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 persist for 12 months before merging into a global model. RNG seed audit trails receive 36 months. Error diagnostics have 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 aggregated aggregation
• Session behavioural profiles: 24 months from last session, then erased
• 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

Essential Definitions and Scope of Personal Data

We take a broad view on what qualifies 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 link back to a person when stitched together, so we treat 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 starts ticking from the last activity or transaction date, spelled out below. We reassess definitions every six months to keep pace with regulatory guidance.

Policy Assessment and Data Breach Protocols

We review 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 inform affected individuals within 72 hours if high risk, file with the ICO, and issue 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 simulate misconfigurations and ransomware to test our response.

Document Versioning and Update Log

We preserve 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 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 verify 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 demonstrates our commitment to accountable data governance.

Data Subject Access Request and Deletion Workflows

When an SAR lands, we produce 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, provided via a one-time secure link that expires in 72 hours. For deletion, we implement a cascade: immediate account suppression and token revocation, then queued erasure of all personal data not subject to legal hold. We create a confirmation report outlining 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.