Playing Wanted Dead Or a Wild Slot game means providing personal data https://wanteddeadorwild.uk/. This document details exactly how long we keep it, why, and what technical protections support each category—all aligned with 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 own retention clock. Identity records stick around for five years after account closure. Financial logs remain for seven, matching 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 review our automated deletion routines, and any schedule slip activates a full incident response. A version-controlled policy log documents every edit, and we provide you 30 days’ notice before material changes become effective. Subject access and deletion requests are handled within statutory deadlines.
Essential 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 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 regard 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.
Gaming Session and Behavioural Analytics Data
All spins on Wanted Dead Or a Wild records reel positions, RNG seed, and net outcome with microsecond precision. We store these raw logs for twenty-four months, then condense them into an anonymous statistical digest utilized 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 receive 36 months. Error diagnostics receive 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 removed
- RNG seed audit trails: 36 months to satisfy technical standards
- Feature trigger heatmaps: 12 months, then integrated into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Safe Gambling and Player Ban Registers
Stake limits, time checks, and timeout settings are stored for your account’s whole period and never purged while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints enter a specialized exclusion register kept permanently under UKGC licence requirements. The register is encrypted separately, checked only at login or registration, and never employed for analytics. Access is confined to qualified compliance staff, and all queries are logged for three years. The register contains only identity blocks—no monetary or gameplay records. We examine it annually to rectify errors and remove deceased individuals. Apart from that, it stays indefinite. This retention is required and exempt from deletion requests.
Time Check and Gaming Duration Enforcement
Reality check clocks use temporary session counters that reset every 24 hours, starting anew from your first spin after midnight. Your preferred interval—say, 30 minutes—is kept persistently and routinely reactivates when you return, even after a long break. Altering the interval mid-session sets the new value instantly 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 correctness. All timer configurations are checkable through the same three-year access log standard. We at no time analyze or promote based on these settings.
Technical Infrastructure 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 adhere to 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 integrates a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor confirms automated purge schedules. Any deviation triggers a Severity 1 incident, notified to our DPO within four hours. We also operate 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 retained 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, avoid 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 confirm forensic decryption works when needed. No plaintext key material ever exits the HSM boundary.
Financial Transaction and Payment Records
Funding, 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 record only the BIN, last four digits, and a tokenised identifier. Chargeback disputes suspend the contested record until final outcome, after which the seven-year clock continues. 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 live and are erased within thirty days of closing. Aggregated, anonymised totals remain for financial reporting without any personal identifiers. All financial data is encrypted and quarantined from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways generate vaulted tokens that map your card to a non-sensitive identifier. We hold them for the account lifetime plus a thirty-day grace interval, then transmit deletion commands to the processor and wipe our own reference. The only remnant left behind is an anonymised transaction hash used in aggregate summaries, themselves deleted after seven years. No usable credentials ever sit on our systems. We check token revocation daily and raise incidents if deletion is unsuccessful. Tokens are linked to our merchant code and cannot be used elsewhere. Weekly reconciliation confirms authenticity, 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.
Registration Account and Identity Verification Data
Core identity profiles—official ID scans, proof of address, biometric selfie matches—are held for five years after your last session or account closure, whichever is later. This covers contractual time limits and anti-money laundering responsibilities. We retrieve only the necessary details: document number, expiry, citizenship. The original image gets deleted upon extraction. Once 5 years pass, all original data is erased, but a cryptographic hash of the verification outcome remains for another two years inside an logging system. Identity data sits encrypted at rest with AES-256-GCM, stored away from analytics, and every access is logged for a three-year period. Non-essential fields like birth location are deleted at the time of verification to minimize the data volume. Yearly audits verify accuracy and proactively delete expired entries.
Document Upload and Biometric Data Processing
Upload an ID through our safe portal and automated checking completes within a minute and a half. We pull the ID number, expiration date, nationality, and a reliability score, then shred the original image right away—it is never stored on disk. The original file stays in an in-memory buffer and disappears after processing. A compacted, watermarked small image is created for audit purposes and stored only for the identity lifecycle. That thumbnail lives in a write-once storage with rigorous controls and is never shared to support staff. Collected information are encoded and saved for the five-year-plus-two hash window. All processing runs on servers in the UK with ISO 27001, and every small image access is recorded immutably.
Specifics of Biometric Data
Liveness verifications capture a brief video feed entirely in memory. Frames are analyzed and removed within milliseconds. Only a data vector of face features persists. This vector has no image data and cannot be turned back into a facial image. It is kept for the entire identity verification process and is purged irrevocably upon account termination or after five years. The data set sits in a specialized HSM with self-expiry and is never sent out. Authentication checks happen inside the HSM’s protected enclave without exposing the original vector. The data set is associated with a anonymous identifier unlinked from marketing data, which makes reidentification highly challenging. Even IT admins are unable to view or rebuild face characteristics from the stored vector.
Data Subject Access Request and Deletion Workflows
When a subject access request arrives, we produce 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, 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 detailing 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.
Marketing Approval and Message Logs
We keep your consent record—timestamped, with IP address, and method-captured—for the life of our association plus six years after withdrawal, to comply with PECR requirements. Delivery logs for e-mails, push alerts, and SMS are retained for only thirteen months. Revoking consent immediately blocks communications while preserving historical proof. A divided database ensures suppression without delay, and consent logs are held in a distinct compliance archive. Send logs contain metadata only—topic, time, condition—not full message content. The six-year post-withdrawal window reflects the statute of limitations for regulatory investigations. Quarterly audits check no expired consents activate mailings. We never personalise offers with gameplay or financial data beyond explicit permissions.
Policy Assessment and Incident Reporting 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 displayed 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 notify affected individuals within 72 hours if high risk, submit with the ICO, and post a transparency notice. Third-party processor breaches must follow the same protocol. We keep a breach notification log audited quarterly. Post-incident reviews update controls as needed. Biannual tabletop exercises simulate misconfigurations and ransomware to test our response.
Document Versioning and Update Log
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 confirm the log’s accuracy. The log is a living document reflecting our evolving data practices. You can retrieve the full change log through a link in our privacy centre at any time. This transparent approach reflects our commitment to accountable data governance.
