Playing Wanted Dead Or a Wild Slot means submitting personal data. This document lays out exactly how long we store it, why, and what technical protections support each category—all aligned with 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 unique retention clock. Identity records stick around for five years after account closure. Financial logs remain for seven, meeting HMRC requirements. Gameplay data gets 24 months before anonymisation is applied. Full card numbers never reach our systems—only tokenised aliases—and every byte is encrypted. Independent auditors verify our automated deletion routines, and any schedule slip activates a full incident response. A version-controlled policy log records every edit, and we offer you 30 days’ notice before material changes become effective. Subject access and deletion requests are processed within statutory deadlines.
Essential Definitions and Scope of Personal Data
We adopt a comprehensive approach on what constitutes 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 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 begins counting from the last activity or transaction date, spelled out below. We review definitions every six months to keep pace with regulatory guidance.
Registration Account and Identity Verification Data
Main identity data—government ID scans, residence proof, biometric selfie matches—are retained for five years after your final session or account termination, whichever comes later. This encompasses statutory limitation periods and anti-money laundering duties. We obtain only the necessary details: document ID, validity, country of citizenship. The original image gets deleted immediately after extraction. Once 5 years pass, all raw data is erased, but a encrypted hash of the verification outcome remains for another two years inside an audit log. Identification data sits stored encrypted with AES-256-GCM, kept separate from analytics, and every data access is tracked for 3 years. Non-essential fields like birth location are discarded at the time of verification to reduce the data size. Yearly audits verify correctness and automatically remove expired entries.
Uploading Documents and Biometric Processing
Submit an ID through our secure portal and automated checking wraps up within 90 seconds. We retrieve the document ID, expiry, nationality, and a confidence score, then shred the original image immediately—it is never stored on disk. The original file stays in an in-memory buffer and vanishes after handling. A compressed, watermarked preview is created for audit purposes and kept only for the identity verification period. That thumbnail lives in a write-once vault with rigorous controls and is never exposed to support staff. Extracted fields are encoded and kept for the five-year plus two-year hash timeframe. All operations runs on servers in the UK with ISO 27001, and every preview retrieval is recorded immutably.
Biometric Data Specifics
Live detection checks collect a short video stream solely in memory. Video frames are analysed and removed within milliseconds of time. Only a numerical vector of facial landmarks survives. This numerical representation contains no image data and cannot be turned back into a picture. It remains for the duration of identity verification and is purged irrevocably upon account closure or after a five-year period. The numerical representation sits in a dedicated HSM with automatic expiration and is never transferred. Login comparisons happen inside the HSM’s secure enclave without disclosing the original vector. The data set is bound to a pseudonymous identifier disconnected from marketing profiles, which makes re-identification highly challenging. Even system administrators cannot view or recreate facial attributes from the saved data.
Infrastructure Setup and Data Residency
All data sits in UK-based ISO 27001 Tier III+ data centres, not copied outside the UK. A hot disaster recovery site in a separate UK zone updates every six hours. Backups are encrypted client-side and maintain identical retention rules. We implement least privilege with hardware MFA for administrators, logging their sessions in an immutable three-year audit trail. Multi-factor authentication combines a hardware token and biometric check. Penetration tests are conducted quarterly, and an independent auditor confirms automated purge schedules. Any deviation triggers a Severity 1 incident, reported to our DPO within four hours. We also keep 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 kept internal 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 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 ensure forensic decryption works when needed. No plaintext key material ever exits the HSM boundary.
Session Gameplay and Analytics of Behavior Data
Every spin on Wanted Dead Or a Wild logs 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 utilized 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 stay 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 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 aggregated aggregation
- Session behavioural profiles: 24 months from last session, then removed
- 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 rotated out
Responsible Gambling and Self-Exclusion Registers
Betting limits, reality checks, and timeout settings are kept for your account’s entire duration and never deleted while it remains active. If you choose to ban yourself, your hashed identity and device fingerprints enter a dedicated exclusion register maintained permanently under UKGC licence requirements. The register is secured separately, accessed only at login or registration, and never employed for analytics. Access is restricted to educated compliance staff, and all queries are tracked for three years. The register holds only identity blocks—no banking or gameplay records. We review it annually to fix errors and remove deceased individuals. If not, it is kept indefinite. This retention is mandatory and exempt from deletion requests.
Time Check and Gaming Duration Enforcement
Reality check counters use transient session counters that restart every 24 hours, restarting from your first spin after midnight https://wanteddeadorwild.uk/. Your selected interval—say, 30 minutes—is saved persistently and routinely reactivates when you visit again, even after a long break. Altering the interval mid-session introduces the new value immediately for the next reminder. These settings are deleted only upon confirmed 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 precision. All timer configurations are auditable through the same three-year access log standard. We do not categorize or market based on these settings.
SAR and Deletion Processes
Upon receiving an SAR, we compile a formatted JSON/CSV export of all non-purged data within one month, prolongable by two months for complex cases. The export covers 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 scheduled erasure of all personal data not subject to legal hold. We produce a confirmation report outlining 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 logged immutably for five years.
Marketing Consent and Communication Logs
We store your consent document—with time stamp, IP-marked, and method-captured—for the life of our partnership plus six years after revocation, to satisfy PECR rules. Delivery logs for e-mails, push messages, and SMS are held for only thirteen months. Cancelling consent right away suppresses communications while preserving historical proof. A divided database ensures suppression without lag, and consent logs are held in a separate compliance archive. Dispatch records contain metadata only—heading, time stamp, status—not full message content. The six-year post-withdrawal window reflects the statute of limitations for regulatory investigations. Quarterly audits verify no expired consents activate mailings. We never tailor offers with gameplay or financial data beyond explicit authorisations.
Monetary Transaction and Billing Records
Deposit, withdrawal, and wager logs are maintained for seven years from the transaction date, per HMRC and FCA rules. We do not store full PANs or CVVs. We collect only the BIN, last four digits, and a tokenised alias. Chargeback disputes freeze the contested record until final outcome, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs verified by auditors. Tokenised card references remain valid only while your account is open and are wiped within thirty days of closure. Combined, anonymised totals endure for financial reporting without any personal identifiers. All financial data is coded and separated from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways produce vaulted tokens that link your card to a non-sensitive reference. We hold them for the account lifetime plus a thirty-day grace period, then transmit 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 sit on our systems. We monitor token revocation daily and initiate incidents if deletion is unsuccessful. Tokens are tied to our merchant code and cannot be used other places. Weekly reconciliation verifies correctness, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are recorded and verifiable. Aggregate reports never disclose individual transaction hashes.
Policy Review and Incident Reporting Protocols
We review 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 sent 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 revise controls as needed. Biannual tabletop exercises test misconfigurations and ransomware to test our response.
Policy Version Control and Revision History
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 transmitted 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 reflects our commitment to accountable data governance.