Playing Wanted Dead Or a Wild Slot means submitting personal data wanteddeadorwild.uk. This document details exactly how long we keep it, the reasons, and what technical protections support 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 specific 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 takes effect. Full card numbers never reach our systems—only tokenised aliases—and every byte is secured. Independent auditors verify our automated deletion routines, and any schedule slip activates a full incident response. A version-controlled policy log tracks every edit, and we give you 30 days’ notice before material changes take effect. Subject access and deletion requests are processed within statutory deadlines.
SAR and Deletion Processes
Upon receiving an SAR, we generate a formatted 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 proceed sequentially: immediate account suppression and token revocation, then queued erasure of all personal data not subject to legal hold. We create 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 logged immutably for five years.
Fundamental Definitions and Range of Personal Data
We cast a wide net on what counts 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 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 cover 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 stay aligned with regulatory guidance.
Gaming Session and Behavioural Analytics 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 compact them into an anonymous statistical digest employed 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 remain 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 goes into credit or marketing profiling. All logs are encrypted and off-limits to marketing teams.
- Spin-level logs: 24 months from event date, then anonymised aggregation
- Session behavioural profiles: 24 months from last session, then deleted
- 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 rotated out
Consent for Marketing and Communication Logs
We maintain your consent record—with time stamp, IP-marked, and method-captured—for the duration of our relationship plus six years after cancellation, to comply with PECR obligations. Send logs for emails, push messages, and SMS are retained for only thirteen months. Revoking consent right away blocks communications while preserving historical proof. A partitioned database ensures suppression without lag, and consent logs are kept in a separate compliance archive. Delivery logs include metadata only—heading, time stamp, status—not full message content. The six-year post-withdrawal timeframe reflects the statute of limitations for regulatory probes. Quarterly audits check no expired consents activate mailings. We never customise offers with gameplay or financial data beyond explicit authorisations.
Monetary Transaction and Billing Records
Deposit, withdrawal, and wager records are kept for seven years from the transaction date, per HMRC and FCA rules. We do not store full PANs or CVVs. We capture only the BIN, last four digits, and a tokenised alias. Chargeback disputes freeze the contested record until final resolution, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs audited by auditors. Tokenised card references stay valid only while your account is live and are erased within thirty days of closure. Combined, anonymised totals endure for financial reporting without any personal information. All financial data is encrypted and separated from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways produce vaulted tokens that map your card to a non-sensitive reference. We keep them for the account lifetime plus a thirty-day grace period, then send deletion commands to the processor and clear our own reference. The only remnant left behind is an anonymised transaction hash used in aggregate reports, themselves purged after seven years. No usable credentials ever sit on our systems. We check token revocation daily and raise incidents if deletion does not work. Tokens are bound to our merchant code and cannot be used elsewhere. Weekly reconciliation confirms correctness, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are logged and checked. Aggregate reports never reveal individual transaction hashes.
User Account and Verification of Identity Data
Core identity profiles—official ID scans, proof of address, biometric selfie matches—are held for five years after your last session or closure of account, whichever occurs later. This encompasses contractual limitation periods and anti-money laundering duties. We retrieve only the necessary details: document ID, expiry, citizenship. The high-resolution image gets deleted upon extraction. Once 5 years pass, all raw data is erased, but a cryptographic hash of the verification data persists for an additional two years inside an audit trail. Identification data sits encrypted at rest with AES-256-GCM, isolated from analytics, and every access is recorded for three years. Optional fields like birthplace are removed at verification time to minimize the data size. Yearly reviews ensure precision and proactively delete outdated records.
File Upload and Biometric Handling
Provide an ID through our secure portal and automated checking finishes within 90 seconds. We pull the ID number, expiration date, citizenship, and a trust score, then destroy the full-resolution image immediately—it is never stored on disk. The original file stays in an temporary memory and vanishes after handling. A reduced, watermarked preview is created for audit purposes and stored only for the identity verification period. That small image lives in a write-once storage with strict controls and is never shown to support staff. Collected information are encoded and kept for the 5-year-plus-2-year hash period. All handling runs on ISO 27001 certified UK servers, and every small image access is logged permanently.
Specifics of Biometric Data
Live detection checks capture a quick video entirely in memory. Images are processed and removed within a few milliseconds. Only a numerical vector of facial landmarks remains. This numerical representation has no image data and cannot be turned back into a face. It stays for the time of identity verification and is irreversibly removed upon closure of account or after 5 years. The numerical representation sits in a specialized HSM with auto-expiry and is never exported. Login comparisons happen inside the HSM’s secure enclave without revealing the raw vector. The data set is associated with a pseudonym disconnected from advertising profiles, which makes reidentification highly challenging. Even system admins cannot see or rebuild facial attributes from the stored vector.
Safe Gambling and Self-Exclusion Registers
Deposit limits, reality checks, and timeout settings are kept for your account’s lifetime and never purged while it remains active. If you self-exclude, your hashed identity and device fingerprints are added to a specialized exclusion register held indefinitely under UKGC licence requirements. The register is coded separately, queried only at login or registration, and never used for analytics. Access is restricted to educated compliance staff, and all queries are recorded for three years. The register stores only identity blocks—no monetary or gameplay records. We examine it annually to rectify errors and remove deceased individuals. If not, it stays indefinite. This retention is obligatory and free from deletion requests.
Reality Check and Gaming Duration Enforcement
Reality check timers use transient session counters that reset every 24 hours, restarting from your first spin after midnight. Your selected interval—say, 30 minutes—is kept persistently and routinely reactivates when you come back, even after a long break. Altering the interval mid-session introduces the new value right away for the next reminder. These settings are purged only upon confirmed 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 precision. All timer configurations are verifiable through the same three-year access log standard. We never analyze or market based on these settings.
Technical Infrastructure and Data Residency
All data sits in UK-based ISO 27001 Tier III+ data centres, never replicated outside the UK. A hot disaster recovery site in a separate UK zone synchronizes every six hours. Backups are encrypted client-side and maintain identical retention rules. We enforce least privilege with hardware MFA for administrators, logging their sessions in an immutable three-year audit trail. Multi-factor authentication integrates a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor verifies automated purge schedules. Any deviation generates a Severity 1 incident, reported to our DPO within four hours. We also keep an air-gapped backup rotated weekly, following 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 stored 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, never 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.
Policy Assessment and Data Breach Protocols
We evaluate this policy every six months or upon material change to the game or regulation. Reviews are recorded with DPO, CISO, and legal counsel. A public summary is published in our privacy centre, minus confidential details. Material changes are emailed 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 issue 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 test misconfigurations and ransomware to test our response.
Document Versioning and Revision History
We keep 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 conveyed 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 confirm 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 demonstrates our commitment to accountable data governance.
