Playing Wanted Dead Or a Wild Slot means handing over personal data. This document lays out exactly how long we store it, the reasons, and what technical protections underpin each category—all built around UK GDPR, the Data Protection Act 2018, and PCI DSS. We process identity documents, financial transactions, gameplay telemetry, responsible gambling markers, and marketing consents, each with its own retention clock. Identity records are retained for five years after account closure. Financial logs stay for seven, matching HMRC requirements. Gameplay data undergoes 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 activates 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 processed within statutory deadlines.

Fundamental Definitions and Range 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 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 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 begins counting from the last activity or transaction date, spelled out below. We reassess definitions every six months to stay aligned with regulatory guidance.

Monetary Transaction and Settlement Records

Funding, withdrawal, and wager histories are maintained 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 alias. Chargeback disputes halt 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 checked by auditors. Tokenised card references stay valid only while your account is active and are erased within thirty days of termination. Combined, anonymised totals endure for financial reporting without any personal information. All financial data is encrypted and quarantined from marketing systems.

Tokenised Payment Instruments and Processor References

Payment gateways generate vaulted tokens that map your card to a non-sensitive identifier. We store them for the account lifetime plus a thirty-day grace interval, then transmit deletion commands to the processor and clear our own link. The only evidence left behind is an anonymised transaction hash used in aggregate summaries, themselves removed after seven years. No usable credentials ever sit on our systems. We track token revocation daily and trigger incidents if deletion fails. Tokens are bound to our merchant code and cannot be used in other contexts. Weekly reconciliation validates correctness, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are logged and verifiable. Aggregate reports never reveal individual transaction hashes.

Responsible Gambling and Player Ban Registers

Betting limits, session reminders, and timeout settings are stored for your account’s entire duration and never removed while it remains active. If you choose to ban yourself, your hashed identity and device fingerprints are placed into a specialized exclusion register maintained permanently under UKGC licence requirements. The register is coded separately, queried only at login or registration, and never utilized for analytics. Permission is restricted to qualified compliance staff, and all searches are tracked for three years. The register holds only identity blocks—no banking or gameplay records. We check it annually to rectify errors and remove deceased individuals. If not, it remains permanent. This retention is obligatory and free from deletion requests.

Session Awareness and Session Limit Enforcement

Reality check timers use short-lived session counters that clear every 24 hours, beginning again from your first spin after midnight. Your chosen interval—say, 30 minutes—is kept persistently and instantly reactivates when you visit again, even after a long break. Modifying the interval mid-session sets the new value immediately for the next reminder. These settings are removed only upon validated account deletion. Session timer data resides in a dedicated, 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 profile or promote based on these settings.

User Account and Verification of Identity Data

Main identity data—government ID scans, proof of address, selfie biometric matches—are kept for five years after your final session or account termination, whichever comes later. This covers statutory limitation periods and anti-money laundering duties. We retrieve only the necessary details: document number, expiry, nationality. The full-resolution image gets shredded immediately after extraction. Once the five-year period pass, all original data is purged, but a encrypted hash of the verification data lives on for another two years inside an audit log. Identity data sits encrypted at rest with AES-256-GCM, stored away from analytics, and every access is logged for three years. Unnecessary fields like birthplace are removed at verification stage to minimize the data volume. Annual reviews confirm accuracy and actively purge expired entries.

File Upload and Biometric Data Processing

Provide an ID through our safe portal and automated validation finishes within a minute and a half. We retrieve the document number, Slot Wanted Dead Or A Wild Live Chat, expiration date, citizenship, and a reliability score, then destroy the high-resolution image immediately—it never touches disk. The source file stays in an in-memory buffer and vanishes after analysis. A compressed, watermarked preview is generated for compliance purposes and stored only for the ID lifecycle. That thumbnail lives in a immutable vault with rigorous controls and is never shown to customer support. Collected information are encrypted and kept for the five-year-plus-two hash window. All handling runs on servers in the UK with ISO 27001, and every small image access is logged permanently.

Biometric Information Details

Liveness checks collect a brief video feed entirely in memory. Images are analyzed and removed within a few milliseconds. Only a data vector of facial points remains. This numerical representation contains no image data and cannot be reverse-engineered into a facial image. It remains for the duration of identity verification and is permanently deleted upon account termination or after a five-year period. The numerical representation sits in a specialized HSM with auto-expiry and is never sent out. Authentication checks happen inside the HSM’s secure enclave without exposing the raw vector. The numerical representation is linked to a anonymous identifier separated from marketing data, which makes re-identifying very hard. Even system admins cannot see or reconstruct face characteristics from the kept numerical representation.

Gaming Session and Behavioural Analytics Data

Every spin on Wanted Dead Or a Wild records 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 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 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 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 erased
• RNG seed audit trails: 36 months to comply with technical standards
• Feature trigger heatmaps: 12 months, then integrated into global model
• Error and crash diagnostic logs: 90 days, then removed

Data Subject Access Request and Deletion Workflows

When a subject access request arrives, we generate a structured JSON/CSV export of all non-purged data within one month, extendable by two months for complex cases. The export spans live databases, encrypted archives, and processor tokens, provided via a one-time secure link that expires in 72 hours. For deletion, we proceed sequentially: immediate account suppression and token revocation, then batched erasure of all personal data not subject to legal hold. We generate a confirmation report specifying 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 recorded immutably for five years.

Marketing Approval and Message Logs

We store your consent document—time-stamped, with IP address, and with capture method—for the duration of our partnership plus six years after cancellation, to meet PECR obligations. Send logs for e-mails, push alerts, and SMS are retained for only thirteen months. Revoking consent right away halts communications while keeping historical proof. A partitioned database guarantees suppression without lag, and consent logs are held in a separate compliance archive. Dispatch records contain metadata only—heading, time, state—not full message body. The six-year post-withdrawal timeframe reflects the statute of limitations for regulatory probes. Quarterly audits confirm no expired consents activate mailings. We never personalise offers with gameplay or financial data beyond explicit permissions.

Infrastructure Setup and Data Residency

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 synchronizes every six hours. Backups are encrypted client-side and follow 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 uses a hardware token and biometric check. Penetration tests are conducted quarterly, and an independent auditor validates automated purge schedules. Any deviation generates a Severity 1 incident, reported to our DPO within four hours. We also keep an air-gapped backup rotated weekly, subject to the same deletion policies.

Encryption Key Lifecycle Management

Master keys change every 90 days automatically inside an HSM. New keys are never exported 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 bind 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 requires 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.

Policy Review 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 posted 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 alert 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 maintain a breach notification log audited quarterly. Post-incident reviews revise controls as needed. Biannual tabletop exercises model misconfigurations and ransomware to test our response.

Document Versioning and Update Log

We maintain 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 verify 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 reflects our commitment to accountable data governance.