Playing Wanted Dead Or a Wild Slot means providing personal data https://wanteddeadorwild.uk/. This document sets forth exactly how long we store it, the rationale, and what technical protections support 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 own retention clock. Identity records are kept for five years after account closure. Financial logs are stored for seven, satisfying HMRC requirements. Gameplay data gets 24 months before anonymisation takes effect. Full card numbers never reach our systems—only tokenised aliases—and every byte is secured. Independent auditors review 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 take effect. Subject access and deletion requests are managed within statutory deadlines.
Core Definitions and Extent of Personal Data
We adopt a comprehensive approach 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 covers 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 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 span 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 keep pace with regulatory guidance.
Account Registration and Identity Verification Data
Core identity profiles—scans of government IDs, proof of address, biometric selfie verifications—are held for a five-year period after your last session or account termination, whichever occurs later. This includes statutory limitation periods and anti-money laundering responsibilities. We retrieve only the necessary details: document ID, validity, nationality. The full-resolution image gets destroyed right after extraction. Once 5 years pass, all raw data is purged, but a encrypted hash of the verification outcome lives on for two more years inside an audit log. Identification data sits encrypted in storage with AES-256-GCM, isolated from analytics, and every access is tracked for three years. Unnecessary fields like birth location are discarded at the time of verification to minimize the data size. Annual reviews ensure precision and proactively delete expired data.
Uploading Documents and Biometric Data Processing
Submit an ID through our secure portal and automatic verification completes within ninety seconds. We extract the ID number, expiry, country of citizenship, and a trust score, then delete the high-resolution image instantly—it never reaches storage. The initial file stays in an temporary memory and vanishes after processing. A compacted, stamped thumbnail is produced for compliance purposes and kept only for the identity lifecycle. That preview lives in a write-once storage with strict controls and is never exposed to support staff. Collected information are encoded and kept for the 5-year-plus-2-year hash period. All operations runs on ISO 27001 certified UK servers, and every small image access is logged permanently.
Biometric Data Specifics
Liveness checks collect a quick video solely in memory. Video frames are analysed and discarded within milliseconds. Only a data vector of face features remains. This vector has no image data and cannot be reconstructed into a picture. It stays for the duration of identity verification and is irreversibly removed upon account termination or after 5 years. The numerical representation sits in a dedicated HSM with automatic expiration and is never exported. Login verifications happen inside the HSM’s protected enclave without exposing the raw vector. The numerical representation is linked to a anonymous identifier separated from advertising profiles, which makes reidentification extremely difficult. Even system administrators cannot see or reconstruct facial features from the saved data.
Safe Gambling and Voluntary Exclusion Registers
Stake limits, reality checks, and timeout settings are kept for your account’s entire duration and never purged while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints enter a specialized exclusion register kept permanently under UKGC licence requirements. The register is secured separately, accessed only at login or registration, and never utilized for analytics. Access is confined to educated compliance staff, and all searches are recorded for three years. The register holds only identity blocks—no monetary or gameplay records. We check it annually to fix errors and remove deceased individuals. If not, it is kept permanent. This retention is required and free from deletion requests.
Session Awareness and Session Limit Enforcement
Reality check timers use temporary session counters that reset every 24 hours, beginning again from your first spin after midnight. Your chosen interval—say, 30 minutes—is saved persistently and instantly reactivates when you visit again, even after a long break. Modifying the interval mid-session applies the new value instantly for the next reminder. These settings are deleted only upon confirmed account deletion. Session timer data sits 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 checkable through the same three-year access log standard. We at no time analyze or advertise based on these settings.
Monetary Transaction and Settlement Records
Deposit, withdrawal, and wager histories are kept for seven years from the transaction date, per HMRC and FCA rules. We seldom store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised alias. Chargeback disputes halt the contested record until final settlement, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs audited by auditors. Tokenised card references are valid only while your account is live and are deleted within thirty days of termination. Combined, anonymised totals remain for financial reporting without any personal identifiers. All financial data is encrypted and isolated from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways generate vaulted tokens that map your card to a non-sensitive alias. We hold them for the account lifetime plus a thirty-day grace window, then send deletion commands to the processor and erase our own reference. The only remnant left behind is an anonymised transaction hash used in aggregate reports, themselves removed after seven years. No usable credentials ever reside 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 elsewhere. Weekly reconciliation confirms validity, and tokens tied to lost or stolen cards are revoked immediately. All token operations are logged and checked. Aggregate reports never reveal individual transaction hashes.
SAR and Deletion Processes
When an SAR lands, we compile a organized 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, delivered via a one-time secure link that expires in 72 hours. For deletion, we cascade: immediate account suppression and token revocation, then queued erasure of all personal data not subject to legal hold. We generate a confirmation report specifying erased versus retained categories and their justifications. This report is kept as auditable proof for as long as the longest surviving data category. All requests are documented immutably for five years.
Marketing Consent and Message Logs
We store your consent document—time-stamped, with IP address, and method-recorded—for the entirety of our association plus six years after cancellation, to comply with PECR obligations. Delivery logs for electronic messages, push messages, and SMS are retained for only thirteen months. Cancelling consent right away halts communications while preserving historical proof. A divided database guarantees suppression without lag, and consent logs are stored in a separate compliance archive. Delivery logs include metadata only—topic, timestamp, state—not full message body. The six-year post-withdrawal timeframe reflects the statute of limitations for regulatory probes. Quarterly audits check no expired consents activate mailings. We never personalise offers with gameplay or financial data beyond explicit permissions.
Gameplay Session and Behavioural Analytics Data
All spins on Wanted Dead Or a Wild logs reel positions, RNG seed, and net outcome with microsecond precision. We store 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—stay 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 have 36 months. Error diagnostics have 90 days. No individual gameplay data goes 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 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 removed
Technical Infrastructure and Data Storage
All data resides 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 maintain 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 occur quarterly, and an independent auditor confirms 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 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 deleted 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 demands dual control and is stored on write-once media in a fireproof safe. Annual recovery drills confirm forensic decryption works when needed. No plaintext key material ever departs the HSM boundary.
Policy Review and Data Breach Protocols
We evaluate 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 sent 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 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 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 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 confirm 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 demonstrates our commitment to accountable data governance.