Playing Wanted Dead Or a Wild Slot game means handing over personal data https://wanteddeadorwild.uk/. This document details exactly how long we retain it, the reasons, and what technical protections underpin each category—all based on 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 specific retention clock. Identity records are retained for five years after account closure. Financial logs are stored for seven, satisfying HMRC requirements. Gameplay data gets 24 months before anonymisation is applied. 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 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 handled within statutory deadlines.
Core Definitions and Scope of Personal Data
We take a broad view on what counts 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 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 begins counting from the last activity or transaction date, spelled out below. We review definitions every six months to stay aligned with regulatory guidance.
Registration Account and ID Verification Data
Core identity profiles—scans of government IDs, residence proof, selfie biometric matches—are retained for a five-year period after your final session or account closure, whichever comes later. This encompasses contractual time limits and AML obligations. We retrieve only the essentials: document number, expiration date, country of citizenship. The full-resolution image gets destroyed right after extraction. Once five years pass, all raw data is purged, but a encrypted hash of the verification data persists for two more years inside an audit log. Identification data sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every data access is recorded for three years. Optional fields like birth location are removed at the time of verification to minimize the data footprint. Yearly audits ensure correctness and proactively delete expired entries.
Document Upload and Biometric Data Processing
Upload an ID through our secure portal and automatic verification wraps up within 90 seconds. We extract the document number, validity, nationality, and a reliability score, then delete the full-resolution image instantly—it is never stored on disk. The initial file stays in an memory buffer and is removed after processing. A compacted, marked preview is produced for audit purposes and kept only for the identity lifecycle. That thumbnail lives in a immutable vault with strict controls and is never shown to client support. Extracted fields are encrypted and kept for the five-year-plus-two hash window. All operations runs on ISO 27001 certified UK servers, and every small image access is recorded immutably.
Biometric Information Details
Liveness checks record a short video stream solely in memory. Frames are analysed and removed within milliseconds of time. Only a mathematical vector of face features survives. This numerical representation contains no image data and cannot be reverse-engineered into a face. It is kept for the time of identity verification and is purged irrevocably upon closure of account or after a five-year period. The data set sits in a dedicated HSM with auto-expiry and is never sent out. Login verifications happen inside the HSM’s protected enclave without exposing the original vector. The vector is linked to a anonymous identifier separated from advertising profiles, which makes reidentification extremely difficult. Even IT admins are unable to view or reconstruct facial features from the kept numerical representation.
Monetary Transaction and Payment Records
Funding, withdrawal, and wager logs are maintained for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised alias. Chargeback disputes halt the contested record until final settlement, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs checked by auditors. Tokenised card references are valid only while your account is open and are deleted within thirty days of closure. Aggregated, anonymised totals endure for financial reporting without any personal identifiers. All financial data is secured and quarantined from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways create vaulted tokens that associate your card to a non-sensitive alias. We store them for the account lifetime plus a thirty-day grace interval, then send deletion commands to the processor and clear our own link. The only evidence left behind is an anonymised transaction hash used in aggregate summaries, themselves deleted after seven years. No usable credentials ever exist on our systems. We check token revocation daily and initiate incidents if deletion does not work. 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 logged and verifiable. Aggregate reports never reveal individual transaction hashes.
Gaming Session and Analytics of Behavior Data
All spins 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 compact 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 stay for 12 months before merging into a global model. RNG seed audit trails get 36 months. Error diagnostics get 90 days. No individual gameplay data feeds into credit or marketing profiling. All logs are encrypted and off-limits to marketing teams.
- Spin-level logs: 24 months from event date, then anonymised aggregation
- Session behavioural profiles: 24 months from last session, then deleted
- RNG seed audit trails: 36 months to satisfy technical standards
- Feature trigger heatmaps: 12 months, then integrated into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Consent for Marketing and Correspondence Records
We maintain your consent document—timestamped, IP-marked, and method-captured—for the duration of our relationship plus six years after cancellation, to meet PECR requirements. Send logs for emails, push alerts, and SMS are held for only thirteen months. Revoking consent right away halts communications while retaining historical proof. A partitioned database provides suppression without latency, and consent logs are kept in a separate compliance archive. Dispatch records include metadata only—heading, timestamp, state—not full message body. The six-year post-withdrawal timeframe matches the statute of limitations for regulatory probes. Quarterly audits verify no expired consents trigger mailings. We never tailor offers with gameplay or financial data beyond explicit authorisations.
Responsible Gambling and Self-Exclusion Registers
Stake limits, time checks, and timeout settings are kept for your account’s whole period and never purged while it is active. If you self-exclude, your hashed identity and device fingerprints enter a dedicated exclusion register kept without time limit under UKGC licence requirements. The register is encrypted separately, queried only at login or registration, and never used for analytics. Access is confined to qualified compliance staff, and all searches are tracked for three years. The register contains only identity blocks—no financial or gameplay records. We check it annually to correct errors and remove deceased individuals. Otherwise, it stays permanent. This retention is required and free from deletion requests.
Reality Check and Session Limit Enforcement
Reality check timers use temporary session counters that clear every 24 hours, beginning again from your first spin after midnight. Your selected interval—say, 30 minutes—is saved persistently and automatically reactivates when you visit again, even after a long break. Altering the interval mid-session applies the new value right away for the next reminder. These settings are removed only upon confirmed account deletion. Session timer data sits in a dedicated, 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 never categorize or advertise based on these settings.
SAR and Deletion Processes
When a subject access request arrives, we compile a formatted JSON/CSV export of all non-purged data within one month, prolongable by two months for complex cases. The export includes 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 specifying erased versus retained categories and their justifications. This report is retained as auditable proof for as long as the longest surviving data category. All requests are recorded immutably for five years.
Technology Framework and Data Location
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 apply 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 are conducted quarterly, and an independent auditor verifies automated purge schedules. Any deviation generates a Severity 1 incident, notified to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, under the same deletion policies.
Management of Encryption Keys
Master keys rotate 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 destroyed inside the HSM, making any backups unrecoverable. We assign each key to a single data partition, do not 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 guarantee forensic decryption works when needed. No plaintext key material ever leaves the HSM boundary.
Policy Evaluation and Breach Notification Protocols
We evaluate 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 notify 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 maintain a breach notification log audited quarterly. Post-incident reviews update controls as needed. Biannual tabletop exercises simulate misconfigurations and ransomware to test our response.
Policy Version Control and Change Log
We maintain 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 transmitted 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.
Tell us about your thoughtsWrite message