Playing Wanted Dead Or A Wild Free Bonuses Slot means providing personal data. This document details exactly how long we retain it, the rationale, and what technical protections sit behind each category—all built around UK GDPR, the Data Protection Act 2018, and PCI DSS. We process identity documents, financial transactions, gameplay telemetry, responsible gambling markers, and marketing consents, each with its unique retention clock. Identity records are kept for five years after account closure. Financial logs stay for seven, satisfying HMRC requirements. Gameplay data undergoes 24 months before anonymisation takes effect. Full card numbers never touch our systems—only tokenised aliases—and every byte is encrypted. Independent auditors verify our automated deletion routines, and any schedule slip initiates a full incident response. A version-controlled policy log documents every edit, and we give you 30 days’ notice before material changes take effect. Subject access and deletion requests are handled within statutory deadlines.
Fundamental Definitions and Extent of Personal Data
We cast a wide net on what counts as personal data. Direct identifiers—name, email, billing address, masked payment details—are accompanied by 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 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 keep pace with regulatory guidance.
Account Registration and Identity Verification Data
Main identity data—scans of government IDs, proof of address, biometric selfie verifications—are held for 5 years after your last activity or closure of account, whichever occurs later. This encompasses contractual time limits and AML obligations. We retrieve only the key information: document ID, expiration date, country of citizenship. The high-resolution image gets destroyed upon extraction. Once 5 years pass, all original data is erased, but a encrypted hash of the verification result persists for an additional two years inside an audit trail. Identity data sits stored encrypted with AES-256-GCM, isolated from analytics, and every data access is tracked for a three-year period. Optional fields like place of birth are deleted at verification time to minimize the data footprint. Annual reviews confirm correctness and automatically remove expired data.
Document Upload and Biometric Data Processing
Provide an ID through our protected portal and automatic verification completes within ninety seconds. We pull the ID number, validity, nationality, and a confidence score, then delete the full-resolution image instantly—it is never stored on disk. The source file stays in an in-memory buffer and is removed after analysis. A compressed, watermarked small image is created for compliance purposes and kept only for the identity lifecycle. That preview lives in a write-once vault with tight controls and is never shown to customer support. Extracted fields are secured and saved for the five-year-plus-two hash window. All operations runs on UK-based ISO 27001 servers, and every preview retrieval is logged permanently.
Specifics of Biometric Data
Live detection checks collect a short video stream solely in memory. Video frames are analyzed and removed within milliseconds of time. Only a mathematical vector of facial landmarks remains. This vector contains no image data and cannot be turned back into a face. It remains for the entire identity verification process and is irreversibly removed upon account closure or after five years. The vector sits in a hardware security module with automatic expiration and is never transferred. Login verifications happen inside the HSM’s safe environment without exposing the unprocessed data. The numerical representation is bound to a pseudonym disconnected from marketing data, which makes re-identifying extremely difficult. Even system administrators cannot view or reconstruct face characteristics from the saved data.
Marketing Consent and Correspondence Records
We maintain your consent log—with time stamp, IP-stamped, and method-recorded—for the entirety of our partnership plus six years after cancellation, to comply with PECR obligations. Send logs for electronic messages, push notifications, and SMS are retained for only thirteen months. Revoking consent immediately halts communications while keeping historical proof. A partitioned database ensures suppression without latency, and consent logs are kept in a separate compliance archive. Delivery logs contain metadata only—topic, time, status—not full message text. The six-year post-withdrawal window reflects the statute of limitations for regulatory inquiries. Quarterly audits verify no expired consents activate mailings. We never tailor offers with gameplay or financial data beyond explicit authorisations.
Gaming Session and Behavioural Analytics Data
All spins on Wanted Dead Or a Wild records reel positions, RNG seed, and net outcome with microsecond precision. We keep these raw logs for twenty-four months, then compress them into an anonymous statistical digest utilized 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 get 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 deleted
- RNG seed audit trails: 36 months to comply with technical standards
- Feature trigger heatmaps: 12 months, then merged into global model
- Error and crash diagnostic logs: 90 days, then cycled out
Monetary Transaction and Payment Records
Deposit, withdrawal, and wager histories are kept for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We collect only the BIN, last four digits, and a tokenised reference. Chargeback disputes halt the contested record until final resolution, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging runs cleanly, with monthly deletion runs verified by auditors. Tokenised card references remain valid only while your account is live and are wiped within thirty days of closing. Combined, anonymised totals endure for financial reporting without any personal information. All financial data is encrypted and isolated from marketing systems.
Tokenised Payment Instruments and Processor References
Payment gateways generate vaulted tokens that map your card to a non-sensitive identifier. We keep them for the account lifetime plus a thirty-day grace interval, then issue deletion commands to the processor and erase our own mapping. The only trace left behind is an anonymised transaction hash used in aggregate summaries, themselves purged after seven years. No usable credentials ever reside on our systems. We monitor token revocation daily and trigger incidents if deletion does not work. Tokens are tied to our merchant code and cannot be used other places. Weekly reconciliation validates validity, and tokens tied to lost or stolen cards are invalidated immediately. All token operations are documented and verifiable. Aggregate reports never expose individual transaction hashes.
Infrastructure Setup and Data Location
All data resides 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 adhere to 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 confirms automated purge schedules. Any deviation generates a Severity 1 incident, reported to our DPO within four hours. We also maintain an air-gapped backup rotated weekly, under the same deletion policies.
Management of Encryption Keys
Master keys rotate 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 destroyed inside the HSM, making any backups unrecoverable. We assign 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.
Safe Gambling and Player Ban Registers
Stake limits, reality checks, and timeout settings are kept for your account’s entire duration and never removed while it is active. If you opt for self-exclusion, your hashed identity and device fingerprints are added to a specialized exclusion register held permanently under UKGC licence requirements. The register is coded separately, checked only at login or registration, and never employed for analytics. Entry is restricted to qualified compliance staff, and all queries are tracked for three years. The register holds only identity blocks—no monetary or gameplay records. We review it annually to correct errors and remove deceased individuals. If not, it remains indefinite. This retention is required and excluded from deletion requests.
Time Check and Gaming Duration Enforcement
Reality check counters use temporary session counters that clear 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 come back, even after a long break. Changing the interval mid-session introduces the new value right away for the next reminder. These settings are purged only upon validated account deletion. Session timer data resides in a dedicated, 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 analyze or promote based on these settings.
Data Subject Access Request and Deletion Workflows
Upon receiving an SAR, we compile a organized JSON/CSV export of all non-purged data within one month, prolongable 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 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 retained as auditable proof for as long as the longest surviving data category. All requests are documented immutably for five years.
Policy Evaluation and Breach Notification Protocols
We evaluate this policy every six months or upon material change to the game or regulation. Reviews are documented with DPO, CISO, and legal counsel. A public summary is published 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 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 preserve 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 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 verify 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.