Playing wanteddeadorawildslot game means providing personal data. This document details exactly how long we retain it, the reasons, and what technical protections sit behind each category—all based on 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 unique retention clock. Identity records are retained for five years after account closure. Financial logs stay for seven, meeting 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 protected. Independent auditors verify our automated deletion routines, and any schedule slip activates a full incident response. A version-controlled policy log tracks every edit, and we give you 30 days’ notice before material changes become effective. Subject access and deletion requests are handled within statutory deadlines.

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 re-identify 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 span live databases, archives, and backups without exception. Each window commences from the last activity or transaction date, spelled out below. We revisit definitions every six months to stay aligned with regulatory guidance.

Access Request and Erasure Workflows

Upon receiving an SAR, we compile a structured JSON/CSV export of all non-purged data within one month, prolongable by two months for complex cases. The export covers 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 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 logged immutably for five years.

Gameplay Session and Behavioral Analytics Data

Each spin on Wanted Dead Or a Wild logs 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 receive 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 anonymised 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 merged into global model
• Error and crash diagnostic logs: 90 days, then cycled out

Controlled Gambling and Voluntary Exclusion Registers

Deposit limits, session reminders, and timeout settings are stored for your account’s entire duration and never deleted while it remains active. If you choose to ban yourself, your hashed identity and device fingerprints are added to a specific exclusion register held without time limit under UKGC licence requirements. The register is coded separately, queried only at login or registration, and never employed for analytics. Entry is confined to qualified compliance staff, and all lookups are tracked for three years. The register contains only identity blocks—no financial or gameplay records. We examine it annually to correct errors and remove deceased individuals. Apart from that, it remains permanent. This retention is mandatory and excluded from deletion requests.

Reality Check and Play Time Restriction Enforcement

Reality check timers use temporary session counters that clear every 24 hours, starting anew from your first spin after midnight. Your preferred interval—say, 30 minutes—is kept persistently and automatically reactivates when you visit again, even after a long break. Modifying the interval mid-session sets the new value right away for the next reminder. These settings are deleted only upon verified account deletion. Session timer data lies in a specialized, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for correctness. All timer configurations are auditable through the same three-year access log standard. We never categorize or advertise based on these settings.

Consent for Marketing and Communication Logs

We store your consent record—time-stamped, with IP address, and method-captured—for the duration of our partnership plus six years after withdrawal, to satisfy PECR obligations. Delivery logs for e-mails, push notifications, and SMS are held for only thirteen months. Withdrawing consent right away suppresses communications while keeping historical proof. A partitioned database ensures suppression without latency, and consent logs are stored in a dedicated compliance archive. Send logs contain metadata only—subject, time stamp, condition—not full message text. The six-year post-withdrawal period reflects the statute of limitations for regulatory inquiries. Quarterly audits verify no expired consents trigger mailings. We never customise offers with gameplay or financial data beyond explicit permissions.

Monetary Transaction and Payment Records

Deposit, withdrawal, and wager logs are maintained for seven years from the transaction date, per HMRC and FCA rules. We do not store full PANs or CVVs. We capture 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 resumes. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs checked by auditors. Tokenised card references remain valid only while your account is active and are erased within thirty days of closure. Combined, anonymised totals persist for financial reporting without any personal information. All financial data is coded and separated from marketing systems.

Secured Payment Instruments and Processor References

Payment gateways generate vaulted tokens that map your card to a non-sensitive identifier. We keep them for the account lifetime plus a thirty-day grace interval, then send deletion commands to the processor and erase our own link. The only remnant left behind is an anonymised transaction hash used in aggregate statements, themselves removed after seven years. No usable credentials ever sit on our systems. We monitor token revocation daily and initiate incidents if deletion fails. Tokens are linked to our merchant code and cannot be used in other contexts. Weekly reconciliation confirms validity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are documented and auditable. Aggregate reports never disclose individual transaction hashes.

Registration Account and Verification of Identity Data

Main identity data—scans of government IDs, residence proof, biometric selfie matches—are kept for 5 years after your last session or closure of account, whichever is later. This encompasses statutory limitation periods and anti-money laundering duties. We obtain only the necessary details: document ID, expiration date, nationality. The full-resolution image gets destroyed right after extraction. Once 5 years pass, all original data is removed, but a cryptographic hash of the verification data lives on for another two years inside an logging system. Personal identity information sits stored encrypted with AES-256-GCM, kept separate from analytics, and every retrieval is recorded for a three-year period. Optional fields like place of birth are discarded at the time of verification to minimize the data footprint. Yearly audits ensure correctness and automatically remove outdated records.

Uploading Documents and Biometric Processing

Provide an ID through our safe portal and automated validation finishes within a minute and a half. We extract the document number, validity, country of citizenship, and a reliability score, then destroy the high-resolution image right away—it is never stored on disk. The original file stays in an in-memory buffer and disappears after processing. A compacted, stamped preview is generated for compliance purposes and retained only for the identity lifecycle. That thumbnail lives in a immutable vault with tight controls and is never shown to client support. Extracted fields are encrypted and stored for the 5-year-plus-2-year hash period. All operations runs on UK-based ISO 27001 servers, and every thumbnail access is recorded immutably.

Biometric Data Specifics

Liveness checks capture a quick video entirely in memory. Images are processed and deleted within a few milliseconds. Only a mathematical vector of facial landmarks survives. This data set contains no image data and cannot be reconstructed into a face. It is kept for the duration of identity verification and is permanently deleted upon account termination or after five years. The numerical representation sits in a hardware security module with self-expiry and is never exported. Login verifications happen inside the HSM’s secure enclave without disclosing the raw vector. The vector is associated with a pseudonymous identifier disconnected from advertising profiles, which makes reidentification extremely difficult. Even system administrators cannot view or rebuild facial features from the kept numerical representation.

Technology Framework and Data Residency

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 synchronizes every six hours. Backups are encrypted client-side and adhere to 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 integrates a hardware token and biometric check. Penetration tests run quarterly, and an independent auditor confirms 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, following the same deletion policies.

Key Lifecycle Administration

Master keys change every 90 days automatically inside an HSM. New keys are never exported 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 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 demands 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 Assessment and Data Breach Protocols

We assess 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 inform affected individuals within 72 hours if high risk, file with the ICO, and issue 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 simulate 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 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 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 shows our commitment to accountable data governance.