Playing Wanted Dead Or a Wild Slot game means handing over personal data https://wanteddeadorwild.uk/. This document lays out exactly how long we store it, why, and what technical protections sit behind 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, satisfying HMRC requirements. Gameplay data receives 24 months before anonymisation kicks in. Full card numbers never touch our systems—only tokenised aliases—and every byte is encrypted. Independent auditors verify our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log tracks every edit, and we offer you 30 days’ notice before material changes are implemented. Subject access and deletion requests are handled within statutory deadlines.
Policy Review and Data Breach Protocols
We assess 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 published 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 notify affected individuals within 72 hours if high risk, report with the ICO, and post 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 model misconfigurations and ransomware to test our response.
Document 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 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 verify 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.
Data Subject Access Request and Deletion Workflows
When an SAR lands, we generate 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, 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 batched erasure of all personal data not subject to legal hold. We produce a confirmation report specifying 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.
Gaming Session and Behavioral Analytics Data
All spins on Wanted Dead Or a Wild records 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 employed 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 remain 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 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 aggregated aggregation
- Session behavioural profiles: 24 months from last session, then deleted
- RNG seed audit trails: 36 months to meet technical standards
- Feature trigger heatmaps: 12 months, then integrated into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Infrastructure Setup and Data Storage
All data resides 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 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 are conducted 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, following the same deletion policies.
Encryption Key Lifecycle Management
Master keys are renewed 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 destroyed inside the HSM, making any backups unrecoverable. We bind 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 leaves the HSM boundary.
Marketing Consent and Message Logs
We store your consent record—with time stamp, IP-marked, and method-recorded—for the life of our association plus six years after withdrawal, to comply with PECR rules. Send logs for emails, push messages, and SMS are retained for only thirteen months. Withdrawing consent right away suppresses communications while retaining historical proof. A partitioned database provides suppression without latency, and consent logs are stored in a dedicated compliance archive. Dispatch records hold metadata only—heading, timestamp, condition—not full message text. The six-year post-withdrawal timeframe matches the statute of limitations for regulatory inquiries. Quarterly audits verify no expired consents activate mailings. We never customise offers with gameplay or financial data beyond explicit consents.
Safe Gambling and Self-Exclusion Registers
Deposit limits, time checks, and timeout settings are kept for your account’s whole period and never removed while it remains active. If you choose to ban yourself, your hashed identity and device fingerprints are added to a specific exclusion register kept permanently under UKGC licence requirements. The register is coded separately, accessed only at login or registration, and never utilized for analytics. Entry is limited to educated compliance staff, and all lookups are tracked for three years. The register stores only identity blocks—no monetary or gameplay records. We check it annually to rectify errors and remove deceased individuals. If not, it stays everlasting. This retention is required and excluded from deletion requests.
Session Awareness and Session Limit Enforcement
Reality check timers use transient session counters that reset every 24 hours, restarting 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. Modifying the interval mid-session applies the new value immediately for the next reminder. These settings are purged only upon verified 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 auditable through the same three-year access log standard. We never categorize or advertise based on these settings.
Registration Account and ID Verification Data
Primary identity records—scans of government IDs, residence proof, biometric selfie verifications—are retained for 5 years after your last session or account closure, whichever occurs later. This encompasses contractual time limits and anti-money laundering duties. We retrieve only the necessary details: ID number, expiry, country of citizenship. The full-resolution image gets shredded immediately after extraction. Once five years pass, all source data is removed, but a hash of the verification outcome persists for two more years inside an audit trail. Personal identity information sits encrypted at rest with AES-256-GCM, isolated from analytics, and every retrieval is logged for a three-year period. Unnecessary fields like birth location are removed at the time of verification to reduce the data footprint. Annual reviews verify precision and actively purge expired data.
Uploading Documents and Biometric Processing
Provide an ID through our protected portal and automatic verification finishes within 90 seconds. We pull the document number, expiry, nationality, and a trust score, then delete the original image instantly—it never touches disk. The source file stays in an temporary memory and is removed after handling. A compressed, watermarked thumbnail is generated for audit purposes and stored only for the identity verification period. That small image lives in a write-once vault with tight controls and is never shown to client support. Extracted fields are encrypted and saved for the five-year plus two-year hash timeframe. All handling runs on ISO 27001 certified UK servers, and every preview retrieval is stored unchangeably.
Biometric Information Details
Liveness verifications collect a quick video completely in memory. Images are analysed and deleted within milliseconds. Only a data vector of facial landmarks persists. This data set contains no image data and cannot be reconstructed into a picture. It stays for the entire identity verification process and is purged irrevocably upon account termination or after a five-year period. The numerical representation sits in a hardware security module with auto-expiry and is never transferred. Login verifications happen inside the HSM’s protected enclave without disclosing the raw vector. The data set is linked to a pseudonymous identifier disconnected from advertising profiles, which makes reidentification highly challenging. Even IT admins cannot view or recreate facial features from the kept numerical representation.
Essential Definitions and Range of Personal Data
We adopt a comprehensive approach on what counts as 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 includes 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 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 cover 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 keep pace with regulatory guidance.
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 do not 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 resolution, after which the seven-year clock continues. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs verified by auditors. Tokenised card references remain valid only while your account is active and are deleted within thirty days of closing. Aggregated, anonymised totals remain for financial reporting without any personal information. All financial data is encrypted and separated from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways generate vaulted tokens that associate your card to a non-sensitive identifier. We keep them for the account lifetime plus a thirty-day grace window, then send deletion commands to the processor and wipe our own link. The only remnant left behind is an anonymised transaction hash used in aggregate summaries, themselves removed after seven years. No usable credentials ever sit on our systems. We track token revocation daily and trigger incidents if deletion fails. Tokens are bound to our merchant code and cannot be used other places. Weekly reconciliation validates validity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are documented and auditable. Aggregate reports never disclose individual transaction hashes.
