Playing Wanted Dead Or a Wild Slot game means submitting personal data. This document sets forth exactly how long we retain it, why, and what technical protections support each category—all built around 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 unique retention clock. Identity records stick around for five years after account closure. Financial logs stay for seven, satisfying HMRC requirements. Gameplay data undergoes 24 months before anonymisation takes effect. Full card numbers never touch our systems—only tokenised aliases—and every byte is secured. Independent auditors review 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 take effect. Subject access and deletion requests are handled within statutory deadlines.
Controlled Gambling and Voluntary Exclusion Registers
Betting limits, reality 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 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 utilized for analytics. Access is limited to trained compliance staff, and all queries are recorded for three years. The register contains only identity blocks—no banking or gameplay records. We examine it annually to rectify errors and remove deceased individuals. If not, it stays everlasting. This retention is required and excluded from deletion requests.
Reality Check and Session Limit Enforcement
Reality check clocks use short-lived session counters that restart every 24 hours, restarting from your first spin after midnight. Your selected interval—say, 30 minutes—is stored persistently and routinely reactivates when you return, even after a long break. Altering the interval mid-session applies the new value instantly for the next reminder. These settings are purged only upon validated 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 verifiable through the same three-year access log standard. We never profile or market based on these settings.
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—are accompanied by 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 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 starts ticking from the last activity or transaction date, spelled out below. We reassess definitions every six months to remain compliant with regulatory guidance.
Gameplay Session and Behavioral Analytics Data
Each spin on Wanted Dead Or a Wild tracks reel positions, RNG seed, and net outcome with microsecond precision. We retain these raw logs for twenty-four months, then condense 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 get 90 days. No individual gameplay data flows 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 meet technical standards
- Feature trigger heatmaps: 12 months, then merged into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Policy Review and Incident Reporting Protocols
We review 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 published 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 inform affected individuals within 72 hours if high risk, file 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 model misconfigurations and ransomware to test our response.
Document Versioning and Change 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 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 demonstrates our commitment to accountable data governance.
Access Request and Erasure Workflows
When an SAR lands, we compile a formatted JSON/CSV export of all non-purged data within one month, extendable by two months for complex cases. The export covers live databases, encrypted archives, and processor tokens, delivered via a one-time secure link that expires in 72 hours. For deletion, we proceed sequentially: immediate account suppression and token revocation, then batched erasure of all personal data not subject to legal hold. We produce a confirmation report detailing 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.
Monetary Transaction and Settlement Records
Deposit, withdrawal, and wager histories are kept for seven years from the transaction date, per HMRC and FCA rules. We do not store full PANs or CVVs. We capture only the BIN, last four digits, and a tokenised alias. Chargeback disputes suspend the contested record until final outcome, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs checked by auditors. Tokenised card references are valid only while your account is active and are deleted within thirty days of termination. Aggregated, anonymised totals endure for financial reporting without any personal information. All financial data is encrypted and isolated from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways generate vaulted tokens that link your card to a non-sensitive alias. We hold them for the account lifetime plus a thirty-day grace interval, then transmit deletion commands to the processor and wipe our own mapping. The only trace left behind is an anonymised transaction hash used in aggregate statements, themselves removed after seven years. No usable credentials ever sit on our systems. We monitor token revocation daily and initiate incidents if deletion does not work. Tokens are linked to our merchant code and cannot be used in other contexts. Weekly reconciliation validates validity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are recorded and checked. Aggregate reports never reveal individual transaction hashes.
Account Registration and Identity Verification Data
Main identity data—official ID scans, proof of address, biometric selfie matches—are retained for a five-year period after your final session or account closure, whichever is later. This encompasses statutory limitation periods and AML obligations. We retrieve only the essentials: document number, validity, country of citizenship. The full-resolution image gets destroyed upon extraction. Once five years pass, all original data is erased, but a hash of the verification result remains for two more years inside an audit log. Personal identity information sits encrypted at rest with AES-256-GCM, kept separate from analytics, and every access is logged for a three-year period. Optional fields like place of birth are discarded at verification stage to minimize the data footprint. Yearly reviews ensure accuracy and actively purge expired entries.
Document Upload and Biometric Data Processing
Submit an ID through our protected portal and automated validation wraps up within a minute and a half. We retrieve the document ID, validity, nationality, and a confidence score, then shred the high-resolution image immediately—it never touches disk. The original file stays in an memory buffer and is removed after analysis. A compacted, stamped small image is generated for auditing purposes and stored only for the identity verification period. That thumbnail lives in a write-once vault with strict controls and is never shared to client support. Collected information are secured and kept for the five-year-plus-two hash window. All operations runs on ISO 27001 certified UK servers, and every thumbnail access is logged permanently.
Specifics of Biometric Data
Liveness checks record a quick video solely in memory https://wanteddeadorwild.uk/. Images are analysed and discarded within milliseconds. Only a numerical vector of face features persists. This vector lacks any image data and cannot be reverse-engineered into a face. It is kept for the entire identity verification process and is irreversibly removed upon account termination or after 5 years. The numerical representation sits in a dedicated HSM with self-expiry and is never exported. Login comparisons happen inside the HSM’s safe environment without exposing the original vector. The data set is associated with a anonymous identifier unlinked from marketing data, which makes re-identifying extremely difficult. Even system administrators cannot see or recreate face characteristics from the kept numerical representation.
Infrastructure Setup and Data Location
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 maintain identical retention rules. We enforce least privilege with hardware MFA for administrators, recording their sessions in an immutable three-year audit trail. Multi-factor authentication combines a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor verifies automated purge schedules. Any deviation generates a Severity 1 incident, notified to our DPO within four hours. We also keep an air-gapped backup rotated weekly, under 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 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, 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.
Consent for Marketing and Communication Logs
We keep your consent record—timestamped, with IP address, and method-recorded—for the life of our relationship plus six years after revocation, to satisfy PECR requirements. Dispatch records for e-mails, push alerts, and SMS are kept for only thirteen months. Withdrawing consent instantly halts communications while retaining historical proof. A partitioned database ensures suppression without lag, and consent logs are held in a dedicated compliance archive. Send logs hold metadata only—topic, time stamp, state—not full message text. The six-year post-withdrawal period matches the statute of limitations for regulatory inquiries. Quarterly audits confirm no expired consents initiate mailings. We never tailor offers with gameplay or financial data beyond explicit permissions.