Playing Online Wanted Dead Or A Wild Slot means submitting personal data. This document details exactly how long we keep it, the rationale, and what technical protections support 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 specific retention clock. Identity records are kept for five years after account closure. Financial logs remain for seven, satisfying HMRC requirements. Gameplay data receives 24 months before anonymisation kicks in. Full card numbers never enter our systems—only tokenised aliases—and every byte is protected. Independent auditors check 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 take effect. Subject access and deletion requests are processed within statutory deadlines.
Core Definitions and Extent of Personal Data
We adopt a comprehensive approach on what qualifies 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 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 span live databases, archives, and backups without exception. Each window starts ticking from the last activity or transaction date, spelled out below. We review definitions every six months to remain compliant with regulatory guidance.
Session Gameplay and Behavioral Analytics Data
Every spin 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 condense 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 remain for 12 months before merging into a global model. RNG seed audit trails have 36 months. Error diagnostics receive 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 aggregated aggregation
- Session behavioural profiles: 24 months from last session, then erased
- RNG seed audit trails: 36 months to comply with technical standards
- Feature trigger heatmaps: 12 months, then merged into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Registration Account and ID Verification Data
Primary identity records—official ID scans, proof of address, biometric selfie verifications—are held for 5 years after your last activity or account closure, whichever is later. This covers statutory limitation periods and AML obligations. We extract only the necessary details: ID number, expiry, country of citizenship. The full-resolution image gets deleted upon extraction. Once the five-year period pass, all source data is purged, but a cryptographic hash of the verification outcome remains for two more years inside an audit trail. Identity data sits encrypted in storage with AES-256-GCM, stored away from analytics, and every data access is tracked for 3 years. Non-essential fields like birthplace are discarded at the time of verification to shrink the data size. Yearly reviews verify accuracy and automatically remove expired entries.
File Upload and Biometric Processing
Provide an ID through our protected portal and automated checking completes within 90 seconds. We pull the document number, expiry, nationality, and a confidence score, then destroy the high-resolution image instantly—it never reaches storage. The source file stays in an temporary memory and disappears after handling. A reduced, stamped preview is generated for compliance purposes and stored only for the identity verification period. That small image lives in a write-once vault with rigorous controls and is never exposed to support staff. Retrieved data are encoded and kept for the five-year-plus-two hash window. All handling runs on UK-based ISO 27001 servers, and every small image access is logged permanently.
Biometric Information Details
Liveness verifications capture a quick video completely in memory. Images are analysed and removed within a few milliseconds. Only a numerical vector of facial landmarks survives. This numerical representation has no image data and cannot be reconstructed into a facial image. It is kept for the entire identity verification process and is permanently deleted upon closure of account or after 5 years. The numerical representation sits in a specialized HSM with automatic expiration and is never transferred. Authentication checks happen inside the HSM’s protected enclave without disclosing the original vector. The vector is bound to a pseudonym disconnected from marketing profiles, which makes re-identifying very hard. Even system admins cannot view or reconstruct facial features from the stored vector.
Marketing Consent and Communication Logs
We maintain your consent log—timestamped, with IP address, and method-recorded—for the entirety of our relationship plus six years after revocation, to satisfy PECR rules. Send logs for electronic messages, push notifications, and SMS are held for only thirteen months. Revoking consent instantly halts communications while keeping historical proof. A segmented database ensures suppression without lag, and consent logs are kept in a distinct compliance archive. Delivery logs hold metadata only—subject, timestamp, status—not full message content. The six-year post-withdrawal window matches the statute of limitations for regulatory probes. Quarterly audits verify no expired consents activate mailings. We never customise offers with gameplay or financial data beyond explicit permissions.
Financial Transaction and Billing Records
Funding, 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 record only the BIN, last four digits, and a tokenised reference. 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 remain valid only while your account is live and are deleted within thirty days of closing. Aggregated, anonymised totals remain for financial reporting without any personal information. All financial data is encrypted and isolated from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways create vaulted tokens that link your card to a non-sensitive alias. We keep them for the account lifetime plus a thirty-day grace window, then issue deletion commands to the processor and wipe our own reference. The only evidence 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 is unsuccessful. Tokens are bound to our merchant code and cannot be used in other contexts. Weekly reconciliation validates correctness, 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.
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, expandable by two months for complex cases. The export covers live databases, encrypted archives, and processor tokens, sent 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 generate a confirmation report outlining 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 logged immutably for five years.
Safe Gambling and Voluntary Exclusion Registers
Betting limits, session reminders, and timeout settings are kept for your account’s lifetime and never purged while it remains active. If you choose to ban yourself, your hashed identity and device fingerprints enter a specialized exclusion register kept indefinitely under UKGC licence requirements. The register is coded separately, checked only at login or registration, and never used for analytics. Entry is confined to educated compliance staff, and all searches are logged for three years. The register contains only identity blocks—no monetary or gameplay records. We review it annually to correct errors and remove deceased individuals. If not, it remains permanent. This retention is obligatory and free from deletion requests.
Session Awareness and Gaming Duration Enforcement
Reality check clocks use short-lived session counters that clear every 24 hours, beginning again from your first spin after midnight. Your preferred interval—say, 30 minutes—is kept persistently and routinely reactivates when you come back, even after a long break. Altering the interval mid-session applies the new value right away for the next reminder. These settings are purged only upon verified account deletion. Session timer data resides in a specialized, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for accuracy. All timer configurations are checkable through the same three-year access log standard. We do not categorize or market based on these settings.
Technical Infrastructure and Data Residency
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 synchronizes every six hours. Backups are encrypted client-side and maintain 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 combines a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor confirms automated purge schedules. Any deviation triggers a Severity 1 incident, reported to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, under the same deletion policies.
Key Lifecycle Administration
Master keys change every 90 days automatically inside an HSM. New keys are kept internal 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 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 demands 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.
Policy Assessment and Data Breach Protocols
We evaluate 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 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 model misconfigurations and ransomware to test our response.
Policy 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 retrieve the full change log through a link in our privacy centre at any time. This transparent approach demonstrates our commitment to accountable data governance.