Data Storage Policy for Wanted Dead Or a Wild Slot Game in UK

Playing Wanted Dead Or a Wild Slot game means providing personal data https://wanteddeadorwild.uk. This document sets forth exactly how long we store it, why, and what technical protections sit behind each category—all based on 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 unique retention clock. Identity records are retained for five years after account closure. Financial logs stay for seven, meeting HMRC requirements. Gameplay data undergoes 24 months before anonymisation is applied. Full card numbers never enter our systems—only tokenised aliases—and every byte is protected. Independent auditors review our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log tracks every edit, and we give you 30 days’ notice before material changes are implemented. Subject access and deletion requests are processed within statutory deadlines.

Consent for Marketing and Communication Logs

We store your consent document—timestamped, IP-stamped, and method-captured—for the duration of our association plus six years after cancellation, to satisfy PECR obligations. Delivery logs for e-mails, push alerts, and SMS are retained for only thirteen months. Revoking consent right away blocks communications while preserving historical proof. A segmented database guarantees suppression without delay, and consent logs are stored in a separate compliance archive. Dispatch records hold metadata only—topic, time stamp, condition—not full message content. The six-year post-withdrawal period reflects the statute of limitations for regulatory probes. Quarterly audits verify no expired consents activate mailings. We never personalise offers with gameplay or financial data beyond explicit permissions.

Account Registration and Verification of Identity Data

Core identity profiles—government ID scans, address verification, biometric selfie matches—are held for 5 years after your final session or closure of account, whichever comes later. This encompasses contractual time limits and AML obligations. We extract only the necessary details: ID number, expiry, country of citizenship. The full-resolution image gets deleted immediately after extraction. Once 5 years pass, all source data is purged, but a encrypted hash of the verification data lives on for an additional two years inside an audit trail. Personal identity information sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every access is logged for a three-year period. Unnecessary fields like birth location are removed at verification stage to reduce the data footprint. Yearly audits confirm accuracy and actively purge outdated records.

File Upload and Biometric Data Processing

Provide an ID through our protected portal and automated validation completes within a minute and a half. We extract the document ID, expiration date, nationality, and a confidence score, then shred the original image instantly—it never reaches storage. The original file stays in an memory buffer and is removed after processing. A compacted, marked preview is generated for compliance purposes and stored only for the identity verification period. That thumbnail lives in a write-once storage with rigorous controls and is never exposed to customer support. Collected information are encrypted and kept for the five-year-plus-two hash window. All handling runs on UK-based ISO 27001 servers, and every small image access is logged permanently.

Biometric Information Details

Liveness verifications collect a short video stream completely in memory. Images are analysed and deleted within a few milliseconds. Only a numerical vector of face features survives. This data set lacks any image data and cannot be reverse-engineered into a picture. It is kept for the time of identity verification and is purged irrevocably upon account closure or after five years. The vector sits in a hardware security module with automatic expiration and is never transferred. Authentication checks happen inside the HSM’s safe environment without revealing the raw vector. The data set is bound to a anonymous identifier unlinked from marketing data, which makes re-identifying very hard. Even IT admins are unable to view or reconstruct facial features from the stored vector.

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 never 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 ibisworld.com automated purging runs cleanly, with monthly deletion runs audited by auditors. Tokenised card references stay valid only while your account is open and are wiped within thirty days of closing. Aggregated, anonymised totals persist for financial reporting without any personal identifiers. All financial data is secured and isolated from marketing systems.

Secured Payment Instruments and Processor References

Payment gateways create vaulted tokens that associate your card to a non-sensitive reference. We store them for the account lifetime plus a thirty-day grace window, then send deletion commands to the processor and clear 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 exist on our systems. We check token revocation daily and raise incidents if deletion fails. Tokens are linked to our merchant code and cannot be used elsewhere. Weekly reconciliation confirms validity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are logged and verifiable. Aggregate reports never reveal individual transaction hashes.

Technology Framework and Data Storage

All data sits 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 synchronizes every six hours. Backups are encrypted client-side and adhere to 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 uses a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor validates automated purge schedules. Any deviation generates a Severity 1 incident, notified to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, following the same deletion policies.

Encryption Key Lifecycle Management

Master keys are renewed every 90 days automatically inside an HSM. New keys are not extracted 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, do not 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 ensure forensic decryption works when needed. No plaintext key material ever departs the HSM boundary.

Essential Definitions and Extent of Personal Data

We cast a wide net on what qualifies 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 includes 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 cover live databases, archives, https://en.wikipedia.org/wiki/Online_skill-based_game 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 stay aligned with regulatory guidance.

Policy Assessment and Breach Notification Protocols

We assess this policy every six months or upon material change to the game or regulation. Reviews are documented 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 alert 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 hold 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 Versioning and Update Log

We keep 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 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 reflects our commitment to accountable data governance.

Session Gameplay and Behavioural Analytics Data

Every spin on Wanted Dead Or a Wild records 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 utilized 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 remain for 12 months before merging into a global model. RNG seed audit trails receive 36 months. Error diagnostics have 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 integrated into global model
Error and crash diagnostic logs: 90 days, then rotated out

Data Subject Access Request and Deletion Workflows

Upon receiving an SAR, we compile 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, provided 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 generate 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 documented immutably for five years.

Safe Gambling and Player Ban Registers

Deposit limits, reality checks, and timeout settings are stored for your account’s lifetime and never removed while it remains active. If you choose to ban yourself, your hashed identity and device fingerprints are placed into a specific exclusion register maintained permanently under UKGC licence requirements. The register is coded separately, checked only at login or registration, and never employed for analytics. Entry is restricted to educated compliance staff, and all searches are recorded 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. If not, it is kept everlasting. This retention is required and exempt from deletion requests.

Session Awareness and Play Time Restriction Enforcement

Reality check counters use transient session counters that restart every 24 hours, beginning again 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. Changing the interval mid-session sets the new value immediately for the next reminder. These settings are removed only upon verified account deletion. Session timer data resides in a specialized, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for precision. All timer configurations are auditable through the same three-year access log standard. We never analyze or advertise based on these settings.