Playing Wanted Dead Or a Wild Slot game means providing personal data. This document sets forth exactly how long we keep it, why, and what technical protections sit behind 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 own retention clock. Identity records are kept for five years after account closure. Financial logs stay for seven, meeting HMRC requirements. Gameplay data receives 24 months before anonymisation kicks in. Full card numbers never reach our systems—only tokenised aliases—and every byte is encrypted. Independent auditors check our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log records every edit, and we offer you 30 days’ notice before material changes are implemented. Subject access and deletion requests are managed within statutory deadlines.
Fundamental 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—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 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 span live databases, archives, and backups without exception. Each window starts ticking from the last activity or transaction date, spelled out below. We reassess definitions every six months to stay aligned with regulatory guidance.
Technology Framework and Data Storage
All data sits in UK-based ISO 27001 Tier III+ data centres, with no replication outside the UK. A hot disaster recovery site in a separate UK zone synchronizes every six hours. Backups are encrypted client-side and adhere to 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 integrates a hardware token and biometric check. Penetration tests occur quarterly, and an independent auditor validates automated purge schedules. Any deviation raises a Severity 1 incident, alerted to our DPO within four hours. We also operate an air-gapped backup rotated weekly, subject to the same deletion policies.
Encryption Key Lifecycle Management
Master keys are renewed every 90 days automatically inside an HSM https://wanteddeadorwild.uk/. New keys are not extracted in plaintext. Rotated keys are retained 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 bind 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 requires 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 leaves the HSM boundary.
Financial Transaction and Billing Records
Funding, withdrawal, and wager logs 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 alias. Chargeback disputes suspend 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 remain valid only while your account is open and are wiped within thirty days of termination. Summarised, anonymised totals persist for financial reporting without any personal identifiers. All financial data is coded and quarantined from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways generate vaulted tokens that map your card to a non-sensitive reference. We store them for the account lifetime plus a thirty-day grace period, then transmit deletion commands to the processor and clear our own link. The only evidence left behind is an anonymised transaction hash used in aggregate statements, 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 other places. Weekly reconciliation confirms correctness, and tokens tied to lost or stolen cards are revoked immediately. All token operations are documented and checked. Aggregate reports never disclose individual transaction hashes.
Safe Gambling and Voluntary Exclusion Registers
Deposit limits, session reminders, and timeout settings are saved for your account’s entire duration and never deleted while it stays active. If you self-exclude, your hashed identity and device fingerprints are added to a dedicated exclusion register held indefinitely under UKGC licence requirements. The register is encrypted separately, checked only at login or registration, and never utilized for analytics. Access is limited to trained compliance staff, and all queries are recorded 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. Apart from that, it is kept indefinite. This retention is mandatory and excluded from deletion requests.
Session Awareness and Play Time Restriction Enforcement
Reality check timers use short-lived session counters that restart every 24 hours, restarting from your first spin after midnight. Your chosen interval—say, 30 minutes—is saved persistently and routinely reactivates when you visit again, even after a long break. Modifying the interval mid-session introduces the new value immediately for the next reminder. These settings are purged only upon verified account deletion. Session timer data sits 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 at no time profile or market based on these settings.
Access Request and Erasure Workflows
Upon receiving an SAR, we generate a formatted JSON/CSV export of all non-purged data within one month, extendable 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 queued erasure of all personal data not subject to legal hold. We create 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 documented immutably for five years.
Gameplay Session and Analytics of Behavior Data
Each spin on Wanted Dead Or a Wild tracks reel positions, RNG seed, and net outcome with microsecond precision. We retain these raw logs for twenty-four months, then compact 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 remain for 12 months before merging into a global model. RNG seed audit trails receive 36 months. Error diagnostics receive 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 aggregated aggregation
- Session behavioural profiles: 24 months from last session, then deleted
- RNG seed audit trails: 36 months to satisfy technical standards
- Feature trigger heatmaps: 12 months, then integrated into global model
- Error and crash diagnostic logs: 90 days, then removed
Registration Account and Identity Verification Data
Core identity profiles—official ID scans, residence proof, biometric selfie matches—are retained for five years after your last session or account closure, whichever is later. This encompasses statutory limitation periods and anti-money laundering responsibilities. We retrieve only the key information: document number, validity, country of citizenship. The full-resolution image gets destroyed right after extraction. Once 5 years pass, all original data is purged, but a encrypted hash of the verification outcome remains for two more years inside an audit trail. Identity data sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every retrieval is tracked for a three-year period. Non-essential fields like birthplace are discarded at verification stage to shrink the data size. Yearly reviews ensure accuracy and proactively delete expired data.
File Upload and Biometric Processing
Provide an ID through our safe portal and automated checking completes within a minute and a half. We retrieve the document ID, validity, citizenship, and a trust score, then destroy the full-resolution image right away—it is never stored on disk. The initial file stays in an memory buffer and is removed after analysis. A compacted, stamped small image is generated for audit purposes and kept only for the identity lifecycle. That small image lives in a write-once storage with tight controls and is never shared to customer support. Collected information are encoded and saved for the five-year plus two-year hash timeframe. All operations runs on servers in the UK with ISO 27001, and every thumbnail access is logged permanently.
Specifics of Biometric Data
Live detection checks collect a brief video feed completely in memory. Video frames are analyzed and deleted within milliseconds. Only a numerical vector of facial landmarks persists. This numerical representation lacks any image data and cannot be reconstructed into a picture. It stays for the entire identity verification process and is purged irrevocably upon account closure or after five years. The data set sits in a specialized HSM with self-expiry and is never transferred. Authentication checks happen inside the HSM’s secure enclave without disclosing the raw vector. The vector is associated with a pseudonym disconnected from advertising profiles, which makes re-identification very hard. Even system administrators are unable to view or rebuild facial attributes from the saved data.
Marketing Approval and Communication Logs
We store your consent document—with time stamp, IP-stamped, and method-captured—for the duration of our association plus six years after cancellation, to satisfy PECR requirements. Dispatch records for electronic messages, push messages, and SMS are held for only thirteen months. Withdrawing consent right away halts communications while keeping historical proof. A partitioned database guarantees suppression without lag, and consent logs are held in a separate compliance archive. Send logs include metadata only—topic, time, condition—not full message content. The six-year post-withdrawal timeframe reflects the statute of limitations for regulatory inquiries. Quarterly audits verify no expired consents trigger mailings. We never tailor offers with gameplay or financial data beyond explicit consents.
Policy Evaluation and Incident Reporting Protocols
We review 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 posted 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, 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 update controls as needed. Biannual tabletop exercises model misconfigurations and ransomware to test our response.
Document Versioning and Update 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 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 check 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.