Playing Wanted Dead Or a Wild Slot game means handing over personal data https://wanteddeadorwild.uk/. This document lays out exactly how long we retain it, why, and what technical protections support 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 unique retention clock. Identity records are kept for five years after account closure. Financial logs stay for seven, meeting HMRC requirements. Gameplay data undergoes 24 months before anonymisation kicks in. Full card numbers never reach our systems—only tokenised aliases—and every byte is secured. 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 take effect. Subject access and deletion requests are processed within statutory deadlines.

Payment Transaction and Billing Records

Deposit, withdrawal, and wager logs are maintained for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised reference. Chargeback disputes halt the contested record until final resolution, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs checked by auditors. Tokenised card references remain valid only while your account is live and are erased within thirty days of closing. Summarised, anonymised totals remain for financial reporting without any personal identifiers. All financial data is encrypted and separated from marketing systems.

Tokenized Payment Instruments and Processor References

Payment gateways generate vaulted tokens that link your card to a non-sensitive identifier. We keep them for the account lifetime plus a thirty-day grace window, then send deletion commands to the processor and erase our own reference. The only remnant left behind is an anonymised transaction hash used in aggregate summaries, themselves purged after seven years. No usable credentials ever exist on our systems. We track token revocation daily and trigger incidents if deletion is unsuccessful. Tokens are bound to our merchant code and cannot be used other places. Weekly reconciliation confirms authenticity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are recorded and verifiable. Aggregate reports never expose individual transaction hashes.

Marketing Approval and Communication Logs

We maintain your consent document—with time stamp, IP-marked, and method-captured—for the life of our association plus six years after revocation, to satisfy PECR requirements. Dispatch records for electronic messages, push messages, and SMS are held for only thirteen months. Cancelling consent instantly blocks communications while preserving historical proof. A partitioned database guarantees suppression without delay, and consent logs are kept in a distinct compliance archive. Dispatch records include metadata only—topic, time, condition—not full message body. The six-year post-withdrawal period mirrors the statute of limitations for regulatory probes. Quarterly audits check no expired consents initiate mailings. We never personalise offers with gameplay or financial data beyond explicit authorisations.

Infrastructure Setup 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 maintain identical retention rules. We enforce 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 validates automated purge schedules. Any deviation triggers a Severity 1 incident, notified to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, following the same deletion policies.

Management of Encryption Keys

Master keys are renewed 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 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 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 departs the HSM boundary.

Controlled Gambling and Self-Exclusion Registers

Deposit limits, time checks, and timeout settings are saved 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 specific exclusion register maintained permanently under UKGC licence requirements. The register is coded separately, queried only at login or registration, and never used for analytics. Entry is limited to trained compliance staff, and all lookups 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. If not, it is kept permanent. This retention is required and free from deletion requests.

Reality Check and Gaming Duration Enforcement

Reality check clocks use temporary session counters that restart every 24 hours, beginning again from your first spin after midnight. Your preferred interval—say, 30 minutes—is kept persistently and instantly reactivates when you come back, 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 verified 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 verifiable through the same three-year access log standard. We at no time categorize or market based on these settings.

Fundamental Definitions and Range of Personal Data

We take a broad view 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 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 begins counting from the last activity or transaction date, spelled out below. We revisit definitions every six months to stay aligned with regulatory guidance.

Account Registration and Verification of Identity Data

Main identity data—official ID scans, residence proof, selfie biometric matches—are held for a five-year period after your last session or account termination, whichever occurs later. This encompasses statutory limitation periods and anti-money laundering duties. We extract only the key information: document ID, validity, country of citizenship. The full-resolution image gets shredded upon extraction. Once five years pass, all original data is removed, but a cryptographic hash of the verification result remains for two more years inside an logging system. Personal identity information sits stored encrypted with AES-256-GCM, isolated from analytics, and every retrieval is logged for a three-year period. Unnecessary fields like birthplace are deleted at verification time to minimize the data volume. Yearly audits verify correctness and automatically remove expired entries.

Document Upload and Biometric Processing

Submit an ID through our protected portal and automated validation finishes within a minute and a half. We extract the document ID, validity, country of citizenship, and a reliability score, then destroy the original image right away—it never reaches storage. The initial file stays in an temporary memory and disappears after processing. A compressed, stamped small image is created for audit purposes and stored only for the ID lifecycle. That small image lives in a write-once storage with rigorous controls and is never shown to support staff. Collected information are encrypted and kept for the five-year plus two-year hash timeframe. All handling runs on servers in the UK with ISO 27001, and every preview retrieval is stored unchangeably.

Biometric Data Specifics

Liveness checks capture a brief video feed entirely in memory. Video frames are processed and deleted within milliseconds of time. Only a mathematical vector of face features survives. This numerical representation has no image data and cannot be turned back into a facial image. It stays for the entire identity verification process and is permanently deleted upon closure of account or after a five-year period. The vector sits in a dedicated HSM with self-expiry and is never exported. Login verifications happen inside the HSM’s safe environment without exposing the raw vector. The vector is linked to a anonymous identifier unlinked from marketing data, which makes reidentification extremely difficult. Even system admins are unable to view or reconstruct facial features from the kept numerical representation.

Data Subject Access Request and Deletion Workflows

When an SAR lands, we produce a formatted JSON/CSV export of all non-purged data within one month, expandable 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 cascade: immediate account suppression and token revocation, then queued erasure of all personal data not subject to legal hold. We produce 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 recorded immutably for five years.

Session Gameplay and Behavioural Analytics 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 compact 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 get 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 meet technical standards
• Feature trigger heatmaps: 12 months, then combined into global model
• Error and crash diagnostic logs: 90 days, then rotated out

Policy Assessment and Data Breach Protocols

We assess this policy every six months or upon material change to the game or regulation. Reviews are documented with DPO, CISO, and legal counsel. A public summary is published 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 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 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 check 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 reflects our commitment to accountable data governance.