Playing Wanted Dead Or a Wild Slot means providing personal data wanteddeadorwild.uk. This document details exactly how long we keep it, why, and what technical protections sit behind 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 specific retention clock. Identity records are retained for five years after account closure. Financial logs are stored for seven, meeting HMRC requirements. Gameplay data receives 24 months before anonymisation takes effect. Full card numbers never reach our systems—only tokenised aliases—and every byte is protected. 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 are implemented. Subject access and deletion requests are managed within statutory deadlines.
Fundamental Definitions and Scope of Personal Data
We take a broad view on what constitutes 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 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 reassess definitions every six months to remain compliant with regulatory guidance.
Gameplay Session and Behavioral Analytics Data
All spins on Wanted Dead Or a Wild records reel positions, RNG seed, and net outcome with microsecond precision. We retain these raw logs for twenty-four months, then compact them into an anonymous statistical digest utilized 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 have 36 months. Error diagnostics have 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 aggregated aggregation
- Session behavioural profiles: 24 months from last session, then erased
- 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 removed
Monetary Transaction and Settlement Records
Deposit, withdrawal, and wager logs are maintained for seven years from the transaction date, per HMRC and FCA rules. We seldom store full PANs or CVVs. We collect only the BIN, last four digits, and a tokenised reference. Chargeback disputes suspend 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 checked by auditors. Tokenised card references are valid only while your account is open and are wiped within thirty days of closing. Summarised, anonymised totals persist for financial reporting without any personal details. All financial data is coded and isolated from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways generate vaulted tokens that map your card to a non-sensitive identifier. We keep them for the account lifetime plus a thirty-day grace window, then transmit deletion commands to the processor and erase our own reference. The only remnant left behind is an anonymised transaction hash used in aggregate reports, themselves deleted after seven years. No usable credentials ever reside on our systems. We track token revocation daily and raise incidents if deletion does not work. Tokens are linked to our merchant code and cannot be used elsewhere. Weekly reconciliation verifies authenticity, and tokens tied to lost or stolen cards are revoked immediately. All token operations are documented and checked. Aggregate reports never reveal individual transaction hashes.
Access Request and Erasure Workflows
When a subject access request arrives, we produce a formatted JSON/CSV export of all non-purged data within one month, extendable 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 queued 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 retained as auditable proof for as long as the longest surviving data category. All requests are logged immutably for five years.
User Account and ID Verification Data
Primary identity records—scans of government IDs, residence proof, biometric selfie verifications—are retained for a five-year period after your final session or closure of account, whichever occurs later. This includes contractual limitation periods and AML obligations. We extract only the key information: ID number, expiry, country of citizenship. The original image gets destroyed right after extraction. Once 5 years pass, all original data is removed, but a encrypted hash of the verification data remains for another two years inside an audit trail. Personal identity information sits encrypted in storage with AES-256-GCM, isolated from analytics, and every retrieval is tracked for a three-year period. Non-essential fields like birthplace are removed at verification time to reduce the data size. Yearly reviews ensure precision and actively purge expired entries.
Uploading Documents and Biometric Handling
Submit an ID through our protected portal and automated validation completes within 90 seconds. We extract the document number, expiry, citizenship, and a reliability score, then delete the high-resolution image right away—it never touches disk. The original file stays in an temporary memory and vanishes after analysis. A compressed, stamped thumbnail is produced for auditing purposes and stored only for the identity lifecycle. That preview lives in a immutable vault with strict controls and is never shared to customer support. Retrieved data are encoded and stored for the 5-year-plus-2-year hash period. All handling runs on servers in the UK with ISO 27001, and every thumbnail access is stored unchangeably.
Biometric Information Details
Live detection checks record a short video stream entirely in memory. Video frames are analyzed and discarded within milliseconds of time. Only a numerical vector of facial points persists. This vector contains no image data and cannot be reconstructed into a face. It stays for the entire identity verification process and is irreversibly removed upon closure of account or after 5 years. The numerical representation sits in a hardware security module with auto-expiry and is never transferred. Login comparisons happen inside the HSM’s secure enclave without exposing the raw vector. The numerical representation is bound to a pseudonymous identifier disconnected from advertising profiles, which makes reidentification very hard. Even IT admins are unable to view or recreate face characteristics from the stored vector.
Controlled Gambling and Self-Exclusion Registers
Betting limits, time checks, and timeout settings are stored for your account’s entire duration and never deleted while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a dedicated exclusion register held indefinitely under UKGC licence requirements. The register is encrypted separately, queried only at login or registration, and never utilized for analytics. Access is limited to qualified compliance staff, and all searches are recorded for three years. The register stores only identity blocks—no banking or gameplay records. We review it annually to fix errors and remove deceased individuals. Otherwise, it stays everlasting. This retention is mandatory and free from deletion requests.
Session Awareness and Play Time Restriction Enforcement
Reality check clocks 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 saved persistently and automatically reactivates when you return, even after a long break. Altering the interval mid-session applies the new value instantly for the next reminder. These settings are deleted only upon validated account deletion. Session timer data lies in a dedicated, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for accuracy. All timer configurations are auditable through the same three-year access log standard. We do not analyze or promote based on these settings.
Marketing Approval and Correspondence Records
We maintain your consent log—time-stamped, with IP address, and method-recorded—for the life of our partnership plus six years after cancellation, to meet PECR obligations. Dispatch records for e-mails, push alerts, and SMS are held for only thirteen months. Revoking consent right away blocks communications while retaining historical proof. A partitioned database ensures suppression without lag, and consent logs are held in a separate compliance archive. Dispatch records hold metadata only—heading, time stamp, condition—not full message body. The six-year post-withdrawal window matches the statute of limitations for regulatory investigations. Quarterly audits verify no expired consents activate mailings. We never personalise offers with gameplay or financial data beyond explicit authorisations.
Policy Review 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 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 model misconfigurations and ransomware to test our response.
Policy Version Control and Revision History
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 communicated 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.
Technical Infrastructure and Data Residency
All data resides in UK-based ISO 27001 Tier III+ data centres, never replicated 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 implement 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 are conducted quarterly, and an independent auditor validates automated purge schedules. Any deviation raises a Severity 1 incident, notified to our DPO within four hours. We also operate 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 kept internal in plaintext. Rotated keys are retained 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, 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 confirm forensic decryption works when needed. No plaintext key material ever departs the HSM boundary.