Playing Wanted Dead Or a Wild Slot means providing personal data. This document sets forth exactly how long we keep it, the reasons, and what technical protections underpin 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 unique retention clock. Identity records are kept for five years after account closure. Financial logs stay for seven, satisfying HMRC requirements. Gameplay data undergoes 24 months before anonymisation kicks in. Full card numbers never enter our systems—only tokenised aliases—and every byte is secured. Independent auditors verify our automated deletion routines, and any schedule slip triggers a full incident response. A version-controlled policy log documents every edit, and we offer you 30 days’ notice before material changes become effective. Subject access and deletion requests are managed within statutory deadlines.
Registration Account and Verification of Identity Data
Core identity profiles—scans of government IDs, residence proof, selfie biometric matches—are held for a five-year period after your final session or account closure, whichever occurs later. This covers contractual time limits and AML obligations. We extract only the key information: document number, validity, country of citizenship. The high-resolution image gets deleted upon extraction. Once five years pass, all raw data is purged, but a cryptographic hash of the verification outcome remains for another two years inside an logging system. Personal identity information sits stored encrypted with AES-256-GCM, kept separate from analytics, and every retrieval is logged for 3 years. Optional fields like birthplace are removed at the time of verification to reduce the data size. Yearly audits verify correctness and automatically remove expired data.
Uploading Documents and Biometric Processing
Provide an ID through our protected portal and automated validation wraps up within ninety seconds. We retrieve the document ID, validity, country of citizenship, and a confidence score, then shred the high-resolution image right away—it never reaches storage. The source file stays in an memory buffer and is removed after analysis. A reduced, marked preview is created for auditing purposes and retained only for the identity lifecycle. That small image lives in a immutable vault with strict controls and is never exposed to support staff. Retrieved data are encoded and kept for the five-year plus two-year hash timeframe. All operations runs on servers in the UK with ISO 27001, and every small image access is logged permanently.
Biometric Information Details
Liveness checks capture a brief video feed completely in memory. Frames are processed and deleted within milliseconds of time. Only a numerical vector of facial landmarks persists. This numerical representation lacks any image data and cannot be reverse-engineered into a picture. It is kept for the entire identity verification process and is irreversibly removed upon account termination or after a five-year period. The numerical representation sits in a specialized HSM with automatic expiration and is never sent out. Login comparisons happen inside the HSM’s safe environment without revealing the unprocessed data. The numerical representation is associated with a pseudonym disconnected from marketing profiles, which makes reidentification very hard. Even system admins cannot view or reconstruct facial features from the stored vector.
Technology Framework and Data Storage
All data is stored 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 syncs every six hours. Backups are encrypted client-side and follow identical retention rules. We enforce 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 run quarterly, and an independent auditor validates automated purge schedules. Any deviation raises a Severity 1 incident, alerted to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, subject to the same deletion policies.
Management of Encryption Keys
Master keys rotate every 90 days automatically inside an HSM https://wanteddeadorwild.uk/. New keys are not extracted 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 removed 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.
Controlled Gambling and Voluntary Exclusion Registers
Deposit limits, time checks, and timeout settings are stored for your account’s entire duration and never deleted while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints enter a dedicated exclusion register kept without time limit under UKGC licence requirements. The register is encrypted separately, queried only at login or registration, and never used for analytics. Access is restricted to qualified compliance staff, and all queries are recorded for three years. The register holds only identity blocks—no monetary or gameplay records. We examine it annually to rectify errors and remove deceased individuals. Apart from that, it stays permanent. This retention is obligatory and exempt from deletion requests.
Session Awareness and Play Time Restriction Enforcement
Reality check timers use transient session counters that reset every 24 hours, starting anew from your first spin after midnight. Your chosen interval—say, 30 minutes—is kept persistently and automatically reactivates when you return, even after a long break. Modifying the interval mid-session introduces the new value immediately for the next reminder. These settings are deleted only upon verified account deletion. Session timer data sits in a specialized, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for precision. All timer configurations are auditable through the same three-year access log standard. We at no time profile or advertise based on these settings.
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 compress 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 get 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 anonymized 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 removed
Policy Evaluation and Breach Notification 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 displayed 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 update controls as needed. Biannual tabletop exercises test misconfigurations and ransomware to test our response.
Policy Version Control 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 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 check 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.
Payment Transaction and Settlement Records
Deposit, withdrawal, and wager logs are retained for seven years from the transaction date, per HMRC and FCA rules. We seldom store full PANs or CVVs. We record 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 resumes. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs verified by auditors. Tokenised card references are valid only while your account is active and are erased within thirty days of closing. Combined, anonymised totals remain for financial reporting without any personal identifiers. All financial data is coded and quarantined from marketing systems.
Secured 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 period, then issue 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 removed after seven years. No usable credentials ever reside on our systems. We monitor token revocation daily and initiate incidents if deletion fails. Tokens are bound to our merchant code and cannot be used in other contexts. Weekly reconciliation verifies validity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are recorded and checked. Aggregate reports never disclose individual transaction hashes.
Marketing Consent and Correspondence Records
We keep your consent record—with time stamp, with IP address, and method-captured—for the life of our association plus six years after withdrawal, to satisfy PECR obligations. Delivery logs for emails, push messages, and SMS are retained for only thirteen months. Cancelling consent immediately halts communications while keeping historical proof. A divided database guarantees suppression without latency, and consent logs are kept in a dedicated compliance archive. Send logs contain metadata only—topic, time, status—not full message text. The six-year post-withdrawal timeframe matches the statute of limitations for regulatory probes. Quarterly audits confirm no expired consents activate mailings. We never tailor offers with gameplay or financial data beyond explicit authorisations.
SAR and Deletion Processes
Upon receiving an SAR, we produce a formatted JSON/CSV export of all non-purged data within one month, expandable by two months for complex cases. The export spans 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 queued erasure of all personal data not subject to legal hold. We generate a confirmation report specifying erased versus retained categories and their justifications. This report is maintained 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 adopt a comprehensive approach on what constitutes 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 span live databases, archives, and backups without exception. Each window begins counting from the last activity or transaction date, spelled out below. We revisit definitions every six months to remain compliant with regulatory guidance.