Software SolutionsPlaying Wanted Dead Or a Wild Slot game means handing over personal data https://wanteddeadorwild.uk. This document details exactly how long we store it, why, and what technical protections sit behind 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 unique retention clock. Identity records stick around for five years after account closure. Financial logs remain for seven, meeting HMRC requirements. Gameplay data gets 24 months before anonymisation takes effect. Full card numbers never touch our systems—only tokenised aliases—and every byte is encrypted. Independent auditors check our automated deletion routines, and any schedule slip triggers 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.
Safe Gambling and Voluntary Exclusion Registers
Betting limits, time checks, and timeout settings are kept for your account’s lifetime and never purged while it is active. If you choose to ban yourself, your hashed identity and device fingerprints are added to a dedicated exclusion register kept without time limit under UKGC licence requirements. The register is secured separately, accessed only at login or registration, and never utilized for analytics. Access is restricted to trained compliance staff, and all queries are tracked for three years. The register stores only identity blocks—no banking or gameplay records. We examine it annually to fix errors and remove deceased individuals. Apart from that, it is kept permanent. This retention is required and exempt from deletion requests.
Reality Check and Gaming Duration Enforcement
Reality check timers use temporary session counters that reset every 24 hours, restarting from your first spin after midnight. Your selected interval—say, 30 minutes—is kept persistently and instantly reactivates when you visit again, even after a long break. Changing the interval mid-session applies the new value right away for the next reminder. These settings are deleted only upon confirmed account deletion. Session timer data resides in a specific, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for correctness. All timer configurations are verifiable through the same three-year access log standard. We do not analyze or advertise based on these settings.
Gaming Session and Analytics of Behavior Data
Each spin on Wanted Dead Or a Wild records 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 employed 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 remain 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 anonymised aggregation
- Session behavioural profiles: 24 months from last session, then deleted
- 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 cycled out
Registration Account and Identity Verification Data
Primary identity records—scans of government IDs, address verification, selfie biometric matches—are retained for 5 years after your last activity or closure of account, whichever occurs later. This encompasses contractual time limits and anti-money laundering responsibilities. We obtain only the necessary details: document ID, expiry, nationality. The high-resolution image gets shredded right after extraction. Once the five-year period pass, all source data is removed, but a cryptographic hash of the verification data persists for an additional two years inside an audit log. Identity data sits encrypted in storage with AES-256-GCM, isolated from analytics, and every access is tracked for a three-year period. Optional fields like birth location are deleted at verification stage to reduce the data footprint. Annual reviews ensure precision and actively purge outdated records.
Document Upload and Biometric Processing
Provide an ID through our safe portal and automatic verification finishes within 90 seconds. We pull the document number, expiry, country of citizenship, and a trust score, then delete the original image immediately—it never touches disk. The source file stays in an temporary memory and disappears after processing. A compressed, watermarked thumbnail is generated for audit purposes and stored only for the identity verification forbes.com period. That preview lives in a write-once vault with tight controls and is never shown to support staff. Extracted fields are secured and saved for the five-year plus two-year hash timeframe. All handling runs on ISO 27001 certified UK servers, and every thumbnail access is logged permanently.
Biometric Data Specifics
Liveness checks collect a quick video entirely in memory. Images are analysed and discarded within milliseconds of time. Only a numerical vector of facial points survives. This numerical representation lacks any image data and cannot be reconstructed into a face. It remains for the duration of identity verification and is irreversibly removed upon account termination or after 5 years. The data set sits in a dedicated HSM with auto-expiry and is never exported. Login verifications happen inside the HSM’s safe environment without exposing the raw vector. The numerical representation is linked to a pseudonymous identifier disconnected from advertising profiles, which makes re-identifying very hard. Even system administrators are unable to view or reconstruct facial attributes from the saved data.
Fundamental Definitions and Scope of Personal Data
We take a broad view on what qualifies as personal data. Direct identifiers—name, email, billing address, masked payment details—are accompanied by 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 identify again a person when stitched together, so we handle 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.
Infrastructure Setup and Data Residency
All data is stored in UK-based ISO 27001 Tier III+ data centres, not copied outside the UK. A hot disaster recovery site in a separate UK zone synchronizes every six hours. Backups are encrypted client-side and follow 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 occur quarterly, and an independent auditor confirms 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, under the same deletion policies.
Management of Encryption Keys
Master keys are renewed every 90 days automatically inside an HSM. New keys are kept internal 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 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 needs dual control and is stored on write-once media in a fireproof safe. Annual recovery drills guarantee forensic decryption works when needed. No plaintext key material ever exits the HSM boundary.
Marketing Consent and Communication Logs
We maintain your consent record—with time stamp, IP-stamped, and method-recorded—for the entirety of our relationship plus six years after cancellation, to meet PECR rules. Delivery logs for emails, push notifications, and SMS are retained for only thirteen months. Cancelling consent instantly halts communications while retaining historical proof. A divided database provides suppression without latency, and consent logs are held in a dedicated compliance archive. Delivery logs hold metadata only—heading, time, status—not full message text. The six-year post-withdrawal timeframe matches the statute of limitations for regulatory investigations. Quarterly audits confirm no expired consents trigger mailings. We never personalise offers with gameplay or financial data beyond explicit consents.
Access Request and Erasure Workflows
When a subject access request arrives, we generate a organized JSON/CSV export of all non-purged data within one month, expandable by two months for complex cases. The export spans live databases, encrypted archives, and processor tokens, delivered via a one-time secure link that expires in 72 hours. For deletion, we proceed sequentially: immediate account suppression and token revocation, then queued erasure of all personal data not subject to legal hold. We produce a confirmation report detailing 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.
Financial Transaction and Settlement Records
Deposit, withdrawal, and wager histories are retained for seven years from the transaction date, per HMRC and FCA rules. We seldom store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised identifier. Chargeback disputes halt the contested record until final outcome, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs audited by auditors. Tokenised card references stay valid only while your account is active and are deleted within thirty days of closure. Combined, anonymised totals remain for financial reporting without any personal information. All financial data is coded and isolated from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways create vaulted tokens that associate your card to a non-sensitive alias. We keep them for the account lifetime plus a thirty-day grace interval, then transmit deletion commands to the processor and erase our own reference. 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 track token revocation daily and initiate incidents if deletion is unsuccessful. Tokens are linked to our merchant code and cannot be used in other contexts. Weekly reconciliation validates correctness, and tokens tied to lost or stolen cards are revoked immediately. All token operations are logged and verifiable. Aggregate reports never disclose individual transaction hashes.
Policy Evaluation and Data Breach Protocols
We evaluate 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 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, file with the ICO, and publish a transparency notice. Third-party processor breaches must follow the same protocol. We keep a breach notification log audited quarterly. Post-incident reviews adjust controls as needed. Biannual tabletop exercises model misconfigurations and ransomware to test our response.
Policy Versioning and Change Log
We keep a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log outlines 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 access the full change log through a link in our privacy centre at any time. This transparent approach demonstrates our commitment to accountable data governance.
