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

Playing Slot Wanted Dead Or A Wild Gambling game means submitting personal data. This document lays out exactly how long we keep it, the reasons, and what technical protections support each category—all aligned with 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 own retention clock. Identity records stick around for five years after account closure. Financial logs are stored for seven, meeting HMRC requirements. Gameplay data gets 24 months before anonymisation takes effect. Full card numbers never enter our systems—only tokenised aliases—and every byte is protected. Independent auditors verify our automated deletion routines, and any schedule slip activates a full incident response. A version-controlled policy log documents every edit, and we provide you 30 days’ notice before material changes take effect. Subject access and deletion requests are processed within statutory deadlines.

Account Registration and Identity Verification Data

Core identity profiles—scans of government IDs, address verification, biometric selfie matches—are held for five years after your last session or account termination, whichever is later. This includes contractual time limits and anti-money laundering responsibilities. We obtain only the essentials: document ID, expiration date, country of citizenship. The original image gets deleted right after extraction. Once 5 years pass, all original data is purged, but a hash of the verification outcome remains for two more years inside an logging system. Identification data sits encrypted at rest with AES-256-GCM, stored away from analytics, and every data access is recorded for three years. Non-essential fields like birthplace are discarded at verification time to reduce the data volume. Yearly reviews ensure precision and proactively delete expired data.

File Upload and Biometric Processing

Upload an ID through our safe portal and automated checking finishes within 90 seconds. We retrieve the document number, expiry, citizenship, and a trust score, then delete the original image immediately—it never touches disk. The original file stays in an temporary memory and disappears after analysis. A compacted, stamped preview is produced for audit purposes and retained only for the ID lifecycle. That small image lives in a immutable vault with strict controls and is never exposed to support staff. Retrieved data are encrypted and saved for the 5-year-plus-2-year hash period. All operations runs on UK-based ISO 27001 servers, and every small image access is stored unchangeably.

Specifics of Biometric Data

Live detection checks capture a short video stream solely in memory. Frames are analysed and removed within milliseconds of time. Only a mathematical vector of facial landmarks remains. This data set lacks any image data and cannot be turned back into a face. It is kept for the duration of identity verification and is permanently deleted upon closure of account or after five years. The data set sits in a dedicated HSM with auto-expiry and is never transferred. Authentication checks happen inside the HSM’s protected enclave without exposing the raw vector. The data set is linked to a pseudonym unlinked from marketing profiles, which makes re-identifying extremely difficult. Even IT admins cannot see or recreate facial attributes from the kept numerical representation.

Consent for Marketing and Communication Logs

We maintain your consent document—time-stamped, with IP address, and method-captured—for the duration of our association plus six years after revocation, to satisfy PECR rules. Delivery logs for electronic messages, push messages, and SMS are retained for only thirteen months. Withdrawing consent immediately suppresses communications while keeping historical proof. A segmented database ensures suppression without latency, and consent logs are kept in a separate compliance archive. Send logs hold metadata only—subject, time, status—not full message content. The six-year post-withdrawal window reflects the statute of limitations for regulatory inquiries. Quarterly audits verify no expired consents trigger mailings. We never customise offers with gameplay or financial data beyond explicit permissions.

Access Request and Erasure Workflows

When a subject access request arrives, we generate a structured JSON/CSV export of all non-purged data within one month, expandable by two months for complex cases. The export includes live databases, encrypted archives, and processor tokens, delivered via a one-time secure link that expires in 72 hours. For deletion, we implement a cascade: immediate account suppression and token revocation, then queued 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 maintained as auditable proof for as long as the longest surviving data category. All requests are logged immutably for five years.

Payment Transaction and Billing 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 reference. Chargeback disputes halt the contested record until final resolution, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs verified by auditors. Tokenised card references remain valid only while your account is open and are erased within thirty days of termination. Combined, anonymised totals endure for financial reporting without any personal information. All financial data is coded and quarantined from marketing systems.

Secured Payment Instruments and Processor References

Payment gateways generate vaulted tokens that link your card to a non-sensitive alias. We keep them for the account lifetime plus a thirty-day grace interval, then transmit deletion commands to the processor and clear our own mapping. The only evidence left behind is an anonymised transaction hash used in aggregate statements, themselves deleted after seven years. No usable credentials ever reside on our systems. We track token revocation daily and raise incidents if deletion is unsuccessful. Tokens are linked to our merchant code and cannot be used in other contexts. Weekly reconciliation validates correctness, and tokens tied to lost or stolen cards are revoked immediately. All token operations are recorded and verifiable. Aggregate reports never expose individual transaction hashes.

Responsible Gambling and Self-Exclusion Registers

Betting limits, time checks, 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 dedicated exclusion register held without time limit under UKGC licence requirements. The register is encrypted separately, queried only at login or registration, and never used for analytics. Permission is restricted to qualified compliance staff, and all lookups are tracked for three years. The register stores only identity blocks—no banking or gameplay records. We check it annually to rectify errors and remove deceased individuals. Apart from that, it remains indefinite. This retention is required and exempt from deletion requests.

Session Awareness and Session Limit Enforcement

Reality check clocks use short-lived session counters that reset every 24 hours, beginning again from your first spin after midnight. Your preferred interval—say, 30 minutes—is saved persistently and instantly reactivates when you visit again, even after a long break. Changing the interval mid-session applies the new value right away for the next reminder. These settings are removed only upon validated account deletion. Session timer data resides 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 never analyze or promote based on these settings.

Essential Definitions and Range of Personal Data

We cast a wide net on what constitutes 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 re-identify 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 begins counting from the last activity or transaction date, spelled out below. We revisit definitions every six months to remain compliant with regulatory guidance.

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 retain these raw logs for twenty-four months, then condense 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 remain 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 anonymized aggregation
• Session behavioural profiles: 24 months from last session, then erased
• RNG seed audit trails: 36 months to meet technical standards
• Feature trigger heatmaps: 12 months, then combined into global model
• Error and crash diagnostic logs: 90 days, then removed

Technology Framework and Data Location

All data is stored 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 adhere to 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 run quarterly, and an independent auditor verifies automated purge schedules. Any deviation triggers a Severity 1 incident, notified to our DPO within four hours. We also keep an air-gapped backup rotated weekly, following the same deletion policies.

Management of Encryption Keys

Master keys change 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 removed inside the HSM, making any backups unrecoverable. We assign 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 ensure forensic decryption works when needed. No plaintext key material ever departs the HSM boundary.

Policy Review and Incident Reporting Protocols

We assess 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 sent 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 keep a breach notification log audited quarterly. Post-incident reviews revise controls as needed. Biannual tabletop exercises test misconfigurations and ransomware to test our response.

Policy Versioning and Change Log

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 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 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 shows our commitment to accountable data governance.