Playing Wanted Dead Or a Wild Slot game means submitting personal data wanteddeadorwild.uk. This document lays out exactly how long we keep it, why, and what technical protections sit behind each category—all based on 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 specific retention clock. Identity records are kept for five years after account closure. Financial logs are stored for seven, matching HMRC requirements. Gameplay data receives 24 months before anonymisation is applied. 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 triggers a full incident response. A version-controlled policy log documents every edit, and we offer you 30 days’ notice before material changes are implemented. Subject access and deletion requests are handled within statutory deadlines.
Fundamental Definitions and Extent of Personal Data
We take a broad view 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 encompasses 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 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 cover live databases, archives, and backups without exception. Each window begins counting from the last activity or transaction date, spelled out below. We reassess definitions every six months to stay aligned with regulatory guidance.
Access Request and Erasure Workflows
Upon receiving an SAR, we produce a structured JSON/CSV export of all non-purged data within one month, expandable 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 cascade: immediate account suppression and token revocation, then batched erasure of all personal data not subject to legal hold. We create a confirmation report specifying 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.
Responsible Gambling and Self-Exclusion Registers
Stake limits, session reminders, and timeout settings are kept for your account’s entire duration and never removed while it is active. If you self-exclude, your hashed identity and device fingerprints enter a dedicated exclusion register held indefinitely under UKGC licence requirements. The register is coded separately, checked only at login or registration, and never utilized for analytics. Permission is confined to qualified compliance staff, and all queries are tracked for three years. The register contains only identity blocks—no banking or gameplay records. We review it annually to correct errors and remove deceased individuals. If not, it is kept permanent. This retention is required and excluded from deletion requests.
Reality Check and Session Limit Enforcement

Reality check counters use transient session counters that restart every 24 hours, starting anew from your first spin after midnight. Your chosen interval—say, 30 minutes—is kept persistently and automatically reactivates when you come back, even after a long break. Changing the interval mid-session sets the new value instantly for the next reminder. These settings are purged only upon verified 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 correctness. All timer configurations are checkable through the same three-year access log standard. We at no time profile or market based on these settings.
Registration Account and Identity Verification Data
Main identity data—official ID scans, proof of address, selfie biometric matches—are kept for five years after your last session or closure of account, whichever is later. This includes contractual time limits and anti-money laundering duties. We obtain only the key information: document ID, validity, nationality. The high-resolution image gets deleted right after extraction. Once the five-year period pass, all source data is erased, but a encrypted hash of the verification outcome lives on for two more years inside an logging system. Identity data sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every access is tracked for three years. Non-essential fields like birth location are removed at the time of verification to minimize the data volume. Annual reviews confirm precision and proactively delete expired data.
Uploading Documents and Biometric Data Processing
Submit an ID through our safe portal and automatic verification completes within a minute and a half. We pull the document number, validity, country of citizenship, and a reliability score, then destroy the original image instantly—it never touches disk. The original file stays in an in-memory buffer and disappears after processing. A compacted, watermarked small image is created for audit purposes and kept only for the ID lifecycle. That small image lives in a write-once vault with strict controls and is never shown to support staff. Retrieved data are secured and saved for the five-year plus two-year hash timeframe. All operations runs on UK-based ISO 27001 servers, and every preview retrieval is stored unchangeably.
Biometric Data Specifics
Live detection checks capture a quick video entirely in memory. Frames are analyzed and deleted within a few milliseconds. Only a data vector of face features remains. This data set has no image data and cannot be turned back into a facial image. It is kept for the time of identity verification and is permanently deleted upon account termination or after five years. The vector sits in a dedicated HSM with automatic expiration and is never transferred. Login comparisons happen inside the HSM’s secure enclave without exposing the raw vector. The numerical representation is bound to a pseudonymous identifier disconnected from marketing profiles, which makes re-identification highly challenging. Even IT admins are unable to view or recreate facial attributes from the kept numerical representation.
Technical Infrastructure and Data Storage
All data is stored in UK-based ISO 27001 Tier III+ data centres, with no replication outside the UK. A hot crunchbase.com disaster recovery site in a separate UK zone updates every six hours. Backups are encrypted client-side and adhere to identical retention rules. We apply least privilege with hardware MFA for administrators, capturing 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 validates 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, following the same deletion policies.
Key Lifecycle Administration
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 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 guarantee forensic decryption works when needed. No plaintext key material ever exits the HSM boundary.
Monetary Transaction and Settlement Records
Funding, withdrawal, and wager records are retained for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised reference. Chargeback disputes suspend the contested record until final settlement, after which the seven-year clock continues. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs verified by auditors. Tokenised card references stay valid only while your account is open and are deleted within thirty days of closure. Combined, anonymised totals persist for financial reporting without any personal information. All financial data is secured and quarantined from marketing systems.

Secured Payment Instruments and Processor References
Payment gateways create vaulted tokens that link your card to a non-sensitive identifier. We keep them for the account lifetime plus a thirty-day grace interval, then transmit deletion commands to the processor and erase our own mapping. The only trace left behind is an anonymised transaction hash used in aggregate reports, themselves purged after seven years. No usable credentials https://www.crunchbase.com/organization/bingosoft ever exist on our systems. We track token revocation daily and trigger incidents if deletion does not work. Tokens are bound to our merchant code and cannot be used elsewhere. Weekly reconciliation verifies validity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are documented and verifiable. Aggregate reports never expose individual transaction hashes.
Gameplay Session and Analytics of Behavior 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 compact 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 persist for 12 months before merging into a global model. RNG seed audit trails get 36 months. Error diagnostics receive 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 erased
- 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 cycled out
Marketing Approval and Correspondence Records
We store your consent log—timestamped, IP-marked, and method-captured—for the entirety of our relationship plus six years after withdrawal, to satisfy PECR requirements. Send logs for emails, push alerts, and SMS are kept for only thirteen months. Withdrawing consent instantly suppresses communications while retaining historical proof. A segmented database provides suppression without latency, and consent logs are kept in a dedicated compliance archive. Dispatch records contain metadata only—heading, timestamp, state—not full message content. The six-year post-withdrawal period matches the statute of limitations for regulatory inquiries. Quarterly audits check no expired consents initiate mailings. We never customise offers with gameplay or financial data beyond explicit permissions.
Policy Assessment and Incident Reporting 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 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 notify affected individuals within 72 hours if high risk, submit with the ICO, and publish a transparency notice. Third-party processor breaches must follow the same protocol. We hold a breach notification log audited quarterly. Post-incident reviews update controls as needed. Biannual tabletop exercises test misconfigurations and ransomware to test our response.
Policy Version Control 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 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 reflects our commitment to accountable data governance.





