Playing Wanted Dead Or a Wild Slot means submitting personal data. This document lays out exactly how long we keep 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 specific retention clock. Identity records are kept for five years after account closure. Financial logs are stored for seven, meeting HMRC requirements. Gameplay data receives 24 months before anonymisation is applied. 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 triggers a full incident response. A version-controlled policy log tracks every edit, and we offer you 30 days’ notice before material changes take effect. Subject access and deletion requests are managed within statutory deadlines.
Fundamental Definitions and Extent of Personal Data
We adopt a comprehensive approach 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 encompasses session length, bet sizing, spin velocity, and how often feature triggers fire. Even pseudonymised logs can identify again 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 begins counting from the last activity or transaction date, spelled out below. We reassess definitions every six months to stay aligned with regulatory guidance.
Technical Infrastructure and Data Storage
All data sits in UK-based ISO 27001 Tier III+ data centres, never replicated 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 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 run quarterly, and an independent auditor verifies automated purge schedules. Any deviation raises a Severity 1 incident, alerted to our DPO within four hours. We also keep an air-gapped backup rotated weekly, subject to the same deletion policies.
Management of Encryption Keys
Master keys change every 90 days automatically inside an HSM. New keys are not extracted 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 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 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 exits the HSM boundary.
Access Request and Erasure Workflows
Upon receiving an SAR, we produce a structured JSON/CSV export of all non-purged data within one month, expandable by two months for complex cases. The export includes live databases, encrypted archives, and processor tokens, delivered via a one-time secure link that expires in 72 hours. For deletion, we cascade: immediate account suppression and token revocation, then scheduled 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 logged immutably for five years.
Safe Gambling and Self-Exclusion Registers
Betting limits, reality checks, and timeout settings are stored for your account’s entire duration and never deleted while it is active. If you choose to ban yourself, your hashed identity and device fingerprints enter a specialized exclusion register kept without time limit under UKGC licence requirements. The register is encrypted separately, accessed only at login Wanted Dead Or A Wild Official Site registration, and never used for analytics. Entry is limited to trained compliance staff, and all lookups are logged for three years. The register stores only identity blocks—no financial or gameplay records. We review it annually to correct errors and remove deceased individuals. Apart from that, it is kept indefinite. This retention is required 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, restarting 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. Modifying 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 precision. All timer configurations are auditable through the same three-year access log standard. We do not profile or market based on these settings.
Payment Transaction and Payment 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 alias. Chargeback disputes suspend the contested record until final resolution, 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 open and are wiped within thirty days of closure. Aggregated, anonymised totals persist for financial reporting without any personal information. All financial data is coded and quarantined from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways generate vaulted tokens that link your card to a non-sensitive identifier. We hold them for the account lifetime plus a thirty-day grace period, then issue deletion commands to the processor and clear our own link. The only trace left behind is an anonymised transaction hash used in aggregate summaries, themselves deleted after seven years. No usable credentials ever sit on our systems. We monitor token revocation daily and trigger incidents if deletion is unsuccessful. Tokens are linked to our merchant code and cannot be used other places. Weekly reconciliation verifies validity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are documented and auditable. Aggregate reports never expose individual transaction hashes.
Gaming Session and Behavioral Analytics Data
Each spin on Wanted Dead Or a Wild tracks 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 used for game design. Session behavioural profiles—average bet, spin cadence, feature buy-ins—stay 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 get 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 erased
- RNG seed audit trails: 36 months to satisfy technical standards
- Feature trigger heatmaps: 12 months, then merged into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Consent for Marketing and Message Logs
We maintain your consent record—time-stamped, IP-stamped, and with capture method—for the life of our relationship plus six years after withdrawal, to satisfy PECR requirements. Dispatch records for emails, push messages, and SMS are retained for only thirteen months. Withdrawing consent right away halts communications while retaining historical proof. A divided database ensures suppression without delay, and consent logs are kept in a distinct compliance archive. Send logs include metadata only—topic, timestamp, state—not full message content. The six-year post-withdrawal timeframe mirrors the statute of limitations for regulatory probes. Quarterly audits check no expired consents activate mailings. We never customise offers with gameplay or financial data beyond explicit authorisations.
Account Registration and Verification of Identity Data
Primary identity records—government ID scans, residence proof, biometric selfie verifications—are held for a five-year period after your final session or account closure, whichever is later. This covers contractual time limits and anti-money laundering responsibilities. We obtain only the essentials: document number, validity, country of citizenship. The high-resolution image gets destroyed right after extraction. Once the five-year period pass, all original data is removed, but a cryptographic hash of the verification data remains for an additional two years inside an audit trail. Identification data sits stored encrypted with AES-256-GCM, isolated from analytics, and every access is recorded for 3 years. Non-essential fields like birth location are removed at the time of verification to minimize the data volume. Yearly audits verify accuracy and proactively delete outdated records.
Document Upload and Biometric Processing
Upload an ID through our secure portal and automatic verification wraps up within ninety seconds. We pull the document number, expiry, citizenship, and a confidence score, then destroy the full-resolution image immediately—it is never stored on disk. The source file stays in an memory buffer and disappears after processing. A compacted, watermarked preview is produced for compliance purposes and retained only for the identity lifecycle. That preview lives in a write-once vault with strict controls and is never shown to client support. Collected information are encoded and kept for the five-year plus two-year hash timeframe. All processing runs on ISO 27001 certified UK servers, and every preview retrieval is recorded immutably.
Specifics of Biometric Data
Live detection checks capture a brief video feed entirely in memory. Frames are analyzed and deleted within milliseconds. Only a data vector of facial landmarks remains. This vector contains no image data and cannot be reconstructed into a facial image. It is kept for the duration of identity verification and is irreversibly removed upon account closure or after a five-year period. The data set sits in a specialized HSM with automatic expiration and is never transferred. Login verifications happen inside the HSM’s secure enclave without exposing the raw vector. The vector is linked to a anonymous identifier unlinked from marketing data, which makes re-identifying extremely difficult. Even system administrators cannot view or recreate facial features from the kept numerical representation.
Policy Review and Breach Notification 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 published 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, submit with the ICO, and issue a transparency notice. Third-party processor breaches must follow the same protocol. We keep a breach notification log audited quarterly. Post-incident reviews revise controls as needed. Biannual tabletop exercises test misconfigurations and ransomware to test our response.
Policy Version Control and Update Log
We keep 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 transmitted 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 confirm 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 reflects our commitment to accountable data governance.