Playing Wanted Dead Or a Wild Slot means handing over personal data wanteddeadorwild.uk. This document sets forth exactly how long we retain it, the reasons, and what technical protections support 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 specific retention clock. Identity records are kept for five years after account closure. Financial logs are stored for seven, matching HMRC requirements. Gameplay data gets 24 months before anonymisation takes effect. Full card numbers never enter our systems—only tokenised aliases—and every byte is secured. Independent auditors check our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log records every edit, and we offer you 30 days’ notice before material changes take effect. Subject access and deletion requests are handled within statutory deadlines.

Consent for Marketing and Message Logs

We keep your consent record—timestamped, IP-stamped, and with capture method—for the duration of our relationship plus six years after cancellation, to comply with PECR obligations. Dispatch records for e-mails, push messages, and SMS are kept for only thirteen months. Cancelling consent right away suppresses communications while preserving historical proof. A segmented database provides suppression without delay, and consent logs are held in a dedicated compliance archive. Delivery logs hold metadata only—subject, timestamp, condition—not full message text. The six-year post-withdrawal window mirrors the statute of limitations for regulatory investigations. Quarterly audits check no expired consents trigger mailings. We never customise offers with gameplay or financial data beyond explicit authorisations.

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

Gaming Session and Behavioural 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 condense them into an anonymous statistical digest utilized 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 have 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 removed
• RNG seed audit trails: 36 months to meet technical standards
• Feature trigger heatmaps: 12 months, then merged into global model
• Error and crash diagnostic logs: 90 days, then rotated out

Financial Transaction and Payment Records

Deposit, withdrawal, and wager records are retained 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 alias. Chargeback disputes freeze the contested record until final settlement, after which the seven-year clock continues. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs verified by auditors. Tokenised card references remain valid only while your account is open and are wiped within thirty days of termination. Aggregated, anonymised totals persist for financial reporting without any personal identifiers. All financial data is coded and isolated from marketing systems.

Tokenized Payment Instruments and Processor References

Payment gateways generate vaulted tokens that link your card to a non-sensitive reference. We keep them for the account lifetime plus a thirty-day grace interval, then send deletion commands to the processor and erase our own mapping. The only trace left behind is an anonymised transaction hash used in aggregate summaries, themselves removed after seven years. No usable credentials ever exist on our systems. We monitor token revocation daily and trigger incidents if deletion fails. Tokens are bound to our merchant code and cannot be used elsewhere. Weekly reconciliation verifies authenticity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are logged and checked. Aggregate reports never disclose individual transaction hashes.

Technology Framework and Data Storage

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 syncs every six hours. Backups are encrypted client-side and follow identical retention rules. We enforce least privilege with hardware MFA for administrators, logging their sessions in an immutable three-year audit trail. Multi-factor authentication combines a hardware token and biometric check. Penetration tests are conducted quarterly, and an independent auditor validates automated purge schedules. Any deviation raises a Severity 1 incident, notified to our DPO within four hours. We also keep an air-gapped backup rotated weekly, subject to 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 stored 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, do not 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 confirm forensic decryption works when needed. No plaintext key material ever departs the HSM boundary.

Data Subject Access Request and Deletion Workflows

When an SAR lands, we generate a formatted JSON/CSV export of all non-purged data within one month, prolongable by two months for complex cases. The export includes 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 scheduled erasure of all personal data not subject to legal hold. We generate a confirmation report detailing erased versus retained categories and their justifications. This report is retained as auditable proof for as long as the longest surviving data category. All requests are documented immutably for five years.

Responsible 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 self-exclude, your hashed identity and device fingerprints are added to a dedicated exclusion register held indefinitely under UKGC licence requirements. The register is coded separately, checked only at login or registration, and never used for analytics. Entry is limited to trained compliance staff, and all searches are tracked for three years. The register holds only identity blocks—no monetary or gameplay records. We review it annually to rectify errors and remove deceased individuals. If not, it stays everlasting. This retention is required and excluded from deletion requests.

Session Awareness and Session Limit Enforcement

Reality check clocks use transient session counters that reset every 24 hours, restarting from your first spin after midnight. Your chosen interval—say, 30 minutes—is saved persistently and routinely 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 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 auditable through the same three-year access log standard. We never profile or advertise based on these settings.

Registration Account and Identity Verification Data

Main identity data—official ID scans, proof of address, biometric selfie verifications—are retained for 5 years after your final session or closure of account, whichever occurs later. This includes statutory limitation periods and anti-money laundering duties. We retrieve only the essentials: document ID, validity, nationality. The full-resolution image gets deleted immediately after extraction. Once 5 years pass, all source data is purged, but a cryptographic hash of the verification result lives on for an additional two years inside an audit trail. Personal identity information sits encrypted in storage with AES-256-GCM, stored away from analytics, and every access is tracked for a three-year period. Non-essential fields like birth location are deleted at verification stage to reduce the data size. Yearly audits confirm accuracy and actively purge expired entries.

File Upload and Biometric Data Processing

Upload an ID through our protected portal and automated checking finishes within 90 seconds. We retrieve the document ID, validity, nationality, and a trust score, then destroy the full-resolution image immediately—it never reaches storage. The source file stays in an in-memory buffer and is removed after processing. A compacted, watermarked preview is created for auditing purposes and kept only for the identity verification period. That small image lives in a immutable vault with tight controls and is never exposed to support staff. Collected information are encoded and saved for the five-year-plus-two hash window. All handling runs on servers in the UK with ISO 27001, and every thumbnail access is recorded immutably.

Biometric Information Details

Live detection checks collect a short video stream solely in memory. Frames are processed and removed within milliseconds of time. Only a numerical vector of facial points persists. This data set contains no image data and cannot be reconstructed into a picture. It is kept for the entire identity verification process and is irreversibly removed upon account termination or after five years. The data set sits in a dedicated HSM with self-expiry and is never exported. Login comparisons happen inside the HSM’s secure enclave without revealing the raw vector. The vector is associated with a anonymous identifier disconnected from marketing profiles, which makes re-identifying very hard. Even system administrators are unable to view or rebuild facial attributes from the kept numerical representation.

Policy Review and Data Breach Protocols

We review this policy every six months or upon material change to the game or regulation. Reviews are minuted with DPO, CISO, and legal counsel. A public summary is posted 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 notify affected individuals within 72 hours if high risk, submit 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 model misconfigurations and ransomware to test our response.

Document Versioning and Change Log

We maintain 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 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 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.