Playing Wanted Dead Or a Wild Slot means handing over personal data wanteddeadorwild.uk. This document sets forth exactly how long we keep 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 specific retention clock. Identity records are retained for five years after account closure. Financial logs remain for seven, matching HMRC requirements. Gameplay data gets 24 months before anonymisation kicks in. Full card numbers never reach our systems—only tokenised aliases—and every byte is secured. Independent auditors review our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log records every edit, and we offer you 30 days’ notice before material changes become effective. Subject access and deletion requests are processed within statutory deadlines.
Core Definitions and Range of Personal Data
We adopt a comprehensive approach on what constitutes 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 covers session length, bet sizing, spin velocity, and how often feature triggers fire. Even pseudonymised logs can identify again 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 begins counting from the last activity or transaction date, spelled out below. We review definitions every six months to keep pace with regulatory guidance.
Infrastructure Setup and Data Location
All data sits 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 synchronizes every six hours. Backups are encrypted client-side and adhere to 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 uses a hardware token and biometric check. Penetration tests are conducted quarterly, and an independent auditor validates automated purge schedules. Any deviation raises a Severity 1 incident, reported to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, following the same deletion policies.
Encryption Key Lifecycle Management
Master keys change 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 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 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.
Responsible Gambling and Player Ban Registers
Deposit limits, reality checks, and timeout settings are kept for your account’s entire duration and never purged while it stays active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a specific exclusion register maintained indefinitely under UKGC licence requirements. The register is secured separately, queried only at login or registration, and never utilized for analytics. Entry is confined to educated compliance staff, and all searches are tracked for three years. The register contains only identity blocks—no financial or gameplay records. We review it annually to correct errors and remove deceased individuals. Otherwise, it stays everlasting. This retention is required and exempt from deletion requests.
Reality Check and Gaming Duration Enforcement
Reality check timers use temporary session counters that clear every 24 hours, starting anew from your first spin after midnight. Your selected interval—say, 30 minutes—is stored persistently and automatically reactivates when you come back, even after a long break. Altering the interval mid-session sets the new value immediately for the next reminder. These settings are purged 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 accuracy. All timer configurations are checkable through the same three-year access log standard. We never categorize or promote based on these settings.
Financial Transaction and Billing Records
Funding, withdrawal, and wager records 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 halt the contested record until final outcome, after which the seven-year clock restarts. 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 active and are erased within thirty days of closure. Combined, anonymised totals endure for financial reporting without any personal information. All financial data is secured and quarantined from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways produce vaulted tokens that map your card to a non-sensitive alias. We keep them for the account lifetime plus a thirty-day grace interval, then issue deletion commands to the processor and erase our own link. The only evidence left behind is an anonymised transaction hash used in aggregate summaries, themselves deleted after seven years. No usable credentials ever exist on our systems. We check token revocation daily and trigger incidents if deletion is unsuccessful. Tokens are bound to our merchant code and cannot be used elsewhere. Weekly reconciliation verifies authenticity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are logged and auditable. Aggregate reports never expose individual transaction hashes.
Registration Account and Identity Verification Data
Primary identity records—government ID scans, proof of address, biometric selfie verifications—are kept for 5 years after your last activity or account closure, whichever comes later. This includes contractual limitation periods and anti-money laundering duties. We retrieve only the essentials: document number, expiration date, country of citizenship. The full-resolution image gets destroyed upon extraction. Once the five-year period pass, all original data is erased, but a encrypted hash of the verification result remains 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 retrieval is tracked for a three-year period. Non-essential fields like birth location are removed at verification time to minimize the data size. Yearly audits verify precision and actively purge expired data.
Document Upload and Biometric Processing
Provide an ID through our secure portal and automated checking completes within ninety seconds. We extract the document ID, validity, nationality, and a confidence score, then shred the high-resolution image right away—it never reaches storage. The source file stays in an temporary memory and disappears after handling. A compacted, marked thumbnail is produced for compliance purposes and retained only for the identity verification period. That small image lives in a immutable vault with rigorous controls and is never shared to support staff. Retrieved data are secured and stored for the five-year-plus-two hash window. All handling runs on ISO 27001 certified UK servers, and every preview retrieval is logged permanently.
Biometric Information Details
Live detection checks capture a quick video entirely in memory. Video frames are analyzed and removed within milliseconds of time. Only a mathematical vector of facial points survives. This data set lacks any image data and cannot be reconstructed into a picture. It stays for the entire identity verification process and is purged irrevocably upon account closure or after a five-year period. The vector sits in a dedicated HSM with auto-expiry and is never sent out. Login comparisons happen inside the HSM’s protected enclave without exposing the raw vector. The numerical representation is bound to a pseudonymous identifier unlinked from marketing data, which makes re-identification very hard. Even IT admins cannot see or recreate facial attributes from the kept numerical representation.
Data Subject Access Request and Deletion Workflows
Upon receiving an SAR, we compile a structured JSON/CSV export of all non-purged data within one month, extendable by two months for complex cases. The export includes live databases, encrypted archives, and processor tokens, delivered via a one-time secure link that expires in 72 hours. For deletion, we implement a cascade: immediate account suppression and token revocation, then queued 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.
Marketing Consent and Communication Logs
We store your consent document—with time stamp, with IP address, and with capture method—for the duration of our association plus six years after withdrawal, to satisfy PECR rules. Send logs for e-mails, push alerts, and SMS are kept for only thirteen months. Revoking consent right away suppresses communications while preserving historical proof. A partitioned database guarantees suppression without lag, and consent logs are stored in a dedicated compliance archive. Delivery logs contain metadata only—heading, time stamp, state—not full message content. The six-year post-withdrawal timeframe mirrors the statute of limitations for regulatory probes. Quarterly audits confirm no expired consents trigger mailings. We never tailor offers with gameplay or financial data beyond explicit permissions.
Gaming Session and Behavioural Analytics Data
Every spin on Wanted Dead Or a Wild tracks reel positions, RNG seed, and net outcome with microsecond precision. We keep these raw logs for twenty-four months, then compact them into an anonymous statistical digest used for game design. Session behavioural profiles—average bet, spin cadence, feature buy-ins—remain 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 have 36 months. Error diagnostics have 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 erased
- RNG seed audit trails: 36 months to comply with 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 documented 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, 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 revise controls as needed. Biannual tabletop exercises model misconfigurations and ransomware to test our response.
Policy Versioning and Update Log
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 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 access the full change log through a link in our privacy centre at any time. This transparent approach shows our commitment to accountable data governance.
