Playing Wanted Dead Or a Wild Slot means handing over personal data. This document details exactly how long we store it, the reasons, and what technical protections sit behind each category—all aligned with 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 specific retention clock. Identity records stick around for five years after account closure. Financial logs stay for seven, meeting HMRC requirements. Gameplay data receives 24 months before anonymisation kicks in. Full card numbers never touch our systems—only tokenised aliases—and every byte is encrypted. Independent auditors review our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log records every edit, and we provide you 30 days’ notice before material changes are implemented. Subject access and deletion requests are processed 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 covers 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 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 span live databases, archives, and backups without exception. Each window starts ticking from the last activity or transaction date, spelled out below. We reassess definitions every six months to remain compliant with regulatory guidance.
Payment Transaction and Billing Records
Funding, withdrawal, and wager records are retained 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 freeze the contested record until final resolution, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs checked by auditors. Tokenised card references remain valid only while your account is live and are deleted within thirty days of closing. Combined, anonymised totals persist for financial reporting without any personal details. All financial data is encrypted and isolated from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways produce vaulted tokens that associate your card to a non-sensitive alias. We hold them for the account lifetime plus a thirty-day grace interval, then issue deletion commands to the processor and clear our own mapping. The only trace left behind is an anonymised transaction hash used in aggregate summaries, themselves purged after seven years. No usable credentials ever reside on our systems. We check token revocation daily and trigger incidents if deletion fails. Tokens are bound to our merchant code and cannot be used in other contexts. Weekly reconciliation verifies correctness, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are recorded and auditable. Aggregate reports never expose individual transaction hashes.
Responsible Gambling and Player Ban Registers
Betting limits, session reminders, and timeout settings are stored for your account’s whole period and never deleted while it stays active https://wanteddeadorwild.uk. If you opt for self-exclusion, your hashed identity and device fingerprints are placed into a dedicated exclusion register maintained permanently under UKGC licence requirements. The register is coded separately, checked only at login or registration, and never used for analytics. Access is confined to educated compliance staff, and all queries are logged for three years. The register holds only identity blocks—no monetary or gameplay records. We check it annually to fix errors and remove deceased individuals. Apart from that, it stays everlasting. This retention is obligatory and excluded from deletion requests.
Session Awareness and Play Time Restriction Enforcement
Reality check timers use short-lived session counters that reset every 24 hours, beginning again from your first spin after midnight. Your selected interval—say, 30 minutes—is stored persistently and instantly reactivates when you return, even after a long break. Modifying the interval mid-session sets the new value instantly for the next reminder. These settings are deleted only upon verified account deletion. Session timer data sits in a specialized, 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 do not profile or advertise based on these settings.
Session Gameplay and Behavioral Analytics Data
Every 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 used 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 stay for 12 months before merging into a global model. RNG seed audit trails receive 36 months. Error diagnostics have 90 days. No individual gameplay data goes 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 removed
- 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
Consent for Marketing and Communication Logs
We maintain your consent log—with time stamp, IP-stamped, and with capture method—for the life of our partnership plus six years after cancellation, to satisfy PECR rules. Send logs for e-mails, push alerts, and SMS are retained for only thirteen months. Cancelling consent right away suppresses communications while preserving historical proof. A divided database guarantees suppression without delay, and consent logs are kept in a separate compliance archive. Send logs include metadata only—topic, time, state—not full message text. The six-year post-withdrawal period mirrors the statute of limitations for regulatory investigations. Quarterly audits confirm no expired consents trigger mailings. We never customise offers with gameplay or financial data beyond explicit consents.
Registration Account and Identity Verification Data
Primary identity records—official ID scans, proof of address, selfie biometric matches—are held for a five-year period after your last session or closure of account, whichever is later. This covers contractual limitation periods and AML obligations. We extract only the key information: document number, expiry, country of citizenship. The original image gets shredded right after extraction. Once five years pass, all source data is erased, but a hash of the verification result lives on for another two years inside an audit log. Identity data sits encrypted at rest with AES-256-GCM, stored away from analytics, and every data access is logged for 3 years. Unnecessary fields like birth location are deleted at the time of verification to minimize the data size. Yearly reviews ensure precision and automatically remove expired data.
File Upload and Biometric Processing
Upload an ID through our secure portal and automated checking wraps up within ninety seconds. We retrieve the document ID, expiration date, country of citizenship, and a confidence score, then destroy the full-resolution image immediately—it never touches disk. The initial file stays in an memory buffer and is removed after handling. A compressed, stamped small image is produced for auditing purposes and kept only for the identity verification period. That thumbnail lives in a immutable vault with tight controls and is never shown to support staff. Collected information are secured and stored for the five-year-plus-two hash window. All processing runs on UK-based ISO 27001 servers, and every preview retrieval is logged permanently.
Biometric Data Specifics
Liveness checks collect a brief video feed solely in memory. Frames are analyzed and discarded within a few milliseconds. Only a numerical vector of facial landmarks persists. This data set contains no image data and cannot be turned back into a face. It remains for the entire identity verification process and is permanently deleted upon account closure or after 5 years. The vector sits in a specialized HSM with auto-expiry and is never sent out. Login verifications happen inside the HSM’s secure enclave without exposing the raw vector. The data set is associated with a anonymous identifier separated from marketing profiles, which makes re-identifying highly challenging. Even system admins are unable to view or rebuild face characteristics from the stored vector.
Access Request and Erasure Workflows
When an SAR lands, we compile a structured 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, provided 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 create a confirmation report specifying erased versus retained categories and their justifications. This report is kept as auditable proof for as long as the longest surviving data category. All requests are recorded immutably for five years.
Technology Framework and Data Storage
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 updates 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 uses a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor verifies automated purge schedules. Any deviation triggers a Severity 1 incident, alerted to our DPO within four hours. We also keep an air-gapped backup rotated weekly, under the same deletion policies.
Encryption Key Lifecycle Management
Master keys rotate every 90 days automatically inside an HSM. New keys are not extracted 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 destroyed inside the HSM, making any backups unrecoverable. We assign 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 needs 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 exits the HSM boundary.
Policy Evaluation and Data Breach Protocols
We assess this policy every six months or upon material change to the game or regulation. Reviews are minuted 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 inform affected individuals within 72 hours if high risk, file with the ICO, and publish 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.
Policy Versioning and Revision History
We preserve a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log details 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.