By 
Playing Wanted Dead Or a Wild Slot means submitting personal data. This document sets forth exactly how long we keep it, the reasons, and what technical protections sit behind each category—all built around UK GDPR, the Data Protection Act 2018, and PCI DSS. We handle 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 receives 24 months before anonymisation takes effect. Full card numbers never enter our systems—only tokenised aliases—and every byte is secured. Independent auditors check 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 handled within statutory deadlines.
Access Request and Erasure Workflows
When an SAR lands, we produce 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, provided via a one-time secure link that expires in 72 hours. For deletion, we proceed sequentially: immediate account suppression and token revocation, then scheduled erasure of all personal data not subject to legal hold. We generate a confirmation report specifying 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.
Account Registration and Identity Verification Data
Core identity profiles—official ID scans, address verification, biometric selfie matches—are kept for a five-year period after your final session or account closure, whichever occurs later. This covers statutory limitation periods and AML obligations. We retrieve only the essentials: ID number, validity, citizenship. The full-resolution image gets destroyed right after extraction. Once 5 years pass, all source data is erased, but a cryptographic hash of the verification result persists for two more years inside an logging system. Identity data sits stored encrypted with AES-256-GCM, stored away from analytics, and every access is logged for three years. Optional fields like place of birth are discarded at the time of verification to reduce the data volume. Annual reviews verify correctness and automatically remove outdated records.
Document Upload and Biometric Data Processing
Provide an ID through our protected portal and automated checking wraps up within ninety seconds. We retrieve the document ID, expiration date, citizenship, and a reliability score, then shred the high-resolution image immediately—it never touches disk. The initial file stays in an temporary memory and disappears after analysis. A compressed, watermarked small image is produced for auditing purposes and kept only for the identity lifecycle. That small image lives in a write-once vault with rigorous controls and is never exposed to client support. Collected information are encrypted and stored for the five-year-plus-two hash window. All operations runs on ISO 27001 certified UK servers, and every preview retrieval is recorded immutably.
Biometric Data Specifics
Liveness verifications capture a short video stream solely in memory. Video frames are analyzed and removed within milliseconds of time. Only a mathematical vector of face features survives. This vector contains no image data and cannot be turned back into a facial image. It is kept for the entire identity verification process and is irreversibly removed upon account closure or after five years. The vector sits in a hardware security module with automatic expiration and is never transferred. Login verifications happen inside the HSM’s safe environment without revealing the unprocessed data. The data set is associated with a pseudonym separated from marketing profiles, which makes re-identifying extremely difficult. Even system admins cannot view or recreate face characteristics from the stored vector.
Session Gameplay and Behavioral Analytics Data
All spins 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 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 persist 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 aggregated 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 keep your consent record—timestamped, with IP address, and method-captured—for the duration of our association plus six years after withdrawal, to comply with PECR obligations https://wanteddeadorwild.uk/. Send logs for e-mails, push notifications, and SMS are held for only thirteen months. Cancelling consent instantly halts communications while keeping historical proof. A divided database ensures suppression without delay, and consent logs are kept in a dedicated compliance archive. Delivery logs include metadata only—subject, time, status—not full message body. The six-year post-withdrawal period matches the statute of limitations for regulatory inquiries. Quarterly audits confirm no expired consents trigger mailings. We never tailor offers with gameplay or financial data beyond explicit permissions.
Payment Transaction and Payment Records
Funding, withdrawal, and wager records are maintained for seven years from the transaction date, per HMRC and FCA rules. We seldom store full PANs or CVVs. We capture only the BIN, last four digits, and a tokenised alias. Chargeback disputes suspend the contested record until final settlement, after which the seven-year clock continues. 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 live and are deleted within thirty days of termination. Aggregated, anonymised totals remain 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 produce vaulted tokens that map your card to a non-sensitive alias. We keep them for the account lifetime plus a thirty-day grace period, then issue deletion commands to the processor and wipe our own mapping. The only remnant left behind is an anonymised transaction hash used in aggregate summaries, themselves removed after seven years. No usable credentials ever sit on our systems. We track token revocation daily and trigger incidents if deletion is unsuccessful. Tokens are bound to our merchant code and cannot be used elsewhere. Weekly reconciliation confirms correctness, and tokens tied to lost or stolen cards are revoked immediately. All token operations are logged and checked. Aggregate reports never disclose individual transaction hashes.
Fundamental Definitions and Extent 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 span live databases, archives, and backups without exception. Each window begins counting from the last activity or transaction date, spelled out below. We reassess definitions every six months to stay aligned with regulatory guidance.
Safe Gambling and Player Ban Registers
Betting limits, session reminders, and timeout settings are stored for your account’s entire duration and never purged while it is active. If you self-exclude, your hashed identity and device fingerprints are added to a specialized exclusion register held indefinitely under UKGC licence requirements. The register is secured separately, queried only at login or registration, and never employed for analytics. Access is confined to educated compliance staff, and all searches are tracked for three years. The register contains only identity blocks—no monetary or gameplay records. We review it annually to fix errors and remove deceased individuals. Otherwise, it remains everlasting. This retention is required and exempt from deletion requests.
Session Awareness and Play Time Restriction Enforcement
Reality check clocks use temporary session counters that clear every 24 hours, beginning again from your first spin after midnight. Your chosen interval—say, 30 minutes—is kept persistently and routinely reactivates when you come back, even after a long break. Modifying the interval mid-session introduces the new value instantly for the next reminder. These settings are deleted only upon confirmed account deletion. Session timer data resides in a specific, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for precision. All timer configurations are checkable through the same three-year access log standard. We at no time categorize or promote based on these settings.
Infrastructure Setup and Data Storage
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 syncs every six hours. Backups are encrypted client-side and adhere to identical retention rules. We implement 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 run 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 maintain an air-gapped backup rotated weekly, subject to 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 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.
Policy Evaluation and Breach Notification Protocols
We assess 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 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 update controls as needed. Biannual tabletop exercises test misconfigurations and ransomware to test our response.
Policy Version Control 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 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 demonstrates our commitment to accountable data governance.
