Playing Wanted Dead Or a Wild Slot game means handing over personal data https://wanteddeadorwild.uk/. This document details exactly how long we keep it, why, and what technical protections support each category—all based on UK GDPR, the Data Protection Act 2018, and PCI DSS. We process 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 remain for seven, satisfying HMRC requirements. Gameplay data receives 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 activates a full incident response. A version-controlled policy log documents every edit, and we give you 30 days’ notice before material changes are implemented. Subject access and deletion requests are handled within statutory deadlines.
Core Definitions and Range of Personal Data
We adopt a comprehensive approach 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 identify again a person when stitched together, so we regard 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 extend across live databases, archives, and backups without exception. Each window commences from the last activity or transaction date, spelled out below. We reassess definitions every six months to stay aligned with regulatory guidance.
Responsible Gambling and Self-Exclusion Registers
Deposit limits, reality checks, and timeout settings are kept for your account’s lifetime and never deleted while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a specific exclusion register maintained indefinitely under UKGC licence requirements. The register is coded separately, queried only at login or registration, and never utilized for analytics. Entry is restricted to qualified compliance staff, and all queries are logged for three years. The register holds only identity blocks—no banking or gameplay records. We examine it annually to fix errors and remove deceased individuals. Otherwise, it remains everlasting. This retention is obligatory and exempt from deletion requests.
Session Awareness and Session Limit Enforcement
Reality check clocks 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 instantly reactivates when you return, even after a long break. Changing the interval mid-session introduces the new value immediately for the next reminder. These settings are deleted only upon verified account deletion. Session timer data lies in a specific, 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 never analyze or market based on these settings.
User Account and Identity Verification Data
Core identity profiles—government ID scans, residence proof, biometric selfie matches—are kept for 5 years after your last activity or account closure, whichever is later. This encompasses contractual limitation periods and anti-money laundering duties. We obtain only the key information: document ID, expiration date, country of citizenship. The high-resolution image gets destroyed right after extraction. Once five years pass, all raw data is erased, but a hash of the verification data persists for another two years inside an audit log. Identity data sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every access is tracked for 3 years. Non-essential fields like birth location are deleted at verification stage to reduce the data footprint. Annual reviews confirm precision and proactively delete outdated records.
Document Upload and Biometric Handling
Upload an ID through our protected portal and automatic verification completes within 90 seconds. We retrieve the ID number, expiration date, nationality, and a reliability score, then destroy the high-resolution image right away—it never reaches storage. The source file stays in an in-memory buffer and disappears after handling. A compacted, stamped thumbnail is produced for auditing purposes and kept only for the ID lifecycle. That small image lives in a write-once vault with strict controls and is never exposed to customer support. Retrieved data are secured and saved for the 5-year-plus-2-year hash period. All handling runs on ISO 27001 certified UK servers, and every small image access is logged permanently.
Biometric Data Specifics
Liveness verifications collect a quick video solely in memory. Frames are processed and removed within milliseconds. Only a data vector of facial points survives. This data set contains no image data and cannot be reconstructed into a facial image. It stays for the time of identity verification and is irreversibly removed upon account termination or after five years. The data set sits in a dedicated HSM with auto-expiry and is never sent out. Authentication checks happen inside the HSM’s safe environment without disclosing the original vector. The vector is bound to a pseudonymous identifier separated from advertising profiles, which makes reidentification very hard. Even IT admins are unable to view or rebuild facial attributes from the kept numerical representation.
Access Request and Erasure Workflows
When an SAR lands, we generate a formatted JSON/CSV export of all non-purged data within one month, extendable by two months for complex cases. The export includes live databases, encrypted archives, and processor tokens, sent 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 produce a confirmation report specifying erased versus retained categories and their justifications. This report is maintained as auditable https://www.ibisworld.com/classifications/naics/721310/rooming-and-boarding-houses-dormitories-and-workers-camps proof for as long as the longest surviving data category. All requests are recorded immutably for five years.
Payment Transaction and Payment Records
Deposit, withdrawal, and wager records are maintained for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We collect only the BIN, last four digits, and a tokenised reference. Chargeback disputes freeze the contested record until final settlement, after which the seven-year clock restarts. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs verified by auditors. Tokenised card references stay valid only while your account is live and are erased within thirty days of closure. Summarised, anonymised totals endure for financial reporting without any personal information. All financial data is secured and separated from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways generate vaulted tokens that link your card to a non-sensitive identifier. We store them for the account lifetime plus a thirty-day grace window, then issue deletion commands to the processor and wipe our own link. The only trace left behind is an anonymised transaction hash used in aggregate reports, themselves deleted after seven years. No usable credentials ever exist on our systems. We check token revocation daily and trigger incidents if deletion fails. Tokens are tied to our merchant code and cannot be used other places. Weekly reconciliation confirms validity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are documented and checked. Aggregate reports never disclose individual transaction hashes.
Marketing Consent and Communication Logs
We keep your consent record—timestamped, IP-marked, and method-captured—for the entirety of our partnership plus six years after withdrawal, to meet PECR rules. Delivery logs for e-mails, push notifications, and SMS are kept for only thirteen months. Cancelling consent right away blocks communications while preserving historical proof. A segmented database ensures suppression without latency, and consent logs are stored in a distinct compliance archive. Dispatch records hold metadata only—topic, timestamp, state—not full message text. The six-year post-withdrawal window reflects the statute of limitations for regulatory investigations. Quarterly audits confirm no expired consents activate mailings. We never customise offers with gameplay or financial data beyond explicit authorisations.
Gaming Session and Analytics of Behavior Data
Each 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 condense them into an anonymous statistical digest used 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 persist for 12 months before merging into a global model. RNG seed audit trails get 36 months. Error diagnostics have 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 deleted
- RNG seed audit trails: 36 months to comply with technical standards
- Feature trigger heatmaps: 12 months, then integrated 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 syncs 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 uses a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor verifies automated purge schedules. Any deviation generates a Severity 1 incident, notified to our DPO within four hours. We also operate an air-gapped backup rotated weekly, under the same deletion policies.
Key Lifecycle Administration
Master keys rotate 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 destroyed 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 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 Evaluation and Data Breach Protocols
We evaluate 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 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, 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 adjust controls as needed. Biannual tabletop exercises model misconfigurations and ransomware to test our response.
Policy Versioning and Update Log
We maintain 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 access the full change log through a link in our privacy centre at any time. This transparent approach shows our commitment to accountable data governance.
