Playing Wanted Dead Or a Wild Slot game means providing personal data. This document lays out 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 manage 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, meeting 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 protected. Independent auditors review our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log documents every edit, and we provide you 30 days’ notice before material changes take effect. Subject access and deletion requests are handled within statutory deadlines.
Core Definitions and Scope of Personal Data
We cast a wide net on what constitutes 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 link back to 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.
Monetary Transaction and Billing Records
Deposit, withdrawal, and wager records 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 halt the contested record until final outcome, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs verified by auditors. Tokenised card references stay valid only while your account is active and are wiped 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.
Tokenized Payment Instruments and Processor References
Payment gateways generate vaulted tokens that map your card to a non-sensitive alias. We store them for the account lifetime plus a thirty-day grace interval, then transmit deletion commands to the processor and wipe our own mapping. The only remnant 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 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 invalidated immediately. All token operations are documented and checked. Aggregate reports never reveal individual transaction hashes.
Safe Gambling and Self-Exclusion Registers
Stake limits, reality checks, and timeout settings are kept for your account’s entire duration and never removed while it is active. If you choose to ban yourself, your hashed identity and device fingerprints enter a specialized exclusion register kept permanently 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 searches are recorded for three years. The register holds only identity blocks—no financial or gameplay records. We check it annually to correct errors and remove deceased individuals. Otherwise, it is kept permanent. This retention is obligatory and exempt from deletion requests.
Session Awareness and Session Limit Enforcement
Reality check timers use transient session counters that reset every 24 hours, beginning again from your first spin after midnight. Your preferred interval—say, 30 minutes—is kept persistently and instantly reactivates when you come back, 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 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 auditable through the same three-year access log standard. We do not analyze or advertise based on these settings.
User Account and Verification of Identity Data
Core identity profiles—scans of government IDs, residence proof, selfie biometric matches—are held for five years after your final session or account termination, whichever comes later. This includes contractual time limits and AML obligations. We retrieve only the necessary details: document number, validity, citizenship. The original image gets destroyed immediately after extraction. Once the five-year period pass, all raw data is purged, but a encrypted hash of the verification data remains for another two years inside an logging system. Identity data sits stored encrypted with AES-256-GCM, kept separate from analytics, and every access is logged for three years. Unnecessary fields like place of birth are discarded at verification time to minimize the data footprint. Yearly reviews ensure correctness and proactively delete outdated records.
Document Upload and Biometric Handling
Upload an ID through our protected portal and automated checking wraps up within ninety seconds. We pull the document number, expiry, nationality, and a reliability score, then destroy the high-resolution image immediately—it is never stored on disk. The original file stays in an memory buffer and vanishes after handling. A reduced, marked thumbnail is generated for audit purposes and kept only for the identity lifecycle. That preview lives in a immutable vault with strict controls and is never shared to support staff. Extracted fields are encrypted and kept for the five-year plus two-year hash timeframe. All handling runs on UK-based ISO 27001 servers, and every preview retrieval is recorded immutably.
Biometric Information Details
Liveness checks capture a brief video feed completely in memory. Video frames are analysed and removed within milliseconds of time. Only a mathematical vector of face features survives. This data set lacks any image data and cannot be turned back into a facial image. It stays for the entire identity verification process and is irreversibly removed upon account termination or after a five-year period. The numerical representation sits in a dedicated HSM with automatic expiration and is never transferred. Authentication checks happen inside the HSM’s safe environment without revealing the unprocessed data. The vector is bound to a pseudonym separated from advertising profiles, which makes re-identification highly challenging. Even system admins cannot view or reconstruct face characteristics from the kept numerical representation.
Access Request and Erasure Workflows
Upon receiving an SAR, we generate a organized JSON/CSV export of all non-purged data within one month, extendable by two months for complex cases. The export includes live databases, encrypted archives, and processor tokens, sent 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 outlining 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.
Consent for Marketing and Correspondence Records
We maintain your consent log—time-stamped, IP-marked, and with capture method—for the entirety of our partnership plus six years after cancellation, to comply with PECR requirements. Dispatch records for e-mails, push alerts, and SMS are retained for only thirteen months. Withdrawing consent instantly halts communications while retaining historical proof. A segmented database guarantees suppression without delay, and consent logs are kept in a dedicated compliance archive. Dispatch records contain metadata only—subject, time, condition—not full message content. The six-year post-withdrawal period reflects the statute of limitations for regulatory investigations. Quarterly audits check no expired consents trigger mailings. We never personalise offers with gameplay or financial data beyond explicit permissions.
Gaming Session and Analytics of Behavior Data
Each spin on Wanted Dead Or a Wild tracks 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—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 anonymised 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 rotated out
Policy Review 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 communicated 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, submit 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 revise controls as needed. Biannual tabletop exercises simulate misconfigurations and ransomware to test our response.
Document Versioning and Change Log
We maintain a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log specifies 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 verify the log’s accuracy. The log is a living document reflecting our evolving data practices. You can access the full change log through a link in our privacy centre at any time. This transparent approach demonstrates our commitment to accountable data governance.
Infrastructure Setup and Data Location
All data resides in UK-based ISO 27001 Tier III+ data centres, never replicated outside the UK https://wanteddeadorwild.uk/. A hot disaster recovery site in a separate UK zone updates every six hours. Backups are encrypted client-side and follow identical retention rules. We enforce least privilege with hardware MFA for administrators, recording their sessions in an immutable three-year audit trail. Multi-factor authentication combines 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 keep an air-gapped backup rotated weekly, following the same deletion policies.
Encryption Key Lifecycle Management
Master keys change every 90 days automatically inside an HSM. New keys are never exported in plaintext. Rotated keys are retained for the data’s retention period plus 12 months for lawful forensic access. https://tracxn.com/d/companies/jackpot-casino/__dOHEvqvkAUTl-ebR1GmBt5Fi7Ix8qqYYjlMKtfWVeNE When a data category is purged, its key is destroyed inside the HSM, making any backups unrecoverable. We link 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 confirm forensic decryption works when needed. No plaintext key material ever departs the HSM boundary.