Playing Wanted Dead Or a Wild Slot game means handing over personal data. This document lays out exactly how long we keep it, the reasons, and what technical protections underpin each category—all aligned with 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 own retention clock. Identity records are retained for five years after account closure. Financial logs stay for seven, satisfying HMRC requirements. Gameplay data gets 24 months before anonymisation kicks in. Full card numbers never reach our systems—only tokenised aliases—and every byte is encrypted. Independent auditors check our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log documents every edit, and we give you 30 days' notice before material changes become effective. Subject access and deletion requests are processed within statutory deadlines.
Core Definitions and Extent of Personal Data
We take a broad view on what counts as personal data. Direct identifiers—name, email, billing address, masked payment details—are accompanied by 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 link back to 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 commences from the last activity or transaction date, spelled out below. We reassess definitions every six months to keep pace with regulatory guidance.
SAR and Deletion Processes
Upon receiving an SAR, we produce a organized JSON/CSV export of all non-purged data within one month, prolongable by two months for complex cases. The export covers 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 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 maintained as auditable proof for as long as the longest surviving data category. All requests are recorded immutably for five years.
Session Gameplay and Behavioral Analytics Data
All spins on Wanted Dead Or a Wild tracks reel positions, RNG seed, and net outcome with microsecond precision. We store 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—persist 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 get 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 rotated out
Registration Account and Verification of Identity Data
Main identity data—government ID scans, proof of address, biometric selfie verifications—are retained for a five-year period after your last activity or account closure, whichever is later. This includes contractual limitation periods and anti-money laundering responsibilities. We obtain only the necessary details: ID number, validity, nationality. The high-resolution image gets shredded right after extraction. Once five years pass, all original data is removed, but a encrypted hash of the verification result lives on 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 recorded for three years. Optional fields like birth location are deleted at verification time to reduce the data footprint. Annual reviews verify precision and automatically remove outdated records.
Document Upload and Biometric Processing
Submit an ID through our protected portal and automated validation completes within a minute and a half. We extract the ID number, validity, citizenship, and a confidence score, then destroy the high-resolution image immediately—it never reaches storage. The initial file stays in an temporary memory and disappears after processing. A reduced, marked thumbnail is generated for audit purposes and kept only for the ID lifecycle. That small image lives in a write-once vault with tight controls and is never exposed to customer support. Collected information are encoded and stored for the 5-year-plus-2-year hash period. All operations runs on ISO 27001 certified UK servers, and every small image access is recorded immutably.
Biometric Information Details
Liveness verifications capture a quick video solely in memory. Frames are analyzed and discarded within milliseconds. Only a numerical vector of facial points persists. This data set contains no image data and cannot be reconstructed into a picture. It is kept for the duration of identity verification and is purged irrevocably upon account closure or after five years. The vector sits in a specialized HSM with automatic expiration and is never sent out. Login verifications happen inside the HSM’s secure enclave without exposing the original vector. The vector is associated with a anonymous identifier disconnected from marketing profiles, which makes re-identification highly challenging. Even IT admins cannot view or recreate facial features from the kept numerical representation.
Marketing Consent and Correspondence Records
We store your consent log—timestamped, IP-marked, and method-recorded—for the life of our relationship plus six years after cancellation, to satisfy PECR obligations. Delivery logs for emails, push notifications, and SMS are retained for only thirteen months. Revoking consent immediately halts communications while preserving historical proof. A partitioned database ensures suppression without lag, and consent logs are held in a dedicated compliance archive. Delivery logs include metadata only—subject, timestamp, state—not full message text. The six-year post-withdrawal timeframe matches the statute of limitations for regulatory investigations. Quarterly audits verify no expired consents activate mailings. We never tailor offers with gameplay or financial data beyond explicit authorisations.
Payment Transaction and Settlement Records
Deposit, withdrawal, and wager histories are retained 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 identifier. Chargeback disputes halt the contested record until final outcome, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs verified by auditors. Tokenised card references are valid only while your account is active and are erased within thirty days of closing. Combined, anonymised totals endure for financial reporting without any personal details. 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 issue deletion commands to the processor and wipe our own mapping. The only trace 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 monitor 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 expose individual transaction hashes.
Infrastructure Setup and Data Storage
All data sits in UK-based ISO 27001 Tier III+ data centres, not copied outside the UK. A hot disaster recovery site in a separate UK zone synchronizes every six hours. Backups are encrypted client-side and maintain identical retention rules. We implement least privilege with hardware MFA for administrators, recording 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 confirms automated purge schedules. Any deviation raises a Severity 1 incident, alerted 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 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 assign 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 exits the HSM boundary.
Safe Gambling and Voluntary Exclusion Registers
Betting limits, time checks, and timeout settings are stored for your account’s entire duration and never removed while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a dedicated exclusion register maintained without time limit under UKGC licence requirements. The register is coded separately, queried only at login or registration, and never utilized for analytics. Permission is limited to trained compliance staff, and all lookups are tracked for three years. The register stores only identity blocks—no monetary or gameplay records. We review it annually to correct errors and remove deceased individuals. Otherwise, it stays indefinite. This retention is mandatory and excluded from deletion requests.
Reality Check and Session Limit Enforcement
Reality check clocks use short-lived session counters that restart every 24 hours, starting anew from your first spin after midnight https://wanteddeadorwild.uk/. Your chosen interval—say, 30 minutes—is kept persistently and instantly reactivates when you visit again, even after a long break. Changing the interval mid-session applies the new value immediately for the next reminder. These settings are removed only upon verified account deletion. Session timer data lies in a specific, 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 analyze or market based on these settings.
Policy Assessment and Incident Reporting 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 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 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 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 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.