Playing Wanted Dead Or a Wild Slot game means handing over personal data https://wanteddeadorwild.uk/. This document lays out exactly how long we retain it, the reasons, 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 unique retention clock. Identity records are kept for five years after account closure. Financial logs are stored for seven, satisfying HMRC requirements. Gameplay data undergoes 24 months before anonymisation is applied. Full card numbers never enter our systems—only tokenised aliases—and every byte is protected. Independent auditors review our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log records every edit, and we provide you 30 days’ notice before material changes are implemented. Subject access and deletion requests are managed within statutory deadlines.
Essential Definitions and Extent of Personal Data
We cast a wide net 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 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 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 starts ticking from the last activity or transaction date, spelled out below. We revisit definitions every six months to stay aligned with regulatory guidance.
Controlled Gambling and Player Ban Registers
Stake limits, reality checks, and timeout settings are saved for your account’s lifetime and never deleted while it is active. If you self-exclude, your hashed identity and device fingerprints are placed into a dedicated exclusion register maintained permanently under UKGC licence requirements. The register is coded separately, accessed only at login or registration, and never employed for analytics. Entry is confined to trained compliance staff, and all searches are tracked for three years. The register stores only identity blocks—no financial or gameplay records. We check it annually to fix errors and remove deceased individuals. Apart from that, it is kept everlasting. This retention is required and excluded from deletion requests.
Reality Check and Session Limit Enforcement
Reality check timers use transient session counters that restart every 24 hours, restarting from your first spin after midnight. Your preferred interval—say, 30 minutes—is saved persistently and automatically reactivates when you come back, even after a long break. Altering the interval mid-session introduces the new value instantly for the next reminder. These settings are purged only upon verified account deletion. Session timer data resides 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 profile or market based on these settings.
User Account and ID Verification Data
Main identity data—scans of government IDs, residence proof, biometric selfie matches—are kept for five years after your last session or closure of account, whichever comes later. This encompasses statutory limitation periods and anti-money laundering duties. We obtain only the key information: ID number, expiration date, citizenship. The original image gets shredded immediately after extraction. Once 5 years pass, all source data is erased, but a encrypted hash of the verification data lives on for another two years inside an logging system. Identity data sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every access is recorded for 3 years. Optional fields like birthplace are discarded at the time of verification to minimize the data size. Annual reviews ensure precision and automatically remove outdated records.
Uploading Documents and Biometric Handling
Submit an ID through our safe portal and automated checking completes within ninety seconds. We pull the document ID, expiration date, citizenship, and a confidence score, then destroy the high-resolution image right away—it never reaches storage. The original file stays in an in-memory buffer and is removed after handling. A compressed, marked small image is created for auditing purposes and retained only for the identity verification period. That preview lives in a write-once storage with strict controls and is never shown to client support. Retrieved data are secured and kept for the five-year plus two-year hash timeframe. All operations runs on ISO 27001 certified UK servers, and every preview retrieval is recorded immutably.
Biometric Information Details
Live detection checks capture a brief video feed solely in memory. Video frames are analyzed and deleted within a few milliseconds. Only a numerical vector of facial landmarks persists. This vector has no image data and cannot be turned back into a picture. It remains for the duration of identity verification and is purged irrevocably upon account closure or after 5 years. The numerical representation sits in a hardware security module with self-expiry and is never exported. Login verifications happen inside the HSM’s safe environment without revealing the unprocessed data. The numerical representation is linked to a pseudonym unlinked from advertising profiles, which makes re-identifying highly challenging. Even system administrators cannot see or reconstruct face characteristics from the kept numerical representation.
Access Request and Erasure Workflows
When an SAR lands, we compile a organized 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 proceed sequentially: 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 maintained as auditable proof for as long as the longest surviving data category. All requests are recorded immutably for five years.
Payment Transaction and Payment Records
Deposit, withdrawal, and wager records are kept for seven years from the transaction date, per HMRC and FCA rules. We seldom store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised reference. Chargeback disputes halt the contested record until final outcome, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs verified by auditors. Tokenised card references stay valid only while your account is live and are deleted within thirty days of closure. Summarised, anonymised totals endure for financial reporting without any personal details. All financial data is secured and quarantined from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways generate vaulted tokens that associate your card to a non-sensitive reference. We store them for the account lifetime plus a thirty-day grace window, then send deletion commands to the processor and erase our own mapping. The only trace left behind is an anonymised transaction hash used in aggregate reports, themselves purged after seven years. No usable credentials ever sit on our systems. We monitor token revocation daily and raise incidents if deletion is unsuccessful. Tokens are linked to our merchant code and cannot be used other places. Weekly reconciliation confirms correctness, and tokens tied to lost or stolen cards are revoked immediately. All token operations are recorded and auditable. Aggregate reports never reveal individual transaction hashes.
Technical Infrastructure and Data Location
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 syncs every six hours. Backups are encrypted client-side and maintain identical retention rules. We implement least privilege with hardware MFA for administrators, logging 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 confirms 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.
Management of Encryption Keys
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 deleted inside the HSM, making any backups unrecoverable. We link 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.
Gaming Session and Behavioural Analytics Data
Every spin on Wanted Dead Or a Wild records reel positions, RNG seed, and net outcome with microsecond precision. We retain 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—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 receive 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 anonymized 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 combined into global model
- Error and crash diagnostic logs: 90 days, then removed
Consent for Marketing and Communication Logs
We maintain your consent log—with time stamp, IP-stamped, and method-recorded—for the life of our partnership plus six years after withdrawal, to comply with PECR rules. Delivery logs for e-mails, push alerts, and SMS are retained for only thirteen months. Cancelling consent right away blocks communications while preserving historical proof. A segmented database ensures suppression without delay, and consent logs are kept in a distinct compliance archive. Dispatch records hold metadata only—subject, time stamp, condition—not full message text. The six-year post-withdrawal window mirrors the statute of limitations for regulatory probes. Quarterly audits check no expired consents activate mailings. We never personalise offers with gameplay or financial data beyond explicit permissions.
Policy Evaluation and Incident Reporting Protocols
We review this policy every six months or upon material change to the game or regulation. Reviews are documented with DPO, CISO, and legal counsel. A public summary is published 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 issue 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 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 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 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 reflects our commitment to accountable data governance.