Playing Wanted Dead Or a Wild Slot means providing personal data. This document sets forth exactly how long we store it, why, and what technical protections support each category—all based on UK GDPR, the Data Protection Act 2018, and PCI DSS. We manage identity documents, financial transactions, gameplay telemetry, responsible gambling markers, and marketing consents, each with its own retention clock. Identity records are kept for five years after account closure. Financial logs stay for seven, matching HMRC requirements. Gameplay data gets 24 months before anonymisation takes effect. Full card numbers never touch our systems—only tokenised aliases—and every byte is protected. Independent auditors verify 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 are implemented. Subject access and deletion requests are handled within statutory deadlines.
Core Definitions and Extent of Personal Data
We cast a wide net on what qualifies as personal data. Direct identifiers—name, email, billing address, masked payment details—sit alongside 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 treat 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 reassess definitions every six months to stay aligned with regulatory guidance.
Gameplay Session and Analytics of Behavior Data
Every spin 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 compress them into an anonymous statistical digest used 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 stay for 12 months before merging into a global model. RNG seed audit trails have 36 months. Error diagnostics get 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 aggregated 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 removed
Infrastructure Setup and Data Location
All data resides 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 implement 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 occur quarterly, and an independent auditor validates automated purge schedules. Any deviation generates a Severity 1 incident, alerted to our DPO within four hours. We also keep an air-gapped backup rotated weekly, under the same deletion policies.
Key Lifecycle Administration
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 link 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 requires 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.
Financial Transaction and Payment 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 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 resumes. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs verified by auditors. Tokenised card references are valid only while your account is active and are wiped within thirty days of closing. Summarised, anonymised totals persist for financial reporting without any personal details. All financial data is coded and quarantined from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways produce vaulted tokens that associate your card to a non-sensitive reference. We keep them for the account lifetime plus a thirty-day grace period, then issue deletion commands to the processor and erase our own mapping. The only trace left behind is an anonymised transaction hash used in aggregate reports, themselves removed after seven years. No usable credentials ever reside on our systems. We track token revocation daily and initiate incidents if deletion fails. Tokens are tied to our merchant code and cannot be used other places. Weekly reconciliation confirms correctness, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are recorded and verifiable. Aggregate reports never expose individual transaction hashes.
Marketing Approval and Message Logs
We store your consent record—time-stamped, IP-stamped, and with capture method—for the entirety of our relationship plus six years after withdrawal, to meet PECR requirements. Send logs for electronic messages, push messages, and SMS are held for only thirteen months. Revoking consent immediately blocks communications while preserving historical proof. A divided database guarantees suppression without delay, and consent logs are held in a distinct compliance archive. Dispatch records contain metadata only—heading, time, state—not full message text. The six-year post-withdrawal timeframe matches the statute of limitations for regulatory inquiries. Quarterly audits check no expired consents initiate mailings. We never personalise offers with gameplay or financial data beyond explicit authorisations.
Data Subject Access Request and Deletion Workflows
When a subject access request arrives, we produce 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, provided via a one-time secure link that expires in 72 hours. For deletion, we proceed sequentially: 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 kept as auditable proof for as long as the longest surviving data category. All requests are recorded immutably for five years.
Account Registration and Verification of Identity Data
Core identity profiles—official ID scans, proof of address, selfie biometric matches—are held for 5 years after your last session or account closure, whichever is later https://wanteddeadorwild.uk/. This includes statutory limitation periods and anti-money laundering duties. We retrieve only the essentials: document ID, expiration date, citizenship. The full-resolution image gets destroyed immediately after extraction. Once the five-year period pass, all source data is purged, but a hash of the verification result persists for an additional two years inside an logging system. Personal identity information sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every retrieval is logged for 3 years. Non-essential fields like birthplace are removed at verification time to shrink the data size. Yearly audits verify correctness and automatically remove expired entries.
Uploading Documents and Biometric Handling
Upload an ID through our protected portal and automated checking completes within ninety seconds. We extract the document number, validity, nationality, and a confidence score, then delete the full-resolution image immediately—it is never stored on disk. The original file stays in an memory buffer and disappears after analysis. A compressed, stamped preview is produced for auditing purposes and kept only for the identity verification period. That small image lives in a write-once storage with strict controls and is never exposed to customer support. Collected information are encoded and stored for the five-year plus two-year hash timeframe. All processing runs on servers in the UK with ISO 27001, and every thumbnail access is stored unchangeably.
Biometric Data Specifics
Live detection checks record a short video stream entirely in memory. Frames are processed and deleted within milliseconds of time. Only a data vector of facial points survives. This data set lacks any image data and cannot be reverse-engineered into a facial image. It remains for the duration of identity verification and is irreversibly removed upon account closure or after 5 years. The data set sits in a hardware security module with automatic expiration and is never exported. Authentication checks happen inside the HSM’s protected enclave without disclosing the raw vector. The data set is bound to a pseudonym separated from marketing profiles, which makes reidentification very hard. Even IT admins cannot see or recreate face characteristics from the stored vector.
Safe Gambling and Self-Exclusion Registers
Betting limits, reality checks, and timeout settings are saved for your account’s lifetime and never removed while it stays active. If you self-exclude, your hashed identity and device fingerprints are added to a specific exclusion register maintained permanently under UKGC licence requirements. The register is encrypted separately, accessed only at login or registration, and never used for analytics. Permission is limited to qualified compliance staff, and all searches are recorded for three years. The register stores only identity blocks—no financial or gameplay records. We check it annually to correct errors and remove deceased individuals. Apart from that, it stays permanent. This retention is obligatory and exempt from deletion requests.
Time Check and Session Limit Enforcement
Reality check timers use transient session counters that reset every 24 hours, restarting from your first spin after midnight. Your chosen interval—say, 30 minutes—is saved persistently and instantly reactivates when you return, even after a long break. Changing the interval mid-session introduces the new value right away for the next reminder. These settings are deleted only upon confirmed 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 never categorize or promote based on these settings.
Policy Review and Data Breach 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 alert affected individuals within 72 hours if high risk, report with the ICO, and publish a transparency notice. Third-party processor breaches must follow the same protocol. We hold a breach notification log audited quarterly. Post-incident reviews adjust controls as needed. Biannual tabletop exercises simulate misconfigurations and ransomware to test our response.
Document Versioning and Update Log
We preserve 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 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 verify 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 reflects our commitment to accountable data governance.
