Information Retention Policy for Wanted Dead Or a Wild Slot Game in UK

Playing Wanted Dead Or a Wild Slot game means submitting personal data wanteddeadorwild.uk. This document details exactly how long we keep it, why, 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 own retention clock. Identity records stick around for five years after account closure. Financial logs are stored 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 secured. Independent auditors verify our automated deletion routines, and any schedule slip triggers a full incident response. A version-controlled policy log tracks every edit, and we offer you 30 days‘ notice before material changes become effective. Subject access and deletion requests are processed within statutory deadlines.

Payment Transaction and Billing Records

Deposit, withdrawal, and wager records are maintained for seven years from the transaction date, per HMRC and FCA rules. We seldom store full PANs or CVVs. We capture only the BIN, last four digits, and a tokenised reference. Chargeback disputes halt the contested record until final settlement, after which the seven-year clock restarts. 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 active and are deleted within thirty days of closing. Aggregated, anonymised totals persist for financial reporting without any personal details. All financial data is encrypted and isolated from marketing systems.

Tokenized Payment Instruments and Processor References

Payment gateways create vaulted tokens that map your card to a non-sensitive identifier. We hold them for the account lifetime plus a thirty-day grace interval, then send deletion commands to the processor and clear our own reference. 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 raise incidents if deletion does not work. Tokens are bound to our merchant code and cannot be used elsewhere. Weekly reconciliation confirms correctness, and tokens tied to lost or stolen cards are revoked immediately. All token operations are recorded and auditable. Aggregate reports never reveal individual transaction hashes.

Access Request and Erasure Workflows

When a subject access request arrives, we compile a formatted JSON/CSV export of all non-purged data within one month, expandable 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 queued erasure of all personal data not subject to legal hold. We produce a confirmation report outlining 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 recorded immutably for five years.

Technology Framework and Data Location

All data is stored in UK-based ISO 27001 Tier III+ data centres, not copied outside the UK. A hot disaster recovery site in a separate UK zone synchronizes every six hours. Backups are encrypted client-side and maintain identical retention rules. We implement 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 generates a Severity 1 incident, notified to our DPO within four hours. We also operate an air-gapped backup rotated weekly, subject to the same deletion policies.

Management of Encryption Keys

Master keys rotate every 90 days automatically inside an HSM. New keys are kept internal 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 removed inside the HSM, making any backups unrecoverable. We link 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 ensure forensic decryption works when needed. No plaintext key material ever exits the HSM boundary.

Session Gameplay and Analytics of Behavior Data

Every spin on Wanted Dead Or a Wild tracks reel positions, RNG seed, and net outcome with microsecond precision. We store these raw logs for twenty-four months, then compress 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 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 anonymised aggregation
• Session behavioural profiles: 24 months from last session, then removed
• RNG seed audit trails: 36 months to satisfy technical standards
• Feature trigger heatmaps: 12 months, then integrated into global model
• Error and crash diagnostic logs: 90 days, then cycled out

Essential 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—coexist with 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 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 commences from the last activity or transaction date, spelled out below. We revisit definitions every six months to stay aligned with regulatory guidance.

Responsible Gambling and Self-Exclusion Registers

Betting limits, reality checks, and timeout settings are stored for your account’s lifetime and never deleted while it stays active. If you choose to ban yourself, your hashed identity and device fingerprints enter a specific exclusion register maintained indefinitely under UKGC licence requirements. The register is encrypted separately, checked only at login or registration, and never used for analytics. Access is limited to trained compliance staff, and all searches are recorded for three years. The register stores only identity blocks—no monetary or gameplay records. We check it annually to correct errors and remove deceased individuals. Otherwise, it stays permanent. This retention is required and excluded from deletion requests.

Reality Check and Session Limit Enforcement

Reality check clocks use transient 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 automatically reactivates when you come back, even after a long break. Altering the interval mid-session introduces the new value right away for the next reminder. These settings are deleted 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 precision. All timer configurations are checkable through the same three-year access log standard. We do not categorize or market based on these settings.

Marketing Consent and Correspondence Records

We maintain your consent log—time-stamped, IP-stamped, and method-recorded—for the duration of our relationship plus six years after revocation, to comply with PECR rules. Delivery logs for e-mails, push messages, and SMS are retained for only thirteen months. Revoking consent immediately suppresses communications while retaining historical proof. A divided database guarantees suppression without lag, and consent logs are stored in a separate compliance archive. Send logs contain metadata only—subject, time stamp, status—not full message text. The six-year post-withdrawal timeframe mirrors the statute of limitations for regulatory probes. Quarterly audits verify no expired consents activate mailings. We never customise offers with gameplay or financial data beyond explicit consents.

Account Registration and Verification of Identity Data

Main identity data—scans of government IDs, proof of address, biometric selfie verifications—are kept for a five-year period after your last activity or account termination, whichever is later. This includes contractual limitation periods and AML obligations. We obtain only the necessary details: ID number, expiration date, nationality. The high-resolution image gets destroyed upon extraction. Once the five-year period pass, all original data is erased, but a encrypted hash of the verification outcome persists for two more years inside an logging system. Identity data sits encrypted at rest with AES-256-GCM, stored away from analytics, and every data access is recorded for three years. Optional fields like place of birth are discarded at verification time to minimize the data footprint. Yearly audits ensure precision and automatically remove expired data.

File Upload and Biometric Processing

Provide an ID through our safe portal and automated checking wraps up within a minute and a half. We extract the document number, expiry, nationality, and a trust score, then delete the full-resolution image immediately—it never touches disk. The original file stays in an memory buffer and disappears after analysis. A reduced, marked preview is generated for compliance purposes and retained only for the identity lifecycle. That small image lives in a write-once vault with strict controls and is never shown to support staff. Retrieved data are secured and saved for the five-year-plus-two hash window. All operations runs on ISO 27001 certified UK servers, and every thumbnail access is logged permanently.

Biometric Information Details

Live detection checks capture a short video stream entirely in memory. Video frames are processed and removed within milliseconds. Only a mathematical vector of facial landmarks persists. This vector has no image data and cannot be reconstructed into a picture. It is kept for the entire identity verification process and is permanently deleted upon closure of account or after five years. The data set sits in a dedicated HSM with auto-expiry and is never transferred. Login verifications happen inside the HSM’s protected enclave without disclosing the unprocessed data. The numerical representation is associated with a pseudonymous identifier disconnected from marketing data, which makes re-identification very hard. Even system admins cannot view or rebuild facial attributes from the saved data.

Policy Review and Breach Notification 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 displayed 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 issue a transparency notice. Third-party processor breaches must follow the same protocol. We maintain a breach notification log audited quarterly. Post-incident reviews adjust controls as needed. Biannual tabletop exercises model misconfigurations and ransomware to test our response.

Document Versioning and Change Log

We keep 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 confirm 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 shows our commitment to accountable data governance.