Playing Wanted Dead Or a Wild Slot means providing personal data. This document details exactly how long we store it, the reasons, and what technical protections support each category—all aligned with 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 specific retention clock. Identity records are retained for five years after account closure. Financial logs stay for seven, matching HMRC requirements. Gameplay data receives 24 months before anonymisation kicks in. Full card numbers never touch our systems—only tokenised aliases—and every byte is secured. Independent auditors review our automated deletion routines, and any schedule slip triggers 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.
Essential Definitions and Scope of Personal Data
We take a broad view on what counts as 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 encompasses session length, bet sizing, spin velocity, and how often feature triggers fire. Even pseudonymised logs can re-identify 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 starts ticking from the last activity or transaction date, spelled out below. We revisit definitions every six months to keep pace with regulatory guidance.
Registration Account and ID Verification Data
Main identity data—scans of government IDs, address verification, selfie biometric matches—are retained for five years after your final session or account termination, whichever occurs later. This includes statutory limitation periods and anti-money laundering duties. We obtain only the essentials: ID number, expiration date, citizenship. The original image gets destroyed right after extraction. Once 5 years pass, all original data is erased, but a cryptographic hash of the verification data remains for two more years inside an audit log. Identity data sits stored encrypted with AES-256-GCM, stored away from analytics, and every data access is logged for a three-year period. Unnecessary fields like birth location are discarded at the time of verification to minimize the data size. Annual reviews confirm precision and automatically remove outdated records.
Uploading Documents and Biometric Processing
Upload an ID through our secure portal and automated checking completes within a minute and a half. We retrieve the document number, expiry, country of citizenship, and a confidence score, then delete the original image instantly—it never touches disk. The source file stays in an temporary memory and vanishes after analysis. A reduced, watermarked small image is produced for auditing purposes and retained only for the identity lifecycle. That thumbnail lives in a write-once vault with tight controls and is never shown to support staff. Collected information are encrypted and stored for the five-year plus two-year hash timeframe. All processing runs on servers in the UK with ISO 27001, and every preview retrieval is recorded immutably.
Specifics of Biometric Data
Liveness checks capture a short video stream entirely in memory. Images are analysed and discarded within milliseconds. Only a numerical vector of facial points persists. This vector lacks any image data and cannot be turned back into a facial image. It remains for the duration of identity verification and is purged irrevocably upon account termination or after a five-year period. The vector sits in a hardware security module with self-expiry and is never sent out. Login verifications happen inside the HSM’s secure enclave without exposing the original vector. The data set is associated with a pseudonym separated from advertising profiles, which makes reidentification highly challenging. Even system admins are unable to view or rebuild face characteristics from the stored vector.
Gaming Session and Behavioral Analytics 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 employed 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 have 36 months. Error diagnostics receive 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
Payment Transaction and Billing Records
Funding, withdrawal, and wager histories are kept 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 identifier. Chargeback disputes freeze the contested record until final outcome, after which the seven-year clock continues. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs audited by auditors. Tokenised card references stay valid only while your account is active and are deleted within thirty days of closing. Summarised, anonymised totals persist for financial reporting without any personal identifiers. All financial data is encrypted and separated from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways create vaulted tokens that map your card to a non-sensitive reference. We hold them for the account lifetime plus a thirty-day grace window, then issue deletion commands to the processor and wipe our own mapping. The only trace left behind is an anonymised transaction hash used in aggregate statements, themselves purged after seven years. No usable credentials ever sit 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 validates correctness, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are recorded and verifiable. Aggregate reports never reveal individual transaction hashes.
Marketing Consent and Communication Logs
We store your consent log—timestamped, with IP address, and with capture method—for the duration of our association plus six years after revocation, to meet PECR rules https://wanteddeadorwild.uk/. Delivery logs for electronic messages, push messages, and SMS are retained for only thirteen months. Withdrawing consent instantly halts communications while keeping historical proof. A partitioned database provides suppression without latency, and consent logs are held in a separate compliance archive. Dispatch records contain metadata only—subject, timestamp, status—not full message text. The six-year post-withdrawal window matches the statute of limitations for regulatory investigations. Quarterly audits verify no expired consents trigger mailings. We never customise offers with gameplay or financial data beyond explicit consents.
SAR and Deletion Processes
Upon receiving an SAR, we produce a formatted JSON/CSV export of all non-purged data within one month, expandable by two months for complex cases. The export covers 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 queued erasure of all personal data not subject to legal hold. We generate a confirmation report detailing 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.
Safe Gambling and Self-Exclusion Registers
Deposit limits, time checks, and timeout settings are kept for your account’s whole period and never purged while it remains active. If you choose to ban yourself, your hashed identity and device fingerprints enter a specific exclusion register held permanently under UKGC licence requirements. The register is secured separately, checked only at login or registration, and never utilized for analytics. Entry is restricted to trained compliance staff, and all queries 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. Otherwise, it stays permanent. This retention is required and exempt from deletion requests.
Time Check and Gaming Duration Enforcement
Reality check clocks use short-lived session counters that clear every 24 hours, beginning again from your first spin after midnight. Your chosen interval—say, 30 minutes—is kept persistently and routinely reactivates when you visit again, even after a long break. Modifying the interval mid-session sets the new value right away for the next reminder. These settings are purged only upon validated account deletion. Session timer data sits in a dedicated, encrypted store separate from gameplay analytics. The 24-hour counter is based on play start, not midnight, for accuracy. All timer configurations are auditable through the same three-year access log standard. We at no time analyze or advertise based on these settings.
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 updates every six hours. Backups are encrypted client-side and maintain identical retention rules. We implement 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 run quarterly, and an independent auditor confirms automated purge schedules. Any deviation triggers a Severity 1 incident, notified to our DPO within four hours. We also keep an air-gapped backup rotated weekly, under the same deletion policies.
Management of Encryption Keys
Master keys change every 90 days automatically inside an HSM. New keys are not extracted 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 needs 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.
Policy Review and Incident Reporting Protocols
We assess this policy every six months or upon material change to the game or regulation. Reviews are recorded with DPO, CISO, and legal counsel. A public summary is published 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 inform 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 maintain 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 maintain a version-controlled history of this policy with semantic versioning and plain-English summaries of each change. The log details 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 retrieve the full change log through a link in our privacy centre at any time. This transparent approach demonstrates our commitment to accountable data governance.