Playing Wanted Dead Or a Wild Slot game means providing personal data https://wanteddeadorwild.uk/. This document sets forth exactly how long we store it, why, and what technical protections sit behind 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 unique retention clock. Identity records are retained for five years after account closure. Financial logs remain for seven, meeting HMRC requirements. Gameplay data undergoes 24 months before anonymisation takes effect. Full card numbers never reach our systems—only tokenised aliases—and every byte is protected. Independent auditors verify our automated deletion routines, and any schedule slip activates a full incident response. A version-controlled policy log documents every edit, and we offer you 30 days’ notice before material changes take effect. Subject access and deletion requests are processed within statutory deadlines.
Gaming Session and Analytics of Behavior Data
Every spin on Wanted Dead Or a Wild tracks reel positions, RNG seed, and net outcome with microsecond precision. We store 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 receive 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 deleted
- RNG seed audit trails: 36 months to comply with technical standards
- Feature trigger heatmaps: 12 months, then integrated into global model
- Error and crash diagnostic logs: 90 days, then removed
Responsible Gambling and Self-Exclusion Registers
Betting limits, session reminders, and timeout settings are saved for your account’s entire duration and never purged while it remains active. If you self-exclude, your hashed identity and device fingerprints are added to a specialized exclusion register maintained indefinitely under UKGC licence requirements. The register is secured separately, accessed only at login or registration, and never employed for analytics. Access is restricted to qualified compliance staff, and all lookups are logged for three years. The register stores only identity blocks—no monetary or gameplay records. We review it annually to rectify errors and remove deceased individuals. Otherwise, it stays indefinite. This retention is required and free from deletion requests.
Session Awareness and Play Time Restriction Enforcement
Reality check counters use temporary session counters that restart every 24 hours, restarting from your first spin after midnight. Your selected interval—say, 30 minutes—is saved persistently and automatically reactivates when you visit again, even after a long break. Altering the interval mid-session sets the new value instantly for the next reminder. These settings are deleted 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 accuracy. All timer configurations are verifiable through the same three-year access log standard. We do not profile or market based on these settings.
Technical Infrastructure and Data Storage
All data sits in UK-based ISO 27001 Tier III+ data centres, never replicated outside the UK. A hot disaster recovery site in a separate UK zone syncs every six hours. Backups are encrypted client-side and follow identical retention rules. We apply least privilege with hardware MFA for administrators, recording their sessions in an immutable three-year audit trail. Multi-factor authentication uses a hardware token and biometric check. Penetration tests occur 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 maintain an air-gapped backup rotated weekly, subject to the same deletion policies.
Management of Encryption Keys
Master keys rotate 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 link 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 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.
User Account and Verification of Identity Data
Core identity profiles—official ID scans, address verification, biometric selfie verifications—are held for five years after your last activity or account termination, whichever is later. This covers statutory limitation periods and anti-money laundering duties. We extract only the essentials: document number, expiration date, country of citizenship. The high-resolution image gets deleted upon extraction. Once the five-year period pass, all source data is removed, but a encrypted hash of the verification result remains for an additional two years inside an audit log. Identification data sits encrypted in storage with AES-256-GCM, kept separate from analytics, and every retrieval is tracked for three years. Unnecessary fields like birth location are removed at verification time to minimize the data volume. Yearly audits verify precision and automatically remove expired data.
Document Upload and Biometric Processing
Submit an ID through our secure portal and automatic verification wraps up within 90 seconds. We retrieve the document number, validity, country of citizenship, and a reliability score, then delete the high-resolution image right away—it never reaches storage. The original file stays in an memory buffer and is removed after processing. A reduced, marked preview is generated for audit purposes and stored only for the ID lifecycle. That thumbnail lives in a write-once vault with rigorous controls and is never shown to customer support. Retrieved data are secured and stored for the 5-year-plus-2-year hash period. All processing runs on servers in the UK with ISO 27001, and every thumbnail access is recorded immutably.
Biometric Data Specifics
Liveness checks collect a brief video feed entirely in memory. Frames are processed and discarded within milliseconds. Only a mathematical vector of facial landmarks persists. This data set contains no image data and cannot be turned back into a facial image. It stays for the entire identity verification process and is irreversibly removed upon closure of account or after five years. The data set sits in a hardware security module with self-expiry and is never sent out. Login comparisons happen inside the HSM’s protected enclave without exposing the original vector. The vector is associated with a anonymous identifier separated from marketing profiles, which makes reidentification highly challenging. Even system administrators cannot view or recreate facial attributes from the saved data.
Financial Transaction and Payment Records
Deposit, withdrawal, and wager logs are kept for seven years from the transaction date, per HMRC and FCA rules. We never store full PANs or CVVs. We capture only the BIN, last four digits, and a tokenised reference. Chargeback disputes suspend the contested record until final resolution, after which the seven-year clock resumes. Data is partitioned quarterly so automated purging operates cleanly, with monthly deletion runs checked by auditors. Tokenised card references are valid only while your account is live and are deleted within thirty days of closing. Combined, anonymised totals endure for financial reporting without any personal identifiers. All financial data is encrypted and isolated from marketing systems.
Secured Payment Instruments and Processor References
Payment gateways produce vaulted tokens that link your card to a non-sensitive alias. We keep them for the account lifetime plus a thirty-day grace window, then issue deletion commands to the processor and clear our own reference. The only evidence left behind is an anonymised transaction hash used in aggregate reports, themselves deleted after seven years. No usable credentials ever reside on our systems. We monitor token revocation daily and raise incidents if deletion is unsuccessful. Tokens are linked to our merchant code and cannot be used elsewhere. Weekly reconciliation validates validity, and tokens tied to lost or stolen cards are revoked immediately. All token operations are logged and verifiable. Aggregate reports never expose individual transaction hashes.
Fundamental Definitions and Range of Personal Data
We adopt a comprehensive approach 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 covers 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 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 cover live databases, archives, and backups without exception. Each window starts ticking from the last activity or transaction date, spelled out below. We review definitions every six months to keep pace with regulatory guidance.
Marketing Approval and Correspondence Records
We maintain your consent document—timestamped, with IP address, and method-captured—for the entirety of our association plus six years after withdrawal, to meet PECR obligations. Delivery logs for e-mails, push alerts, and SMS are retained for only thirteen months. Cancelling consent instantly blocks communications while keeping historical proof. A divided database ensures suppression without delay, and consent logs are stored in a dedicated compliance archive. Send logs hold metadata only—subject, time stamp, status—not full message text. The six-year post-withdrawal timeframe reflects the statute of limitations for regulatory inquiries. Quarterly audits confirm no expired consents trigger mailings. We never customise offers with gameplay or financial data beyond explicit authorisations.
Access Request and Erasure Workflows
Upon receiving an SAR, we compile a formatted JSON/CSV export of all non-purged data within one month, prolongable 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 implement a cascade: immediate account suppression and token revocation, then batched erasure of all personal data not subject to legal hold. We create a confirmation report specifying 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 recorded immutably for five years.
Policy Assessment and Incident Reporting Protocols
We review 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 displayed 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 notify 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 hold 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 Update Log
We keep 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 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 verify 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.