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, the rationale, 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 own retention clock. Identity records are kept for five years after account closure. Financial logs are stored for seven, satisfying HMRC requirements. Gameplay data receives 24 months before anonymisation takes effect. 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 activates a full incident response. A version-controlled policy log tracks every edit, and we provide you 30 days‘ notice before material changes take effect. Subject access and deletion requests are handled within statutory deadlines.
Policy Assessment and Incident Reporting Protocols
We review 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 issue a transparency notice. Third-party processor breaches must follow the same protocol. We maintain a breach notification log audited quarterly. Post-incident reviews adjust controls as needed. Biannual tabletop exercises simulate misconfigurations and ransomware to test our response.
Policy Version Control and Revision History
We preserve a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log outlines 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 communicated 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 demonstrates our commitment to accountable data governance.
Consent for Marketing and Correspondence Records
We maintain your consent record—with time stamp, IP-marked, and method-captured—for the life of our association plus six years after withdrawal, to satisfy PECR rules. Delivery logs for e-mails, push notifications, and SMS are retained for only thirteen months. Cancelling consent right away halts communications while preserving historical proof. A segmented database guarantees suppression without latency, and consent logs are held in a dedicated compliance archive. Delivery logs include metadata only—subject, time stamp, condition—not full message body. The six-year post-withdrawal timeframe matches the statute of limitations for regulatory investigations. Quarterly audits check no expired consents trigger mailings. We never personalise offers with gameplay or financial data beyond explicit permissions.
Gameplay Session and Analytics of Behavior Data
All spins 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 compress them into an anonymous statistical digest used for game design. Session behavioural profiles—average bet, spin cadence, feature buy-ins—stay 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 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 combined into global model
- Error and crash diagnostic logs: 90 days, then cycled out
Payment Transaction and Billing Records
Deposit, withdrawal, and wager logs are maintained for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised reference. Chargeback disputes suspend the contested record until final settlement, after which the seven-year clock continues. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs checked by auditors. Tokenised card references stay valid only while your account is active and are deleted within thirty days of closing. Combined, anonymised totals remain for financial reporting without any personal details. All financial data is encrypted and separated from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways generate 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 send deletion commands to the processor and wipe our own link. The only evidence left behind is an anonymised transaction hash used in aggregate summaries, themselves removed after seven years. No usable credentials ever reside 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 in other contexts. Weekly reconciliation verifies correctness, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are recorded and verifiable. Aggregate reports never reveal individual transaction hashes.
Technical Infrastructure and Data Residency
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 updates 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 integrates 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, reported to our DPO within four hours. We also keep an air-gapped backup rotated weekly, under the same deletion policies.
Management of Encryption Keys
Master keys are renewed every 90 days automatically inside an HSM. New keys are never exported 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 deleted inside the HSM, making any backups unrecoverable. We bind 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 requires dual control and is stored on write-once media in a fireproof safe. Annual recovery drills guarantee forensic decryption works when needed. No plaintext key material ever departs the HSM boundary.
User Account and ID Verification Data
Main identity data—government ID scans, proof of address, biometric selfie matches—are retained for five years after your last activity or closure of account, whichever is later. This includes statutory limitation periods and anti-money laundering duties. We retrieve only the key information: document number, expiry, citizenship. The high-resolution image gets destroyed right after extraction. Once the five-year period pass, all source data is removed, but a hash of the verification result persists for another two years inside an audit trail. Identity data sits stored encrypted with AES-256-GCM, kept separate from analytics, and every data access is logged for 3 years. Optional fields like birth location are discarded at the time of verification to minimize the data footprint. Yearly audits confirm precision and actively purge outdated records.
Document Upload and Biometric Processing
Submit an ID through our secure portal and automatic verification completes within 90 seconds. We extract the document number, expiration date, nationality, and a confidence score, then destroy the full-resolution image instantly—it never touches disk. The initial file stays in an temporary memory and vanishes after processing. A compacted, stamped thumbnail is produced for compliance purposes and stored only for the identity verification period. That small image lives in a write-once storage with tight controls and is never shown to support staff. Retrieved data are encrypted and saved for the 5-year-plus-2-year hash period. All operations runs on ISO 27001 certified UK servers, and every thumbnail access is recorded immutably.
Biometric Information Details
Liveness verifications capture a brief video feed solely in memory. Images are analysed and removed within milliseconds of time. Only a numerical vector of facial points remains. This data set has no image data and cannot be reverse-engineered into a picture. It stays for the entire identity verification process and is permanently deleted upon account closure or after 5 years. The numerical representation sits in a hardware security module with auto-expiry and is never exported. Login verifications happen inside the HSM’s safe environment without disclosing the original vector. The vector is linked to a pseudonymous identifier disconnected from marketing data, which makes reidentification very hard. Even IT admins are unable to view or rebuild facial features from the stored vector.
Fundamental Definitions and Extent of Personal Data
We cast a wide net 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 encompasses 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 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 extend across live databases, archives, and backups without exception. Each window commences from the last activity or transaction date, spelled out below. We reassess definitions every six months to stay aligned with regulatory guidance.
Controlled Gambling and Self-Exclusion Registers
Stake limits, session reminders, and timeout settings are saved for your account’s entire duration and never deleted while it stays active. If you opt for self-exclusion, your hashed identity and device fingerprints are placed into a dedicated exclusion register maintained indefinitely under UKGC licence requirements. The register is secured separately, checked only at login or registration, and never utilized for analytics. Permission is restricted to trained compliance staff, and all lookups are logged for three years. The register holds only identity blocks—no financial or gameplay records. We check it annually to fix errors and remove deceased individuals. Otherwise, it remains everlasting. This retention is obligatory and excluded from deletion requests.
Session Awareness and Play Time Restriction Enforcement
Reality check clocks use temporary session counters that restart every 24 hours, restarting from your first spin after midnight. Your preferred interval—say, 30 minutes—is stored persistently and instantly reactivates when you visit again, even after a long break. Altering the interval mid-session introduces the new value instantly for the next reminder. These settings are purged only upon verified account deletion. Session timer data sits in a dedicated, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for accuracy. All timer configurations are auditable through the same three-year access log standard. We at no time analyze or advertise based on these settings.
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, expandable by two months for complex cases. The export covers 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 outlining 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.