Data Storage Policy for Wanted Dead Or a Wild Slot in the United Kingdom

Playing Wanted Dead Or a Wild Slot means handing over personal data. This document lays out exactly how long we retain it, why, and what technical protections sit behind each category—all built around UK GDPR, the Data Protection Act 2018, and PCI DSS. We manage identity documents, financial transactions, gameplay telemetry, responsible gambling markers, and marketing consents, each with its own retention clock. Identity records are retained 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 reach our systems—only tokenised aliases—and every byte is secured. 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 offer you 30 days’ notice before material changes are implemented. Subject access and deletion requests are managed within statutory deadlines.

Essential 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—sit alongside 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 identify again 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 cover 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.

Registration Account and Verification of Identity Data

Primary identity records—official ID scans, address verification, biometric selfie matches—are held for a five-year period after your final session or account closure, whichever occurs later. This includes statutory limitation periods and anti-money laundering responsibilities. We obtain only the essentials: ID number, expiry, citizenship. The original image gets destroyed right after extraction. Once 5 years pass, all source data is removed, but a hash of the verification outcome persists for another two years inside an audit trail. Personal identity information sits stored encrypted with AES-256-GCM, kept separate from analytics, and every data access is logged for three years. Unnecessary fields like place of birth are removed at verification stage to shrink the data size. Annual reviews confirm precision and proactively delete outdated records.

Uploading Documents and Biometric Data Processing

Submit an ID through our protected portal and automated checking wraps up within a minute and a half. We extract the document ID, validity, country of citizenship, and a confidence score, then destroy the full-resolution image right away—it is never stored on disk. The initial file stays in an in-memory buffer and disappears after handling. A compacted, marked preview is generated for auditing purposes and retained only for the identity lifecycle. That preview lives in a write-once storage with rigorous controls and is never shared to client support. Extracted fields are encoded and stored for the 5-year-plus-2-year hash period. All processing runs on ISO 27001 certified UK servers, and every thumbnail access is recorded immutably.

Biometric Data Specifics

Liveness verifications collect a brief video feed solely in memory. Images are processed and discarded within a few milliseconds. Only a mathematical vector of facial points remains. This vector contains no image data and cannot be reconstructed into a facial image. It stays for the time of identity verification and is purged irrevocably upon account closure or after five years. The vector sits in a dedicated HSM with self-expiry and is never transferred. Authentication checks happen inside the HSM’s protected enclave without disclosing the raw vector. The data set is linked to a pseudonym separated from marketing data, which makes reidentification highly challenging. Even system administrators cannot see or recreate face characteristics from the saved data.

Controlled Gambling and Self-Exclusion Registers

Stake limits, session reminders, and timeout settings are saved for your account’s lifetime and never removed while it stays active. If you opt for self-exclusion, your hashed identity and device fingerprints enter a specialized exclusion register held permanently under UKGC licence requirements. The register is secured separately, accessed only at login or registration, and never used for analytics. Entry is restricted to trained compliance staff, and all searches are logged for three years. The register holds only identity blocks—no banking or gameplay records. We review it annually to rectify errors and remove deceased individuals. Apart from that, it is kept indefinite. This retention is obligatory and free from deletion requests.

Session Awareness and Session Limit Enforcement

Reality check counters use temporary session counters that restart every 24 hours, beginning again from your first spin after midnight. Your chosen interval—say, 30 minutes—is stored persistently and instantly reactivates when you visit again, even after a long break. Altering the interval mid-session sets the new value immediately for the next reminder. These settings are purged only upon confirmed 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 correctness. All timer configurations are auditable through the same three-year access log standard. We do not profile or promote based on these settings.

Gaming Session and Behavioural Analytics Data

Each spin on Wanted Dead Or a Wild logs 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 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 stay 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 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 anonymised 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 merged into global model
• Error and crash diagnostic logs: 90 days, then rotated out

Consent for Marketing and Message Logs

We maintain your consent record—with time stamp, IP-marked, and with capture method—for the life of our association plus six years after revocation, to comply with PECR obligations. Send logs for emails, push messages, and SMS are kept for only thirteen months. Withdrawing consent instantly blocks communications while retaining historical proof. A segmented database guarantees suppression without delay, and consent logs are stored in a dedicated compliance archive. Send logs include metadata only—topic, time, condition—not full message text. The six-year post-withdrawal period reflects the statute of limitations for regulatory inquiries. Quarterly audits confirm no expired consents trigger mailings. We never customise offers with gameplay or financial data beyond explicit authorisations.

Monetary Transaction and Settlement Records

Deposit, withdrawal, and wager logs are retained for seven years from the transaction date, per HMRC and FCA rules. We seldom store full PANs or CVVs. We capture 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 restarts. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs audited by auditors. Tokenised card references are valid only while your account is live and are erased within thirty days of termination. Summarised, anonymised totals endure for financial reporting without any personal details. All financial data is secured and isolated from marketing systems.

Secured Payment Instruments and Processor References

Payment gateways produce vaulted tokens that map your card to a non-sensitive alias. We store them for the account lifetime plus a thirty-day grace window, then transmit deletion commands to the processor and clear our own reference. The only remnant left behind is an anonymised transaction hash used in aggregate summaries, themselves purged after seven years. No usable credentials ever reside on our systems. We check token revocation daily and initiate incidents if deletion fails. Tokens are tied to our merchant code and cannot be used in other contexts. Weekly reconciliation validates authenticity, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are recorded and auditable. Aggregate reports never reveal individual transaction hashes.

SAR and Deletion Processes

When a subject access request arrives, we produce a structured JSON/CSV export of all non-purged data within one month, extendable by two months for complex cases https://wanteddeadorwild.uk/. The export covers live databases, encrypted archives, and processor tokens, provided 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 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 logged immutably for five years.

Infrastructure Setup and Data Residency

All data sits 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 follow 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 run quarterly, and an independent auditor validates automated purge schedules. Any deviation triggers a Severity 1 incident, alerted 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 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 destroyed inside the HSM, making any backups unrecoverable. We link 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 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 leaves the HSM boundary.

Policy Review and Breach Notification 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 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 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 simulate misconfigurations and ransomware to test our response.

Policy Version Control and Update Log

We keep 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 check 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.