Playing Wanted Dead Or a Wild Slot means handing over personal data https://wanteddeadorwild.uk/. This document sets forth exactly how long we retain it, the rationale, and what technical protections sit behind each category—all aligned with 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 retained for five years after account closure. Financial logs are stored for seven, matching HMRC requirements. Gameplay data gets 24 months before anonymisation is applied. Full card numbers never reach our systems—only tokenised aliases—and every byte is encrypted. Independent auditors verify our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log records every edit, and we give you 30 days’ notice before material changes are implemented. Subject access and deletion requests are handled within statutory deadlines.
Fundamental Definitions and Extent of Personal Data
We cast a wide net 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 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 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 cover live databases, archives, and backups without exception. Each window commences from the last activity or transaction date, spelled out below. We review definitions every six months to remain compliant with regulatory guidance.
Account Registration and Identity Verification Data
Main identity data—scans of government IDs, proof of address, biometric selfie verifications—are kept for 5 years after your last session or account closure, whichever is later. This includes contractual time limits and AML obligations. We obtain only the key information: document number, expiry, country of citizenship. The full-resolution image gets destroyed immediately after extraction. Once the five-year period pass, all raw data is purged, but a hash of the verification result remains for two more years inside an audit log. Identification data sits stored encrypted with AES-256-GCM, kept separate from analytics, and every data access is recorded for three years. Unnecessary fields like birthplace are removed at verification stage to reduce the data size. Yearly reviews verify accuracy and proactively delete outdated records.
Document Upload and Biometric Processing
Provide an ID through our secure portal and automatic verification finishes within 90 seconds. We pull the document ID, expiration date, country of citizenship, and a reliability score, then destroy the full-resolution image instantly—it never reaches storage. The initial file stays in an temporary memory and vanishes after processing. A compressed, marked thumbnail is produced for compliance purposes and stored only for the identity lifecycle. That preview lives in a write-once vault with strict controls and is never shown to client support. Extracted fields are encrypted and saved for the five-year-plus-two hash window. All processing runs on ISO 27001 certified UK servers, and every thumbnail access is logged permanently.
Biometric Data Specifics
Live detection checks collect a quick video entirely in memory. Video frames are analyzed and deleted within milliseconds of time. Only a data vector of facial landmarks remains. This numerical representation has no image data and cannot be turned back into a face. It stays for the time of identity verification and is irreversibly removed upon account termination or after a five-year period. The vector sits in a specialized HSM with self-expiry and is never sent out. Login comparisons happen inside the HSM’s secure enclave without exposing the original vector. The data set is linked to a pseudonymous identifier separated from marketing profiles, which makes re-identification very hard. Even IT admins cannot see or reconstruct facial attributes from the kept numerical representation.
Responsible Gambling and Self-Exclusion Registers
Deposit 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 are added to a specific exclusion register kept permanently under UKGC licence requirements. The register is secured separately, accessed only at login or registration, and never employed for analytics. Access is limited to educated compliance staff, and all searches are tracked for three years. The register contains only identity blocks—no banking or gameplay records. We check it annually to fix errors and remove deceased individuals. Apart from that, it remains permanent. This retention is obligatory and excluded from deletion requests.
Session Awareness and Play Time Restriction Enforcement
Reality check timers use transient session counters that clear every 24 hours, restarting from your first spin after midnight. Your selected interval—say, 30 minutes—is stored persistently and automatically reactivates when you return, even after a long break. Modifying the interval mid-session applies the new value immediately for the next reminder. These settings are removed only upon validated 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 at no time categorize or advertise based on these settings.
Marketing Approval and Correspondence Records
We maintain your consent document—with time stamp, IP-stamped, and with capture method—for the duration of our association plus six years after cancellation, to meet PECR requirements. Dispatch records for emails, push notifications, and SMS are kept for only thirteen months. Cancelling consent instantly suppresses communications while retaining historical proof. A segmented database guarantees suppression without latency, and consent logs are held in a dedicated compliance archive. Delivery logs include metadata only—subject, time, condition—not full message text. The six-year post-withdrawal period 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.
SAR and Deletion Processes
Upon receiving an SAR, we compile a organized 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, sent via a one-time secure link that expires in 72 hours. For deletion, we cascade: immediate account suppression and token revocation, then queued erasure of all personal data not subject to legal hold. We produce a confirmation report specifying 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.
Session Gameplay and Behavioural Analytics Data
All spins 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 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 persist 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 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 deleted
- RNG seed audit trails: 36 months to comply with technical standards
- Feature trigger heatmaps: 12 months, then combined into global model
- Error and crash diagnostic logs: 90 days, then removed
Monetary Transaction and Payment Records
Deposit, withdrawal, and wager logs are kept for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We collect only the BIN, last four digits, and a tokenised identifier. Chargeback disputes freeze the contested record until final resolution, 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 are valid only while your account is open and are deleted within thirty days of closure. Summarised, anonymised totals persist for financial reporting without any personal details. All financial data is encrypted and separated from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways produce vaulted tokens that map your card to a non-sensitive reference. We store them for the account lifetime plus a thirty-day grace window, then send deletion commands to the processor and wipe our own link. The only evidence left behind is an anonymised transaction hash used in aggregate statements, themselves removed after seven years. No usable credentials ever reside on our systems. We track token revocation daily and raise incidents if deletion fails. Tokens are linked to our merchant code and cannot be used elsewhere. Weekly reconciliation validates correctness, and tokens tied to lost or stolen cards are revoked immediately. All token operations are documented and checked. Aggregate reports never expose individual transaction hashes.
Technology Framework and Data Storage
All data sits 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 syncs every six hours. Backups are encrypted client-side and maintain identical retention rules. We enforce 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 run quarterly, and an independent auditor confirms automated purge schedules. Any deviation raises a Severity 1 incident, reported 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 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 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 ensure forensic decryption works when needed. No plaintext key material ever exits the HSM boundary.
Policy Assessment and Data Breach 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 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, report with the ICO, and post 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 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 confirm 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 reflects our commitment to accountable data governance.
