Data Storage Policy for Wanted Dead Or a Wild Slot in the United Kingdom

Playing Wanted Dead Or a Wild Slot game means providing personal data wanteddeadorwild.uk. This document details exactly how long we retain 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 unique retention clock. Identity records are kept for five years after account closure. Financial logs remain for seven, matching HMRC requirements. Gameplay data receives 24 months before anonymisation is applied. Full card numbers never reach our systems—only tokenised aliases—and every byte is encrypted. Independent auditors review our automated deletion routines, and any schedule slip activates 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 handled within statutory deadlines.

Gameplay Session and Behavioural Analytics Data

Each spin on Wanted Dead Or a Wild tracks 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—stay 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 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 anonymized 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 combined into global model
• Error and crash diagnostic logs: 90 days, then rotated out

Essential Definitions and Scope of Personal Data

We adopt a comprehensive approach 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 includes session length, bet sizing, spin velocity, and how often feature triggers fire. Even pseudonymised logs can identify again 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 extend across live databases, archives, and backups without exception. Each window starts ticking from the last activity or transaction date, spelled out below. We revisit definitions every six months to remain compliant with regulatory guidance.

Consent for Marketing and Message Logs

We keep your consent record—with time stamp, IP-stamped, and method-captured—for the entirety of our relationship plus six years after cancellation, to satisfy PECR obligations. Dispatch records for e-mails, push messages, and SMS are kept for only thirteen months. Cancelling consent instantly blocks communications while keeping historical proof. A divided database guarantees suppression without latency, and consent logs are stored in a distinct compliance archive. Send logs hold metadata only—subject, time, condition—not full message text. The six-year post-withdrawal window reflects the statute of limitations for regulatory probes. Quarterly audits check no expired consents activate mailings. We never personalise offers with gameplay or financial data beyond explicit permissions.

Safe Gambling and Voluntary Exclusion Registers

Deposit limits, reality checks, and timeout settings are saved for your account’s entire duration and never purged while it stays active. If you self-exclude, your hashed identity and device fingerprints are placed into a dedicated exclusion register maintained indefinitely under UKGC licence requirements. The register is encrypted separately, queried only at login or registration, and never used for analytics. Access is limited to educated compliance staff, and all queries are logged for three years. The register holds only identity blocks—no monetary or gameplay records. We examine it annually to rectify errors and remove deceased individuals. If not, it is kept everlasting. This retention is required and excluded from deletion requests.

Reality Check and Play Time Restriction Enforcement

Reality check clocks use short-lived session counters that restart every 24 hours, beginning again from your first spin after midnight. Your chosen interval—say, 30 minutes—is stored persistently and automatically reactivates when you come back, even after a long break. Changing the interval mid-session sets the new value right away for the next reminder. These settings are purged only upon validated 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 accuracy. All timer configurations are auditable through the same three-year access log standard. We do not analyze or advertise based on these settings.

Access Request and Erasure Workflows

When an SAR lands, we produce a organized JSON/CSV export of all non-purged data within one month, prolongable by two months for complex cases. The export spans live databases, encrypted archives, and processor tokens, delivered 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 generate a confirmation report detailing 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.

Technical Infrastructure and Data Location

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 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 uses a hardware token and biometric check. Penetration tests run quarterly, and an independent auditor confirms automated purge schedules. Any deviation triggers a Severity 1 incident, alerted to our DPO within four hours. We also operate an air-gapped backup rotated weekly, following the same deletion policies.

Management of Encryption Keys

Master keys rotate 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 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 ensure forensic decryption works when needed. No plaintext key material ever exits the HSM boundary.

Account Registration and ID Verification Data

Main identity data—scans of government IDs, proof of address, selfie biometric matches—are retained for a five-year period after your last activity or closure of account, whichever occurs later. This covers contractual limitation periods and anti-money laundering responsibilities. We extract only the essentials: document number, validity, nationality. The original image gets shredded upon extraction. Once five years pass, all original data is erased, but a hash of the verification outcome remains for an additional two years inside an audit trail. Identification data sits encrypted at rest with AES-256-GCM, isolated from analytics, and every data access is tracked for a three-year period. Unnecessary fields like birth location are discarded at verification time to reduce the data volume. Annual reviews ensure correctness and automatically remove outdated records.

File Upload and Biometric Data Processing

Provide an ID through our secure portal and automatic verification completes within 90 seconds. We pull the document number, validity, nationality, and a confidence score, then destroy the full-resolution image immediately—it never touches disk. The initial file stays in an in-memory buffer and disappears after processing. A compressed, marked preview is produced for audit purposes and retained only for the identity verification period. That preview lives in a immutable vault with tight controls and is never shown to client support. Retrieved data are encoded and stored for the 5-year-plus-2-year hash period. All operations runs on servers in the UK with ISO 27001, and every thumbnail access is logged permanently.

Biometric Information Details

Live detection checks record a brief video feed completely in memory. Video frames are analyzed and discarded within milliseconds of time. Only a mathematical vector of facial points persists. This vector contains no image data and cannot be turned back into a face. It is kept for the entire identity verification process and is purged irrevocably upon account closure or after a five-year period. The numerical representation sits in a specialized HSM with auto-expiry and is never transferred. Login comparisons happen inside the HSM’s safe environment without disclosing the original vector. The data set is associated with a anonymous identifier separated from marketing profiles, which makes re-identification extremely difficult. Even system admins cannot see or recreate facial features from the kept numerical representation.

Payment Transaction and Payment Records

Deposit, withdrawal, and wager logs are kept 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 identifier. Chargeback disputes suspend the contested record until final resolution, 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 are valid only while your account is open and are deleted within thirty days of closing. Summarised, anonymised totals remain for financial reporting without any personal information. All financial data is secured and separated from marketing systems.

Secured Payment Instruments and Processor References

Payment gateways produce vaulted tokens that associate your card to a non-sensitive alias. We keep them for the account lifetime plus a thirty-day grace window, then send deletion commands to the processor and clear our own reference. The only evidence 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 initiate incidents if deletion is unsuccessful. Tokens are bound 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 logged and verifiable. Aggregate reports never disclose individual transaction hashes.

Policy Review and Incident Reporting 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 displayed 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, submit with the ICO, and publish a transparency notice. Third-party processor breaches must follow the same protocol. We maintain a breach notification log audited quarterly. Post-incident reviews update controls as needed. Biannual tabletop exercises simulate misconfigurations and ransomware to test our response.

Policy Version Control and Change Log

We preserve a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log details 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 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.