Data Retention Policy for Wanted Dead Or a Wild Slot in the United Kingdom

Playing Wanteddeadorawildslot game means handing over personal data. This document details exactly how long we keep it, the reasons, 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 own retention clock. Identity records stick around for five years after account closure. Financial logs remain for seven, meeting HMRC requirements. Gameplay data undergoes 24 months before anonymisation takes effect. Full card numbers never enter our systems—only tokenised aliases—and every byte is secured. Independent auditors verify 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 become effective. Subject access and deletion requests are handled within statutory deadlines.

Essential Definitions and Range 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 includes 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 extend across 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 stay aligned with regulatory guidance.

Payment Transaction and Billing Records

Deposit, withdrawal, and wager logs are kept 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 identifier. Chargeback disputes freeze the contested record until final outcome, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs verified by auditors. Tokenised card references stay valid only while your account is live and are wiped within thirty days of termination. Summarised, anonymised totals remain for financial reporting without any personal information. All financial data is secured and quarantined from marketing systems.

Tokenised Payment Instruments and Processor References

Payment gateways generate vaulted tokens that map your card to a non-sensitive reference. We keep them for the account lifetime plus a thirty-day grace window, then issue deletion commands to the processor and wipe our own link. The only trace 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 monitor token revocation daily and raise incidents if deletion is unsuccessful. Tokens are bound to our merchant code and cannot be used other places. Weekly reconciliation verifies authenticity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are recorded and auditable. Aggregate reports never disclose individual transaction hashes.

User Account and Identity Verification Data

Core identity profiles—scans of government IDs, proof of address, biometric selfie matches—are kept for a five-year period after your last session or account closure, whichever comes later. This encompasses contractual limitation periods and anti-money laundering duties. We retrieve only the essentials: document number, expiration date, citizenship. The full-resolution image gets shredded right after extraction. Once five years pass, all source data is erased, but a hash of the verification data remains for another two years inside an audit trail. Identity data 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 place of birth are discarded at verification stage to shrink the data volume. Yearly reviews verify correctness and proactively delete expired data.

Uploading Documents and Biometric Data Processing

Submit an ID through our safe portal and automatic verification wraps up within 90 seconds. We pull the ID number, expiry, country of citizenship, and a trust score, then delete the high-resolution image right away—it never reaches storage. The original file stays in an temporary memory and vanishes after handling. A reduced, marked preview is created for compliance purposes and stored only for the identity lifecycle. That small image lives in a write-once storage with rigorous controls and is never shown to customer support. Collected information are encrypted and saved for the five-year plus two-year hash timeframe. All operations runs on servers in the UK with ISO 27001, and every small image access is logged permanently.

Biometric Information Details

Live detection checks collect a brief video feed completely in memory. Images are analysed and removed within milliseconds of time. Only a numerical vector of face features survives. This data set has no image data and cannot be reverse-engineered into a face. It remains for the entire identity verification process and is irreversibly removed upon closure of account or after 5 years. The numerical representation sits in a dedicated HSM with auto-expiry and is never exported. Authentication checks happen inside the HSM’s protected enclave without exposing the raw vector. The vector is associated with a pseudonym separated from marketing data, which makes re-identifying highly challenging. Even IT admins cannot see or rebuild facial attributes from the saved data.

Session Gameplay and Behavioral Analytics Data

All spins on Wanted Dead Or a Wild logs reel positions, RNG seed, and net outcome with microsecond precision. We store these raw logs for twenty-four months, then condense them into an anonymous statistical digest utilized 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 stay for 12 months before merging into a global model. RNG seed audit trails receive 36 months. Error diagnostics get 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 anonymized aggregation
• Session behavioural profiles: 24 months from last session, then removed
• RNG seed audit trails: 36 months to comply with technical standards
• Feature trigger heatmaps: 12 months, then merged into global model
• Error and crash diagnostic logs: 90 days, then removed

Marketing Approval and Correspondence Records

We store your consent log—timestamped, IP-stamped, and method-captured—for the entirety of our partnership plus six years after withdrawal, to comply with PECR requirements. Send logs for electronic messages, push alerts, and SMS are kept for only thirteen months. Withdrawing consent instantly blocks communications while retaining historical proof. A segmented database guarantees suppression without latency, and consent logs are held in a distinct compliance archive. Delivery logs hold metadata only—topic, time, status—not full message text. The six-year post-withdrawal timeframe matches the statute of limitations for regulatory probes. Quarterly audits check no expired consents initiate mailings. We never tailor offers with gameplay or financial data beyond explicit consents.

Controlled Gambling and Player Ban Registers

Betting limits, time checks, and timeout settings are kept for your account’s entire duration and never purged while it stays active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a specialized exclusion register kept indefinitely under UKGC licence requirements. The register is coded separately, queried only at login or registration, and never used for analytics. Access is restricted to qualified compliance staff, and all queries are recorded for three years. The register stores only identity blocks—no monetary or gameplay records. We review it annually to correct errors and remove deceased individuals. Apart from that, it remains indefinite. This retention is obligatory and free from deletion requests.

Session Awareness and Gaming Duration Enforcement

Reality check timers use short-lived session counters that reset every 24 hours, starting anew 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. Altering the interval mid-session applies the new value right away for the next reminder. These settings are purged only upon validated account deletion. Session timer data sits in a specific, 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 analyze or market based on these settings.

Access Request and Erasure Workflows

When a subject access request arrives, we produce a organized JSON/CSV export of all non-purged data within one month, extendable by two months for complex cases. The export includes 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 scheduled 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 maintained as auditable proof for as long as the longest surviving data category. All requests are documented immutably for five years.

Technology Framework and Data Location

All data resides 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 updates every six hours. Backups are encrypted client-side and follow identical retention rules. We apply least privilege with hardware MFA for administrators, capturing 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 operate 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 kept internal in plaintext. Rotated keys are stored 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 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 guarantee forensic decryption works when needed. No plaintext key material ever leaves the HSM boundary.

Policy Review and Breach Notification 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 communicated 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, report with the ICO, and post 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 simulate misconfigurations and ransomware to test our response.

Policy Versioning and Revision History

We preserve 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 conveyed 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 demonstrates our commitment to accountable data governance.