Playing Slot Wanted Dead Or A Wild Free Bonuses means submitting personal data. This document details exactly how long we store it, the reasons, and what technical protections underpin each category—all based on 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 stick around 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 records every edit, and we offer you 30 days’ notice before material changes take effect. Subject access and deletion requests are managed within statutory deadlines.
Financial Transaction and Billing Records
Deposit, withdrawal, and wager records are kept for seven years from the transaction date, per HMRC and FCA rules. We do not store full PANs or CVVs. We record only the BIN, last four digits, and a tokenised alias. Chargeback disputes freeze the contested record until final settlement, after which the seven-year clock continues. Data is partitioned quarterly so automated purging works cleanly, with monthly deletion runs verified by auditors. Tokenised card references stay valid only while your account is open and are erased within thirty days of closing. Summarised, anonymised totals endure for financial reporting without any personal identifiers. All financial data is encrypted 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 keep them for the account lifetime plus a thirty-day grace window, then transmit deletion commands to the processor and erase our own reference. The only trace 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 fails. Tokens are bound to our merchant code and cannot be used in other contexts. Weekly reconciliation validates validity, 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.
Access Request and Erasure Workflows
When a subject access request arrives, 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, sent via a one-time secure link that expires in 72 hours. For deletion, we proceed sequentially: immediate account suppression and token revocation, then batched 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 maintained as auditable proof for as long as the longest surviving data category. All requests are documented immutably for five years.
Essential Definitions and Scope of Personal Data
We cast a wide net 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 includes 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 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 span live databases, archives, and backups without exception. Each window commences from the last activity or transaction date, spelled out below. We revisit definitions every six months to stay aligned with regulatory guidance.
Consent for Marketing and Communication Logs
We store your consent document—with time stamp, IP-stamped, and with capture method—for the life of our association plus six years after cancellation, to satisfy PECR rules. Send logs for e-mails, push notifications, and SMS are kept for only thirteen months. Revoking consent instantly suppresses communications while preserving historical proof. A segmented database ensures suppression without delay, and consent logs are kept in a separate compliance archive. Dispatch records hold metadata only—subject, timestamp, status—not full message text. The six-year post-withdrawal window matches the statute of limitations for regulatory probes. Quarterly audits confirm no expired consents activate mailings. We never tailor offers with gameplay or financial data beyond explicit permissions.
Controlled Gambling and Self-Exclusion Registers
Stake limits, session reminders, and timeout settings are stored for your account’s whole period and never purged while it remains active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a dedicated exclusion register kept permanently under UKGC licence requirements. The register is coded separately, checked only at login or registration, and never used for analytics. Entry is limited to qualified compliance staff, and all searches are recorded for three years. The register stores only identity blocks—no monetary or gameplay records. We check it annually to correct errors and remove deceased individuals. If not, it stays indefinite. This retention is obligatory and exempt from deletion requests.
Session Awareness and Session Limit Enforcement
Reality check timers use temporary session counters that clear every 24 hours, starting anew from your first spin after midnight. Your chosen interval—say, 30 minutes—is saved persistently and automatically 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 removed only upon verified 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 correctness. All timer configurations are checkable through the same three-year access log standard. We do not analyze or advertise based on these settings.
Session Gameplay and Behavioural Analytics Data
Every spin on Wanted Dead Or a Wild logs reel positions, RNG seed, and net outcome with microsecond precision. We retain 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 stay 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 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 anonymised aggregation
- Session behavioural profiles: 24 months from last session, then erased
- RNG seed audit trails: 36 months to satisfy technical standards
- Feature trigger heatmaps: 12 months, then combined into global model
- Error and crash diagnostic logs: 90 days, then cycled out
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 syncs 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 uses a hardware token and biometric check. Penetration tests run quarterly, and an independent auditor validates automated purge schedules. Any deviation triggers a Severity 1 incident, alerted to our DPO within four hours. We also operate an air-gapped backup rotated weekly, following the same deletion policies.
Key Lifecycle Administration
Master keys rotate every 90 days automatically inside an HSM. New keys are not extracted 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 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 demands 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 Evaluation and Data Breach 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 communicated 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, file with the ICO, and publish 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 model misconfigurations and ransomware to test our response.
Document Versioning and Revision History
We maintain 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 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.
User Account and Identity Verification Data
Primary identity records—official ID scans, address verification, biometric selfie verifications—are retained for five years after your last session or closure of account, whichever comes later. This encompasses statutory limitation periods and anti-money laundering responsibilities. We retrieve only the necessary details: document number, expiry, country of citizenship. The high-resolution image gets deleted upon extraction. Once five years pass, all source data is purged, but a cryptographic hash of the verification outcome remains for another two years inside an logging system. Identity data sits encrypted at rest with AES-256-GCM, kept separate from analytics, and every retrieval is recorded for 3 years. Unnecessary fields like birthplace are discarded at verification stage to shrink the data size. Annual reviews confirm accuracy and actively purge expired data.
File Upload and Biometric Processing
Upload an ID through our safe portal and automated checking wraps up within 90 seconds. We extract the document ID, validity, nationality, and a confidence score, then delete the full-resolution image immediately—it is never stored on disk. The source file stays in an memory buffer and vanishes after analysis. A compacted, stamped preview is produced for audit purposes and retained only for the identity verification period. That preview lives in a write-once storage with tight controls and is never shared to client support. Retrieved data are secured and kept for the five-year plus two-year hash timeframe. All operations runs on UK-based ISO 27001 servers, and every small image access is logged permanently.
Biometric Data Specifics
Liveness verifications record a quick video solely in memory. Frames are analyzed and removed within milliseconds of time. Only a data vector of facial points remains. This numerical representation has no image data and cannot be reverse-engineered into a facial image. It is kept for the entire identity verification process and is permanently deleted upon account termination or after a five-year period. The data set sits in a specialized HSM with auto-expiry and is never sent out. Authentication checks happen inside the HSM’s secure enclave without exposing the raw vector. The vector is associated with a pseudonymous identifier disconnected from marketing profiles, which makes re-identifying highly challenging. Even system admins cannot see or reconstruct facial features from the saved data.