Playing Wanted Dead Or a Wild Slot means submitting personal data https://wanteddeadorwild.uk/. This document sets forth exactly how long we store 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 are stored for seven, matching HMRC requirements. Gameplay data receives 24 months before anonymisation takes effect. Full card numbers never enter our systems—only tokenised aliases—and every byte is protected. 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 provide you 30 days’ notice before material changes take effect. Subject access and deletion requests are managed within statutory deadlines.

Technology Framework and Data Storage

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 implement least privilege with hardware MFA for administrators, recording their sessions in an immutable three-year audit trail. Multi-factor authentication uses a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor verifies automated purge schedules. Any deviation raises 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 deleted 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 guarantee forensic decryption works when needed. No plaintext key material ever exits the HSM boundary.

Gaming Session and Analytics of Behavior Data

Every spin on Wanted Dead Or a Wild records reel positions, RNG seed, and net outcome with microsecond precision. We store 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—stay for the same 24-month window and are then deleted. Feature trigger heatmaps stay for 12 months before merging into a global model. RNG seed audit trails receive 36 months. Error diagnostics receive 90 days. No individual gameplay data feeds 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 comply with technical standards
• Feature trigger heatmaps: 12 months, then merged into global model
• Error and crash diagnostic logs: 90 days, then cycled out

Essential 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 link back to 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 span live databases, archives, and backups without exception. Each window begins counting from the last activity or transaction date, spelled out below. We review definitions every six months to remain compliant with regulatory guidance.

Consent for Marketing and Message Logs

We keep your consent document—time-stamped, IP-stamped, and method-captured—for the entirety of our relationship plus six years after cancellation, to meet PECR requirements. Delivery logs for electronic messages, push notifications, and SMS are kept for only thirteen months. Revoking consent right away halts communications while keeping historical proof. A segmented database provides suppression without delay, and consent logs are stored in a dedicated compliance archive. Dispatch records hold metadata only—subject, timestamp, condition—not full message text. The six-year post-withdrawal period mirrors the statute of limitations for regulatory probes. Quarterly audits confirm no expired consents initiate mailings. We never personalise offers with gameplay or financial data beyond explicit consents.

Payment Transaction and Settlement Records

Deposit, withdrawal, and wager histories are maintained for seven years from the transaction date, per HMRC and FCA rules. We do not store full PANs or CVVs. We collect only the BIN, last four digits, and a tokenised alias. Chargeback disputes halt the contested record until final resolution, after which the seven-year clock continues. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs audited by auditors. Tokenised card references are valid only while your account is open and are wiped within thirty days of termination. Aggregated, anonymised totals persist for financial reporting without any personal identifiers. All financial data is encrypted and separated from marketing systems.

Tokenised Payment Instruments and Processor References

Payment gateways create vaulted tokens that map your card to a non-sensitive alias. We hold them for the account lifetime plus a thirty-day grace interval, then issue deletion commands to the processor and clear our own reference. The only evidence left behind is an anonymised transaction hash used in aggregate reports, themselves removed after seven years. No usable credentials ever exist on our systems. We track token revocation daily and raise incidents if deletion fails. Tokens are tied to our merchant code and cannot be used elsewhere. Weekly reconciliation confirms authenticity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are documented and verifiable. Aggregate reports never disclose individual transaction hashes.

SAR and Deletion Processes

When a subject access request arrives, we compile a formatted JSON/CSV export of all non-purged data within one month, prolongable 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 cascade: immediate account suppression and token revocation, then scheduled 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 retained as auditable proof for as long as the longest surviving data category. All requests are recorded immutably for five years.

Responsible Gambling and Player Ban Registers

Deposit limits, time checks, and timeout settings are kept for your account’s whole period and never removed while it is active. If you self-exclude, your hashed identity and device fingerprints are added to a dedicated exclusion register kept indefinitely under UKGC licence requirements. The register is coded separately, accessed only at login or registration, and never utilized for analytics. Permission is limited to educated compliance staff, and all searches are recorded for three years. The register contains only identity blocks—no monetary or gameplay records. We examine it annually to fix errors and remove deceased individuals. Otherwise, it stays everlasting. This retention is obligatory and exempt from deletion requests.

Session Awareness and Session Limit Enforcement

Reality check counters use temporary session counters that reset every 24 hours, beginning again from your first spin after midnight. Your selected interval—say, 30 minutes—is saved persistently and routinely reactivates when you visit again, even after a long break. Changing the interval mid-session applies the new value right away for the next reminder. These settings are deleted only upon validated account deletion. Session timer data resides 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 at no time analyze or advertise based on these settings.

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

Document Versioning and Change Log

We maintain 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 retrieve the full change log through a link in our privacy centre at any time. This transparent approach shows our commitment to accountable data governance.

Registration Account and Verification of Identity Data

Main identity data—scans of government IDs, residence proof, selfie biometric matches—are kept for a five-year period after your last activity or account termination, whichever occurs later. This includes contractual limitation periods and anti-money laundering duties. We obtain only the key information: ID number, expiration date, nationality. The original image gets destroyed upon extraction. Once five years pass, all source data is removed, but a cryptographic hash of the verification result remains for an additional two years inside an logging system. Identification data sits stored encrypted with AES-256-GCM, isolated from analytics, and every data access is tracked for three years. Optional fields like birth location are deleted at verification time to reduce the data volume. Yearly audits ensure accuracy and automatically remove expired data.

Document Upload and Biometric Handling

Submit an ID through our secure portal and automated checking finishes within ninety seconds. We retrieve the ID number, expiry, country of citizenship, and a trust score, then destroy the full-resolution image right away—it is never stored on disk. The original file stays in an temporary memory and vanishes after analysis. A reduced, stamped preview is produced for compliance purposes and kept only for the ID lifecycle. That thumbnail lives in a immutable vault with tight controls and is never shown to client support. Extracted fields are encrypted and stored for the five-year plus two-year hash timeframe. All operations runs on UK-based ISO 27001 servers, and every preview retrieval is stored unchangeably.

Biometric Information Details

Liveness checks capture a short video stream completely in memory. Frames are analyzed and removed within milliseconds. Only a data vector of facial points persists. This numerical representation has no image data and cannot be reverse-engineered into a face. It stays for the time of identity verification and is irreversibly removed upon closure of account or after five years. The data set sits in a specialized HSM with auto-expiry and is never exported. Authentication checks happen inside the HSM’s safe environment without disclosing the original vector. The vector is associated with a pseudonymous identifier unlinked from marketing profiles, which makes re-identifying very hard. Even IT admins cannot view or reconstruct face characteristics from the kept numerical representation.