Playing Wanted Dead Or a Wild Slot game means providing personal data https://wanteddeadorwild.uk/. This document sets forth exactly how long we keep it, the rationale, and what technical protections support 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 are retained for five years after account closure. Financial logs stay for seven, meeting HMRC requirements. Gameplay data undergoes 24 months before anonymisation is applied. Full card numbers never enter our systems—only tokenised aliases—and every byte is secured. Independent auditors check 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 take effect. Subject access and deletion requests are managed within statutory deadlines.

Essential Definitions and Scope of Personal Data

We adopt a comprehensive approach on what counts as 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 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 cover live databases, archives, and backups without exception. Each window commences from the last activity or transaction date, spelled out below. We reassess definitions every six months to stay aligned with regulatory guidance.

SAR and Deletion Processes

When a subject access request arrives, we generate a organized JSON/CSV export of all non-purged data within one month, expandable by two months for complex cases. The export includes live databases, encrypted archives, and processor tokens, sent via a one-time secure link that expires in 72 hours. For deletion, we implement a cascade: immediate account suppression and token revocation, then scheduled 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 retained as auditable proof for as long as the longest surviving data category. All requests are logged immutably for five years.

Technology Framework and Data Storage

All data resides in UK-based ISO 27001 Tier III+ data centres, never replicated 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 apply least privilege with hardware MFA for administrators, recording their sessions in an immutable three-year audit trail. Multi-factor authentication integrates a hardware token and biometric check. Penetration tests run quarterly, and an independent auditor verifies automated purge schedules. Any deviation triggers a Severity 1 incident, reported to our DPO within four hours. We also keep an air-gapped backup rotated weekly, subject to the same deletion policies.

Key Lifecycle Administration

Master keys are renewed 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 deleted inside the HSM, making any backups unrecoverable. We bind each key to a single data partition, never reuse, and conduct quarterly witnessed key ceremonies logged immutably for five years. The offline archive of old keys needs 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 leaves the HSM boundary.

Controlled Gambling and Voluntary Exclusion Registers

Stake limits, time checks, and timeout settings are saved for your account’s lifetime and never removed while it remains active. If you self-exclude, your hashed identity and device fingerprints are placed into a dedicated exclusion register held without time limit under UKGC licence requirements. The register is encrypted separately, accessed only at login or registration, and never employed for analytics. Access is restricted to trained compliance staff, and all lookups are tracked for three years. The register stores only identity blocks—no monetary or gameplay records. We check it annually to fix errors and remove deceased individuals. If not, it remains indefinite. This retention is obligatory and free from deletion requests.

Session Awareness and Play Time Restriction Enforcement

Reality check timers use temporary session counters that clear every 24 hours, beginning again from your first spin after midnight. Your chosen interval—say, 30 minutes—is stored persistently and routinely reactivates when you visit again, even after a long break. Modifying the interval mid-session introduces the new value right away for the next reminder. These settings are purged only upon validated account deletion. Session timer data resides in a specific, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for accuracy. All timer configurations are checkable through the same three-year access log standard. We never analyze or market based on these settings.

Consent for Marketing and Communication Logs

We maintain your consent record—timestamped, IP-marked, and with capture method—for the life of our partnership plus six years after cancellation, to satisfy PECR rules. Delivery logs for electronic messages, push messages, and SMS are kept for only thirteen months. Cancelling consent instantly halts communications while preserving historical proof. A segmented database ensures suppression without latency, and consent logs are stored in a dedicated compliance archive. Delivery logs contain metadata only—subject, time stamp, status—not full message content. The six-year post-withdrawal timeframe mirrors the statute of limitations for regulatory investigations. Quarterly audits verify no expired consents trigger mailings. We never personalise offers with gameplay or financial data beyond explicit authorisations.

Payment Transaction and Settlement Records

Funding, withdrawal, and wager records are retained for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We capture only the BIN, last four digits, and a tokenised alias. Chargeback disputes halt the contested record until final settlement, after which the seven-year clock continues. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs checked by auditors. Tokenised card references stay valid only while your account is live and are erased within thirty days of termination. Summarised, anonymised totals persist for financial reporting without any personal information. All financial data is encrypted and isolated from marketing systems.

Secured Payment Instruments and Processor References

Payment gateways generate vaulted tokens that map your card to a non-sensitive alias. We hold them for the account lifetime plus a thirty-day grace window, then send deletion commands to the processor and clear our own link. The only remnant left behind is an anonymised transaction hash used in aggregate statements, themselves removed after seven years. No usable credentials ever exist on our systems. We check token revocation daily and initiate incidents if deletion is unsuccessful. Tokens are linked to our merchant code and cannot be used other places. Weekly reconciliation verifies validity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are logged and checked. Aggregate reports never disclose individual transaction hashes.

User Account and Identity Verification Data

Primary identity records—government ID scans, proof of address, biometric selfie matches—are kept for a five-year period after your last activity or account termination, whichever is later. This encompasses statutory limitation periods and anti-money laundering responsibilities. We obtain only the essentials: ID number, validity, citizenship. The original image gets destroyed immediately after extraction. Once the five-year period pass, all raw data is removed, but a encrypted hash of the verification result persists for two more years inside an logging system. Personal identity information sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every access is recorded for 3 years. Optional fields like birth location are deleted at verification stage to shrink the data volume. Yearly audits confirm accuracy and proactively delete outdated records.

Document Upload and Biometric Processing

Submit an ID through our protected portal and automated checking completes within 90 seconds. We pull the ID number, expiration date, country of citizenship, and a confidence score, then shred the full-resolution image immediately—it is never stored on disk. The original file stays in an temporary memory and is removed after analysis. A compacted, watermarked thumbnail is produced for audit purposes and retained only for the ID lifecycle. That preview lives in a write-once storage with strict controls and is never shown to customer support. Collected information are encrypted and saved for the five-year plus two-year hash timeframe. All handling runs on UK-based ISO 27001 servers, and every thumbnail access is logged permanently.

Specifics of Biometric Data

Liveness checks record a brief video feed completely in memory. Images are processed and discarded within a few milliseconds. Only a data vector of facial landmarks survives. This vector contains no image data and cannot be reverse-engineered into a picture. It stays for the time of identity verification and is irreversibly removed upon account closure or after a five-year period. The numerical representation sits in a specialized HSM with self-expiry and is never sent out. Login verifications happen inside the HSM’s secure enclave without revealing the raw vector. The data set is bound to a pseudonymous identifier disconnected from marketing data, which makes re-identifying extremely difficult. Even IT admins cannot see or reconstruct facial attributes from the saved data.

Gameplay Session and Behavioral Analytics Data

Every spin on Wanted Dead Or a Wild records reel positions, RNG seed, and net outcome with microsecond precision. We retain these raw logs for twenty-four months, then condense them into an anonymous statistical digest used 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 remain 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 aggregated aggregation
• Session behavioural profiles: 24 months from last session, then erased
• RNG seed audit trails: 36 months to meet technical standards
• Feature trigger heatmaps: 12 months, then combined into global model
• Error and crash diagnostic logs: 90 days, then removed

Policy Assessment and Incident Reporting Protocols

We evaluate 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, report with the ICO, and post 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 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 check 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 shows our commitment to accountable data governance.