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

Playing Wanted Dead Or a Wild Slot game means submitting personal data https://wanteddeadorwild.uk/. This document sets forth exactly how long we retain it, why, and what technical protections underpin each category—all aligned with 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 unique retention clock. Identity records stick around for five years after account closure. Financial logs stay for seven, matching HMRC requirements. Gameplay data receives 24 months before anonymisation is applied. Full card numbers never enter our systems—only tokenised aliases—and every byte is secured. Independent auditors review our automated deletion routines, and any schedule slip activates 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 handled within statutory deadlines.

SAR and Deletion Processes

Upon receiving an SAR, we produce a structured 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 cascade: immediate account suppression and token revocation, then scheduled 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 maintained as auditable proof for as long as the longest surviving data category. All requests are logged immutably for five years.

Marketing Approval and Message Logs

We maintain your consent document—with time stamp, IP-stamped, and method-recorded—for the duration of our relationship plus six years after withdrawal, to meet PECR obligations. Dispatch records for electronic messages, push messages, and SMS are held for only thirteen months. Revoking consent instantly blocks communications while keeping historical proof. A segmented database guarantees suppression without delay, and consent logs are held in a separate compliance archive. Send logs contain metadata only—heading, time, status—not full message content. 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.

Technology Framework and Data Location

All data is stored 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 adhere to 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 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 keep 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 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 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 exits the HSM boundary.

Fundamental Definitions and Extent of Personal Data

We take a broad view on what counts as 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 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 span live databases, archives, and backups without exception. Each window starts ticking from the last activity or transaction date, spelled out below. We review definitions every six months to keep pace with regulatory guidance.

Registration Account and Identity Verification Data

Core identity profiles—official ID scans, residence proof, biometric selfie matches—are held for 5 years after your last activity or account termination, whichever comes later. This includes contractual limitation periods and AML obligations. We extract only the necessary details: document number, validity, nationality. The high-resolution image gets deleted upon extraction. Once five years pass, all raw data is purged, but a cryptographic hash of the verification outcome lives on for another two years inside an audit trail. Personal identity information sits stored encrypted with AES-256-GCM, stored away from analytics, and every access is recorded for three years. Unnecessary fields like place of birth are deleted at the time of verification to reduce the data size. Yearly audits verify precision and actively purge expired entries.

File Upload and Biometric Handling

Submit an ID through our secure portal and automated validation finishes within ninety seconds. We retrieve the document ID, expiry, country of citizenship, and a reliability score, then destroy the high-resolution image right away—it never reaches storage. The original file stays in an memory buffer and is removed after handling. A compressed, marked small image is generated for auditing purposes and retained only for the identity lifecycle. That small image lives in a write-once storage with rigorous controls and is never exposed 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 small image access is stored unchangeably.

Specifics of Biometric Data

Liveness checks capture a short video stream solely in memory. Video frames are analysed and deleted within milliseconds of time. Only a numerical vector of facial points remains. This numerical representation has no image data and cannot be turned back into a facial image. It is kept for the time of identity verification and is irreversibly removed upon closure of account or after a five-year period. The numerical representation sits in a dedicated HSM with automatic expiration and is never transferred. Login comparisons happen inside the HSM’s secure enclave without revealing the unprocessed data. The vector is associated with a pseudonym disconnected from advertising profiles, which makes re-identifying extremely difficult. Even system administrators cannot see or recreate face characteristics from the saved data.

Payment Transaction and Settlement Records

Funding, withdrawal, and wager histories 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 reference. Chargeback disputes freeze the contested record until final resolution, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs audited by auditors. Tokenised card references stay valid only while your account is open and are wiped within thirty days of termination. Summarised, anonymised totals endure for financial reporting without any personal identifiers. All financial data is coded and separated from marketing systems.

Secured Payment Instruments and Processor References

Payment gateways produce vaulted tokens that link your card to a non-sensitive identifier. We keep them for the account lifetime plus a thirty-day grace interval, then issue deletion commands to the processor and wipe 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 reside 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 in other contexts. Weekly reconciliation verifies correctness, and tokens tied to lost or stolen cards are revoked immediately. All token operations are documented and auditable. Aggregate reports never expose individual transaction hashes.

Controlled Gambling and Player Ban Registers

Betting limits, session reminders, and timeout settings are saved for your account’s lifetime and never removed while it remains active. If you choose to ban yourself, your hashed identity and device fingerprints enter a dedicated exclusion register held without time limit under UKGC licence requirements. The register is coded separately, checked only at login or registration, and never employed for analytics. Entry is confined to qualified compliance staff, and all lookups are logged for three years. The register holds only identity blocks—no banking or gameplay records. We check it annually to correct errors and remove deceased individuals. If not, it remains indefinite. This retention is mandatory and exempt from deletion requests.

Time Check and Gaming Duration Enforcement

Reality check timers use short-lived session counters that clear every 24 hours, starting anew from your first spin after midnight. Your preferred interval—say, 30 minutes—is stored 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 verified account deletion. Session timer data lies in a dedicated, 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 never categorize or market based on these settings.

Gameplay Session 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 receive 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 erased
• 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 cycled out

Policy Assessment and Breach Notification 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 displayed 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 notify 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 maintain a breach notification log audited quarterly. Post-incident reviews adjust controls as needed. Biannual tabletop exercises test misconfigurations and ransomware to test our response.

Policy Version Control and Revision History

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 verify the log’s accuracy. The log is a living document reflecting our evolving data practices. You can view the full change log through a link in our privacy centre at any time. This transparent approach reflects our commitment to accountable data governance.