Playing slot wanted dead or a wild player assistance means handing over personal data. This document sets forth exactly how long we keep it, why, and what technical protections support each category—all built around 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 retained 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 enter our systems—only tokenised aliases—and every byte is secured. Independent auditors review 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 take effect. Subject access and deletion requests are handled within statutory deadlines.
Essential Definitions and Scope of Personal Data
We cast a wide net on what qualifies 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 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 treat 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 reassess definitions every six months to remain compliant with regulatory guidance.
SAR and Deletion Processes
When an SAR lands, we compile 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, delivered via a one-time secure link that expires in 72 hours. For deletion, we implement a cascade: immediate account suppression and token revocation, then batched erasure of all personal data not subject to legal hold. We produce a confirmation report detailing 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 recorded immutably for five years.
Technical Infrastructure 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 follow identical retention rules. We enforce least privilege with hardware MFA for administrators, logging their sessions in an immutable three-year audit trail. Multi-factor authentication uses a hardware token and biometric check. Penetration tests are conducted quarterly, and an independent auditor validates 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.
Key Lifecycle Administration
Master keys change every 90 days automatically inside an HSM. New keys are kept internal 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 removed inside the HSM, making any backups unrecoverable. We assign 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 requires 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.
Safe Gambling and Voluntary Exclusion Registers
Stake limits, session reminders, and timeout settings are stored for your account’s whole period and never deleted while it stays active. If you choose to ban yourself, your hashed identity and device fingerprints are placed into a specific exclusion register held without time limit under UKGC licence requirements. The register is secured separately, accessed only at login or registration, and never used for analytics. Access is limited to qualified compliance staff, and all lookups are logged for three years. The register stores only identity blocks—no financial or gameplay records. We review it annually to correct errors and remove deceased individuals. Apart from that, it stays indefinite. This retention is mandatory and free from deletion requests.
Time Check and Gaming Duration Enforcement
Reality check clocks use transient session counters that restart every 24 hours, beginning again from your first spin after midnight. Your preferred interval—say, 30 minutes—is saved persistently and automatically reactivates when you return, even after a long break. Changing the interval mid-session sets the new value immediately for the next reminder. These settings are deleted only upon confirmed account deletion. Session timer data lies 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 never categorize or advertise based on these settings.
Gaming Session and Analytics of Behavior Data
All spins on Wanted Dead Or a Wild records reel positions, RNG seed, and net outcome with microsecond precision. We store 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—persist 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 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 meet technical standards
- Feature trigger heatmaps: 12 months, then combined into global model
- Error and crash diagnostic logs: 90 days, then rotated out
Payment Transaction and Billing Records
Deposit, withdrawal, and wager histories 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 reference. Chargeback disputes suspend the contested record until final settlement, 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 are valid only while your account is active and are wiped within thirty days of closing. Aggregated, anonymised totals remain for financial reporting without any personal details. All financial data is coded and quarantined from marketing systems.
Tokenized Payment Instruments and Processor References
Payment gateways generate vaulted tokens that associate your card to a non-sensitive alias. We hold them for the account lifetime plus a thirty-day grace period, then transmit deletion commands to the processor and wipe our own reference. The only remnant left behind is an anonymised transaction hash used in aggregate summaries, themselves removed after seven years. No usable credentials ever exist on our systems. We track token revocation daily and initiate incidents if deletion is unsuccessful. Tokens are bound to our merchant code and cannot be used in other contexts. Weekly reconciliation validates correctness, and tokens tied to lost or stolen cards are cancelled immediately. All token operations are recorded and auditable. Aggregate reports never reveal individual transaction hashes.
Account Registration and Identity Verification Data
Main identity data—government ID scans, address verification, biometric selfie matches—are kept for five years after your last activity or closure of account, whichever occurs later. This covers contractual limitation periods and AML obligations. We retrieve only the key information: ID number, expiration date, citizenship. The full-resolution image gets shredded immediately after extraction. Once 5 years pass, all raw data is removed, but a hash of the verification data persists for another two years inside an audit log. Identity data sits stored encrypted with AES-256-GCM, kept separate from analytics, and every retrieval is tracked for a three-year period. Non-essential fields like birthplace are removed at the time of verification to minimize the data volume. Yearly audits confirm precision and automatically remove expired data.
Uploading Documents and Biometric Processing
Submit an ID through our secure portal and automated checking finishes within a minute and a half. We pull the document number, expiration date, country of citizenship, and a reliability score, then destroy the high-resolution image instantly—it never touches disk. The original file stays in an in-memory buffer and disappears after handling. A reduced, marked preview is generated for audit purposes and kept only for the identity lifecycle. That small image lives in a immutable vault with strict controls and is never shown to support staff. Retrieved data are encrypted and saved for the five-year plus two-year hash timeframe. All operations runs on ISO 27001 certified UK servers, and every thumbnail access is stored unchangeably.
Biometric Information Details
Liveness checks record a quick video solely in memory. Video frames are analyzed and removed within a few milliseconds. Only a mathematical vector of facial landmarks persists. This vector lacks any image data and cannot be reconstructed into a picture. It remains for the duration of identity verification and is permanently deleted upon account closure or after a five-year period. The data set sits in a dedicated HSM with automatic expiration and is never transferred. Login comparisons happen inside the HSM’s safe environment without revealing the original vector. The data set is bound to a anonymous identifier separated from advertising profiles, which makes re-identifying extremely difficult. Even IT admins cannot view or reconstruct facial attributes from the saved data.
Marketing Approval and Correspondence Records
We maintain your consent document—timestamped, IP-marked, and method-captured—for the life of our partnership plus six years after withdrawal, to comply with PECR rules. Delivery logs for electronic messages, push alerts, and SMS are retained for only thirteen months. Cancelling consent right away suppresses communications while preserving historical proof. A segmented database guarantees suppression without latency, and consent logs are kept in a separate compliance archive. Send logs include metadata only—subject, time, condition—not full message body. The six-year post-withdrawal window reflects the statute of limitations for regulatory probes. Quarterly audits check no expired consents trigger mailings. We never tailor offers with gameplay or financial data beyond explicit authorisations.
Policy Assessment 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 published 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 inform affected individuals within 72 hours if high risk, file with the ICO, and post a transparency notice. Third-party processor breaches must follow the same protocol. We keep a breach notification log audited quarterly. Post-incident reviews update controls as needed. Biannual tabletop exercises simulate misconfigurations and ransomware to test our response.
Document Versioning and Revision History
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 confirm the log’s accuracy. The log is a living document reflecting our evolving data practices. You can view the full change log through a link in our privacy centre at any time. This transparent approach shows our commitment to accountable data governance.