Playing Wanted Dead Or a Wild Slot game means handing over personal data. This document sets forth exactly how long we keep it, why, and what technical protections sit behind each category—all based on UK GDPR, the Data Protection Act 2018, and PCI DSS. We process identity documents, financial transactions, gameplay telemetry, responsible gambling markers, and marketing consents, each with its own retention clock. Identity records stick around for five years after account closure. Financial logs are stored for seven, meeting 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 review our automated deletion routines, and any schedule slip triggers a full incident response. A version-controlled policy log documents every edit, and we offer you 30 days’ notice before material changes are implemented. Subject access and deletion requests are handled within statutory deadlines.
Core 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 includes session length, bet sizing, spin velocity, and how often feature triggers fire. Even pseudonymised logs can identify again 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 extend across live databases, archives, and backups without exception. Each window begins counting from the last activity or transaction date, spelled out below. We review definitions every six months to keep pace with regulatory guidance.
Financial Transaction and Payment Records
Deposit, withdrawal, and wager logs are retained 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 alias. Chargeback disputes freeze the contested record until final settlement, after which the seven-year clock resumes. 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 open and are erased within thirty days of closure. Summarised, anonymised totals endure for financial reporting without any personal information. All financial data is coded and quarantined from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways create vaulted tokens that link your card to a non-sensitive alias. We store them for the account lifetime plus a thirty-day grace period, then transmit deletion commands to the processor and erase our own reference. The only trace 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 monitor token revocation daily and raise incidents if deletion is unsuccessful. Tokens are bound to our merchant code and cannot be used elsewhere. Weekly reconciliation verifies authenticity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are recorded and checked. Aggregate reports never reveal individual transaction hashes.
Registration Account and ID Verification Data
Primary identity records—government ID scans, address verification, selfie biometric matches—are retained for 5 years after your final session or account termination, whichever occurs later. This covers statutory limitation periods and anti-money laundering duties. We retrieve only the essentials: document ID, expiration date, citizenship. The high-resolution image gets destroyed upon extraction. Once 5 years pass, all original data is removed, but a hash of the verification data remains for an additional two years inside an audit log. Personal identity information sits encrypted in storage with AES-256-GCM, stored away from analytics, and every retrieval is tracked for three years. Optional fields like birthplace are removed at verification time to shrink the data footprint. Yearly reviews verify correctness and proactively delete expired data.
Document Upload and Biometric Processing
Upload an ID through our secure portal and automated validation completes within 90 seconds. We retrieve the document number, expiry, nationality, and a confidence score, then delete the full-resolution image immediately—it never reaches storage. The source file stays in an memory buffer and vanishes after analysis. A reduced, watermarked preview is generated for compliance purposes and retained only for the ID lifecycle. That small image lives in a immutable vault with rigorous controls and is never shown to customer support. Retrieved data are encrypted and stored for the 5-year-plus-2-year hash period. All processing runs on ISO 27001 certified UK servers, and every thumbnail access is recorded immutably.
Biometric Information Details
Live detection checks capture a brief video feed completely in memory. Images are analyzed and removed within milliseconds. Only a data vector of facial points persists. This numerical representation contains no image data and cannot be reverse-engineered into a face. It stays for the time of identity verification and is permanently deleted upon account closure or after a five-year period. The data set sits in a hardware security module with self-expiry and is never transferred. Authentication checks happen inside the HSM’s safe environment without disclosing the unprocessed data. The vector is linked to a anonymous identifier unlinked from marketing data, which makes re-identifying highly challenging. Even system admins are unable to view or reconstruct face characteristics from the kept numerical representation.
SAR and Deletion Processes
When a subject access request arrives, we produce a formatted JSON/CSV export of all non-purged data within one month, prolongable by two months for complex cases. The export spans live databases, encrypted archives, and processor tokens, delivered 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 detailing 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.
Policy Assessment and Data Breach Protocols
We assess 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 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 publish a transparency notice. Third-party processor breaches must follow the same protocol. We keep a breach notification log audited quarterly. Post-incident reviews update controls as needed. Biannual tabletop exercises model 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 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 retrieve the full change log through a link in our privacy centre at any time. This transparent approach reflects our commitment to accountable data governance.
Technical Infrastructure and Data Storage
All data resides 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 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 integrates a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor confirms automated purge schedules. Any deviation generates 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.
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 removed inside the HSM, making any backups unrecoverable. We link 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 demands 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 leaves the HSM boundary.
Marketing Approval and Communication Logs
We store your consent record—timestamped, IP-stamped, and with capture method—for the entirety of our association plus six years after withdrawal, to meet PECR requirements. Delivery logs for e-mails, push alerts, and SMS are retained for only thirteen months. Cancelling consent immediately blocks communications while keeping historical proof. A divided database ensures suppression without latency, and consent logs are stored in a distinct compliance archive. Send logs hold metadata only—topic, time, state—not full message content. The six-year post-withdrawal timeframe reflects the statute of limitations for regulatory probes. Quarterly audits confirm no expired consents activate mailings. We never tailor offers with gameplay or financial data beyond explicit permissions.
Gameplay Session and Behavioral Analytics Data
All spins on Wanted Dead Or a Wild tracks reel positions, RNG seed, and net outcome with microsecond precision https://wanteddeadorwild.uk/. We retain these raw logs for twenty-four months, then compress them into an anonymous statistical digest used 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 have 36 months. Error diagnostics get 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 integrated into global model
- Error and crash diagnostic logs: 90 days, then cycled out
Controlled Gambling and Voluntary Exclusion Registers
Deposit limits, reality checks, and timeout settings are kept for your account’s whole period and never purged while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a specialized exclusion register held permanently under UKGC licence requirements. The register is coded separately, accessed only at login or registration, and never used for analytics. Permission is limited to educated compliance staff, and all searches are tracked for three years. The register holds only identity blocks—no financial or gameplay records. We review it annually to fix errors and remove deceased individuals. Apart from that, it remains everlasting. This retention is obligatory and excluded from deletion requests.
Reality Check and Session Limit Enforcement
Reality check counters use temporary session counters that reset every 24 hours, beginning again from your first spin after midnight. Your selected interval—say, 30 minutes—is kept persistently and automatically reactivates when you come back, even after a long break. Altering the interval mid-session sets 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 at no time categorize or advertise based on these settings.