Playing Wanted Dead Or a Wild Slot game means providing personal data https://wanteddeadorwild.uk/. This document lays out exactly how long we keep it, why, and what technical protections underpin each category—all built around UK GDPR, the Data Protection Act 2018, and PCI DSS. We handle 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, meeting HMRC requirements. Gameplay data undergoes 24 months before anonymisation kicks in. Full card numbers never enter our systems—only tokenised aliases—and every byte is protected. Independent auditors verify our automated deletion routines, and any schedule slip triggers 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 managed within statutory deadlines.

Core 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—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 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 extend across 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 remain compliant with regulatory guidance.

Session Gameplay and Behavioural 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—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 have 36 months. Error diagnostics have 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 aggregated 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

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 reference. 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 are valid only while your account is open and are deleted within thirty days of closure. Aggregated, anonymised totals persist 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 associate your card to a non-sensitive alias. We hold them for the account lifetime plus a thirty-day grace window, then issue deletion commands to the processor and wipe our own mapping. The only trace left behind is an anonymised transaction hash used in aggregate summaries, themselves purged after seven years. No usable credentials ever reside on our systems. We check 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 verifies correctness, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are logged and auditable. Aggregate reports never reveal individual transaction hashes.

Access Request and Erasure Workflows

When an SAR lands, we generate a formatted JSON/CSV export of all non-purged data within one month, expandable by two months for complex cases. The export covers live databases, encrypted archives, and processor tokens, delivered via a one-time secure link that expires in 72 hours. For deletion, we implement a cascade: immediate account suppression and token revocation, then batched erasure of all personal data not subject to legal hold. We generate 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 documented immutably for five years.

Registration Account and Verification of Identity Data

Core identity profiles—government ID scans, proof of address, biometric selfie verifications—are kept for 5 years after your final session or account termination, whichever occurs later. This encompasses statutory limitation periods and anti-money laundering duties. We retrieve only the key information: document number, expiration date, country of citizenship. The high-resolution image gets shredded immediately after extraction. Once five years pass, all original data is purged, but a encrypted hash of the verification result persists for another two years inside an audit log. Identification data sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every data access is logged for a three-year period. Optional fields like birth location are removed at verification time to reduce the data size. Yearly reviews ensure precision and actively purge expired data.

Document Upload and Biometric Data Processing

Upload an ID through our protected portal and automated checking wraps up within ninety seconds. We pull the document number, expiration date, citizenship, and a trust score, then shred the original image immediately—it never reaches storage. The initial file stays in an temporary memory and is removed after handling. A reduced, watermarked thumbnail is created for compliance purposes and stored only for the identity verification period. That preview lives in a immutable vault with tight controls and is never exposed to client support. Retrieved data are secured and saved for the five-year plus two-year hash timeframe. All handling runs on ISO 27001 certified UK servers, and every preview retrieval is stored unchangeably.

Biometric Information Details

Live detection checks record a quick video solely in memory. Video frames are processed and removed within milliseconds of time. Only a data vector of face features persists. This data set lacks any image data and cannot be reconstructed into a facial image. It stays for the duration of identity verification and is irreversibly removed upon account closure or after five years. The vector sits in a dedicated HSM with automatic expiration and is never sent out. Login verifications happen inside the HSM’s protected enclave without exposing the original vector. The vector is linked to a pseudonym unlinked from advertising profiles, which makes re-identifying extremely difficult. Even IT admins cannot view or recreate facial attributes from the stored vector.

Marketing Consent and Communication Logs

We store your consent record—time-stamped, IP-marked, and method-recorded—for the entirety of our relationship plus six years after revocation, to meet PECR obligations. Send logs for emails, push messages, and SMS are retained for only thirteen months. Cancelling consent immediately blocks communications while keeping historical proof. A partitioned database provides suppression without lag, and consent logs are kept in a distinct compliance archive. Dispatch records contain metadata only—subject, time, state—not full message body. The six-year post-withdrawal window matches the statute of limitations for regulatory inquiries. Quarterly audits verify no expired consents activate mailings. We never personalise offers with gameplay or financial data beyond explicit consents.

Safe Gambling and Player Ban Registers

Deposit limits, reality checks, and timeout settings are stored for your account’s whole period and never removed while it remains active. If you self-exclude, your hashed identity and device fingerprints enter a specialized exclusion register kept permanently under UKGC licence requirements. The register is secured separately, checked only at login or registration, and never employed for analytics. Permission is confined to qualified compliance staff, and all searches are tracked for three years. The register stores only identity blocks—no banking or gameplay records. We review it annually to fix errors and remove deceased individuals. If not, it stays everlasting. This retention is obligatory and excluded from deletion requests.

Session Awareness and Play Time Restriction Enforcement

Reality check counters use short-lived session counters that restart every 24 hours, starting anew from your first spin after midnight. Your chosen interval—say, 30 minutes—is kept persistently and automatically reactivates when you visit again, even after a long break. Changing the interval mid-session sets the new value immediately for the next reminder. These settings are removed only upon confirmed account deletion. Session timer data sits 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 checkable through the same three-year access log standard. We never categorize or market based on these settings.

Infrastructure Setup and Data Residency

All data sits in UK-based ISO 27001 Tier III+ data centres, not copied outside the UK. A hot disaster recovery site in a separate UK zone syncs 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 combines a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor verifies automated purge schedules. Any deviation generates 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.

Key Lifecycle Administration

Master keys rotate 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 deleted inside the HSM, making any backups unrecoverable. We link 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 ensure forensic decryption works when needed. No plaintext key material ever departs the HSM boundary.

Policy Evaluation and Incident Reporting Protocols

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

Policy Versioning and Revision History

We maintain a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log specifies 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 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 reflects our commitment to accountable data governance.