Playing Wanted Dead Or a Wild Slot means submitting personal data wanteddeadorwild.uk. This document sets forth exactly how long we store 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 own retention clock. Identity records are kept for five years after account closure. Financial logs are stored for seven, matching HMRC requirements. Gameplay data undergoes 24 months before anonymisation kicks in. Full card numbers never enter our systems—only tokenised aliases—and every byte is secured. Independent auditors check our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log tracks every edit, and we provide you 30 days’ notice before material changes are implemented. Subject access and deletion requests are handled within statutory deadlines.
Fundamental Definitions and Range of Personal Data
We cast a wide net on what qualifies as 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 encompasses 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 starts ticking from the last activity or transaction date, spelled out below. We revisit definitions every six months to keep pace with regulatory guidance.
Gaming Session and Analytics of Behavior Data
All spins 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 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 get 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 anonymized 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 cycled out
Marketing Approval and Correspondence Records
We keep your consent document—timestamped, with IP address, and method-captured—for the duration of our relationship plus six years after withdrawal, to comply with PECR obligations. Send logs for electronic messages, push notifications, and SMS are kept for only thirteen months. Withdrawing consent right away halts communications while retaining historical proof. A partitioned database ensures suppression without lag, and consent logs are stored in a distinct compliance archive. Send logs include metadata only—subject, timestamp, condition—not full message text. The six-year post-withdrawal window reflects the statute of limitations for regulatory inquiries. Quarterly audits check no expired consents trigger mailings. We never personalise offers with gameplay or financial data beyond explicit permissions.
Registration Account and Identity Verification Data
Main identity data—government ID scans, proof of address, biometric selfie verifications—are held for 5 years after your final session or account closure, whichever comes later. This covers contractual limitation periods and AML obligations. We obtain only the necessary details: document number, expiration date, citizenship. The original image gets destroyed immediately after extraction. Once five years pass, all source data is removed, but a encrypted hash of the verification outcome remains for two more years inside an audit log. Identity data sits stored encrypted with AES-256-GCM, kept separate from analytics, and every data access is logged for three years. Non-essential fields like place of birth are deleted at verification stage to shrink the data footprint. Annual reviews verify correctness and actively purge expired data.
File Upload and Biometric Data Processing
Provide an ID through our safe portal and automatic verification finishes within a minute and a half. We pull the document number, expiry, country of citizenship, and a reliability score, then shred the original image instantly—it never touches disk. The original file stays in an temporary memory and vanishes after analysis. A reduced, stamped thumbnail is generated for auditing purposes and retained only for the identity verification period. That thumbnail lives in a write-once storage with rigorous controls and is never shown to support staff. Collected information are encrypted and kept for the five-year plus two-year hash timeframe. All operations runs on ISO 27001 certified UK servers, and every small image access is recorded immutably.
Biometric Information Details
Liveness checks capture a brief video feed solely in memory. Images are analysed and discarded within a few milliseconds. Only a mathematical vector of facial points survives. This data set lacks any image data and cannot be reverse-engineered into a facial image. It remains for the duration of identity verification and is irreversibly removed upon account termination or after five years. The data set sits in a dedicated HSM with self-expiry and is never sent out. Authentication checks happen inside the HSM’s protected enclave without exposing the original vector. The data set is linked to a pseudonym unlinked from marketing profiles, which makes re-identification very hard. Even system administrators cannot see or rebuild facial attributes from the stored vector.
Responsible Gambling and Self-Exclusion Registers
Betting limits, time checks, and timeout settings are saved for your account’s lifetime and never purged while it stays active. If you choose to ban yourself, your hashed identity and device fingerprints are added to a specialized exclusion register held permanently under UKGC licence requirements. The register is coded separately, accessed only at login or registration, and never employed for analytics. Entry is limited to trained compliance staff, and all queries are tracked for three years. The register holds only identity blocks—no financial or gameplay records. We examine it annually to fix errors and remove deceased individuals. Apart from that, it stays permanent. This retention is obligatory and free from deletion requests.
Reality Check and Session Limit Enforcement
Reality check timers use temporary session counters that clear every 24 hours, restarting from your first spin after midnight. Your selected interval—say, 30 minutes—is saved persistently and routinely reactivates when you visit again, 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 confirmed 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 at no time categorize or promote based on these settings.
Monetary Transaction and Billing Records
Funding, withdrawal, and wager records are kept for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We capture only the BIN, last four digits, and a tokenised alias. Chargeback disputes suspend the contested record until final settlement, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs verified by auditors. Tokenised card references remain valid only while your account is active and are deleted within thirty days of closure. Aggregated, anonymised totals remain for financial reporting without any personal details. All financial data is coded and separated from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways create vaulted tokens that associate your card to a non-sensitive identifier. We store them for the account lifetime plus a thirty-day grace interval, then issue deletion commands to the processor and wipe our own mapping. The only evidence left behind is an anonymised transaction hash used in aggregate summaries, themselves removed after seven years. No usable credentials ever reside on our systems. We check token revocation daily and trigger incidents if deletion is unsuccessful. Tokens are tied to our merchant code and cannot be used other places. Weekly reconciliation verifies correctness, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are logged and verifiable. Aggregate reports never expose individual transaction hashes.
Data Subject Access Request and Deletion Workflows
Upon receiving an SAR, we generate a formatted 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, sent via a one-time secure link that expires in 72 hours. For deletion, we cascade: immediate account suppression and token revocation, then batched erasure of all personal data not subject to legal hold. We create a confirmation report outlining 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 documented immutably for five years.
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 updates every six hours. Backups are encrypted client-side and follow identical retention rules. We apply least privilege with hardware MFA for administrators, recording their sessions in an immutable three-year audit trail. Multi-factor authentication integrates a hardware token and biometric check. Penetration tests are conducted quarterly, and an independent auditor verifies automated purge schedules. Any deviation generates a Severity 1 incident, notified to our DPO within four hours. We also keep an air-gapped backup rotated weekly, following the same deletion policies.
Management of Encryption Keys
Master keys are renewed 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 removed 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 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 notify 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 hold a breach notification log audited quarterly. Post-incident reviews adjust controls as needed. Biannual tabletop exercises model misconfigurations and ransomware to test our response.
Document Versioning and Change Log
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 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 verify 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.