Playing Wanted Dead Or a Wild Slot game means submitting personal data. This document sets forth exactly how long we store it, the rationale, and what technical protections support each category—all built around 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 specific retention clock. Identity records stick around for five years after account closure. Financial logs are stored 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 encrypted. Independent auditors check our automated deletion routines, and any schedule slip triggers a full incident response. A version-controlled policy log tracks every edit, and we give you 30 days’ notice before material changes become effective. Subject access and deletion requests are handled within statutory deadlines.

Data Subject Access Request and Deletion Workflows

Upon receiving an SAR, we produce a organized JSON/CSV export of all non-purged data within one month, prolongable by two months for complex cases. The export spans 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 scheduled 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 maintained as auditable proof for as long as the longest surviving data category. All requests are documented immutably for five years.

Safe Gambling and Player Ban Registers

Betting limits, session reminders, and timeout settings are kept for your account’s whole period and never removed while it remains active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a dedicated exclusion register held without time limit under UKGC licence requirements. The register is encrypted separately, accessed only at login or registration, and never used for analytics. Permission is restricted to qualified compliance staff, and all queries are recorded for three years. The register contains only identity blocks—no financial or gameplay records. We check it annually to correct errors and remove deceased individuals. Otherwise, it stays everlasting. This retention is obligatory and exempt from deletion requests.

Time Check and Session Limit Enforcement

Reality check timers use temporary session counters that clear every 24 hours, beginning again from your first spin after midnight. Your selected interval—say, 30 minutes—is saved persistently and routinely reactivates when you visit again, even after a long break. Changing the interval mid-session introduces the new value instantly for the next reminder. These settings are deleted only upon verified account deletion. Session timer data resides 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 checkable through the same three-year access log standard. We never profile or promote based on these settings.

Technical Infrastructure and Data Residency

All data is stored in UK-based ISO 27001 Tier III+ data centres, not copied outside the UK. A hot disaster recovery site in a separate UK zone syncs 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 triggers 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.

Key Lifecycle Administration

Master keys change 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 deleted inside the HSM, making any backups unrecoverable. We assign 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 needs 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 exits the HSM boundary.

Consent for Marketing and Communication Logs

We maintain your consent log—time-stamped, IP-stamped, and with capture method—for the duration of our association plus six years after revocation, to comply with PECR requirements. Send logs for electronic messages, push alerts, and SMS are held for only thirteen months. Revoking consent instantly suppresses communications while retaining historical proof. A segmented database provides suppression without latency, and consent logs are held in a separate compliance archive. Delivery logs hold metadata only—subject, time, status—not full message text. The six-year post-withdrawal period reflects the statute of limitations for regulatory probes. Quarterly audits check no expired consents trigger mailings. We never customise offers with gameplay or financial data beyond explicit consents.

Account Registration and Verification of Identity Data

Primary identity records—scans of government IDs, address verification, selfie biometric matches—are kept for five years after your last session or account termination, whichever comes later. This encompasses contractual limitation periods and AML obligations. We retrieve only the essentials: document number, expiration date, country of citizenship. The high-resolution image gets shredded immediately after extraction. Once the five-year period pass, all original data is removed, but a cryptographic hash of the verification result remains for another two years inside an logging system. Identification data sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every data access is recorded for 3 years. Non-essential fields like birth location are removed at verification stage to minimize the data footprint. Yearly reviews verify correctness and automatically remove outdated records.

Uploading Documents and Biometric Data Processing

Submit an ID through our protected portal and automatic verification finishes within a minute and a half. We extract the document ID, validity, nationality, and a confidence score, then destroy the original image instantly—it never touches disk. The source file stays in an temporary memory and is removed after handling. A compacted, watermarked thumbnail is produced for auditing purposes and stored only for the identity lifecycle. That thumbnail lives in a write-once vault with rigorous controls and is never shown to customer support. Extracted fields are encoded and stored for the 5-year-plus-2-year hash period. All operations runs on ISO 27001 certified UK servers, and every preview retrieval is logged permanently.

Biometric Data Specifics

Live detection checks capture a short video stream completely in memory. Frames are analyzed and discarded within milliseconds of time. Only a data vector of facial points remains. This data set has no image data and cannot be reconstructed into a picture. It is kept for the duration of identity verification and is permanently deleted upon account termination or after five years. The vector sits in a dedicated HSM with self-expiry and is never sent out. Authentication checks happen inside the HSM’s secure enclave without revealing the raw vector. The numerical representation is bound to a anonymous identifier unlinked from advertising profiles, which makes re-identifying highly challenging. Even system administrators cannot view or rebuild facial features from the stored vector.

Payment Transaction and Payment Records

Funding, withdrawal, and wager histories are maintained for seven years from the transaction date, per HMRC and FCA rules. We seldom store full PANs or CVVs. We collect 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 resumes. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs verified by auditors. Tokenised card references remain valid only while your account is live and are wiped within thirty days of termination. Summarised, anonymised totals remain for financial reporting without any personal identifiers. All financial data is encrypted and separated from marketing systems.

Tokenized Payment Instruments and Processor References

Payment gateways produce vaulted tokens that associate 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 erase our own reference. The only remnant left behind is an anonymised transaction hash used in aggregate reports, themselves deleted after seven years. No usable credentials ever sit on our systems. We track token revocation daily and raise incidents if deletion fails. Tokens are linked to our merchant code and cannot be used other places. Weekly reconciliation confirms validity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are logged and checked. Aggregate reports never reveal individual transaction hashes.

Session Gameplay and Behavioural Analytics 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 compact them into an anonymous statistical digest utilized for game design. Session behavioural profiles—average bet, spin cadence, feature buy-ins—persist for the same 24-month window and are then deleted. Feature trigger heatmaps stay 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 merged into global model
• Error and crash diagnostic logs: 90 days, then removed

Core Definitions and Range of Personal Data

We cast a wide net on what constitutes personal data https://wanteddeadorwild.uk/. 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 link back to a person when stitched together, so we treat 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 revisit definitions every six months to remain compliant with regulatory guidance.

Policy Review 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 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, submit 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 Revision History

We preserve 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 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 confirm 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.